You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did you do?
Try to deploy eck-operator chart v2.7.0 through ArgoCD.
What did you expect to see?
Everything in sync. I expect the caBundle of the webhook to not be set when it is not configured, especially not when manageCerts is true. This behavior was changed in #6489
What did you see instead? Under which circumstances?
Argo keeps going out-of-sync because the webhook caBundle desired state is Cg==, but the eck operator also sets the value.
This happens when using the defaults for the webhook config.
I see the problem. We should be able to improve this by including the webhook client configuration CA only when certificates are not managed by the operator.
Bug Report
What did you do?
Try to deploy eck-operator chart v2.7.0 through ArgoCD.
What did you expect to see?
Everything in sync. I expect the caBundle of the webhook to not be set when it is not configured, especially not when manageCerts is true. This behavior was changed in #6489
What did you see instead? Under which circumstances?
Argo keeps going out-of-sync because the webhook caBundle desired state is
Cg==
, but the eck operator also sets the value.This happens when using the defaults for the
webhook
config.Environment
ECK version:
https://github.com/elastic/cloud-on-k8s/releases/tag/v2.7.0
Kubernetes information:
Irrelevant
Values:
The text was updated successfully, but these errors were encountered: