postgres initContainer failed to pull image

[sh4mu]

Hi all,

I'm using the postgres chart and defining the initContainer. The associated image requires a secret, that is present on the namespace.
I believe I'm doing everything as expected, but I'm not able to pull the initContainers image.
Unsure I'm doing something wrong, or there is an error on the helm chart definitions. Can you help?

Here is the relevant values.yaml part

postgres:
  global:
    imagePullSecrets:
      - name: my-registry-creds
   initContainers:
    - name: copy-sql-scripts
       image: registry.local/feature-handling-datamodel:dev-latest
       imagePullPolicy: Always
       command: ["/bin/sh", "-c"]
       args:
         - cp -r /flyway/sql/admin/* /docker-entrypoint-initdb.d/
       volumeMounts:
         - name: initdb-scripts
           mountPath: /docker-entrypoint-initdb.d

We were using the bitnami legacy chart and it worked with the exact same config. It appears the cloudpirates helm is configured in the same way. However, the pod is unable to fetch the image

 kubelet                  Failed to pull image "registry.local/feature-handling-datamodel:dev-latest": failed to pull and unpack image "registry.local/feature-handling-datamodel:dev-latest": failed to resolve reference "registry..local/feature-handling-datamodel:dev-latest": unexpected status from HEAD request to https://registry.local/v2/feature-handling-datamodel/manifests/dev-latest: 500 Internal Server

[zOnlyKroks]

I sadly cannot replicate this issue. The postgres chart correctly applies global.imagePullSecrets to all initContainers, which I verified by deploying to your kind cluster. The most likely cause is your values structure. If using the chart directly, you should have global: at the root level, not nested under postgres:. Alternatively, your my-registry-creds secret may not exist in the namespace or the "500 Internal Server" error indicates your registry itself is having issues.

[sh4mu]

Hi @zOnlyKroks , thanks for the feedback. Indeed there is no issue, it was a misconfiguration from my side.