[GitHub] [dolphinscheduler] ikiler commented on issue #10904: [Feature][Flink] Flink on kubernetes

[GitBox <gi...@apache.org>]

ikiler commented on issue #10904:
URL: https://github.com/apache/dolphinscheduler/issues/10904#issuecomment-1305715406

   > > Hi, @RuiFG Flink and Spark can submit application by Flink/Spark Operator, and this way is so native k8s. In my opinion,I think we maybe clould use Operator mode,not ShellCommandExecutor. In this way,we can submit an application by a yaml file @caishunfeng
   > 
   > https://github.com/GoogleCloudPlatform/spark-on-k8s-operator https://github.com/apache/flink-kubernetes-operator cool, DS build image, uses operator through `KubernetesClient`
   
   Hi @RuiFG I checked the official documentation of operator, but I feel that the key problem is still unsolved, that is how to get his status after the batch task ends, the operator only provides how to manage a running task, but for the batch task to get his information after the end is important.
   Or did I miss some points in doc?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org