-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
namespaceSelector of ValidatingWebhookConfiguration keeps on changing #4813
Comments
Hello,
What do you mean? KEDA operator modifies the manifest but only the Could you share the error that you see in ArgoCD? (and a picture if its possible to see how it looks in ArgoCD UI if you are using it) |
Hello @JorTurFer, Thanks for your feedback. We would expect it to be the way you describe it. Upon further investigation, we believe that it indeed not Keda, but the AKS admissions enforcer that edits the selector. We'll investigate options to deactivate that enforcer via annotation, as proposed in Azure/AKS#1771 and linked issues. |
Which is the problem exactly? The permanent out of sync status or the selector itself? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
Report
We are deploying Keda to our AKS clusters with the Helm chart (2.11.1) and ArgoCD (2.6.2). Generally speaking, Keda works perfectly, but we see some problems synchronizing the ValidatingWebhookConfiguration resource, as namespaceSelectors of the webhooks change after the initial deployment.
Expected Behavior
The webhook configurations remains stable. All parameters can be controlled via the Helm chart.
Actual Behavior
The namespaceSelector is intially empty and changes during runtime.
Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
2.11.1
Kubernetes Version
1.26
Platform
Microsoft Azure
Scaler Details
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: