-
Epic
-
Resolution: Duplicate
-
Undefined
-
None
-
[Networking] Build designate-operator correctly for OCP with FIPS enabled
-
False
-
-
False
-
Committed
-
Proposed
-
To Do
-
Committed
-
Proposed
-
0% To Do, 0% In Progress, 100% Done
-
-
-
Networking; VANS
According to scan with check-payload tool designate-operator is not build properly for OCP with FIPS enabled. Scan results on upstream image (I didn't found d/s one for this operator):
+------------------------------+-----------------+------------------------------+----------------------------------------------------+ | OPERATOR NAME | EXECUTABLE NAME | STATUS | IMAGE | +------------------------------+-----------------+------------------------------+----------------------------------------------------+ | | | openssl library not present | quay.io/openstack-k8s-operators/designate-operator | | designate-operator-container | /manager | go binary is not CGO_ENABLED | quay.io/openstack-k8s-operators/designate-operator | +------------------------------+-----------------+------------------------------+----------------------------------------------------+
