Custom names for k8s services besides "ray-head"

Hey folks, we want multiple people to be able to launch their own ray clusters, however the guide here - Deploying a Static Cluster — Ray v2.0.0.dev0 uses explicit service names and environment variables to get service ip, so we cannot have multiple ray-head services at the same time. Is there a workaround for this?

One could have each person use the configs as is by having each person launch a Ray cluster in their own namespace.

If that’s not tenable, then the config for each cluster must have a unique service name.
The selector fields for each head service must also be unique and match the corresponding fields of each cluster’s head deployment.

The environment variables are set up by K8s automatically and use upper-case versions of the service name.

Actually, does Ray use the component label internally…?
Let me check.

It does not. Either of the above suggestions should work.

This works, thanks a lot @Dmitri

1 Like