-
Notifications
You must be signed in to change notification settings - Fork 212
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
Enable persistence for pulsar-manager #343
Conversation
The pulsar-manager persistence fix has been merged, so it would be nice if this fix was merged too 😄 |
Any chance we can get this merged? LGTM! |
@vfauth Thanks for the contribution. Do you have a chance to rebase the changes and ensure that this works with recent versions? |
@Mortom123 Please check this PR, is something like this needed after #457? |
Yes this is an open issue. However I think it could be quite charming to use the Zookeper as store for the Pulsar-Manager configuration data. @lhotari |
1353ae6
to
e93f9fa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks for the contribution @vfauth ! This is merged now and will be included in the next release of the chart. |
Motivation
Currently, pulsar-manager volume is not persistent, which means that after a pod restart admin accounts must be recreated every time. I want to change that.
Modifications
Switch pulsar-manager from a Deployment to a StatefulSet and add settings to enable persistence. The settings are inspired by those offered for other components.
Also, the Docker image will always reinitialize the DB, so I made a PR to fix that too.
Verifying this change