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 2020/01/08 11:02:00 UTC

[jira] [Commented] (FLINK-9953) Active Kubernetes integration

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

Yang Wang commented on FLINK-9953:
----------------------------------

Since all the tasks have finished, i will close this ticket as {{Fixed}}. All the advanced features, including per-job, will be put into [phase2|https://issues.apache.org/jira/browse/FLINK-14460]. Thanks for all the contribution to this feature.

> Active Kubernetes integration
> -----------------------------
>
>                 Key: FLINK-9953
>                 URL: https://issues.apache.org/jira/browse/FLINK-9953
>             Project: Flink
>          Issue Type: New Feature
>          Components: Deployment / Kubernetes, Runtime / Coordination
>            Reporter: Till Rohrmann
>            Assignee: Yang Wang
>            Priority: Major
>             Fix For: 1.10.0
>
>          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. Only session cluster is supported.
> Phrase2 is mainly focused on production optimization, including per-job cluster, k8s native high-availability, storage, network, log collector and etc.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)