[
https://issues.apache.org/jira/browse/FLINK-9953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956596#comment-16956596
]
Yang Wang commented on FLINK-9953:
----------------------------------
[~trohrmann] [~kkl0u]
Thanks for your comments and share the client changing progress with me. It is
ok for me to leave the changes of `CliFrontend` and `KubernetesCustomCli` at
last. Since we have reached an agreement about session cluster, i will try to
give the initial basic k8s integration to support this. For per job execution
mode, i will hold it before we have a clear plan.
# Start a flink session cluster
{code:java}
./bin/kubernetes-session.sh -d -id flink-session-example-1 \
-i flink-k8s:latest \
-jm 2048 -tm 4096 -s 8 \
-Dkubernetes.jobmanager.cpu=0.5 -Dkubernetes.taskmanager.cpu=2 \
{code}
# Submit a flink job to a session cluster
{code:java}
flink run -kid flink-session-example-1 \
examples/streaming/WindowJoin.jar
{code}
> 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)
