[
https://issues.apache.org/jira/browse/SPARK-24793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542003#comment-16542003
]
Yinan Li commented on SPARK-24793:
----------------------------------
Good points, Erik. I think
[sparkctl|https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/tree/master/sparkctl]
is also a good alternative for supporting the set of functionalities proposed.
It is positioned better to operate on the driver pods than kubectl, while still
looks familiar to users who are used to kubectl.
> Make spark-submit more useful with k8s
> --------------------------------------
>
> Key: SPARK-24793
> URL: https://issues.apache.org/jira/browse/SPARK-24793
> Project: Spark
> Issue Type: Improvement
> Components: Kubernetes
> Affects Versions: 2.3.0
> Reporter: Anirudh Ramanathan
> Assignee: Anirudh Ramanathan
> Priority: Major
>
> Support controlling the lifecycle of Spark Application through spark-submit.
> For example:
> {{
> --kill app_name If given, kills the driver specified.
> --status app_name If given, requests the status of the driver
> specified.
> }}
> Potentially also --list to list all spark drivers running.
> Given that our submission client can actually launch jobs into many different
> namespaces, we'll need an additional specification of the namespace through a
> --namespace flag potentially.
> I think this is pretty useful to have instead of forcing a user to use
> kubectl to manage the lifecycle of any k8s Spark Application.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
