Skip to content
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

[Doc][KubeRay] Update PyTorch Mnist Training doc for KubeRay 1.2.0 #47321

Conversation

MortalHappiness
Copy link
Member

Why are these changes needed?

The documentation "Train a PyTorch model on Fashion MNIST with CPUs on Kubernetes" is outdated for KubeRay 1.2.0 release:

  • Ray image changes from ray:2.9.0 to ray:2.34.0 and the CPU resources request must be changed to work. See the related issues and PRs for details.
  • The output of kubectl get pods are wrong. All pods should be prefixed with rayjob-pytorch-mnist-

Related issue number

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 :(

@MortalHappiness MortalHappiness marked this pull request as ready for review August 24, 2024 18:04
@MortalHappiness
Copy link
Member Author

@kevin85421 PTAL

@MortalHappiness
Copy link
Member Author

@anyscalesam anyscalesam added P2 Important issue, but not time-critical core Issues that should be addressed in Ray Core docs An issue or change related to documentation kuberay Issues for the Ray/Kuberay integration that are tracked on the Ray side labels Aug 26, 2024
@kevin85421 kevin85421 added the go add ONLY when ready to merge, run all tests label Aug 27, 2024
@jjyao jjyao merged commit cefedcf into ray-project:master Sep 4, 2024
5 checks passed
ujjawal-khare pushed a commit to ujjawal-khare-27/ray that referenced this pull request Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Issues that should be addressed in Ray Core docs An issue or change related to documentation go add ONLY when ready to merge, run all tests kuberay Issues for the Ray/Kuberay integration that are tracked on the Ray side P2 Important issue, but not time-critical
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants