[
https://issues.apache.org/jira/browse/FLINK-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954723#comment-16954723
]
Till Rohrmann commented on FLINK-9953:
--------------------------------------
Hi [~felixzheng], thanks for sharing your design document with us. It looks
very detailed :-) I just skimmed over it briefly and I think you are right
about the slight differences. In particular the worker pod lifecycle management
and state storage is more detailed and I wasn't aware that we need to persist
HA state. [~fly_in_gis] correct me if I'm wrong about it because I don't know
the actual state of the implementation.
I think it would be awesome if we could join forces on implementing the active
K8s integration for Flink. Not exactly sure how to best organize the remaining
work because [~fly_in_gis] has written already some code. Maybe you guys could
share the current state of the work and see which points are diverging and what
still needs to be done. Happy to help with reviewing the 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. 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)
