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.