[
https://issues.apache.org/jira/browse/AIRFLOW-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164214#comment-17164214
]
ASF GitHub Bot commented on AIRFLOW-3126:
-----------------------------------------
fengsi commented on pull request #8150:
URL: https://github.com/apache/airflow/pull/8150#issuecomment-663383722
Thanks for testing it, @xEviL!
The global `pod_template_file` setting will likely affect
`KubernetesPodOperator` too, and that's not a good thing – I'm using both
`KubernetesExecutor` and custom `KubernetesPodOperator`(s).
Logically, `KubernetesExecutor` is still more on Airflow side, but I don't
think it makes sense to have the same K8s settings globally applied to all
K8s-related _**operators**_, as they have nothing to do with executors
executing them, and in most cases they are totally independent.
----------------------------------------------------------------
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]
> kubernetes executor not allowing new PV
> ---------------------------------------
>
> Key: AIRFLOW-3126
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3126
> Project: Apache Airflow
> Issue Type: Bug
> Components: executors
> Affects Versions: 1.10.0
> Reporter: Rahul Singh
> Assignee: Brandon Willard
> Priority: Major
>
> Kubernetes executor allows only two PV one for dag and other for logs , in
> project scenario there are multiple PV needed , like separate PV to store
> data , PV to store common script files etc . Current implementation is very
> static to only two PV.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
