A PersistentVolume is Kubernetes storage that lets Airflow mount shared DAG files independently of individual pod images. It hides the underlying storage technology, but teams must still arrange a way to push or pull DAG code onto the volume. section 17.2.7
Mounting DAGs from a local volume
Declare a ReadWriteMany PersistentVolume backed by the host's /data directory, bind it to a 250Mi PersistentVolumeClaim, and apply the manifest with kubectl. Configure the Airflow Helm chart with dags.persistence.enabled: true and existingClaim: local-path-dag-volume-claim, then deploy with helm upgrade.
This approach suits multiple teams sharing an Airflow environment, but its CI/CD design depends on the chosen volume type. Git synchronization is an alternative when DAGs should come from a repository instead. section 17.2.7






