-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[doc][kuberay] state rayStartParams
is optional starting with KubeRay 1.4.0
#53943
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
Conversation
doc/source/cluster/kubernetes/user-guides/persist-kuberay-custom-resource-logs.md
Outdated
Show resolved
Hide resolved
cc @MortalHappiness would you mind reviewing this PR? Thanks! |
doc/source/cluster/kubernetes/user-guides/configuring-autoscaling.ipynb
Outdated
Show resolved
Hide resolved
doc/source/cluster/kubernetes/user-guides/persist-kuberay-custom-resource-logs.md
Outdated
Show resolved
Hide resolved
9600cc8
to
c127d0d
Compare
doc/source/cluster/kubernetes/user-guides/persist-kuberay-custom-resource-logs.md
Outdated
Show resolved
Hide resolved
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.
Remove the following comments from the YAML files. We can also remove rayStartParams: {}
directly. I just want to avoid having the same comment appear in multiple places, as it may be hard to maintain if we decide to update it later.
# rayStartParams is optional with RayCluster CRD from KubeRay 1.4.0 or later but required in earlier versions.
# rayStartParams: {}
doc/source/cluster/kubernetes/user-guides/persist-kuberay-custom-resource-logs.md
Outdated
Show resolved
Hide resolved
Have you installed Vale? |
e52a991
to
0a54f2c
Compare
Yes, as a VS Code extension. I don't see any Vale warnings for the changes. |
I have already requested the Ray doc team to review. |
doc/source/cluster/kubernetes/user-guides/configuring-autoscaling.ipynb
Outdated
Show resolved
Hide resolved
@@ -971,6 +971,11 @@ | |||
"Earlier versions only support `rayStartParams` or resource limits, and don't recognize resource requests.\n", | |||
"```\n", | |||
"\n", | |||
"```{admonition} rayStartParams is optional if using autoscaler image with Ray 2.45.0 or later.\n", | |||
"`rayStartParams` is optional with RayCluster CRD from KubeRay 1.4.0 or later but required in earlier versions.\n", | |||
"If you omit `rayStartParams` and want to use autoscaling, the autoscaling image must have Ray 2.45.0 or later.\n", |
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.
sounds like this is repeated from right above?
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.
I think they're about related but different things. The paragraph above this one is about resource limits being optional. This paragraph is about rayStartParams
being optional. Lmk what you think?
Added suggested edits and rebased on master. |
Fixed the conflicts. Ready for another review. Thanks! |
…ay 1.4.0 but that if autoscaling is used, the autoscaler image must have Ray 2.45.0 or later. closes ray-project/kuberay#3580 Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com> Co-authored-by: Dhyey Shah <dhyey2019@gmail.com> Signed-off-by: David Xia <david@davidxia.com>
cc @davidxia please ping me when all CI tests pass. Thanks. |
…ay 1.4.0 (#53943) but that if autoscaling is used, the autoscaler image must have Ray 2.45.0 or later. closes ray-project/kuberay#3580 ## Checks - [x] I've signed off every commit(by using the -s flag, i.e., `git commit -s`) in this PR. - [x] I've run `scripts/format.sh` to lint the changes in this PR. - [ ] I've included any doc changes needed for https://docs.ray.io/en/master/. - [ ] 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 `.rst` file. - [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 - [x] Unit tests - [ ] Release tests - [ ] This PR is not tested :( Signed-off-by: David Xia <david@davidxia.com> Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com> Co-authored-by: Dhyey Shah <dhyey2019@gmail.com> Co-authored-by: Kai-Hsun Chen <kaihsun@anyscale.com> Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
…ay 1.4.0 (ray-project#53943) but that if autoscaling is used, the autoscaler image must have Ray 2.45.0 or later. closes ray-project/kuberay#3580 ## Checks - [x] I've signed off every commit(by using the -s flag, i.e., `git commit -s`) in this PR. - [x] I've run `scripts/format.sh` to lint the changes in this PR. - [ ] I've included any doc changes needed for https://docs.ray.io/en/master/. - [ ] 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 `.rst` file. - [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 - [x] Unit tests - [ ] Release tests - [ ] This PR is not tested :( Signed-off-by: David Xia <david@davidxia.com> Co-authored-by: angelinalg <122562471+angelinalg@users.noreply.github.com> Co-authored-by: Dhyey Shah <dhyey2019@gmail.com> Co-authored-by: Kai-Hsun Chen <kaihsun@anyscale.com> Signed-off-by: ChanChan Mao <chanchanmao1130@gmail.com>
but that if autoscaling is used, the autoscaler image must have Ray 2.45.0 or later.
closes ray-project/kuberay#3580
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.