feat(argo-rollouts): Add notification secret and configmap (#1163)

* fixing the error on the argo rollouts controller needing the notifications configmap and rollout

Signed-off-by: Ian Muge <ian.muge@ardoq.com>

* bump chart version

Signed-off-by: Ian Muge <ian.muge@ardoq.com>

* updating changelog

Signed-off-by: Ian Muge <ian.muge@ardoq.com>

* fix structure to be simialr to argocd-notification as suggested

Signed-off-by: Ian Muge <ian.muge@ardoq.com>

* Bump Minor version as we are adding a new feature

Signed-off-by: Ian Muge <ian.muge@ardoq.com>

* Updated helm docs, all tests are green, locally

Signed-off-by: Ian Muge <ian.muge@ardoq.com>

* Apply changes from code review

Signed-off-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com>

Co-authored-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com>

charts/argo-rollouts/values.yaml

@@ -237,3 +237,34 @@ dashboard:
       # - secretName: argorollouts-example-tls
       #   hosts:
       #     - argorollouts.example.com
+
+notifications:
+  secret:
+    # -- Whether to create notifications secret
+    create: false
+    # -- Generic key:value pairs to be inserted into the notifications secret
+    items: {}
+      # slack-token:
+
+  # -- Configures notification services
+  notifiers: {}
+    # service.slack: |
+    #   token: $slack-token
+
+  # -- Notification templates
+  templates: {}
+    # template.my-purple-template: |
+    #   message: |
+    #     Rollout {{.rollout.metadata.name}} has purple image
+    #   slack:
+    #       attachments: |
+    #           [{
+    #             "title": "{{ .rollout.metadata.name}}",
+    #             "color": "#800080"
+    #           }]
+
+  # -- The trigger defines the condition when the notification should be sent
+  triggers: {}
+    # trigger.on-purple: |
+    #   - send: [my-purple-template]
+    #     when: rollout.spec.template.spec.containers[0].image == 'argoproj/rollouts-demo:purple'