-
Epic
-
Resolution: Won't Do
-
Critical
-
None
-
ACM Downstream and Support External Secrets Operator
-
False
-
-
False
-
To Do
-
ACM-644 - Key and Secret Management
Epic Goal
- We would like to have an official way to do SecretsManagement.
ExternalSecretsOperator (https://github.com/external-secrets/external-secrets/)
It has large adoption and is e.g. used by Redhat's ValidatedPatterns (https://redhat-gitops-patterns.io/secrets/vault/).
Why is this important?
- we want to provide an official supported solution for SecretsManagement. We know there are many ways and this looks best regarding
adoption and supported providers.
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
- depends on
-
OCPSTRAT-1539 External Secrets Operator (ESO) support in OpenShift (TechPreview)
-
- Closed
-
- duplicates
-
-
- Approved
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- links to
