Replies: 2 comments
-
|
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Releasing next chart and how release it is held on devlist |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Official Helm Chart version
1.18.0 (latest released)
Apache Airflow version
3.0.2
Kubernetes Version
1.31
Helm Chart configuration
Docker Image customizations
None
What happened
All Pods stuck in image pull backoffs.
What you think should happen instead
1.18.0 version of the chart differs from main, and does not use the documented
imagePullSecretslist.How to reproduce
Simply require images that are in a private registry or behind a proxy requiring auth. Then attempt to use
imagePullSecretsin yourvalues.yamlAnything else
Hi maintainers,
I recently deployed Airflow using the official Helm chart 1.18.0 in an on-prem Kubernetes environment where private registry authentication is required. While troubleshooting image pull failures, I noticed that the documentation and
values.yamlon main reference newer support forimagePullSecrets, but those changes are not included in the 1.18.0 release.The result was some confusion and time spent debugging because templates on main reflect functionality that is not actually available in the last tagged version.
Would it be possible to cut a new Helm chart release (e.g., 1.19.0) including the recent improvements from main, particularly around handling
imagePullSecrets?Thanks very much for the great work on this chart!
Are you willing to submit PR?
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions