[
https://issues.apache.org/jira/browse/AIRFLOW-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149699#comment-17149699
]
ASF GitHub Bot commented on AIRFLOW-6062:
-----------------------------------------
hcheng4 commented on pull request #8546:
URL: https://github.com/apache/airflow/pull/8546#issuecomment-652648926
[Not a contribution]
@dimberman a multi-namespace mode sounds like a great idea. Is there a
discussion already ongoing? If there's agreement design-wise, I can see if
there's appetite and bandwidth here for a patch contribution.
It may be the case that longer-term the restrictions of an in-namespace
Kubernetes deployment are too much and it's undesirable to support that going
forward, but that doesn't feel like the type of compatibility-breaking change
that's appropriate for a patch release IMHO.
----------------------------------------------------------------
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:
us...@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
> Fix For: 1.10.10
>
>
> 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)
