mppetkov commented 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.
**- 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.
----------------------------------------------------------------
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
