-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Allow setting resource inclusion/exclusion #2591
Comments
Hi @aqeelat , thank you for your issue. FYI: The following works well for now, it's just not declared in values.yaml though. :) configs:
cm:
resource.exclusions: |
- apiGroups:
- "*"
kinds:
- "*"
clusters:
- https://192.168.0.20 |
Hi @yu-croco - the key is not part of CM as there is link to upstream with all supported attributes. The exclusions really depends what you have in cluster (crossplane, external-secrets, kyverno, etc. are typically here). |
Hi @pdrastil , thank you for your comment.
|
We also had issues with this while upgrading. I think moving this config to |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is your feature request related to a problem?
Since it is part of the declarative setup, it would be useful to add it to the chart as well
https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#resource-exclusioninclusion
Related helm chart
argo-cd
Describe the solution you'd like
Adding an option for it in values.yaml
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: