Open alita1991 opened 4 weeks ago
If I'm not wrong, in Kubernetes Pods and Configmap are decoupled so it's not related to the operator, it's default behavior. You'll need to find another way (watchers, kustomize or tools that will handle it for you)
I solved this problem with https://github.com/stakater/Reloader, but I'm seeking a solution to minimize additional steps. For example, if the Redis Operator can create the ConfigMap via CR, it should be enough to know when to trigger a RollingUpgrade, the easiest way is with an annotation that stores the hash value of ConfigMap data.
What version of redis operator are you using?
redis-operator version: 0.16.0
Does this issue reproduce with the latest release? Yes
What operating system and processor architecture are you using (
kubectl version
)?kubectl version
OutputWhat did you do?
What did you expect to see? Redis instance should be restarted
What did you see instead? Redis instance is not restarted to start with the new config