You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/18 16:35:00 UTC

[jira] [Commented] (AIRFLOW-3729) Support env variables with pod runtime information in KubernetesPodOperator

    [ https://issues.apache.org/jira/browse/AIRFLOW-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746458#comment-16746458 ] 

ASF GitHub Bot commented on AIRFLOW-3729:
-----------------------------------------

bbcbruno commented on pull request #4554: [AIRFLOW-3729] Support env variables with pod runtime information in KubernetesPodOperator
URL: https://github.com/apache/airflow/pull/4554
 
 
   ### Jira
   
   - [X] https://issues.apache.org/jira/browse/AIRFLOW-3729
   
   ### Description
   
   - [X] Here are some details about my PR, including screenshots of any UI changes:
   
   
   
   Support to export pod runtime information to env variables ([k8s docs](https://kubernetes.io/docs/tasks/inject-data-application/environment-variable-expose-pod-information/))
   
   Ex: namespace / pod name / pod ip / node name / etc
   
   
   ### 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


> Support env variables with pod runtime information in KubernetesPodOperator
> ---------------------------------------------------------------------------
>
>                 Key: AIRFLOW-3729
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3729
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: kubernetes
>            Reporter: Bruno Campos
>            Priority: Minor
>
> Support to export pod runtime information to env variables ([https://kubernetes.io/docs/tasks/inject-data-application/environment-variable-expose-pod-information/)]
> Ex: namespace / pod name / pod ip / node name / etc



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