fix: update more /docs/references links

Signed-off-by: aramissennyeydd <aramis.sennyey@doordash.com>

docs/features/kubernetes/configuration.md

@@ -195,11 +195,11 @@ strategy.
 
 This method can be quite helpful when used in combination with an ingestion
 procedure like the
-[`GkeEntityProvider`](https://backstage.io/docs/reference/plugin-catalog-backend-module-gcp.gkeentityprovider/)
+[`GkeEntityProvider`](https://backstage.io/api/stable/classes/_backstage_plugin-catalog-backend-module-gcp.index.GkeEntityProvider.html)
 (installation documented
 [here](https://github.com/backstage/backstage/tree/master/plugins/catalog-backend-module-gcp#installation))
 or the
-[`AwsEKSClusterProcessor`](https://backstage.io/docs/reference/plugin-catalog-backend-module-aws.awseksclusterprocessor/)
+[`AwsEKSClusterProcessor`](https://backstage.io/api/stable/classes/_backstage_plugin-catalog-backend-module-aws.index.AwsEKSClusterProcessor.html)
 to automatically update the set of clusters tracked by Backstage.
 
 For this method to work any entity that would be using this `Resource` to help drive the Kubernetes details in the Catalog's Entity pages needs to have a `dependsOn` relationship setup. Here's a quick example:

docs/features/kubernetes/installation.md

@@ -75,7 +75,7 @@ Backstage app.
 If either existing
 [cluster locators](https://backstage.io/docs/features/kubernetes/configuration#clusterlocatormethods)
 don't work for your use-case, it is possible to implement a custom
-[KubernetesClustersSupplier](https://backstage.io/docs/reference/plugin-kubernetes-backend.kubernetesclusterssupplier).
+[KubernetesClustersSupplier](https://backstage.io/api/stable/interfaces/_backstage_plugin-kubernetes-node.KubernetesClustersSupplier.html).
 
 Here's a very simplified example: