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
We install the nexus3 helm charts using our own custom core registry (we have a registry containing the nexus3 images only, then nexus3 itself serves up the images for all our normal services). That being said, we override the image.repository helm value to point to this custom core registry. However, the initContainers in the deployment.yaml (and statefulset.yaml) hardcode the image values, forcing us to make edits to those specs manually. It would be convenient if the init containers could override the repository they are obtained from via helm values as well.
The text was updated successfully, but these errors were encountered:
@jmccrumm I'd be willing to add values to override the init container image but it's not implicitly related to the primary image so the current values aren't relevant. I was already planning on changing the default to a Chainguard image for zero CVEs.
We install the nexus3 helm charts using our own custom core registry (we have a registry containing the nexus3 images only, then nexus3 itself serves up the images for all our normal services). That being said, we override the
image.repository
helm value to point to this custom core registry. However, theinitContainers
in thedeployment.yaml
(andstatefulset.yaml
) hardcode theimage
values, forcing us to make edits to those specs manually. It would be convenient if the init containers could override the repository they are obtained from via helm values as well.The text was updated successfully, but these errors were encountered: