Not working with latest Airflow Helm Chart #84
Replies: 3 comments
-
|
Sry that I labeled my question as a bug - I didn't know how else to get in contact with you. |
Beta Was this translation helpful? Give feedback.
-
|
I experienced the same issue and figured out what the problem is. As a workaround, we can create a RWX volume and mount it on both webserver and scheduler pods, at dags file path. |
Beta Was this translation helpful? Give feedback.
-
|
Here is my custom values with verion 1.13.1 chart. dags:
persistence:
enabled: true
size: 1Gi
storageClassName: azurefile-csi
accessMode: ReadWriteMany
webserver:
extraVolumes:
- name: dags
persistentVolumeClaim:
claimName: airflow-staging-dags
extraVolumeMounts:
- name: dags
mountPath: /opt/airflow/dagsYou'll need to change the claimName based on your helm release name. My helm release name is airflow-staging. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
First of all: thank you for this great idea and work!!! Unfortunately, I couldn't manage to use it when deployed to an AKS via the latest airflow helm chart, using airflow version 2.8.3: any dag-py file (that I create with this plugin) and store under
/opt/airflow/dagsdoesn't either show up in the dag section - or it isn't added to DagBag when usingairflow dags reserialize. The logs don't reveal much more information.Is it possible that the plugin can't be used in the aks context?
Thanks for your help!!
Beta Was this translation helpful? Give feedback.
All reactions