[
https://issues.apache.org/jira/browse/AIRFLOW-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161220#comment-17161220
]
ASF GitHub Bot commented on AIRFLOW-3126:
-----------------------------------------
mik-laj commented on pull request #8150:
URL: https://github.com/apache/airflow/pull/8150#issuecomment-661028873
@cccs-pg I'm not a Kubernetes expert, but can't this option be configured
with `pod_template_file` option in `kubernetes` section?
https://github.com/apache/airflow/blob/37fa2063f2bfe712c6e64941edfe2a6618127130/airflow/config_templates/config.yml#L1750
It seems to me that we have a similar problem as in this change.
https://github.com/apache/airflow/pull/7365#issuecomment-660980484
Could you please give us more context? Why did you decide to implement a new
option when you can use the existing one?
----------------------------------------------------------------
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)
