GitHub user miloaissatu created a discussion: GitSync and Persistence behaviour conflicts with docs
### Official Helm Chart version 1.18.0 (latest released) ### Apache Airflow version 3.1.6 ### Kubernetes Version 1.33.5 ### Helm Chart configuration Documentation here suggests that gitsync and persistence can be used together. https://airflow.apache.org/docs/helm-chart/1.18.0/manage-dag-files.html#mounting-dags-using-git-sync-sidecar-with-persistence-enabled. This is not what the helm chart does. Is the documentation wrong? Or is the helm chart wrong? Is there a configuration combination where I can have either the scheduler or the dag processor run the periodic gitsyncs, and everything else mount the RWX dags volume? ### Docker Image customizations _No response_ ### What happened Across all deployments, the combination of `executor=KubernetesExecutor`, `dags.persistence.enabled=true` and `dags.gitSync.enabled=true` means none of them run the gitsync sidecar. ### What you think should happen instead `dags.persistence.enabled=true` and `dags.gitSync.enabled=true` should run gitsync sidecar on scheduler (should this be dagprocessor on airflow 2/3?) deployment. Other deployments should mount persistentvolume containing dags. ### How to reproduce Set `executor=KubernetesExecutor`, `dags.persistence.enabled=true` and `dags.gitSync.enabled=true` in values. There will be no deployments with gitsync sidecar. ### Anything else _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) GitHub link: https://github.com/apache/airflow/discussions/60617 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
