Ability to refresh configuration of Spring Cloud app when multiple configmaps get changed

[iulianm82]

Hi,

Does Spring Cloud Kubernetes Configuration Watcher support having an application running onto a kubernetes pod be notified after multiple configmaps were changed?
As my configmaps have different names, is there a way to have them linked to my app? Basically, I would need to work around the rule of configmaps and my application having the same name (which is obviously not possible, as one application can have only one name, right?).

The current approach of achieving what I described above it by using a list of sources, as decribed at this link, but this support will be deprecated in future versions and, I guess, eventually removed.

If there currently linking multiple configmaps to the same application is not supported, is there any plan to add it in the future?

Thanks,
Iulian

[ryanjbaxter]

Good feature request....no it is not possible at the moment, but we could do something similar to what we do with non-default actuator paths and ports. Maybe add an annotation to the configmap/secret that specifies the application name?

For example, boot.spring.io/application-name.

[iulianm82]

Thanks.
Could you please keep the current support of using list of sources at least until you add the support we discussed above in Configuration Watcher? We are currently using list of sources to link multiple configmaps to our application. It's OK if you deprecate it in a future version, like I read on another thread.
Based on your answer, we'll know whether we need or not do something within our software. Thanks!

[ryanjbaxter]

It won't be removed until our next major release, and yes we will add support for this before that happens.

[bilak]

@ryanjbaxter hello is there any plan to develop this feature request? We are planning to integrate configuration watcher in our cluster and we also need to watch multiple configmaps/secrets. Thanks

[ryanjbaxter]

Yes it is something I want to work on. If you have any interest in helping out we always welcome contributions from the community!

[bilak]

@ryanjbaxter I can help with that I think we can benefit from that also, but we should agree whether what I mean is sufficient.

Currently application vs configmap is resolved only by configmap name http watcher example here.

rotected Flux<ResponseEntity<Void>> refresh(ObjectMeta objectMeta) {

		return kubernetesReactiveDiscoveryClient.getInstances(objectMeta.getName()).flatMap(si -> {

We can extend that and add some labels or annotations. The problem is that labels and annotations ar simple key value (string:string). So we have two options:

• prefix for example spring-app-{appname}: true. In this case we will be able to simply enable/disable some of applications to be notified about changes without actually removing the appname from configmap.
• property with values separated by comma something like spring-additional-apps: app1,app2,...

In both cases prefix or property name should be configurable like spring.cloud.kubernetes.configuration.watcher.configLabel or spring.cloud.kubernetes.configuration.watcher.secretLabel

I prefer the later (property separated by coma) because at least it looks like some list.

Last thing which I don't know is do we need to somehow modify also ConfigMapWatcherChangeDetector#isSpringCloudKubernetesConfig?

[ryanjbaxter]

I think option 2 is the best approach.

Last thing which I don't know is do we need to somehow modify also ConfigMapWatcherChangeDetector#isSpringCloudKubernetesConfig?

No I don't think so. That still needs to be in place.

[natesh1221]

Hi @iulianm82
The current approach of achieving what I described above it by using a list of sources, as decribed at this link, but this support will be deprecated in future versions and, I guess, eventually removed.
I was trying out the approach in the above mentioned link with multiple config-maps, but seems like it refreshes only the properties from configmap named with application-name. Any luck here to make it work?
Also @ryanjbaxter In spring-cloud-kubernetes-config-watcher, is there a way to provide different reload strategies which we have in propertysource-reload.

Thanks.

[ryanjbaxter]

@madboynatesh yes, you would have to set the property as an environment variable in the deployment of the config-watcher

[Nirvandil]

Hello. I need this feature too.
I'm trying to get services load ConfigMaps with name as spring convention for profiles-specific properties, e.g. application "myApp" should load CMs "myApp", and when it runs with active profile "debug" also should load properties form CM "myApp-debug". I can achieve loading properties, but can't get properties refreshed with Spring Cloud Kubernetes Configuration Watcher, because it will send "/refresh" requests only when CM "myApp" changes and will completely ignore "myApp-debug" changes.