-
Epic
-
Resolution: Done
-
Major
-
None
-
None
According to scan with check-payload tool keystone-operator is not build properly for OCP with FIPS enabled. Scan results:
- upstream image
+-----------------------------+-----------------+------------------------------+---------------------------------------------------+ | OPERATOR NAME | EXECUTABLE NAME | STATUS | IMAGE | +-----------------------------+-----------------+------------------------------+---------------------------------------------------+ | | | openssl library not present | quay.io/openstack-k8s-operators/keystone-operator | | keystone-operator-container | /manager | go binary is not CGO_ENABLED | quay.io/openstack-k8s-operators/keystone-operator | +-----------------------------+-----------------+------------------------------+---------------------------------------------------+
- downstream image
+-----------------------------+-----------------+------------------------------+----------------------------------------------------------------------+ | OPERATOR NAME | EXECUTABLE NAME | STATUS | IMAGE | +-----------------------------+-----------------+------------------------------+----------------------------------------------------------------------+ | keystone-operator-container | /manager | go binary is not CGO_ENABLED | registry.redhat.io/rhosp-dev-preview/keystone-rhel9-operator:0.1.2-6 | +-----------------------------+-----------------+------------------------------+----------------------------------------------------------------------+
1.
|
[Security] Build barbican & keystone operator correctly for OCP with FIPS enabled | Closed | Unassigned |