Skip to content
New issue

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

[CORE] Set ray client server host when starting ray. #48836

Open
surenyufuz opened this issue Nov 21, 2024 · 2 comments
Open

[CORE] Set ray client server host when starting ray. #48836

surenyufuz opened this issue Nov 21, 2024 · 2 comments
Labels
core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability triage Needs triage (eg: priority, bug/not-bug, and owning component)

Comments

@surenyufuz
Copy link
Contributor

surenyufuz commented Nov 21, 2024

Description

When starting ray processes, we can use the flag --dashboard-host to set the host for the dashboard server to bind , either localhost (127.0.0.1) or 0.0.0.0.

So can we do the same thing with ray client server ? For example, add a flag which could be like --ray-client-server-host.

Currently, ray client server port could be set from node-ip-address.

code

For some security reasons, I should keep the node ip address which is not 127.0.0.1 and only set 127.0.0.1 for ray client server to bind. As far as I can see, ray client server is only used to be connected from users' scripts, set the host to 127.0.0.1 for it would not cause other problems.

@surenyufuz surenyufuz added enhancement Request for new feature and/or capability triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Nov 21, 2024
@Superskyyy
Copy link
Contributor

You mean in the case that you will only dispatch from within the head node so there isn't a need to expose the client server host to the public right?

@surenyufuz
Copy link
Contributor Author

surenyufuz commented Nov 22, 2024

You mean in the case that you will only dispatch from within the head node so there isn't a need to expose the client server host to the public right?

Thanks for your reply. Not exactly, maybe I can use an exposed proxy with authentication logic to check whether a user could connect to the ray client server, the proxy and the head node are deployed on the same Kubernetes node, both of them could connect with each other by the host net.

@jcotant1 jcotant1 added the core Issues that should be addressed in Ray Core label Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Issues that should be addressed in Ray Core enhancement Request for new feature and/or capability triage Needs triage (eg: priority, bug/not-bug, and owning component)
Projects
None yet
Development

No branches or pull requests

3 participants