You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2019/11/19 02:59:01 UTC

[jira] [Issue Comment Deleted] (FLINK-9953) Active Kubernetes integration

     [ https://issues.apache.org/jira/browse/FLINK-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yang Wang updated FLINK-9953:
-----------------------------
    Comment: was deleted

(was: Hi [~felixzheng],
Do you have some time to help with the code review? This is last PRs based on others. Hope to get some feedback from you. https://github.com/apache/flink/pull/9986)

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