[
https://issues.apache.org/jira/browse/FLINK-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Wang closed FLINK-9953.
----------------------------
Release Note:
Support natively running Flink on Kubernetes
* Active resource management. Flink KubernetesResourceManager will allocate
TaskManager pods dynamically based on the resource requirement of the jobs.
* Using Flink bundled scripts to start/stop session cluster on Kuberenetes. Do
not need external tools anymore.
* Compared with Yarn deployment, different Flink cluster could get better
isolation by leveraging the ability of Kubernetes.
Resolution: Fixed
> 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)
