Bitnami Airflow chart 19.0.3 (Airflow version 2.10) not creating pods with unique names #41885
Replies: 6 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.
-
still didn't figured out the issue or root cause |
Beta Was this translation helpful? Give feedback.
-
If you are using the Bitnami Helm Chart - are you sure this is the right issue tracker for the problem? Bitnami Helm CHart is not maintained by the Airflow repo. |
Beta Was this translation helpful? Give feedback.
-
@jscheffl - can you help to understand why airflow is not updating the pod metadata.name, its creating with the exact same name we use in the pod_template.yaml file. are we suppose to do anything in addition to get the unique pod names |
Beta Was this translation helpful? Give feedback.
-
I believe there is a lot of context missing. Which executor are you using? Is it about the POD names of Airflow or the workload? How is your DAG code looking like? How is your Kubernetes config looking like? And most prominent: If it was working before - which other parameters have you adjusted that so that it was working before? If you found a bug, then it is okay to post it. But this is not a research forum. |
Beta Was this translation helpful? Give feedback.
-
My apologies, i would have raised under Q&A. I am using the kubernetes executor. and its about POD names for the workloads DAG: sys.path.append(os.path.dirname(os.path.realpath(file))) #Utils now = datetime.now() default_args = { executor_config = test_akr_dag_utils.executor('test') dag = DAG(DAG_NAME, default_args=default_args,schedule_interval='@once') Executor yaml
|
Beta Was this translation helpful? Give feedback.
-
Apache Airflow version
2.10.0
If "Other Airflow 2 version" selected, which one?
No response
What happened?
Pods are not getting unique names. In the earlier version of the chart we used to get unique pod names. but after upgrading to the latest chart, its not generating random pod names, instead its trying to use the metadata.name value as the pod name and i am facing issue when try to create multiple pods
What you think should happen instead?
Pods should get unique names
How to reproduce
Upgrade to Bitnami chart version from 13.1.1 to 19.0.3
Operating System
Debian GNU/Linux 12
Versions of Apache Airflow Providers
2.10
Deployment
Official Apache Airflow Helm Chart
Deployment details
Helm deployment
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions