-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
[Telemetry] Build telemetry-operator correctly for OCP with FIPS enabled
-
False
-
-
False
-
Committed
-
No Docs Impact
-
To Do
-
RHOSSTRAT-224 - FIPS Support in OSO 18.0
-
Committed
-
Committed
-
0% To Do, 0% In Progress, 100% Done
-
Release Note Not Required
-
Done
-
Automated
-
-
-
Approved
According to scan with check-payload tool telemetry-operator is not build properly for OCP with FIPS enabled. Scan results:
- upstream image
+------------------------------+-----------------+------------------------------+----------------------------------------------------+ | OPERATOR NAME | EXECUTABLE NAME | STATUS | IMAGE | +------------------------------+-----------------+------------------------------+----------------------------------------------------+ | telemetry-operator-container | /manager | go binary is not CGO_ENABLED | quay.io/openstack-k8s-operators/telemetry-operator | +------------------------------+-----------------+------------------------------+----------------------------------------------------+
- downstream image
+------------------------------+-----------------+------------------------------+-----------------------------------------------------------------------+ | OPERATOR NAME | EXECUTABLE NAME | STATUS | IMAGE | +------------------------------+-----------------+------------------------------+-----------------------------------------------------------------------+ | telemetry-operator-container | /manager | go binary is not CGO_ENABLED | registry.redhat.io/rhosp-dev-preview/telemetry-rhel9-operator:0.1.2-6 | +------------------------------+-----------------+------------------------------+-----------------------------------------------------------------------+
