Request new Helm chart release (1.19.0?) to include recent improvements from main

[tpanza]

Official Helm Chart version

1.18.0 (latest released)

Apache Airflow version

3.0.2

Kubernetes Version

1.31

Helm Chart configuration

# List of existing Kubernetes secrets containing Base64 encoded credentials to connect to private
# registries. Items can be either strings or {name: secret} objects.
imagePullSecrets:
  - artifactory-pull-secret

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 imagePullSecrets list.

How to reproduce

Simply require images that are in a private registry or behind a proxy requiring auth. Then attempt to use imagePullSecrets in your values.yaml

Anything 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.yaml on main reference newer support for imagePullSecrets, 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?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg[bot]]

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.

[potiuk]

Releasing next chart and how release it is held on devlist

[tpanza]

Any updates to this? Will we get a new release sometime soon? There has not been a release for ~6 months

[potiuk]

We have just discussed releases of Helm Chart among the release managment team and we are aiming to introduce regular cadence of releases:

https://cwiki.apache.org/confluence/display/AIRFLOW/Release+Plan

Note that this is what is the intention, not committment, and it very much depends on time that volunteers can spend so that users like you can get the software for absolutely free. So a good idea is also to give back to the community for the free software you get from it. So - since you have some expectations to us, I will have an expectation to you - please subscribe to the devlist, and patiently wait when new helm chart release candidate is released. When we do it, we ask the users to test if the release candidate is good for them, has no issues, and whether it works as expected. Usually the voting period for release candidate is at least 72 hrs and we expect people like you (who are eager to get it) to report their test status.

It would be surprising to not see you among the people testing it @tpanza

[tpanza]

Thanks @potiuk . I have subscribed to the devlist. Also, some brief context on my usage: I am running Airflow inside a highly regulated corporate environment on a private k8s cluster. The official Helm repository/index is an approved "external software source" that is proxied in, via Artifactory. The GitHub repo, currently, is not. I have requests pending to change that. Assuming that is approved, and as long as the release candidate is available on a branch in this repo, then I should be able to help with testing.

[potiuk]

Cool . The plan is to release voting candidate this week.

BTW. You can also just copy the chart from main and host it anywhere locally - or even copy the whole of it to local folder - and install it from there. The chart is not really (unlike whel package) - somewhat pre-processed package - it's literally a bunch of template files put together and when you install chart you basically point to the folder that contains them.

[tpanza]

@potiuk #61371