Epic Goal

• Define the deployment model of GitOps Operator on Developer Sandbox

Why is this important?

• We need to define a GitOps deployment strategy that is multi-tenant safe, secure by design, scalable, and optimized to minimize support and operational costs.

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:
  • The deployment strategy is signed off by the DevSandbox Architect and GitOps Architect  We should have a well writtent deployment strategy doc.