Feature Overview (aka. Goal Summary)  

Users can easily understand and find product offerings with the updated filtering option “Designed for FIPS” in the OperatorHub (and other Red Hat catalogs).

Goals (aka. expected user outcomes)

We as Red Hat has updated the official Red Hat wording about FIPS is reflected in: https://docs.google.com/presentation/d/1Rt0AoUK12__2CQgWM_Qk9A7GPEqKMO4mQZhW3mA4pU8/edit#slide=id.g285e61acaf3_1_66 (slides 2 & 3)

We describe our solutions as “Designed for FIPS”, then to meet the FIPS 140 regulatory requirement the solution must use a FIPS validated cryptographic module.

Hence, we want to accurately message the expectations of our product offerings that are designed for FIPS with the validated cryptographic module across the OperatorHub and other Red Hat catalogs to our customers.

Requirements (aka. Acceptance Criteria):

• OpenShift console: CONSOLE-4032 OperatorHub changes the display text of the filtering option for FIPS to “Designed for FIPS”
  • This needs backporting to OCP 4.14, 4.15, and the upcoming 4.16 release.

• Red Hat Ecosystem catalog: changes the display text of the filtering option for FIPS to “Designed for FIPS”

• No changes in the actual CSV annotation/operator metadata format

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

<your text here>

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

<your text here>

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>