[
https://issues.apache.org/jira/browse/FLINK-24066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17407151#comment-17407151
]
Yang Wang commented on FLINK-24066:
-----------------------------------
Hmm. Thanks for creating this ticket.
AFAIK, the Yarn session cluster has the same behavior. And I do not feel any
concrete differences between them except for personal taste.
> Provides a new stop entry for Kubernetes session mode
> -----------------------------------------------------
>
> Key: FLINK-24066
> URL: https://issues.apache.org/jira/browse/FLINK-24066
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Reporter: liuzhuo
> Priority: Minor
> Labels: pull-request-available
>
> For the current Native Kubernetes session mode, the way to stop a session is：
> {code:java}
> # (3) Stop Kubernetes session by deleting cluster deployment
> $ kubectl delete deployment/my-first-flink-cluster
> {code}
> or
> {code:java}
> $ echo 'stop' | ./bin/kubernetes-session.sh \
> -Dkubernetes.cluster-id=my-first-flink-cluster \
> -Dexecution.attached=true
> {code}
> I think a more friendly interface should be added to stop the session mode,
> such as:
> {code:java}
> $ ./bin/kubernetes-session.sh stop
> -Dkubernetes.cluster-id=my-first-flink-cluster
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
