[
https://issues.apache.org/jira/browse/FLINK-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957763#comment-16957763
]
Zili Chen commented on FLINK-9953:
----------------------------------
Great to see we make progress on active k8s integration. It makes sense to me
we start in k8s session cluster support.
For semantic of per-job cluster, after an offline discussion with [~felixzheng]
we agreed on short-comings on current per-job mode including requiring
pre-generated JobGraph or extract JobGraph from jar lack of supporting
multi-part job. We have a driver-mode-like solution for per-job cluster, which
can be implemented individually, which means we don't have to break current
per-job mode, and fits well in FLIP-73 abstraction.
I am going to start a dedicated thread for such per-job cluster discussion
later.
> 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. Phrase2 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)
