Epic: Notifications GA

Epic Goal

Make Notifications generally available. 

Why is this important?

The Argo Project made Notifications part of Argo CD in version 2.3 (March '22), and OpenShift GitOps has provided Tech Preview support since v1.6.0 (July '22).

Scenarios

Acceptance Criteria (Mandatory)

• Version support: Customers can create, use, and update notifications in all supported versions of the OpenShift GitOps operator, on all supported versions of OCP

• Upstream version: The operator is using the latest version of Argo CD which includes the latest version of Notifications

• Team familiarity: At least two team members in different timezones are familiar with the relevant code, these people are known to the rest of the team as SMEs for Notifications
• Testing: CI is passing and includes automated tests for the relevant parts of the codebase
• Test coverage: The team is satisfied with the test coverage for the relevant parts of the code
• Documentation: A page or section exists in the official GitOps docs for Notifications, and describes how to configure Notifications when using OpenShift GitOps, as well as any differences between the operator and the upstream when using Notifications.
• Support resources: CEE team members have an instructional/training document for Notifications. This training is linked to in this spreadsheet: https://docs.google.com/spreadsheets/d/1Px40DbUVZCXZdPyNQtrS4FJ9Fagmzmvl219ACnkvpFM/edit#gid=0 

Dependencies (internal and external)

1. Manage Notifications via a CR: https://issues.redhat.com/browse/GITOPS-2304 
   1. Spike to assess if we can manage Notifications config in a CR: https://issues.redhat.com/browse/GITOPS-2878 
2. Controller doesn't trust TLS certs: https://issues.redhat.com/browse/GITOPS-2809 (targeted for 1.11)
3. Not using correct repo-server service: https://issues.redhat.com/browse/GITOPS-2867 (two customer cases, targeted for 1.10.2)
4. Expose metrics for monitoring: https://issues.redhat.com/browse/GITOPS-2241 
5. Test failure: https://issues.redhat.com/browse/GITOPS-2857 

Previous Work (Optional):

1. ...

Open questions:

1. ...

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment