Allow using Watcher when ConfigMaps and Secrets are maintained by external team

Is your feature request related to a problem? Please describe.

I want to use Spring Cloud Kubernetes Configuration Watcher to monitor and call /refresh for shared ConfigMaps and Secrets maintained by centralised platform team in my project.

The problem is that I do not have permissions to add necessary labels:

• spring.cloud.kubernetes.secret / spring.cloud.kubernetes.secret.informer.enabled
• spring.cloud.kubernetes.config / spring.cloud.kubernetes.config.informer.enabled

and annotations

• spring.cloud.kubernetes.secret.apps / spring.cloud.kubernetes.configmap.apps

in order for Watcher to fire the /refresh calls to the apps.

Note! I do have permissions for getting, listing and watching these ConfigMaps and Secrets, but not editing them.

Documentation I have used so far:

• https://docs.spring.io/spring-cloud-kubernetes/docs/current/reference/html/#spring-cloud-kubernetes-configuration-watcher
• https://docs.spring.io/spring-cloud-kubernetes/docs/current/reference/html/#monitoring-configmaps-and-secrets

Describe the solution you'd like
What would really help is that it was possible (as an alternative solution) to explicitly configure the name of ConfigMaps and Secrets in the Watcher deployment, as environment variables, in addition to which apps to refresh. Or, if you have any suggestion on an alternative solution, not requiring changes to the ConfigMap and Secret resources.

Start with the configuration watcher documentation sections linked in the issue, then review the closed pull request #1660 to understand the work already undertaken. Compare that approach with the requested ability to target externally maintained ConfigMaps and Secrets without labels or annotations, and verify whether refresh calls for the configured applications are covered.