spring-cloud-kubernetes | Kubernetes integration with Spring Cloud Discovery Client | Microservice library

Based on Eugene's reply:

No, this is impossible at the moment to do so. You can go to GitHub and create an issue with the explanation of your use case, and this feature can be created within the future releases.

On further analysis and going through the docs, disabling of these features must be set in bootstrap.yml - https://docs.spring.io/spring-cloud-kubernetes/docs/current/reference/html/index.html#kubernetes-ecosystem-awareness.

Of course env variable will have precedence

You need to grant neccessary permissions to your spring app, with dependency spring-cloud-starter-kubernetes-fabric8-all that you're using, you will need to grant these permissions: "configmaps", "pods", "services", "endpoints", "secrets".

Below is an example from Spring Cloud document :

You can mount all env variables from secret in the following way:

The el filter must return a boolean value. The discovered service, which should be filtered, is injected as #root in the expression. So #root.metadata.name retrieves the actual name of the kubernetes service.

This part of code of KubernetesDiscoveryClient does the filtering:

Seems you're likely using an account that isn't authorised from what I can find online. There's little in the way of a single solution I can identify one, but there is one potentially helpful resource:

https://stackoverflow.com/a/58701728/7619034

There were others but SO doesn't like links (to external sites). I can suggest if this does not help at all

According to the latest documentation, you should set

We are working on providing SC LoadBalancer support now: https://github.com/spring-cloud/spring-cloud-kubernetes/issues/516.

I did a some googling and little research. I foud following:

1. The missing class com.azure.data.cosmos.internal.directconnectivity.rntbd.RntbdConstants$RntbdContextRequestHeader is a part of azure-cosmosdb-direct, pls see pom.xml, class is located here.
2. azure-cosmosdb-direct is missing from your dependency list. I assume it's incomplete or hidden for some reason(?)
3. Looking at exception stacktrace it's clear that at com.azure.data.cosmos.internal.directconnectivity.rntbd.RntbdContextRequest$Headers.(RntbdContextRequest.java:126) is a place where exceptiom occurs. So that means RntbdContextRequest class actually existsts (it's also is a part of azure-cosmosdb-direct). Therefore you have needed dependency, but it probably has wrong version.

I propose you to look a bit deeper into how azure-cosmosdb-direct dependency is injected in your project and fix its version. Just try to declare it directly in your pom.xml with the latest version.

Hope I helped you.