Epic Goal

Leverage the OperatorPolicy kind to manage OpenShift Gitops. Create appropriate integrations with GitopsClusters kind & controller.

Why is this important?

The easier it is to setup OpenShift GitOps in push or pull mode, the more likely a user will consume the technology.

Scenarios

1. Install OpenShift GitOps on the ACM hub (push)
2. Install OpenShift GitOps more than once on the ACM hub (push)
3. Install OpenShift GitOps on one or more ManagedClusters (pull)
4. Install OpenShift GitOps on ACM hub and ManagedClusters (push & pull)

Acceptance Criteria

push and pull models are easier to use.

Dependencies (internal and external)

1. gitopscluster kind & controller
2. operatorPolicy kind & controller

Previous Work (Optional):

1. gitopscluster kind & controller
2. operatorPolicy kind & controller

Open questions:

1. How should we integrate that this operator deploys and gitopsclusters.

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.