[GitHub] kppullin opened a new pull request #4307: [AIRFLOW-3501] k8s executor - Support loading dags from image.

[GitBox <gi...@apache.org>]

kppullin opened a new pull request #4307: [AIRFLOW-3501] k8s executor - Support loading dags from image.
URL: https://github.com/apache/incubator-airflow/pull/4307
 
 
   ### Jira
   
   - [X] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-3501\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-3501
     - In case you are fixing a typo in the documentation you can prepend your commit with \[AIRFLOW-3501\], code changes always need a Jira issue.
   
   ### Description
   
   - [X] Here are some details about my PR, including screenshots of any UI changes:
   
   This PR adds a new config property named `use_container_dags` to the `kubernetes` configuration section.
   
   When this property is set to `True`, airflow will uses the dags packaged into the running docker container instead of loading them from a kubernetes volume mount or from a git init container.
   
   Prior to this change airflow forced loading dags either from a volume claim or an init container.
   
   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.
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   ### Commits
   
   - [X] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [X] In case of new functionality, my PR adds documentation that describes how to use it.
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.
     - All the public functions and the classes in the PR contain docstrings that explain what it does
   
   ### Code Quality
   
   - [X] Passes `flake8`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services