-
Notifications
You must be signed in to change notification settings - Fork 508
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
Best practice for fault-tolerant redis with kuberay #2684
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, we add the KubeRay documentation to the Ray repository so that it will automatically appear on the Ray website at https://docs.ray.io/en/latest/cluster/kubernetes/user-guides.html. Would you mind opening a PR to the Ray repository for the documentation and leaving this PR only for the YAML?
Then, you can cc @rueian and me to review. Thanks! |
Hi @spencer-p, LGTM mostly. Thanks for the nice doc. |
Of course. I had figured that would be the next step. To be clear we want to omit this from the best-practice dir in this repo entirely? |
- Suggest disabling AOF on gcsfuse, s3 - Update redis version - Don't provide a default storageClass
Doc is at ray-project/ray#49887, will remove from this PR |
* Draft kuberay + redis + persistent volume best practice * Address review comments 1 - Suggest disabling AOF on gcsfuse, s3 - Update redis version - Don't provide a default storageClass * Remove best practice doc for gcs/redis/disk Moved to ray-project/ray#49887
Why are these changes needed?
Addresses #2582
Related issue number
Closes #2582
Checks