Currently, after a secret is updated, we have to restart the pods ourselves (by patching the deployments). This should be automated.
Possible solutions:
- Scan all deployments that use the secret and patch them (to restart)
- Add an entry in
kcu.yml that links a secret with the deployments to restart (although this may change over time and the effect will surprise the developer)