Description
Description
When configuring Airflow using a Helm chart, the core section allows you to set the plugins_folder. This setting is applied equally across all web servers and schedulers. Many users utilize git-sync, and it's common for the plugins' path to be located within a git-synced repository.
With Airflow version 2.0.0 and above, Dag Serialization is enabled by default, which means that the web server cannot use a git-sync sidecar. This is generally not an issue when developing custom operators, but it can cause confusion if you want to customize the web UI and the plugins folder on the web server is not synced through git-sync.
Therefore, it would be beneficial to guide the explicit setting of the plugins_folder in the Helm chart, allowing separate configurations for the web server and scheduler. This approach would enable more flexible management of each component's settings, allowing finer adjustments to meet specific requirements.
Use case/motivation
When attempting to customize the Airflow Web UI based on AirflowPlugin, I followed the guidance to write scripts in the plugins directory. However, with Airflow version 2.0.0 and above, there was confusion in using the webserver plugins because git-sync does not operate as a sidecar for the webserver.
As documented at Airflow's Helm Chart Guide, it is generally not recommended to use git-sync with persistence together. This recommendation has significantly limited the possible workarounds to address this issue.
Related issues
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct