-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Allow setting volume mounts for dex container
-
False
-
None
-
False
-
To Do
-
-
Epic Goal
Allow users to add volumes and volume mounts to dex deployment.
RFE: GITOPS-5899
Github issue: https://github.com/argoproj-labs/argocd-operator/issues/1597
Why is this important?
This feature will enable seamless integration with external Identity Providers by allowing the required certificates or configurations to be mounted into the Dex container.
Scenarios
- User wants to configure external Identity Provider example keycloak with has custom TLS. Without a option to mount the keycloak's root CA in dex, user has to either hardcode the rootCA in ArgoCD CR or disable TLS verification completely. With volume mount option, user can mount a CA file and reference it in dex configs via .spec.sso.dex.config field in ArgoCD CR.
Other Considerations
- <Call out anything explicitly as Out of Scope?>
- <Call out internal and external dependencies?>
- <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:
- Product Manager or stakeholder has reviewed and accepted the work.