Epic Goal

• Establish a CI scenario running in FIPS mode.

Why is this important?

• We need to be able to demonstrate MicroShift running correctly on a FIPS-enabled host.

Scenarios

1. Test basic functionality, including accessing a workload.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions::

1. Should it run as a pre-submit or periodic job?
2. Does it need to run a specific workload to verify FIPS mode?
3. What other tests need to be run.

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>