Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Specify an image pull secret

See original GitHub issue

Description

Add a parameter images.airflow.imagePullSecrets to support this secret for fetching airflow images.

Use case/motivation

When deploying custom images (e.g. the extended images with DAGs embedded or dependencies installed) they are often pushed somewhere like a private Gitlab repository. To successfully pull them after, secrets would need to be specified similar to this.

Related issues

Don’t believe any other issue pertains, but may have missed something.

Are you willing to submit a PR?

Yes I am willing to submit a PR!

Code of Conduct

I agree to follow this project’s Code of Conduct

Issue Analytics

State:
Created a year ago
Comments:8 (6 by maintainers)

Top GitHub Comments

1reaction

DSamuylovcommented, Jun 11, 2022

@onemec could you elaborate on how did you fix it? I am actually looking for a solution for the exactly the same use case that you describe in this issue.

1reaction

onemeccommented, Jun 7, 2022

It seems that this actually uses the following:

{{- end }}
{{- if or .Values.registry.secretName .Values.registry.connection }}
imagePullSecrets:
  - name: {{ template "registry_secret" . }}

Providing further documentation or the ability to specify this within the values.yaml file for Helm parameters would help simplify using this feature.