[
https://issues.apache.org/jira/browse/AIRFLOW-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164390#comment-17164390
]
ASF GitHub Bot commented on AIRFLOW-3126:
-----------------------------------------
xEviL commented on pull request #8150:
URL: https://github.com/apache/airflow/pull/8150#issuecomment-663499869
> I'm gonna test if global pod_template_file setting would ruin
KubernetesPodOperator or not. Hopefully not
`KubernetesPodOperator` should not be affected by Airflow configuration,
have a look at:
https://github.com/apache/airflow/blob/master/airflow/providers/cncf/kubernetes/operators/kubernetes_pod.py#L365
and
https://github.com/apache/airflow/blob/458d7d4cb0ffb2a525f85e5c06de2852186507c8/airflow/kubernetes/pod_generator.py#L190
Airflow `settings` are not imported anywhere, so only constructor arguments
are relevant (for the operator).
In our test setup we also ran `KubernetesPodOperator` which we already use
since a few months, but now also from `KubernetesExecutor` - it works!
----------------------------------------------------------------
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)
