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

Yang Wang commented on FLINK-15641:
-----------------------------------

The "local://" schema makes sense to me, which means located in the jobmanager 
locally. It could be both supported for K8s and YARN. 
 * For k8s deployment, these local jars could be baked in the image or 
downloaded by init-container.
 * For YARN deployment, these should be prepared beforehand. If the uses 
specify as "file://" schema, then these jars will be shipped via YARN 
distributed cache.

Maybe we could use the following command to submit an application cluster(i.e. 
per-job cluster mode). 
{code:java}
./bin/flink run-application -e kubernetes-application \
-Dkubernetes.cluster-id=flink-native-k8s-app-1 \
local:///opt/flink/examples/streaming/WindowJoin.jar

./bin/flink run-application -e kubernetes-application \
-Dkubernetes.cluster-id=flink-native-k8s-app-1 \
hdfs://myhdfs/flink/artifacts/WindowJoin.jar

./bin/flink run-application -e yarn-application \
file:///opt/flink/examples/streaming/WindowJoin.jar{code}
[~felixzheng] I will spin off the init-container from the current umbrella and 
add more subtasks if needed. 

> Support to start init container
> -------------------------------
>
>                 Key: FLINK-15641
>                 URL: https://issues.apache.org/jira/browse/FLINK-15641
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Deployment / Kubernetes
>            Reporter: Yang Wang
>            Priority: Major
>
> >> Why do we need init container?
> The init container could be used to prepare the use jars and dependencies. 
> Then we could always set the user image to Flink official image both for 
> standalone per-job on K8s or native K8s per-job. When the JobManager and 
> TaskManager container launched, the user jars will already exist there. I 
> think many users are running standalone per-job cluster in production by 
> using this way.
> The init container only works for K8s cluster.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to