update

Signed-off-by: Kai-Hsun Chen <kaihsun@anyscale.com>
ray-project · Sep 30, 2024 · a87f0c2 · a87f0c2
1 parent beb90d2
commit a87f0c2
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/doc/source/cluster/kubernetes/k8s-ecosystem/istio.md b/doc/source/cluster/kubernetes/k8s-ecosystem/istio.md
@@ -66,7 +66,7 @@ In this mode, you _must_ disable the KubeRay init container injection by setting
 
 ```bash
 # Set ENABLE_INIT_CONTAINER_INJECTION=false on the KubeRay operator.
-helm upgrade kuberay-operator kuberay/kuberay-operator --version 1.1.1 \
+helm upgrade kuberay-operator kuberay/kuberay-operator --version 1.2.2 \
   --set env\[0\].name=ENABLE_INIT_CONTAINER_INJECTION \
   --set-string env\[0\].value=false
 

diff --git a/doc/source/cluster/kubernetes/user-guides/observability.md b/doc/source/cluster/kubernetes/user-guides/observability.md
@@ -52,7 +52,7 @@ Although `Status.State` can represent the cluster situation, it's still only a s
 If you deployed KubeRay with Helm, then enable the `RayClusterStatusConditions` gate in the `featureGates` of your Helm values.
 
 ```bash
-helm upgrade kuberay-operator kuberay/kuberay-operator --version 1.2.1 \
+helm upgrade kuberay-operator kuberay/kuberay-operator --version 1.2.2 \
   --set featureGates\[0\].name=RayClusterStatusConditions \
   --set featureGates\[0\].enabled=true
 ```

diff --git a/doc/source/cluster/kubernetes/user-guides/tls.md b/doc/source/cluster/kubernetes/user-guides/tls.md
@@ -88,11 +88,11 @@ kubectl create secret generic ca-tls --from-file=ca.key --from-file=ca.crt
 * `ca.crt`: CA's self-signed certificate
 
 This step is optional because the `ca.key` and `ca.crt` files have
-already been included in the Kubernetes Secret specified in [ray-cluster.tls.yaml](https://github.com/ray-project/kuberay/blob/v1.0.0/ray-operator/config/samples/ray-cluster.tls.yaml).
+already been included in the Kubernetes Secret specified in [ray-cluster.tls.yaml](https://github.com/ray-project/kuberay/blob/v1.2.2/ray-operator/config/samples/ray-cluster.tls.yaml).
 
 # Step 2: Create separate private key and self-signed certificate for Ray Pods
 
-In [ray-cluster.tls.yaml](https://github.com/ray-project/kuberay/blob/v1.0.0/ray-operator/config/samples/ray-cluster.tls.yaml), each Ray
+In [ray-cluster.tls.yaml](https://github.com/ray-project/kuberay/blob/v1.2.2/ray-operator/config/samples/ray-cluster.tls.yaml), each Ray
 Pod (both head and workers) generates its own private key file (`tls.key`) and self-signed
 certificate file (`tls.crt`) in its init container. We generate separate files for each Pod
 because worker Pods do not have deterministic DNS names, and we cannot use the same