[
https://issues.apache.org/jira/browse/AIRFLOW-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163979#comment-17163979
]
ASF GitHub Bot commented on AIRFLOW-3126:
-----------------------------------------
fengsi commented on pull request #8150:
URL: https://github.com/apache/airflow/pull/8150#issuecomment-663245578
> In my opinion, our mistake was to add a large number of configuration
options to Airflow. This makes it very difficult to maintain. I am trying to
change the approach and recommend using the `pod_template_file` option. I know
that changing habits can be problematic for many users and there were even
command that would facilitate migrations, but it is not finished yet.
I agree that there are too many options. Some of them are conflicting and
there is also messy logic validating (but still not complete) them.
There are several issues with the `pod_template_file`, though:
1. NO documentation at all, not even a simple example.
2. Is it a fixed/hard-coded manifest file? If so, I'd think its use cases
are very limited.
----------------------------------------------------------------
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)
