mik-laj opened a new issue #14728: URL: https://github.com/apache/airflow/issues/14728
Hello, A lot of production Apache Airflow environments deployed on a cloud platform - AWS, Google uses object storage for storing DAG files. This is due to the popularity of Cloud Composer or Amazon Managed Workflows for Apache Airflow (MWAA) services that have adopted this deployment model. For some users, these services didn't their expectations (e.g. due to a version shift) and are planning to migrate to Helm Chart. I think we should help with these migrations and prepare a solution that will allow the use of Helm Chart together with object storages. I think adding two examples to the documentation describing how to use a side-car would be enough, but I am open to discussing another idea to support these syncrhonziations. The current documentation describes only the following [DAG file management methods](http://apache-airflow-docs.s3-website.eu-central-1.amazonaws.com/docs/helm-chart/latest/manage-dags-files.html): - Bake DAGs in Docker image - Mounting DAGs using Git-Sync sidecar with Persistence enabled - Mounting DAGs using Git-Sync sidecar without Persistence - Mounting DAGs from an externally populated PVC Best regards. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
