You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/04/06 22:39:00 UTC
[jira] [Updated] (FLINK-24066) Provides a new stop entry for Kubernetes session mode
[ https://issues.apache.org/jira/browse/FLINK-24066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-24066:
-----------------------------------
Labels: pull-request-available stale-minor (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> 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, stale-minor
>
> 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.20.1#820001)