Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

k8s - configmap adds watch for all available configmap in the namespace.

See original GitHub issue

Describe the bug Version 2.0.1 apps needs only configmap injection so included only implementation group: 'org.springframework.cloud', name: 'spring-cloud-starter-kubernetes-client-config' and bootstarp.yml config as follows

spring:
  application:
    name: my-test-app
  cloud:
    loadbalancer:
      cache:
        enabled: false
    kubernetes:
      enabled: ${KUBERNETES_CONFIG_ENABLED:false}
      reload:
        enabled: ${KUBERNETES_CONFIG_ENABLED:false}
      config:
        enabled: ${KUBERNETES_CONFIG_ENABLED:false}
        name: ${SPRING_APPLICATION_NAME:unknown}
        namespace: default
      discovery:
        enabled: false
      loadbalancer:
        enabled: false

when we start the application we can see logs saying its adding watch for all the configmap that are available in the namespace. we have 1000’s of configmap so worried about any performance issue it may cause.

example

CongifMap app1 was added.
Configuration change was not detected.
CongifMap app2 was added.
Configuration change was not detected.
CongifMap app3 was added.
Configuration change was not detected.
CongifMap app4 was added.
Configuration change was not detected.
CongifMap app5 was added.
Configuration change was not detected.
...

Why not only add watch for configmap that default/mentioned or filter before adding the watch?