wave-k8s / wave

Kubernetes configuration tracking controller
Apache License 2.0
646 stars 82 forks source link

Scope a specific configmap or secret #99

Closed whitelion-github closed 3 years ago

whitelion-github commented 3 years ago

Is it possible to scope a specific configmap or secret in the deployment ?

wonderhoss commented 3 years ago

I assume you mean to limit Wave to just a certain ConfigMap / Secret? That is not currently possible.

The idea behind Wave is to ensure that no matter what configuration a Deployment consumes, any changes to these will result in a rollout of that Deployment. Not needing to specifically list these means there is no chance of the watched config going out of sync with what the Deployment actually uses.

What is your use case for wanting to limit Wave in this way?

github-actions[bot] commented 3 years ago

This issue has been inactive for 60 days. If the issue is still relevant please comment to re-activate the issue. If no action is taken within 7 days, the issue will be marked closed.

whitelion-github commented 3 years ago

We're using cert-manager and want to force a rollout when the secret containing the certificate change (new cert). You're right, whatever configmap or secret modified, it would answer the our need. Tks.