I am adding this because I noticed that helm-operator doesn't always restart
the deployments when a new configmap or secret has changed. This means that
changes do not actually take effect when we expect.
By adding this annotation, the reloader controller will restart the frontend
and backend deployments when any configmap or secret is updated. We can test
it and go back to a limited amount of data sources in the annotation if we
see it restarts too often or does something strange.
(note: copy of the same pr in the helm-charts repo)
I am adding this because I noticed that helm-operator doesn't always restart the deployments when a new configmap or secret has changed. This means that changes do not actually take effect when we expect.
By adding this annotation, the reloader controller will restart the frontend and backend deployments when any configmap or secret is updated. We can test it and go back to a limited amount of data sources in the annotation if we see it restarts too often or does something strange.
(note: copy of the same pr in the helm-charts repo)