tpanza opened a new issue, #59263:
URL: https://github.com/apache/airflow/issues/59263
### Official Helm Chart version
1.18.0 (latest released)
### Apache Airflow version
3.0.2
### Kubernetes Version
1.31
### Helm Chart configuration
```yaml
# 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
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
