kubernetes.client.namespace not honored when using ConfigMap PropertySource and DefaultKubernetesClient

Given a Service A1 in namespace A and a POD B1 running in namespace B with the following ConfigMap for Pod B1:

apiVersion: v1
kind: ConfigMap
metadata:
  name: B1
data:
  application.yml: |-
    server:
      port: 8092
    spring:
      profiles: kubernetes
      cloud:
        kubernetes:
          client:
            namespace: A
          discovery:
            enabled: true
    A1:
      ribbon:
        NIWSServerListClassName: org.springframework.cloud.kubernetes.ribbon.KubernetesServerList
        KubernetesNamespace: A
        PortName: https

The DefaultKubernetesClient uses the namespace where POD B1’s ConfigMap is applied instead of the value from kubernetes.client.namespace when asked to get all services from KubernetesDiscoveryClient#getInstances. The problem is that ConfigMapConfigProperties#determineSources set’s the namespace for the client to the namespace the ConfigMap is deployed to.

Using the same configuration above with spring-cloud-configuration where the application.yml is served from a GIT repo work perfectly fine.

[HJK181]

I’m not willing to invest more time in this issue. I already invested a lot of time and effort to debug the issue and give you a description with the class and method name where things go wrong.

If you are not interested in fixing it, feel free to close the issue.

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.