We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Users may want Ray head to be accessible from outside Kubernetes. One option is to use Kubernetes Service with type LoadBalancer and specify loadBalancerIP. However, KubeRay currently does not expose loadBalancerIP to users. See https://discuss.ray.io/t/specify-ip-adress-for-the-head-as-a-loadbalancer-service-type/9008 for more details.
LoadBalancer
loadBalancerIP
No response
https://discuss.ray.io/t/specify-ip-adress-for-the-head-as-a-loadbalancer-service-type/9008
The text was updated successfully, but these errors were encountered:
KubeRay originally only exposed serviceType to users. Then, we found that it is not enough, and thus exposed custom annotations and labels.
serviceType
I currently have two thoughts:
Any thoughts? cc @DmitriGekhtman @architkulkarni @Jeffwan
Sorry, something went wrong.
We should expose as many fields as people ask for.
Probably we should have just exposed the entire service (maybe we did in the initial version?)
architkulkarni
Successfully merging a pull request may close this issue.
Search before asking
Description
Users may want Ray head to be accessible from outside Kubernetes. One option is to use Kubernetes Service with type
LoadBalancer
and specifyloadBalancerIP
. However, KubeRay currently does not exposeloadBalancerIP
to users. See https://discuss.ray.io/t/specify-ip-adress-for-the-head-as-a-loadbalancer-service-type/9008 for more details.Use case
No response
Related issues
https://discuss.ray.io/t/specify-ip-adress-for-the-head-as-a-loadbalancer-service-type/9008
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: