-
Epic
-
Resolution: Done
-
Undefined
-
None
-
None
-
Secret encryption
-
Strategic Product Work
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-980 - Enforce Data/Secret Encryption for the Control-Planes, Etcd, and Nodes
-
OCPSTRAT-980Enforce Data/Secret Encryption for the Control-Planes, Etcd, and Nodes
-
0% To Do, 0% In Progress, 100% Done
-
Hypershift Sprint 245, Hypershift Sprint 246, Hypershift Sprint 247
-
0
-
0
-
0
User Story:
- As a service provider/consumer I want to make sure secrets are encrypted with key owned by the consumer
Acceptance Criteria:
Expose and propagate input for kms secret encryption similar to what we do in AWS.
See related discussion:
https://redhat-internal.slack.com/archives/CCV9YF9PD/p1696950850685729
(optional) Out of Scope:
Detail about what is specifically not being delivered in the story
Engineering Details:
- (optional) https://github/com/link.to.enhancement/
- (optional) https://issues.redhat.com/link.to.spike
- Engineering detail 1
- Engineering detail 2
This requires/does not require a design proposal.
This requires/does not require a feature gate.