Hi 👋 I’m setting up the integration with Ray, and it seems to work nicely when creating a fresh RayCluster (using

@task(task_config=RayJobConfig(worker_node_config=[WorkerNodeConfig(…)]))

). I can see the cluster starting, the job getting scheduled and distributed, and completing successfully. I’m having trouble with using an existing RayCluster (in the same cluster) though. What is the correct approach for that? From the docs here I read that I should be able to use

@task(task_config=RayJobConfig(address="<RAY_CLUSTER_ADDRESS>"))

. However when trying that it seems

worker_node_config

is a required argument. I tried using an empty list instead:

@task(
    container_image=...,
    task_config=RayJobConfig(
        worker_node_config=[],  # No need to create a Ray cluster but argument is required, maybe just setting to empty list helps?
        address="<http://kuberay-cluster-head-svc.kuberay.svc.cluster.local:8265>",
        runtime_env=...
    ),
)

But then it still tries to start a new RayCluster instead of using the existing one found at `address`:

❯ k get rayclusters.ray.io -A
NAMESPACE             NAME                                         DESIRED WORKERS   AVAILABLE WORKERS   CPUS   MEMORY   GPUS   STATUS   AGE
<flyte-project-<flyte-domain>   ahvfr924w8k2vgvf97wp-n0-0-raycluster-crb9z                                         100m   500Mi    0      ready    2m25s
kuberay               kuberay-cluster                              1                 1                   2      3G       0      ready    3h37m
...

The address works fine if I just run:

k run kuberay-test --rm --tty -i --restart='Never' --image ... --command -- ray job submit --address <http://kuberay-cluster-head-svc.kuberay.svc.cluster.local:8265> -- python -c "import ray; ray.init(); print(ray.cluster_resources())"

Interesting. I’m using Ray myself and will likely need to fix some issues with the plugin so I might be able to take a look at this if you file an issue.

this is odd, I don't seem to find logic to handle an empty

worker_node_config

list and avoiding creating a new cluster. @shy-evening-51366 Please report this on an issue to track it

Morning 👋 sure thing. Workaround is very simple so it’s definitely not critical by the way.