[
https://issues.apache.org/jira/browse/FLINK-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954560#comment-16954560
]
Yang Wang commented on FLINK-9953:
----------------------------------
Hi [~felixzheng],Thanks for your comments. And welcome to join.
I have gone through your design doc and find that the key difference is the
per-job cluster. I think in the per-job cluster in flink means it is dedicated
cluster for only one job and will not accept more other jobs. The users could
put their jars in the image. And the `ClassPathJobGraphRetriever` will be used
to generate and retrieve the job graph in flink master pod. So i suggest to add
kubernetes-job.sh to start per-job cluster. It will not need a user jar as
required argument. `flink run` could be used to submitted a flink job to
existed session.
> Active Kubernetes integration
> -----------------------------
>
> Key: FLINK-9953
> URL: https://issues.apache.org/jira/browse/FLINK-9953
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Coordination
> Reporter: Till Rohrmann
> Assignee: Yang Wang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This is the umbrella issue tracking Flink's active Kubernetes integration.
> Active means in this context that the {{ResourceManager}} can talk to
> Kubernetes to launch new pods similar to Flink's Yarn and Mesos integration.
> Phase1 implementation will have complete functions to make flink running on
> kubernetes. Phrase1 is mainly focused on production optimization, including
> k8s native high-availability, storage, network, log collector and etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
