[
https://issues.apache.org/jira/browse/FLINK-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956176#comment-16956176
]
Kostas Kloudas commented on FLINK-9953:
---------------------------------------
Hi [~fly_in_gis], unfortunately, as [~trohrmann] said, the {{CliFrontend}} is a
bit of a moving target as part of the FLIP-73, but we are *not* touching the
{{ClusterDescriptor}} and {{ClusterSpecification}} interfaces.
Now for the Per Job execution mode, we have discussed with [~tison] in the past
in the threads about FLIP-74, FLIP-73 and the general thread, "[DISCUSS] Flink
client api enhancement for downstream project" and the consensus seems to be
that there are some cases that need to be clarified for the interplay between
per-job and attached/detached mode, before we have a clear plan there.
Given the above, it is safe to work on introducing the K8-related
{{ClusterDescriptor}} and {{ClusterSpecification}} and maybe wait a bit for the
client side, including the custom command line for K8.
Is this ok for you?
> 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)
