[cherry-pick][2.58.0][docs] Backport KubeRay v1.7 feature docs

[dstrodtman]

Why

The KubeRay v1.7 blog highlights several features whose docs currently live only on master. The corresponding pages are missing (404) or incomplete on the latest (2.58.0) docs build, and several blog links point at /master as a result. This backports the doc pages so the 2.58.0 latest docs cover the released KubeRay v1.7 surface.

What (cherry-picks onto releases/2.58.0)

Commit	Blog feature	Gap on latest
#64303	RayJob SidecarMode retry	new page was missing
#65249	RayService incremental upgrade rollback (beta)	#rollback section missing
#65074	NetworkPolicy support (alpha)	new page was missing
#65429	Embedded RocksDB GCS backend	example version pin missing
#65513	Fix docs for KubeRay v1.7	wrong NetworkPolicy field names + incorrect kubernetes pip guidance
#65483	Customizable Ingress options	ingressOptions undocumented

Each commit is applied with cherry-pick -x (provenance preserved) and DCO sign-off.

Not duplicating

• No open PR cherry-picks these into releases/2.58.0 (checked by PR number and by --base releases/2.58.0).
• The two History Server refinements ([doc][History server] Update doc for history server for RAY_ROOT_DIR -> STORAGE_ROOT_DIR #65441, [Docs][KubeRay] Use RayJob sample YAML for History Server docs #65505) are intentionally excluded — they already landed on releases/2.58.0 (c6061c10b97, d8277b53b0d) and that page is already identical to master.
• Broad, non-feature changes touching these files on master (llms.txt page descriptions [doc] Add curated page descriptions for the remaining llms.txt pages #65115, the "Ray Pod" terminology rename [docs] Retire the "Ray Pod" term from the Kubernetes docs #65423, the vendored CRD API reference [docs] vendor the KubeRay CRD API reference into the Ray docs #65428) are deliberately left out to keep this a tight, low-risk release-branch backport.

Testing

• Verified every new/changed page's {ref}/{doc} cross-reference target resolves on this branch (fail_on_warning: true build safety).
• Verified both new toctree entries (network-policy, rayjob-sidecar-submitter-restart) point at files that exist on the branch.
• Confirmed each touched file matches master except for the intentionally-excluded frontmatter/rename hunks above.
• A full local Sphinx docs build is recommended before marking ready for review.

AI assistance (Claude Code) was used to prepare this backport.

[gemini-code-assist]

Code Review

This pull request updates the KubeRay documentation to cover features introduced in KubeRay v1.7.0, including built-in Ingress support, NetworkPolicies, RayJob sidecar submitter restarts, and RayService incremental upgrade rollbacks. The review feedback recommends updating the installation examples to reference KubeRay v1.7.0 instead of v1.6.0, and updating the Ray version in the sidecar restart guide to v2.58.0 to align with the target release branch.

[gemini-code-assist]

Since this PR backports KubeRay v1.7 features (such as ingressOptions, NetworkPolicy, and SidecarSubmitterRestart), the operator installation guide should be updated to install KubeRay v1.7.0 instead of v1.6.0. Otherwise, users following this guide will not be able to use the newly documented features.

Suggested change

	kubectl create namespace ray-system
	helm install kuberay-operator kuberay/kuberay-operator --version 1.6.0 -n ray-system
	kubectl create namespace ray-system
	helm install kuberay-operator kuberay/kuberay-operator --version 1.7.0 -n ray-system

[gemini-code-assist]

Update the Kustomize ref to v1.7.0 to match the Helm installation version and ensure compatibility with the backported KubeRay v1.7 features.

Suggested change

	kubectl create namespace ray-system
	kubectl create -k "github.com/ray-project/kuberay/ray-operator/config/default?ref=v1.6.0" -n ray-system
	kubectl create namespace ray-system
	kubectl create -k "github.com/ray-project/kuberay/ray-operator/config/default?ref=v1.7.0" -n ray-system

[gemini-code-assist]

Since this documentation is being backported to the 2.58.0 release branch, the example Ray version and image tags should be updated from 2.56.0 to 2.58.0 to remain consistent with the target release branch.

  rayClusterSpec:
    rayVersion: '2.58.0'
    headGroupSpec:
      rayStartParams: {}
      template:
        spec:
          containers:
          - name: ray-head
            image: rayproject/ray:2.58.0
            resources:
              limits:
                cpu: "1"
                memory: "5Gi"
            volumeMounts:
            - mountPath: /home/ray/samples
              name: code-sample
          volumes:
          - name: code-sample
            configMap:
              name: ray-job-code-sample
    workerGroupSpecs:
    - replicas: 1
      groupName: small-group
      rayStartParams: {}
      template:
        spec:
          containers:
          - name: ray-worker
            image: rayproject/ray:2.58.0
            resources:
              limits:
                cpu: "1"
                memory: "1Gi"