Feature Overview

• To connect dex to a Keycloak server secured by a private CA.
• There should be new field in the dex ArgoCD CRD, to allow mounting ConfigMaps containing the certificates.

Goals

• All the other containers besides dex which are part of the GitOps / ArgoCD Operator allow mounting volumes with the operator ArgoCD-CR. Adding this to dex would help allowing a new usecase

Requirements

Use Cases

• < What are we making, for who, and why/what problem are we solving?>

Out of Scope

• <Defines what is not included in this story>

Dependencies

• < Link or at least explain any known dependencies. >

Background and Strategic Fit

• < What does the person writing code, testing, documenting need to know? >

Assumptions

• < Are there assumptions being made regarding prerequisites and dependencies?>
• < Are there assumptions about hardware, software, or people resources?>

Customer Considerations

• < Are there specific customer environments that need to be considered (such as working with existing h/w and software)? >

Documentation/QE Considerations

• < What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)? >
• < Does this feature have a doc impact? Possible values are: New Content, Updates to existing content, Release Note, or No Doc Impact>

Impact

• < If the feature is ordered with other work, state the impact of this feature on the other work >

Related Architecture/Technical Documents

• <links>

Definition of Ready

• The objectives of the feature are clearly defined and aligned with the business strategy.
• All feature requirements have been clearly defined by Product Owners.
• The feature has been broken