jacobhjkim opened a new issue #9528:
URL: https://github.com/apache/airflow/issues/9528


   <!--
   
   Welcome to Apache Airflow!  For a smooth issue process, try to answer the 
following questions.
   Don't worry if they're not all applicable; just try to include what you can 
:-)
   
   If you need to include code snippets or logs, please put them in fenced code
   blocks.  If they're super-long, please use the details tag like
   <details><summary>super-long log</summary> lots of stuff </details>
   
   Please delete these comment blocks before submitting the issue.
   
   -->
   
   **Description**
   
   Use [git-sync](https://github.com/kubernetes/git-sync) to update Airflow 
DAGs when using the official [Airflow Helm 
Chart](https://github.com/apache/airflow/tree/master/chart).
   
   **Use case / motivation**
   
   <!-- What do you want to happen?
   
   Rather than telling us how you might implement this solution, try to take a
   step back and describe what you are trying to achieve.
   
   -->
   
   Currently, if you use the official [Airflow Helm 
Chart](https://github.com/apache/airflow/tree/master/chart) the only way to 
update DAGs is to build a new Airflow image. Building a new Airflow Image and 
deploying every time when there is a change in DAG seems like overkill. So I 
propose updating DAGs by using 
[git-sync](https://github.com/kubernetes/git-sync)
   >git-sync is a simple command that pulls a git repository into a local 
directory. It is a perfect "sidecar" container in Kubernetes - it can 
periodically pull files down from a repository so that an application can 
consume them.
   
   


----------------------------------------------------------------
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]


Reply via email to