operator: preserve bootstrap user password during flux migrations #438
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a "forward port" of #433 because it skipped my mind that this is required in main despite the impending removal of flux.
Prior to this commit, toggling useFlux from true <-> false would result in the bootstrap user's password being re-minted due to the chart gating the check for existing Secrets with
.Release.IsUpgrade
and the operator failing to set that field.This commit bumps the chart to a version that always runs the lookup check to correctly manage transitions to and from flux installations.
Additionally, this commit includes an update to the operator's integration test suite which self hosts a helm repository if a replace directive targeting the redpanda helm chart is found in the go.mod. This makes it possible to test local changes of the helm chart in both flux and defluxed modes.