[
https://issues.apache.org/jira/browse/AIRFLOW-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163390#comment-17163390
]
ASF GitHub Bot commented on AIRFLOW-3126:
-----------------------------------------
xEviL commented on pull request #8150:
URL: https://github.com/apache/airflow/pull/8150#issuecomment-662916215
@mik-laj I think what you are proposing is a good direction, however
`pod_template_file` at the moment lacks (any) documentation (with regards to
use with `KubernetesExecutor`), this is why people start adding things that are
missing.
I now need to do both what is proposed in this PR (mount an extra volume),
but also mount a `configMap` and a `secret` as a file.
Perhaps if there are examples for these in the doc: on how to use
`pod_template_file` for worker config with `KubernetesExecutor` - then the
feature will be used more and PRs like this will go away.
I'm still looking for how to do this - would appreciate any pointers.
----------------------------------------------------------------
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)
