chore(helm)!: Rearrange values to be somewhat consistent with the listener-operator value changes #641
+56
−40
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.
Description
Part of stackabletech/issues#763
Note
These changes aren't exactly consistent with listener-operator changes from stackabletech/listener-operator#334, but are a step towards consistency, and make it easier should we decide to split secret-operator into a CSI Provisioner Deployment and CSI Node Driver DaemonSet.
Helm Values changes
Caution
The original values are no longer valid.
image.repositoryhas been moved tosecretOperator.image.repository.image.taghas been moved tosecretOperator.image.tag.image.pullPolicyhas been moved tosecretOperator.image.pullPolicy.csiProvisionervalues have been moved toexternalProvisioner.csiNodeDriverRegistrarvalues have been moved tonodeDriverRegistrar.node.drivervalues have been moved tosecretOperator.securityContextvalues have been moved tosecretOperator.securityContext.Tip
In addition, the following new value is available.
This is part of stackabletech/issues#765.
priorityClassNameDetails