[ray] Redis has started but no raylets have registered yet error when connecting to a ray cluster in a private kuberenetes cluster

[jCrompton]

I'm trying to connect to a ray (0.8.0) cluster in my private kuberenetes cluster (using the yaml file provided in the docs) but I get a redis authentication error. I have the ray head node exposed as a NodePort, what am I missing?

Ray version 0.8.0

[jCrompton]

Since I'm on 0.8.0 I had to pass in the default redis password, on 0.9.0 I was able to connect without a password but my redis cluster thinks no raylets have been registered (very similar to this issue #5437) exception:

Exception: Redis has started but no raylets have registered yet.

How do I resolve this in a kubernetes yaml file though, I need the ray-head nodes' public IP in the config but there is no environment variable for the public IP so is the only solution to start the container shell into the container and then run the ray start command with the determined public IP?

[jCrompton]

Any updates on this, I have tried in ray v0.9.dev too with the same issue

[jCrompton]

Pleasseeeeeeee

[stale]

Hi, I'm a bot from the Ray team :)

To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.

If there is no further activity in the 14 days, the issue will be closed!

• If you'd like to keep the issue open, just leave any comment, and the stale label will be removed!
• If you'd like to get more attention to the issue, please tag one of Ray's contributors.

You can always ask for help on our discussion forum or Ray's public slack channel.

[richardliaw]

@jCrompton did you figure this out?