Andrew Sy Kim

> run a job in local cluster, without build a remote RayCluster A RayJob can run on an existing cluster using the [clusterSelector field](https://github.com/ray-project/kuberay/blob/master/ray-operator/apis/ray/v1/rayjob_types.go#L79). This way you can create a...

> kuberay still need to create a k8s job to submit job There's a HTTP submission mode that doesn't use submitter Job https://github.com/ray-project/kuberay/blob/master/ray-operator/apis/ray/v1/rayjob_types.go#L92

> @andrewsykim I can invest some time to learn go and how to add tests, but first: are you okay with this breaking change? Anyone who currently uses ray and...

> My submitter Pod's docker image has configured an ENTRYPOINT which I do not wish to override. I just want to set the args but kuberay will override the command...

RayJob works best for running ephemeral clusters that are cleaned up after running a single job. However, if you want to run additional jobs on the same RayCluster used for...

> In our ML platform, we want to enable users to run their jobs using our CLI. On the backend, we want to leverage the RayJob manifest to create the...

> Right now, we achieve it using RayCluster manifest (to create the cluster) and JobSubmissionClient to submit the job to it. We want to, however, replace the JobSubmissionClient and switch...

> it expects the working_dir to be an existing directory in the cluster (head node's main container). I don't think this is supported. RayJob assumes the source code is available...

> Online examples in your samples suggest creating a ConfigMap object to store the scripts and then mounting it onto the container. We can create multiple key-value pairs (one for...

Yes, that and the new `InteractiveMode` for RayJob introcued in v1.3