[jira] [Resolved] (AIRFLOW-3501) Add config option to load dags in an image with the kubernetes executor.

["Aizhamal Nurmamat kyzy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AIRFLOW-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aizhamal Nurmamat kyzy resolved AIRFLOW-3501.
---------------------------------------------
    Resolution: Done

Resolving. Will relocate to components afterwards.

> Add config option to load dags in an image with the kubernetes executor.
> ------------------------------------------------------------------------
>
>                 Key: AIRFLOW-3501
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3501
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: kubernetes
>            Reporter: Kevin Pullin
>            Assignee: Kevin Pullin
>            Priority: Major
>
> Currently the airflow kubernetes executor forces loading dags either from a volume claim or an init container.  There should be an option to bypass these settings and instead use dags packaged into the running image.
> The motivation for this change is to allow for an airflow image to be built and released via a CI/CD pipeline upon a new commit to a dag repository.  For example, given a new git commit to a dag repo, a CI/CD server can build an airflow docker image, run tests against the current dags, and finally push the entire bundle as a single, complete, well-known unit to kubernetes.
> There's no need to worry that a git init container will fail, having to have a separate pipeline to update dags on a shared volume, etc.  And if issues arise from an update, the configuration can be easily rolled back to the prior version of the image.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)