Overview

The notification services represent integration with services such as slack, email or custom webhook. Services are configured in argocd-notifications-cm ConfigMap using service.<type>.(<custom-name>) keys and might reference sensitive data from argocd-notifications-secret Secret. Following example demonstrates slack service configuration:

  1.   service.slack: |
  2.     token: $slack-token

The slack indicates that service sends slack notification; name is missing and defaults to slack.

Sensitive Data

Sensitive data like authentication tokens should be stored in <secret-name> Secret and can be referenced in service configuration using $<secret-key> format. For example $slack-token referencing value of key slack-token in <secret-name> Secret.

Custom Names

Service custom names allow configuring two instances of the same service type.

  1.   service.slack.workspace1: |
  2.     token: $slack-token-workspace1
  3.   service.slack.workspace2: |
  4.     token: $slack-token-workspace2
  1. apiVersion: argoproj.io/v1alpha1
  2. kind: Application
  3. metadata:
  4.   annotations:
  5.     notifications.argoproj.io/subscribe.on-sync-succeeded.workspace1: my-channel
  6.     notifications.argoproj.io/subscribe.on-sync-succeeded.workspace2: my-channel

Service Types