Background:

Argo CD notifications controller was released as a TP feature with OpenShift GitOps v1.6. Notifications controller allows users to configure triggers (to express what events should lead to the firing of notifications) and templates (what the notification message should look like when it goes out). These triggers and templates are currently configured within the argocd-notifications-cm configmap. This is a common pattern for upstream argo-cd. However, for an operator this is an anti-pattern. Users should not directly modify resoruces like configmaps and secrets. These are meant for the operator to control, and detected changes will be reverted. 

We want to correct this experience within our operator to make it so that users can configure notifications through the CR, but having an indefinite number of triggers/templates configured directly into the argo-cd CR would not be ideal, and would also make for a bad user experience. 

The purpose of this spike is to identify a solution that allows users to update notifications configuration through the CR, without having to either modify configmaps/secrets manually, or clutter the CR itself with this information. Some alternatives that could be considered would be resource injection/embedding, or an approach similar to keycloak installation using templates

Acceptance criteria:

• Investigate options by looking at other operators/previous implementations and compile a design document with proposed approach to achieve this goal