[
https://issues.apache.org/jira/browse/FLINK-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956740#comment-16956740
]
Canbin Zheng commented on FLINK-9953:
-------------------------------------
Sorry for the late reply.
I agree with [~trohrmann] that we only support session execution mode and use
Deployment to manage worker pods in the first MVP, it considerably narrows the
scope of the initial commit and helps forward this feature quickly.
> at the moment I don't yet fully understand why we need to persist RM state.
I believe there are several reasons to persist the RM state for failures
handling and some edge exception cases, since it not necessary blocks the first
experimental release, we can leave this discussion after that.
[~fly_in_gis] thanks, looking forward to your work!
> 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)
