-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Update to airflow 2.8.1 with kubernetes provider 7.13.0 broke scheduler #37008
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. |
@jmaicher Thanks for sharing the detailed information. This is a bug. This will trigger Kubernetes version upgrade. |
FYI @hussein-awala / @potiuk |
thanks @dirrao . It's not as "super" high priority as I understand, simply bumping mi vesion fr the k8s client from #36684 solves it - correct @jmaicher ? Do I understand it correctly ? If so we can just make sure we get the #36684 merged quickly and possibly release an ad-hoc new k8s provider - cc: @eladkal @raphaelauv ? |
This fix #37040 is most likely available in the next cncf kubernetes provider release. |
The kubernetes version bump (#37040) has been released with apache-airflow-providers-cncf-kubernetes:8.0.0 and is included in airflow:2.8.2. Thanks for the support, this issue can be closed. |
Thanks for the information |
Apache Airflow Provider(s)
cncf-kubernetes
Versions of Apache Airflow Providers
apache-airflow-providers-cncf-kubernetes==7.13.0
kubernetes==23.6.0
Apache Airflow version
2.8.1
Operating System
debian 12 (bookworm)
Deployment
Official Apache Airflow Helm Chart
Deployment details
Official helm chart with official airflow image (2.8.1)
What happened
When upgrading from 2.8.0 to 2.8.1 the airflow scheduler ended in a CrashLoopBackOff with:
What you think should happen instead
No response
How to reproduce
Deployment on a kubernetes cluster with a sub-resource that is named following the a/b/c naming scheme.
Anything else
The problem was likely introduced with b9c574c and the bug has been already fixed in the python kubernetes client, see kubernetes-client/python#2091. An upgrade of the kubernetes client is already planned (#36678), but we wanted to make this issue visible as it likely breaks other deployments as well.
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: