-
Task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
NEW
-
OBSDA-390 - Integration of Perses: backend & frontend / Internal Customers - OCP web console & RHACM console
-
NEW
-
-
-
Sprint 266
Background
Every component installed with COO must be compliant with FIPS, this includes the Perses operator
Outcomes
- The Perses operator that is installed with OCP via COO is FIPS compliant
Steps
- include the FIPS shims as described: https://docs.google.com/presentation/d/1o3IowxHX6BsnxGkIInaQ0lBgnn_K5Ex8jxwCYCeNsqs/edit#slide=id.g2679cb578c3_0_17
- Validate the image using: https://github.com/openshift/check-payload
- is depended on by
-
OU-453 Onboard the Perses Operator into COO konflux
- New