[
https://issues.apache.org/jira/browse/AIRFLOW-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164000#comment-17164000
]
ASF GitHub Bot commented on AIRFLOW-3126:
-----------------------------------------
brandonwillard commented on pull request #8150:
URL: https://github.com/apache/airflow/pull/8150#issuecomment-663259152
@mik-laj, sorry for the late response, but I don't really have much to add
beyond what @fengsi and @xEviL have already said.
It took far too much context-specific setup, effort, and time just to answer
some basic questions regarding the `pod_template_file` feature and I can't see
myself doing that again—especially not for documentation/example
purposes. That documentation and examples work needs to be done by the
original developers (or whoever knows this feature best) if it's going to get
done soon and accurately.
Plus, my guess is that this templating approach will ultimately lead to the
need for more robust templating features (e.g. such as those offered by Jinja
and the like), and some important questions and goals surrounding that should
be addressed first.
----------------------------------------------------------------
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)
