ray
ray copied to clipboard
Add section on launching clusters on Kubernetes to Getting Started
Why are these changes needed?
Hopefully this helps give a quick overview of using KubeRay for deploying clusters to Kubernetes
Related issue number
Closes #42129
Checks
- [x] I've signed off every commit(by using the -s flag, i.e.,
git commit -s) in this PR. - [ ] I've run
scripts/format.shto lint the changes in this PR. - [x] I've included any doc changes needed for https://docs.ray.io/en/master/.
- [x] I've added any new APIs to the API Reference. For example, if I added a
method in Tune, I've added it in
doc/source/tune/api/under the corresponding.rstfile.
- [x] I've added any new APIs to the API Reference. For example, if I added a
method in Tune, I've added it in
- [x] I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
- Testing Strategy
- [ ] Unit tests
- [ ] Release tests
- [ ] This PR is not tested :(
@kevin85421 Hi! Should the link just go directly there? It seemed like the rest of the drop downs had a bit of information, so I wanted to make sure this had the minimal amount needed for deploying to Kubernetes
Should the link just go directly there?
Yes, adding a link directly is fine. KubeRay tries to maintain a single source of truth for documents. We are trying to avoid maintaining consistency between the same content across different documents.
@kevin85421 Makes sense, hopefully this is more aligned with what you were expecting
I will ask our doc team to review it.
Sure!:
Added section for getting started:
Where it leads to:
@can-anyscale just checking to see if the above looks good. Thanks!
@angelinalg Thank you! also sorry, I may have screwed something up by updating my branch with main 😞
cc @angelinalg or @can-anyscale would you mind merging this PR? Thanks!
@kevin85421 @angelinalg @can-anyscale Just wanted to gently nudge on this if possible.
merged, thank you