Epic Goal

• As part of https://issues.redhat.com/browse/OCPSTRAT-809 the node team has been working on a tool to scan binaries to report whether they are compiled properly for FIPS compliance. Today the tool starts with inputs like a release payload or container image. We would like to be able to use the tool with a MicroShift binary, which is not inside of a container image. We should work with the node team to extend the tool to support that use case, then we can add automated verification that we are building MicroShift properly.

Why is this important?

• ...

Scenarios

1. ...

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. ...

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>