-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
ArgoCD Notifications Controller - Permission issue #16022
Comments
solved by creating clusterrole and clusterrolebinding. |
I have also encountered into this after upgrading from v2.8.4 to v2.8.5, since |
Confirming this also happens via https://github.com/argoproj/argo-helm/tree/main/charts/argo-cd with the upgrade to Helm release argo-cd to v5.48.0 |
This should have been fixed by https://github.com/argoproj/argo-cd/pull/16057/files. |
Updated yesterday with helm chart directly from the main branch and still same issue.
Edit: Using argo-helm version not manifest. Fixed by argoproj/argo-helm#2315 |
I think technically yes, #16057 fixes the notifications controller by listing Application resources in its installed namespace when edit: I got it, this part states that users need to apply extra manifests if they want to use Applications in any namespace, but I think that's easy to miss. |
@davidmendezph the fix has been merged but still needs to be released. It'll be in 2.8.6. I'm working through some CI issues, but should get that cut today. @motoki317 let's stick with adding the cluster role as an opt-in for now. If you'd like to update the docs to be more clear, that would be appreciated! |
ArgoCD versions 2.10 and below have reached EOL. Can you upgrade and let us know if the issue is still present, please? |
Checklist:
argocd version
.Describe the bug
I am trying to use argocd notifications to send the slack notifications. But I see a frequent error in notifications pod.
To Reproduce
Current version I have.
Expected behavior
There should not be any error and notification should be sent on Slack.
Screenshots
Version
The text was updated successfully, but these errors were encountered: