Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-7704

Support Argo CD Notifications in Any Namespace

XMLWordPrintable

    • Support Argo CD Notifications in Any Namespace
    • M
    • False
    • Hide

      None

      Show
      None
    • False
    • RFE-6839ArgoCD Notifications should work for Applications in any Namespace
    • Done
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      This enhancement enables cluster administrators to delegate the management of Argo CD notification settings to application teams in additional namespaces.

      With this update, teams can configure their own triggers, templates, and subscriptions for their Applications without requiring administrator access to the control plane namespace. This is achieved by adding the target namespace to both spec.sourceNamespaces and spec.notifications.sourceNamespaces in the ArgoCD Custom Resource (CR).
      Show
      This enhancement enables cluster administrators to delegate the management of Argo CD notification settings to application teams in additional namespaces. With this update, teams can configure their own triggers, templates, and subscriptions for their Applications without requiring administrator access to the control plane namespace. This is achieved by adding the target namespace to both spec.sourceNamespaces and spec.notifications.sourceNamespaces in the ArgoCD Custom Resource (CR).

      Epic Goal

      Support upstream Argo CD in any namespace feature in operator

      https://argo-cd.readthedocs.io/en/stable/operator-manual/notifications/#namespace-based-configuration 

      Why is this important?

      A common installation method for Argo CD Notifications is to install it in a dedicated namespace to manage a whole cluster. In this case, the administrator is the only person who can configure notifications in that namespace generally. However, in some cases, it is required to allow end-users to configure notifications for their Argo CD applications. For example, the end-user can configure notifications for their Argo CD application in the namespace where they have access to and their Argo CD application is running in.

      Scenarios

      1. ...

      Other Considerations

      • <Call out anything explicitly as Out of Scope?>
      • <Call out internal and external dependencies?>
      • <Are there any known previous works?>
      • <Any unanswered questions?>

      Definition of Ready

      • The epic has been broken down into stories.
      • Stories have been scoped.
      • The epic has been stack ranked.

      Definition of Done

      • Code Complete:
        • All code has been written, reviewed, and approved.
      • Tested:
        • Unit tests have been written and passed.
        • Integration tests have been completed.
        • System tests have been conducted, and all critical bugs have been fixed.
        • Tested on OpenShift either upstream or downstream on a local build.
      • Documentation:
        • User documentation or release notes have been written.
      • Build:
        • Code has been successfully built and integrated into the main repository / project.
      • Review:
        • Code has been peer-reviewed and meets coding standards.
        • All acceptance criteria defined in the user story have been met.
        • Tested by reviewer on OpenShift.
      • Deployment:
        • The feature has been deployed on OpenShift cluster for testing.
      • Acceptance:
        • Product Manager or stakeholder has reviewed and accepted the work.

              nmirasch@redhat.com Neus Miras Chueca
              rh-ee-sghadi Siddhesh Ghadi
              Crimson
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: