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/10/18 02:31: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=16954206#comment-16954206 ] 

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

I have made an new complete implementation based on the [ML discussion|[http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Best-practice-to-run-flink-on-kubernetes-td31532.html]] and [Implementation doc|[https://docs.google.com/document/d/1-jNzqGF6NfZuwVaFICoFQ5HFFXzF5NVIagUZByFMfBY/edit?usp=sharing].] Some key changes are as follows.
 * Fabric8 flink kubernetes client implementation
 * Use deployment for flink master
 * Dynamically allocation for TaskManager pod
 * Support submission from cli by FlinkKubernetesCustomCli
 * Use configmap to save log4j and flink-conf.yaml
 * Support cluster id, nodeport and load banlancer
 * Support both perjob and session mode

 

As more and more users are interested in this feature and want to have a taste. I hope to take over this JIRA and push the integration faster. [~trohrmann], could be re-assign this ticket to me, including the 1-11 subtasks? I will create another umbrella JIRA for phase2 implementation. It is mainly focused on the production optimization, including k8s native high-availability, storage, network, log collector and etc.

> 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: Chunhui Shi
>            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.
>  
> Document can be found here: [https://docs.google.com/document/d/1Zmhui_29VASPcBOEqyMWnF3L6WEWZ4kedrCqya0WaAk/edit?usp=sharing] 



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