[2.5.0] imagePullSecrets not used for internal pods

[glagny]

trafficstars

Hi everyone :), when I install the release 2.5.0 (also tested with older version), the .Values.image.imageRegistryName is used as prefix for image pull (like for chaos-operator, event-tracker, subscriber, workflow-controller pods) but not the .Values.image.ImagePullSecrets, the configuration of this part of the values are:

image:
  imagePullSecrets:
    - name: <SECRET NAME>
  imageRegistryName: <PRIVATE REGISTRY HERE>/litmuschaos

and I still get ImagePullBackOff with the good image shape ( like <PRIVATE REGISTRY HERE>/litmuschaos/litmusportal-event-tracker:2.5.0 for example) but there is no imagePullSecrets in the yaml file. Does anyone encounter the problem ? A big thanks in advance !

[imrajdas]

Hi @glagny, you can set the imageRegistry here- https://github.com/litmuschaos/litmus-helm/blob/e1dc34ed03cc991281f7a7251f5d3478d34bdb94/charts/litmus/values.yaml#L27

helm install .... --set image.imageRegistryName="xyz.com/litmuchaos"

[glagny]

Hi @rajdas98 , thanks for your answer ! but I already specified the imageRegistryName(cf the description of the values.yaml that I use during the helm install on my first message). The problem is that the specified imageRegistryName is applied on the child pods (chaos-operator, event-tracker, subscriber, workflow-controller created during the first connection to the web UI), but not the imagePullSecrets and obviously I got an "unauthorized" error from my private registry

[glagny]

Hi @rajdas98 :) any news about the previous question ? Thanks in advance

[uditgaurav]

Hi @glagny , We can set the image registry from the UI that is from dashboard itself. This is available in 3.x. Feel free to try it out and let us know your feedback. Thanks!