[
https://issues.apache.org/jira/browse/AIRFLOW-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150129#comment-17150129
]
ASF GitHub Bot commented on AIRFLOW-6062:
-----------------------------------------
mppetkov edited a comment on pull request #8546:
URL: https://github.com/apache/airflow/pull/8546#issuecomment-652901414
One more vote for the generic multi-namespace approach, it would be amazing
if we have functionality like that. Actually, that's why I have contributed the
fix. In my company we need to run each worker Pod into a specific namespace
based on a condition.
From what I understand, Airflow needs to provide the following options in
the **airflow.cfg** to make this approach generic.
**- default_namespace: 'namespace1'**
Airflow will create each worker Pod in this specific namespace unless the
value is not overwritten.
**- allowed_namespaces: ['\*']**
Airflow can create a worker Pod in all namespaces (probably the whitelist
property should have * as a value)
**- allowed_namespaces: ['namespace1', 'namespace2', 'namespace3']**
Airflow can create a worker Pod in any namespace that is part of the
**allowed_namespaces** property.
**- denied_namespaces: ['namespace1', 'namespace2', 'namespace3']**
Airflow cannot create a worker Pod in any namespace that is part of the
**denied_namespaces** property.
What do you think about this approach?
----------------------------------------------------------------
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)
