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
When using the "Applications in any namespace" feature, notification subscriptions added to AppProject resources have no effect if the Application resource is in another namespace.
There are no errors in any argo-cd pod logs. The notification-controller just doesn't seem to honor the annotations on the AppProject if the Application is not in the argocd namespace.
Sanity checks:
Moving the Application to the argocd namespace makes the notifications work.
Adding the subscribe-annotation directly to the Application resource (instead of the AppProject) also works.
While this PR made subscribe annotations on Applications in any namespace work, it may have overlooked the case where the annotations are on the AppProject instead, which are always in the argocd system namespace.
Checklist:
argocd version
.Describe the bug
When using the "Applications in any namespace" feature, notification subscriptions added to
AppProject
resources have no effect if theApplication
resource is in another namespace.There are no errors in any argo-cd pod logs. The notification-controller just doesn't seem to honor the annotations on the AppProject if the Application is not in the
argocd
namespace.Sanity checks:
Application
to theargocd
namespace makes the notifications work.subscribe
-annotation directly to theApplication
resource (instead of theAppProject
) also works.To Reproduce
Enable app-in-any-namespace-feature:
Setup notification triggers and templates:
Create an AppProject with notification subscriptions enabled:
Create an application that is part of the AppProject above but does not include its own notification annotations:
Then sync the
netshoot
application. No notifications will be send and the logs will show no errors or warnings.Expected behavior
According to the documentation at https://argocd-notifications.readthedocs.io/en/stable/subscriptions/, I would expect the above example to "just work". And indeed it does just work when moving the Application to the
argocd
namespace.More thoughts
I feel like this may have something to do with:
While this PR made
subscribe
annotations on Applications in any namespace work, it may have overlooked the case where the annotations are on theAppProject
instead, which are always in theargocd
system namespace.Version
Logs
No relevant logs :(
The text was updated successfully, but these errors were encountered: