-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: Zookeeper-operator does not restart pods when static configs are changed #454
Comments
@hoyhbx -- Your suggestion for improvement sounds sensible. Is this something you could implement and provide a PR for? Thanks! |
@hoyhbx Have one more question, Could you please try changing |
I tried changing the I think it would be nice for zookeeper-operator to automatically trigger a rolling update when the config is changed, I have seen this behavior in many other operators, such as rabbitmq's cluster operator and https://github.com/banzaicloud/koperator We are happy to provide a PR for this issue. |
Just hit this, any chance that we can get #469 merged? |
Description
When I change the fields under
spec.config
, zookeeper-operator does not issue a rolling update to roll out the changed config. For example, if I change thespec.config.commitLogCount
field to100
, the operator reconciles the configMap to reflect the change. So in the pod,/conf/zoo.cfg
which is where the configMap mounted has thecommitLogCount
field set to100
. But the/data/conf/zoo.cfg
which is the config used by zookeeper still has thecommitLogCount
set to default value as500
.Steps to reproduce:
/data/conf/zoo.cfg
:Importance
should-have
Location
Zookeeper-operator is missing the functionality to restart the pods when config is changed.
Suggestions for an improvement
We suggest to attach the hash of config as annotations to zookeeper's statefulSet's template. So that when the config is changed, the changed annotation would trigger statefulSet's rolling update.
The text was updated successfully, but these errors were encountered: