Describe the bug
When the application starts, it reads the configuration from the specified file path and creates a MapPropertySource.

But in the logic of listening, KubernetesClientConfigMapPropertySource. class is compared to it.



View the real situation of Environment. getPropertySources() in the JVM.

So the mismatch between these two will result in the application not being hot loaded when the file content changes.
Describe the bug
When the application starts, it reads the configuration from the specified file path and creates a MapPropertySource.

But in the logic of listening, KubernetesClientConfigMapPropertySource. class is compared to it.


View the real situation of Environment. getPropertySources() in the JVM.

So the mismatch between these two will result in the application not being hot loaded when the file content changes.