[jira] [Commented] (AIRFLOW-6062) Scheduler doesn't delete worker pods from namespaces different than the scheduler's namespace

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

dimberman commented on pull request #7123: [AIRFLOW-6062] Executor would only delete workers in its own namespace
URL: https://github.com/apache/airflow/pull/7123
 
 
   ---
   Issue link: WILL BE INSERTED BY [boring-cyborg](https://github.com/kaxil/boring-cyborg)
   The KubernetesExecutor was only able to delete worker pods in its own namespace. This PR will match delete commands to the namespace of the pod.
    
   - [ ] Description above provides context of the change
   - [ ] Commit message/PR title starts with `[AIRFLOW-NNNN]`. AIRFLOW-NNNN = JIRA ID<sup>*</sup>
   - [ ] Unit tests coverage for changes (not needed for documentation changes)
   - [ ] Commits follow "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)"
   - [ ] Relevant documentation is updated including usage instructions.
   - [ ] I will engage committers as explained in [Contribution Workflow Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example).
   
   <sup>*</sup> For document-only changes commit message can start with `[AIRFLOW-XXXX]`.
   
   ---
   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).
   Read the [Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines) for more information.
   
 
----------------------------------------------------------------
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:
users@infra.apache.org


> Scheduler doesn't delete worker pods from namespaces different than the scheduler's namespace
> ---------------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-6062
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6062
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: executor-kubernetes
>    Affects Versions: 1.10.5
>            Reporter: Mihail Petkov
>            Assignee: Daniel Imberman
>            Priority: Blocker
>
> When you run Airflow's task instances as worker pods in different namespaces into a Kubernetes cluster, the scheduler can delete only the pods that are living in the same namespace where the scheduler lives. It's trying to delete all pods that are in the namespace defined in the airflow.cfg file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)