Ryan Baxter

Since the discovery server is supplying the service data you need to set `all-namespaces` to `true` on the discovery server not on the discovery client. The easiest way would be...

You will need to remove this https://github.com/vksaamy/Petclinc_spring_cloud_discovery_server/blob/main/PetClinic01/visits-svc1/pom.xml#L127-L136

It looks like the InformerDiscoveryClient is still on the classpath, some dependency is pulling that in. Maybe do a maven tree command and look at which spring-cloud-kubernetes dependencies are on...

Try setting `kubernetes.informer.enabled=false`

What permissions does the app have? I am not sure why it's happening. If you can provide a much simpler sample to reproduce I am happy to look at it...

There is not much more I can suggest until I have a simple reproducible sample to work with

Once again there is no environment variable setting the `all-namespace` property to true in the deployment of the discovery server https://github.com/vksaamy/Petclinc_spring_cloud_discovery_server/blob/eed4c58e775dce2f388d311249a80b54e4786c89/PetClinic03/K3S/discoveryserver_deployment.yml#L67-L83

@damon008 please try using Spring Cloud 2023.0.1 and let us know if this is still an issue @wind57 Can you describe what you mean by it doesn't work when you...

I think we could probably use some additional documentation in Spring Cloud Gateway [here](https://github.com/spring-cloud/spring-cloud-gateway/blob/main/docs/modules/ROOT/pages/spring-cloud-gateway/the-discoveryclient-route-definition-locator.adoc). Actually you don't need to include spring-cloud-kubernetes-client-loadbalancer, you just need to include spring-cloud-starter-loadbalancer. The reason it...

Closing in favor of https://github.com/spring-cloud/spring-cloud-kubernetes/issues/1042