Skip to content

Notifications

Overview

Argo CD Notifications was merged into core Argo CD codebase as a part of the v2.3 release. The notifications controller is now available as an optional workload that can be configured through the Argo CD operator.

Installation

Argo CD Notifications controller can be enabled/disabled using a new toggle within the Argo CD CR with default specs as follows:

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  name: example-argocd
spec:
  notifications:
    enabled: True

Users may also specify advanced configuration such as the number of replicas for the notifications controller, as well as the resource requirements for the same. The full list of available settings can be found in the API spec.

Notifications are disabled by default. Enabling notifications results in the operator creating the following resources on the cluster:

  • <argocd-instance-name>-notifications-controller deployment
  • <argocd-instance-name>-argocd-notifications-controller serviceAccount
  • <argocd-instance-name>-argocd-notifications-controller role
  • <argocd-instance-name>-argocd-notifications-controller roleBinding
  • <argocd-instance-name>-argocd-notifications-cm configmap
  • <argocd-instance-name>-argocd-notifications-secret secret

The operator creates the argocd-notifications-cm configmap which is populated with a set of default templates and triggers out of the box, in line with what is provided by the upstream Argo CD project. argocd-notifications-cm is editable to users, and will not be reconciled/overwritten by the operator. The argocd-notifications-secret is an empty secret that can be used to configure credentials for the supported notifications services.

Instructions for appropriate configuration of these resources can be found within upstream documentation.

Notifications in Any Namespace

By default, Argo CD Notifications uses a centralized configuration model where all notification settings are managed in the main Argo CD namespace (typically argocd). The operator supports delegating notification configuration to specific namespaces, allowing teams to manage their own notification settings.

For detailed information on enabling and using notifications in any namespace, see the Notifications in Any Namespace documentation.

Uninstallation

Argo CD Notifications controller can be disabled by setting .spec.notifications.enabled to false :

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  name: example-argocd
spec:
  notifications:
    enabled: false

This will clean up all the aforementioned notifications-controller resources that were created by the operator.