-
Notifications
You must be signed in to change notification settings - Fork 98
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
redpanda: replace bash jobs with go utilities #1534
Conversation
I'm leaving this in draft for the moment as we'll need to perform a release of the operator to pick up |
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.
It looks good. There is new operator release https://github.com/redpanda-data/redpanda-operator/releases/tag/v2.2.3-24.2.4
6cfc9a5
to
04f316c
Compare
04f316c
to
2bff635
Compare
This commit removes the bash scripts that used to power the post_upgrade and post_install_upgrade job with the recently implement `sync-cluster-config` sub command of the redpanda operator. `bootstrap.yaml` will now be correctly populated with secret values from cluster inception. bootstrap will contain place holder values in the form of `$REDPANDA_PROPERTY_NAME` which are filled out by the envsubst init container. The post_upgrade job has been removed as the post_install_upgrade job performed the majority of it's behavior sans setting cloud storage secrets which it now does thanks to the aforementioned bootstrap yaml envsubst'ing.
2bff635
to
b527f59
Compare
this is causing startup to hang: #1564 |
This commit removes the bash scripts that used to power the post_upgrade and post_install_upgrade job with the recently implement
sync-cluster-config
sub command of the redpanda operator.bootstrap.yaml
will now be correctly populated with secret values from cluster inception. bootstrap will contain place holder values in the form of$REDPANDA_PROPERTY_NAME
which are filled out by the envsubst init container.The post_upgrade job has been removed as the post_install_upgrade job performed the majority of it's behavior sans setting cloud storage secrets which it now does thanks to the aforementioned bootstrap yaml envsubst'ing.