fix: do not overwrite manually created operator configuration resource #302
+153
−83
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.
...with values provided via Helm.
Previously, when instructed to create/update the operator configuration
resource via Helm, the operator manager would update any operator
configuration resource it finds with the provided value. This would
likely lead to unexpected results if people transition from a manually
configured operator configuration resource to a Helm-managed values.
Now the operator will refuse to overwrite the existing resource in this
scenario and log an error.
Also: Describe the behavior around creating the operator configuration
resource via Helm in more detail in the docs.