github.com/argoproj-labs/argocd-operator@v0.10.0/docs/usage/notifications.md (about)

     1  ## Overview
     2  
     3  [Argo CD Notifications](https://blog.argoproj.io/notifications-for-argo-bb7338231604) 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. 
     4  
     5  ## Installation
     6  
     7  Argo CD Notifications controller can be enabled/disabled using a new toggle within the Argo CD CR with default specs as follows:
     8  
     9  ``` yaml
    10  apiVersion: argoproj.io/v1alpha1
    11  kind: ArgoCD
    12  metadata:
    13    name: example-argocd
    14  spec:
    15    notifications:
    16      enabled: True
    17  ```
    18  
    19  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](../reference/api.html.md#argoproj.io/v1alpha1.ArgoCDNotificationsSpec)
    20  
    21  Notifications is disabled by default. Enabling notifications results in the operator creating the following resources on the cluster:
    22  
    23  *  `<argocd-instance-name>-notifications-controller` deployment
    24  *  `<argocd-instance-name>-argocd-notifications-controller` serviceAccount
    25  *  `<argocd-instance-name>-argocd-notifications-controller` role
    26  *  `<argocd-instance-name>-argocd-notifications-controller` roleBinding
    27  *  `<argocd-instance-name>-argocd-notifications-cm` configmap
    28  *  `<argocd-instance-name>-argocd-notifications-secret` secret
    29  
    30  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.
    31  
    32  Instructions for appropriate configuration of these resources can be found within [upstream documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/notifications/)
    33  
    34  
    35  ## Uninstallation
    36  
    37  Argo CD Notifications controller can be disabled by setting `.spec.notifications.enabled` to `false` :
    38  
    39  ``` yaml
    40  apiVersion: argoproj.io/v1alpha1
    41  kind: ArgoCD
    42  metadata:
    43    name: example-argocd
    44  spec:
    45    notifications:
    46      enabled: false
    47  ```
    48  This will clean up all the aforementioned notifications-controller resources that were created by the operator.