Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

imagePullSecret structure doesn't match in deployments vs service accounts #154

Open
renehernandez opened this issue Dec 15, 2023 · 2 comments

Comments

@renehernandez
Copy link

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 }}
@renehernandez
Copy link
Author

I can open a PR with a fix if there is interest

@hagaibarel
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants