[ 
https://issues.apache.org/jira/browse/FLINK-15656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640626#comment-17640626
 ] 

lekelei edited comment on FLINK-15656 at 11/29/22 11:18 AM:
------------------------------------------------------------

[~wangyang0918] 

Hello, I am using the function of pod-template, and I have a question: through 
the pod-template.YAML file provided in the reference document[Native Kubernetes 
| Apache 
Flink|https://nightlies.apache.org/flink/flink-docs-master/zh/docs/deployment/resource-providers/native_kubernetes/#pod-template],
 I can download the dependent jar files to the

/opt/flink/artifact directory through the init container, but what is the way 
for the Flink jobmanager to load these jar packages? Mounting directly to the 
Flink jobmanager lib directory via emptyDir will overwrite the original lib 
directory and is not a viable method. I hope you can help me with this if you 
have time, thank you very much!


was (Author: JIRAUSER297957):
[~wangyang0918] 

Hello, I am using the function of pod-template, and I have a question: through 
the pod-template.YAML file provided in the reference document[[Native 
Kubernetes | Apache 
Flink|https://nightlies.apache.org/flink/flink-docs-master/zh/docs/deployment/resource-providers/native_kubernetes/#pod-template]],
 I can download the dependent jar files to the

/opt/flink/artifact directory through the init container, but what is the way 
for the Flink jobmanager to load these jar packages? Mounting directly to the 
Flink jobmanager lib directory via emptyDir will overwrite the original lib 
directory and is not a viable method. I hope you can help me with this if you 
have time, thank you very much!

> Support user-specified pod templates
> ------------------------------------
>
>                 Key: FLINK-15656
>                 URL: https://issues.apache.org/jira/browse/FLINK-15656
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Deployment / Kubernetes
>            Reporter: Canbin Zheng
>            Assignee: Yang Wang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.13.0
>
>
> The current approach of introducing new configuration options for each aspect 
> of pod specification a user might wish is becoming unwieldy, we have to 
> maintain more and more Flink side Kubernetes configuration options and users 
> have to learn the gap between the declarative model used by Kubernetes and 
> the configuration model used by Flink. It's a great improvement to allow 
> users to specify pod templates as central places for all customization needs 
> for the jobmanager and taskmanager pods.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to