[helm-chart] Include webhook client configuration CA only when certificates are not managed by the operator or cert-manager #6642
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 includes the webhook client configuration CA only when certificates are managed by the user, not when they are managed by the operator or cert-manager.
Currently, when certificates are managed by the operator or cert-manager, the webhook manifest is generated with client configuration CA set to
Cg==
. As soon as the webhook is created, the operator or cert-manager will generate a cert and update the client configuration CA. This is an issue when deploying ECK with tools like ArgoCD because the tool will indefinitely be in conflict with the operator or cert-manager by always resetting the generated CA.Resolves #6641.