[
https://issues.apache.org/jira/browse/AIRFLOW-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164595#comment-17164595
]
ASF GitHub Bot commented on AIRFLOW-3126:
-----------------------------------------
mik-laj commented on pull request #8150:
URL: https://github.com/apache/airflow/pull/8150#issuecomment-663685993
@xEviL I confirm that pod_template_file option does not affect
kubernetesPodOperaator. It's only for KubernetesExecutor.. pod_mutation_hook
is global and is used by both the operator and the executor.
Wouldn't you like to write some documentation that explains how you set up
Kubernetes executor? I know our documentation for an executor is incomplete,
but even writing one section is a step forward. I will try to motivate other
people to complete documentation for other sections.
> Is it a fixed/hard-coded manifest file? If so, I'd think its use cases are
very limited.
@fengsi In most cases, a static configuration is sufficient. If you want
more dynamic configuration, you can extend this with [the pod mutation
hook](https://airflow.readthedocs.io/en/latest/kubernetes.html#pod-mutation-hook)
or
[executor_config](https://github.com/apache/airflow/blob/master/airflow/example_dags/example_kubernetes_executor_config.py).
If you want to base your logic based on task attributes, you can modify
executor_config with [the cluster
policy](https://airflow.readthedocs.io/en/latest/concepts.html#cluster-policy).
Of course we can think about improving this, but I think we need to focus on
adding extra volumes 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)
