Goal:
As an admin / business /developer I want to rely on the stability of an EUS release but at the same time benefit from the agility and traceability that the OpenShift-GitOps-Operator brings for my deployments and cluster-management with the GitOps pattern. The GitOps-Operator brings the advantage that I do not have to rely on third party products but brings GitOps functionality with kubernetes native means and maintained by Red Hat.

Justification:
Currently, the GitOps-Operator is TP in OCP 4.6 only. TPs are not fully supported and compatibility to GA-versions is not given. This can lead to problems if the cluster is updated to the next EUS release. This might render the complete GitOps infrastructure that was set up useless.

Furthermore, in a mixed environment (some clusters are on EUS, some advance with the "normal" lifecycle) customers would be forced to adapt different ways of managing their clusters/applications, which results in a bad product experience and would force different ways of maintenance for different environments which is an avoidable extra effort.

Acceptance criteria:

• GitOps-Operator is GAed for OCP 4.6