You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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/dags doesn't either show up in the dag section - or it isn't added to DagBag when using airflow 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!!
The text was updated successfully, but these errors were encountered:
I experienced the same issue and figured out what the problem is.
This code editor stores DAG files in airflow-webserver. Airflow helm charts for airflowVersion > 2.0, it deploys airflow-scheduler as a separate pod along side the airflow-webserver, and DAGs files should be stored inside the airflow-scheduler pod. https://github.com/apache/airflow/blob/cae96630e1ddc1d3aae867c41d137e1d1fd7d465/chart/templates/webserver/webserver-deployment.yaml#L271-L283
As long as webserver and schedulerr pods are not using a shared volume for DAGs files, this code editor will not work.
As a workaround, we can create a RWX volume and mount it on both webserver and scheduler pods, at dags file path.
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/dags
doesn'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!!
The text was updated successfully, but these errors were encountered: