kaxil opened a new pull request #15492:
URL: https://github.com/apache/airflow/pull/15492


   When using `pod_template_file` or `full_pod_spec`, Pod identifying labels
   were not applied to the POD which meant `reattach_on_restart` did not
   work for them.
   
   ```python
   {
        "dag_id": "dag",
        "kubernetes_pod_operator": "True",
        "task_id": "task",
        "try_number": "1",
        "airflow_version": 2.0.2,
        "execution_date": "2016-01-01T0100000100",
   }
   ```
   
   This commit fixes that and makes the labels consistent whether users
   use `pod_template_file`, `full_pod_spec` or just pass params to
   KubernetesPodOperator.
   
   closes https://github.com/apache/airflow/issues/13918
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
   


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