Skip to content

Conversation

davidxia
Copy link
Contributor

@davidxia davidxia commented Jun 19, 2025

but that if autoscaling is used, the autoscaler image must have Ray 2.45.0 or later.

closes ray-project/kuberay#3580

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • 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.
  • 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 :(

@davidxia davidxia marked this pull request as ready for review June 19, 2025 02:12
@davidxia davidxia requested review from a team, pcmoritz and kevin85421 as code owners June 19, 2025 02:12
@kevin85421
Copy link
Member

cc @MortalHappiness would you mind reviewing this PR? Thanks!

@davidxia davidxia force-pushed the docs44 branch 2 times, most recently from 9600cc8 to c127d0d Compare June 19, 2025 18:34
@davidxia davidxia requested a review from MortalHappiness June 19, 2025 18:34
Copy link
Member

@kevin85421 kevin85421 left a 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: {}

@kevin85421
Copy link
Member

Have you installed Vale?

@davidxia davidxia force-pushed the docs44 branch 2 times, most recently from e52a991 to 0a54f2c Compare June 23, 2025 22:53
@davidxia
Copy link
Contributor Author

Have you installed Vale?

Yes, as a VS Code extension. I don't see any Vale warnings for the changes.

@kevin85421
Copy link
Member

I have already requested the Ray doc team to review.

@@ -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",
Copy link
Contributor

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?

Copy link
Contributor Author

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?

@davidxia
Copy link
Contributor Author

Added suggested edits and rebased on master.

@davidxia
Copy link
Contributor Author

davidxia commented Jul 1, 2025

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>
@kevin85421 kevin85421 added the go add ONLY when ready to merge, run all tests label Jul 3, 2025
@kevin85421
Copy link
Member

cc @davidxia please ping me when all CI tests pass. Thanks.

@kevin85421
Copy link
Member

cc @jjyao @edoakes would you mind merging this PR? Thanks.

@edoakes edoakes merged commit a526909 into ray-project:master Jul 3, 2025
6 checks passed
@davidxia davidxia deleted the docs44 branch July 3, 2025 23:49
elliot-barn pushed a commit that referenced this pull request Jul 7, 2025
…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>
ccmao1130 pushed a commit to ccmao1130/ray that referenced this pull request Jul 29, 2025
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Follow up of #3202: update doc
6 participants