ashb opened a new pull request #4883: [AIRFLOW-4053] Fix KubePodOperator Xcom 
on Kube 1.13.0
URL: https://github.com/apache/airflow/pull/4883
 
 
   
   Make sure you have checked _all_ steps below.
   
   ### Jira
   https://issues.apache.org/jira/browse/AIRFLOW-4053
   
   ### Description
   
   Newer versions of Kube return "failed" events for the side car container
   when the ^C causes the python process to exit with 1
   
   Kube 1.13 runs a different number of kube-dns pods (2 by default, 1.9
   and 1.10 ran only 1) so the setup scripts needed changing a little bit.
   
   To get a Kube 1.13 cluster I had to upgrade minikube, and it no longer
   works on a dist without systemd installed (#systemdsucks) so I had to
   update the travis dist to xenial which is no bad thing!
   
   (This version of minikube doesn't need the localkube bootstrapper set
   anymore, it handles driver=none much more gracefully)
   
   
   ### Tests
   
   - [x] Existing tests good enough, and still pass
   
   ### 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
   
   - None
   
   ### Code Quality
   
   - [x] Passes `flake8`
   

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


With regards,
Apache Git Services

Reply via email to