Skip to content

Commit

Permalink
cleanup wording
Browse files Browse the repository at this point in the history
Signed-off-by: zachaller <zachaller@users.noreply.github.com>
  • Loading branch information
zachaller committed Aug 3, 2023
1 parent d00adbf commit d2e1cd9
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/features/notifications.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,8 +61,8 @@ for their Rollout resources. For example, the end-user can configure notificatio

To use this feature all you need to do is create the same configmap named `argo-rollouts-notification-configmap` and possibly
a secret `argo-rollouts-notification-secret` in the namespace where the rollout object lives. When it is configured this way the controller
will send notifications using both the controller level configuration aka the configmap located in the same namespaces as the controller
as well as the namespace level configuration where the rollout object is at.
will send notifications using both the controller level configuration (the configmap located in the same namespaces as the controller) as well as
the configmap located in the same namespaces where the rollout object is at.

To enable you need to add a flag to the controller `--self-service-notification-enabled`

Expand Down

0 comments on commit d2e1cd9

Please sign in to comment.