Goal 

To ensure OpenShift GitOps operator can be deployed, managed, and utilized effectively within HyperShift OpenShift hosted clusters.

Why is this important? OpenShift GitOps offers a declarative way to implement continuous deployment for cloud-native applications. With the growing adoption of hosted-control planes (using HyperShift) as a cost-effective and portable OpenShift form factor, it becomes critical to ensure that GitOps, like other layered operators, is fully functional in this environment. This will extend the value of OpenShift and uphold the promise of seamless portability and compatibility across different OpenShift architectures.

Scenarios

• Deploying the OpenShift GitOps operator on a HyperShift hosted OpenShift cluster.
• Managing application lifecycles using GitOps on a HyperShift hosted OpenShift cluster.
• Updating and maintaining the GitOps operator within the HyperShift environment.

Note: Cluster-bot today runs HyperShift by default

Acceptance Criteria (Mandatory)

• OpenShift GitOps operator can be successfully deployed on HyperShift hosted OpenShift cluster.
• CI pipeline is established and running successfully with automated tests covering all the mentioned scenarios.
• User can manage application lifecycle using GitOps on a HyperShift hosted OpenShift cluster.
• Documentation and technical enablement details are provided for release.
• The GitOps operator can be updated and maintained within the HyperShift environment without disruption.

Open Questions:

• What are the specific challenges, if any, in deploying the GitOps operator in a HyperShift Hosted Cluster environment?
• Do we need any additional resources or infrastructure to support the GitOps operator on HyperShift?