[doc] update links for KubeRay 1.4.2

[rueian]

Why are these changes needed?

cc @kevin85421

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

[gemini-code-assist]

Summary of Changes

Hello @rueian, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on synchronizing the documentation and internal scripts with the latest KubeRay version, 1.4.2. The primary goal is to ensure that all examples, installation instructions, and references within the documentation accurately reflect the current stable release, providing users with up-to-date and correct information. Additionally, a minor improvement was made to a Kubernetes command in one of the examples.

Highlights

• Documentation Updates: Updated numerous documentation files to reference KubeRay version 1.4.2 instead of 1.4.0. This includes installation commands, example YAML file URLs, and version mentions in various guides.
• Script Variable Updates: Updated KubeRay version variables in internal scripts (init-config.sh and run_gcs_ft_on_k8s.py) to v1.4.2.
• Example Command Refinement: Improved the clarity of a kubectl port-forward command in the verl-post-training.md example by replacing a hardcoded head pod name with a $HEAD_POD variable.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates KubeRay version references from 1.4.0 to 1.4.2 across various documentation files and scripts. The changes are mostly straightforward version bumps in URLs and commands. There is one high severity issue where the URL for the sample YAML is incorrect, and I've provided a suggestion to fix it. The change in doc/source/cluster/kubernetes/examples/verl-post-training.md to use $HEAD_POD instead of a hardcoded name is a good improvement for correctness. Overall, a good set of updates to keep the documentation in sync with the new release.

[kevin85421]

please ping me when all CI tests pass.