Remove extranous arguments from examples

[thomasdesr]

Why are these changes needed?

These examples are a little misleading, clean them up to clarify behavior.

Related issue number

n/a

Checks

• I've made sure the tests are passing.
• Testing Strategy
  • Unit tests
  • Manual tests
  • This PR is not tested :(

[kevin85421]

0.0.0.0 is necessary in some cases. For example, if I want to access the port 8265 in my devbox via the $DEVBOX_IP:8265, I need to set 0.0.0.0.

[thomasdesr]

Yeah totally understand there might be cases where something like this might be appropriate, but its probably not the right default since most users run kubectl on the device they're going to be connecting from.

Also while our dev box setup isn't putting that on the public internet, but other user setups may accidentally do so.

[kevin85421]

since most users run kubectl on the device they're going to be connecting from.

I don't think so. Most users use Macs with ARM chips, but Ray/KubeRay are not friendly to ARM chips. Hence, I think most of them running KubeRay on devbox.

[kevin85421]

Also while our dev box setup isn't putting that on the public internet, but other user setups may accidentally do so.

We can add comments mentioning the security concerns. However, I think we should still keep 0.0.0.0. It's not necessary to include 0.0.0.0 in the default command, but we at least need to mention it in the comments.

[anyscalesam]

I was about to say the same too... in practice most dev/test would want 0.0.0.0 just to expose the Ray Dashboard quickly so you can get up and running which was the aim of this example.

[kevin85421]

Chatted with @thomasdesr offline. We should not use 0.0.0.0. If users are running a Kind cluster on devbox, we can use:

ssh -L 8265:localhost:8265 devbox
# In devbox
kubectl port-forward svc/$HEAD_SVC 8265 8265
# Access 127.0.0.1:8265 in your laptop's browser.

[kevin85421]

Could we also mention the ssh -L 8265:localhost:8265 devbox solution in the comments? Thanks!