Epic Goal

• Define the deployment model of GitOps Operator on Developer Sandbox
• Pass the Performance Test. See https://docs.google.com/document/d/1xpV-N5Ij2h-YmBpN0mdUf1na6JxVdpJCd3lNX-Y3NMA/edit?tab=t.0#heading=h.9bv2x3exwcvi  (Flow to on/off-board a new operator/team)

Why is this important?

• The Developer Sandbox is a free trial environment. Although we do not have paying customers, we had 13.4k user sign-ups and influenced approximately $2 million in deals last quarter. Enabling GitOps on the Developer Sandbox will support Red Hat’s growth by helping teams experience the value of OpenShift and understand how GitOps integrates with other Red Hat products.
• The Developer Sandbox provides a place for users to quickly and easily interact with GitOps Operator/Argo CD, which is a valuable part of the sales experience. In addition, having our team involved in maintaining GitOps on a production cluster enables easier testing and faster iteration when issues arise.

Scenarios

1. Single Argo CD instance per cluster
2. Mulitple instance. An Argo CD instance per tenant.

Other Considerations

• The cloud cost of running GitOps Operator and Argo CD instances (per namespace/tenant)
• The deployment model may affect/increase the complexity of troubleshooting.
• <Are there any known previous works?>
• <Any unanswered questions?>

Definition of Ready

• The epic has been broken down into stories.
• Stories have been scoped.
• The epic has been stack ranked.

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Integration tests have been completed.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written.
• Build:
  • Code has been successfully built and integrated into the main repository / project.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.
• Acceptance:
  • Performance Test passed.