OCP/Telco Definition of Done
Epic Template descriptions and documentation.{}

Epic Goal

• The Windows Machine Config Operator needs to be FIPS compliant

More details:

FIPS 140 support for OpenShift bundled products and operators
FIPS Workshop
KONFLUX-4158

Why is this important?

• FIPS compliance is a critical feature of OpenShift which allows Red Hat to sell into key governmental and non-governmental market segments.
• All operators in the Red Hat Operators catalog must be FIPS compliant by January 31st, 2025.

Acceptance Criteria

• • WMCO Builds are FIPS compliant
  • Konflux static checks verify container image compliance

Dependencies (internal and external)

1. Go toolset support for FIPS
2. UBI 9 support for FIPS
3. golang.org/x/crypto FIPS compliant

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>