Ability to provide imagePullSecret for internal Spilo images

[DARB-CCM-S-20]

Please, answer some short questions which should help us to understand your problem / question better?

• Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
• v1.8.2
• Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s]
• Bare Metal K8s
• Are you running Postgres Operator in production? [yes | no]
• no
• Type of issue? [Bug report, question, feature request, etc.]
• feature request

When override the default spilo docker_image parameter there is no option to provide any imagePullSecrets for fetching this image. As a result, if you try to pull from a private registry then the Postgres pods end up in ImagePullBackOff

[jurim76]

There is some hack to enable imagePullSecrets Define in postgresql-operator-default-configuration.yaml kubernetes: pod_service_account_definition: '{ "apiVersion": "v1", "kind": "ServiceAccount", "metadata": { "name": "postgres-pod" }, "imagePullSecrets": [ { "name": "secret" } ] }

[yevon]

I just did came across with this problem, this just prevents zalando operator from being used in private registries. Any news about this? I just assumed that it would use the image.imagePullSecrets for all docker images from the chart but it was not the case.

[starizard]

+1, Is there any way to set the imagePullSecret if we are using custom spilo images?