-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
-
None
-
False
-
-
False
-
-
-
OCM Core Sprint 251, OCM Core Sprint 252
Logically, the encryption fields structure is:
- Encryption Keys
- Key ARN
- etcd encryption
- FIPS cryptography
Lack of spacing between "Key ARN" and "etcd encryption" is confusing, because these two look tighter-related than the rest but actually are unrelated.
Steps to reproduce
- https://console.redhat.com/openshift/create/osd
- choose CCS
- choose AWS
- reveal Advanced encryption section
- choose Use custom KMS keys to reveal Key ARN field
- check Enable additional etcd encryption to reveal FIPS cryptography field
Actual spacing
Expected spacing
Spacing between Key ARN–etcd encryption should be ≤
spacing Encryption Keys–Key ARN and etcd encryption–FIPS cryptography.
ROSA v1 has it OK:
- is triggering
-
OCMUI-1749 [ROSA wizard] style regression for radio button descriptions
- Closed
- relates to
-
OCMUI-820 ROSA wizard v2: Update v2 Cluster Settings - Details step for Rosa usage
- Closed
- mentioned on