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
Currently the imagePullSecret values are handle different between ServiceAccount and Deployment resources. This, in turn, prevents us from properly configuring secrets to pull from private registries.
deployment config:
{{- if not (empty .Values.image.pullSecrets) }}
imagePullSecrets:
{{ toYaml .Values.image.pullSecrets | indent 8 }}
{{- end }}
service account config:
{{- if .Values.autoscaler.image.pullSecrets }}
imagePullSecrets:
{{- range .Values.autoscaler.image.pullSecrets }}
- name: {{ . }}
{{- end }}
{{- end }}
The text was updated successfully, but these errors were encountered:
I think you're right and there shouldn't be a difference in the structure. Just note that we actually have two places where we configure this, for coredns itself and in the autoscaler configurations (the deployment and service account for each).
Would be happy to review if you're willing to create PR for this.
Currently the
imagePullSecret
values are handle different betweenServiceAccount
andDeployment
resources. This, in turn, prevents us from properly configuring secrets to pull from private registries.deployment config:
service account config:
The text was updated successfully, but these errors were encountered: