XML

Word

Printable

Epic Name:
TLSSecurityProfile
Work Type:
Strategic Product Work
Blocked:
False
Blocked Reason:
None
Ready:
False
Color Status:
Not Selected
Epic Status:
To Do
Feature Link:
OCPSTRAT-284 - Standardization around configurable TLS security profiles for layered products and components
Hierarchy Progress Bar:

100% To Do, 0% In Progress, 0% Done

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

Why is this important?

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.
The registry should have a new configuration parameter "tlsSecurityProfile", see https://access.redhat.com/documentation/en-us/openshift_container_platform/4.8/html/security_and_compliance/tls-security-profiles for reference
The default value should be "modern"
The operator can use the existing support for the REGISTRY_HTTP_TLS_CIPHERSUITES environment variable and set the ciphers there according to the chosen profile
Specified ciphers in the modern profile should be used by registry server

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>