Specify registry address for .Values.controller.extraInitContainers

[larstobi]

I would like to be able to specify a private registry address when I add an extraInitContainers item to the .Values.controller.extraInitContainers value in values.yaml.

Example:

controller:
 extraInitContainers:
   - name: nginx-conf
     image: busybox:latest
     registry: myprivateregistry.org

Currently, if I add the registry property, it is ignored.

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[larstobi]

I think maybe this is the place in the helm chart:

ingress-nginx/charts/ingress-nginx/templates/controller-deployment.yaml

Line 183 in ca81d5b

{{- if (or .Values.controller.extraInitContainers .Values.controller.extraModules) }}

[Gacko]

extraInitContainers are directly getting passed into the template, so you need to define them as Kubernetes expects them. They are not changed in any way by the chart. For the same reason we sadly cannot apply the .global.image.registry logic there, which would enable you to set the registry for all images in a single place.

Have you tried prepending the registry to the image value?

[Gacko]

/kind support