tall-exabyte-99685
05/31/2023, 11:02 PMglamorous-carpet-83516
05/31/2023, 11:40 PM@task
def t1():
ray.init(<ip_address>)
ray.remote(...)
tall-exabyte-99685
06/14/2023, 5:35 PMglamorous-carpet-83516
06/14/2023, 5:59 PMtall-exabyte-99685
06/14/2023, 6:11 PMaddress
. In the latest plugin source code (flytekitplugins/ray/task.py
) I see this `dataclass`:
@dataclass
class RayJobConfig:
worker_node_config: typing.List[WorkerNodeConfig]
head_node_config: typing.Optional[HeadNodeConfig] = None
runtime_env: typing.Optional[dict] = None
address: typing.Optional[str] = None
I would expect this address to work to send a job to an existing Ray Cluster deployed on Kubernetes AWS:
address="<ray://ray-cluster-kuberay-head-svc.ray-cluster-namespace.svc.cluster.local:10001>"
It seems like regardless of weather the address
field is present or not, the plugin spins up a new ephemeral Ray cluster. I did get it working via your example without the plugin @glamorous-carpet-83516 but I was just curious if there was a way to do this via the plugin. Thanks for your help!