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

Canbin Zheng commented on FLINK-9953:
-------------------------------------

[~trohrmann] Thanks very much for taking time to read my design doc.

I think this is something really great to have. We plan to run Flink on 
Kubernetes natively in production shortly, our clusters could be massive and 
may rapidly scale up on size or number of the cluster.

Since this is a significant feature, and the maintenance and enhancement work 
in the future could be much larger than the initial commit. I have some 
suggestions to forward this feature.
 # We can further discuss the design proposals to reach a general consensus, 
especially on resource resolution, managed pods lifecycle management, worker 
store, garbage collection and user-oriented interfaces(shell scripts), after 
that we merge the current design docs into a final one, maybe we need a new 
FLIP too.
 # Take some time to list the small features we want to have and make more 
small plans on proceeding the implementations incrementally in phases, it’s 
better to keep the initial commit as small as possible to ease the code 
reviewing and help the initial version merged into Flink release more quickly, 
then we start to iteratively improve it according to the plans made and the 
feedbacks from users.

> 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)

Reply via email to