You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Default image is eck/eck-operator:2.15.0. https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s_installation.html#k8s_fips_compliant_installation_using_helm
This document says to set image.repository=docker.elastic.co/eck/eck-operator-fips, which gives us this image eck/eck-operator-fips:2.15.0.
If we do not do that, but we set config.ubiOnly=true, we get this image eck/eck-operator-ubi:2.15.0.
However, if we set both fips and ubi we get this image eck/eck-operator-fips-ubi:2.15.0, which doesn't exist because the actual image is eck/eck-operator-ubi-fips:2.15.0.
The text was updated successfully, but these errors were encountered:
ke5C2Fin
changed the title
eck/eck-operator
eck/eck-operator fips and ubi
Nov 14, 2024
Thank you for reporting this. The issue is indeed a bug in how the Helm chart constructs the image name when it contains -fips and config.ubiOnly is enabled. We’ll work on resolving this. In the meantime, I think you can use the following workaround:
Default image is
eck/eck-operator:2.15.0
.https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s_installation.html#k8s_fips_compliant_installation_using_helm
This document says to set
image.repository=docker.elastic.co/eck/eck-operator-fips
, which gives us this imageeck/eck-operator-fips:2.15.0
.If we do not do that, but we set
config.ubiOnly=true
, we get this imageeck/eck-operator-ubi:2.15.0
.However, if we set both fips and ubi we get this image
eck/eck-operator-fips-ubi:2.15.0
, which doesn't exist because the actual image iseck/eck-operator-ubi-fips:2.15.0
.The text was updated successfully, but these errors were encountered: