Epic Goal

Migrate from DeploymentConfig to standard Kubernetes Deployment for RHSSO instance setup by GitOps Operator.

Why is this important?

GitOps operator uses DeploymentConfig to setup RHSSO (Keycloak) instance on Openshift. DeploymentConfig is deprecated[1] from Openshift 4.14 onwards and not recommended to use. We should move away from DeploymentConfig and use standard Kubernetes deployment to setup RHSSO instance. 

[1] https://access.redhat.com/articles/7041372 

Other Considerations

• The code for setting up RHSSO/keycloak is part of ArgoCD Operator codebase.
• It is implemented to use Deployments to setup keycloak when installing on Kuberentes and DeploymentConfig on Openshift. 
• We should consider unifying this logic. 

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:
  • Product Manager or stakeholder has reviewed and accepted the work.