-
Notifications
You must be signed in to change notification settings - Fork 9k
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
Airflow Chart - Service token file does not exist #23895
Comments
add scheduler.automountServiceAccountToken : true |
I'm still encountering the same issue even after setting scheduler.automountServiceAccountToken: true. I also tried configuring the serviceAccount with create: false and name: "default", but I'm facing the same error. I'm using Oracle Kubernetes Engine (OKE) for this setup. Any insights or suggestions would be greatly appreciated. |
Have face same issue from an upgrade from 16.1.7 to 16.8.3, but with 16.2.1 not having this issue. |
Please, try with This was probably caused by #22382, a PR addressing security improvements for the chart. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
working! Thank's it was necessary to put it on the web and in the scheduler too |
Name and Version
bitnami/airflow/16.3.0
What architecture are you using?
None
What steps will reproduce the bug?
requiriments.txt
authlib
discord-webhook
kubernetes>=21.7.0,<24
apache-airflow-providers-apache-spark
pytz
Are you using any custom parameters or values?
What do you see instead?
Additional information
Starting from version 16.3.0, when using the "CeleryKubernetesExecutor" executor, there began to be issues with the pod scheduler. This problem does not occur in version 16.2.1.
The text was updated successfully, but these errors were encountered: