build: update release version to v1.13.3

For the patch release update the examples and docs to v1.13.3 Signed-off-by: travisn <[email protected]>
travisn · Jan 25, 2024 · 93de9be · 93de9be
1 parent 7c97d13
commit 93de9be
Show file tree

Hide file tree

Showing 11 changed files with 30 additions and 30 deletions.
diff --git a/Documentation/Getting-Started/quickstart.md b/Documentation/Getting-Started/quickstart.md
@@ -36,7 +36,7 @@ To configure the Ceph storage cluster, at least one of these local storage optio
 A simple Rook cluster is created for Kubernetes with the following `kubectl` commands and [example manifests](https://github.com/rook/rook/blob/master/deploy/examples).
 
 ```console
-$ git clone --single-branch --branch v1.13.2 https://github.com/rook/rook.git
+$ git clone --single-branch --branch v1.13.3 https://github.com/rook/rook.git
 cd rook/deploy/examples
 kubectl create -f crds.yaml -f common.yaml -f operator.yaml
 kubectl create -f cluster.yaml

diff --git a/Documentation/Storage-Configuration/Monitoring/ceph-monitoring.md b/Documentation/Storage-Configuration/Monitoring/ceph-monitoring.md
@@ -44,7 +44,7 @@ There are two sources for metrics collection:
 From the root of your locally cloned Rook repo, go the monitoring directory:
 
 ```console
-$ git clone --single-branch --branch v1.13.2 https://github.com/rook/rook.git
+$ git clone --single-branch --branch v1.13.3 https://github.com/rook/rook.git
 cd rook/deploy/examples/monitoring
 ```
 

diff --git a/Documentation/Upgrade/rook-upgrade.md b/Documentation/Upgrade/rook-upgrade.md
@@ -78,11 +78,11 @@ With this upgrade guide, there are a few notes to consider:
 
 Unless otherwise noted due to extenuating requirements, upgrades from one patch release of Rook to
 another are as simple as updating the common resources and the image of the Rook operator. For
-example, when Rook v1.13.2 is released, the process of updating from v1.13.0 is as simple as running
+example, when Rook v1.13.3 is released, the process of updating from v1.13.0 is as simple as running
 the following:
 
 ```console
-git clone --single-branch --depth=1 --branch v1.13.2 https://github.com/rook/rook.git
+git clone --single-branch --depth=1 --branch v1.13.3 https://github.com/rook/rook.git
 cd rook/deploy/examples
 ```
 
@@ -94,7 +94,7 @@ Then, apply the latest changes from v1.13, and update the Rook Operator image.
 
 ```console
 kubectl apply -f common.yaml -f crds.yaml
-kubectl -n rook-ceph set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.13.2
+kubectl -n rook-ceph set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.13.3
 ```
 
 As exemplified above, it is a good practice to update Rook common resources from the example
@@ -128,8 +128,8 @@ In order to successfully upgrade a Rook cluster, the following prerequisites mus
 
 ## Rook Operator Upgrade
 
-The examples given in this guide upgrade a live Rook cluster running `v1.12.10` to
-the version `v1.13.2`. This upgrade should work from any official patch release of Rook v1.12 to any
+The examples given in this guide upgrade a live Rook cluster running `v1.12.11` to
+the version `v1.13.3`. This upgrade should work from any official patch release of Rook v1.12 to any
 official patch release of v1.13.
 
 Let's get started!
@@ -156,7 +156,7 @@ by the Operator. Also update the Custom Resource Definitions (CRDs).
 Get the latest common resources manifests that contain the latest changes.
 
 ```console
-git clone --single-branch --depth=1 --branch v1.13.2 https://github.com/rook/rook.git
+git clone --single-branch --depth=1 --branch v1.13.3 https://github.com/rook/rook.git
 cd rook/deploy/examples
 ```
 
@@ -195,7 +195,7 @@ The largest portion of the upgrade is triggered when the operator's image is upd
 When the operator is updated, it will proceed to update all of the Ceph daemons.
 
 ```console
-kubectl -n $ROOK_OPERATOR_NAMESPACE set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.13.2
+kubectl -n $ROOK_OPERATOR_NAMESPACE set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.13.3
 ```
 
 ### **3. Update Ceph CSI**
@@ -225,18 +225,18 @@ watch --exec kubectl -n $ROOK_CLUSTER_NAMESPACE get deployments -l rook_cluster=
 ```
 
 As an example, this cluster is midway through updating the OSDs. When all deployments report `1/1/1`
-availability and `rook-version=v1.13.2`, the Ceph cluster's core components are fully updated.
+availability and `rook-version=v1.13.3`, the Ceph cluster's core components are fully updated.
 
 ```console
 Every 2.0s: kubectl -n rook-ceph get deployment -o j...
 
-rook-ceph-mgr-a         req/upd/avl: 1/1/1      rook-version=v1.13.2
-rook-ceph-mon-a         req/upd/avl: 1/1/1      rook-version=v1.13.2
-rook-ceph-mon-b         req/upd/avl: 1/1/1      rook-version=v1.13.2
-rook-ceph-mon-c         req/upd/avl: 1/1/1      rook-version=v1.13.2
-rook-ceph-osd-0         req/upd/avl: 1//        rook-version=v1.13.2
-rook-ceph-osd-1         req/upd/avl: 1/1/1      rook-version=v1.12.10
-rook-ceph-osd-2         req/upd/avl: 1/1/1      rook-version=v1.12.10
+rook-ceph-mgr-a         req/upd/avl: 1/1/1      rook-version=v1.13.3
+rook-ceph-mon-a         req/upd/avl: 1/1/1      rook-version=v1.13.3
+rook-ceph-mon-b         req/upd/avl: 1/1/1      rook-version=v1.13.3
+rook-ceph-mon-c         req/upd/avl: 1/1/1      rook-version=v1.13.3
+rook-ceph-osd-0         req/upd/avl: 1//        rook-version=v1.13.3
+rook-ceph-osd-1         req/upd/avl: 1/1/1      rook-version=v1.12.11
+rook-ceph-osd-2         req/upd/avl: 1/1/1      rook-version=v1.12.11
 ```
 
 An easy check to see if the upgrade is totally finished is to check that there is only one
@@ -245,14 +245,14 @@ An easy check to see if the upgrade is totally finished is to check that there i
 ```console
 # kubectl -n $ROOK_CLUSTER_NAMESPACE get deployment -l rook_cluster=$ROOK_CLUSTER_NAMESPACE -o jsonpath='{range .items[*]}{"rook-version="}{.metadata.labels.rook-version}{"\n"}{end}' | sort | uniq
 This cluster is not yet finished:
-  rook-version=v1.12.10
-  rook-version=v1.13.2
+  rook-version=v1.12.11
+  rook-version=v1.13.3
 This cluster is finished:
-  rook-version=v1.13.2
+  rook-version=v1.13.3
 ```
 
 ### **5. Verify the updated cluster**
 
-At this point, the Rook operator should be running version `rook/ceph:v1.13.2`.
+At this point, the Rook operator should be running version `rook/ceph:v1.13.3`.
 
 Verify the CephCluster health using the [health verification doc](health-verification.md).
diff --git a/deploy/examples/direct-mount.yaml b/deploy/examples/direct-mount.yaml
@@ -18,7 +18,7 @@ spec:
       dnsPolicy: ClusterFirstWithHostNet
       containers:
         - name: rook-direct-mount
-          image: rook/ceph:v1.13.2
+          image: rook/ceph:v1.13.3
           command: ["/bin/bash"]
           args: ["-m", "-c", "/usr/local/bin/toolbox.sh"]
           imagePullPolicy: IfNotPresent

diff --git a/deploy/examples/images.txt b/deploy/examples/images.txt
@@ -8,4 +8,4 @@
  registry.k8s.io/sig-storage/csi-provisioner:v3.6.3
  registry.k8s.io/sig-storage/csi-resizer:v1.9.2
  registry.k8s.io/sig-storage/csi-snapshotter:v6.3.2
- rook/ceph:v1.13.2
+ rook/ceph:v1.13.3
diff --git a/deploy/examples/multus-validation.yaml b/deploy/examples/multus-validation.yaml
@@ -101,7 +101,7 @@ spec:
       serviceAccountName: rook-ceph-multus-validation
       containers:
         - name: multus-validation
-          image: rook/ceph:v1.13.2
+          image: rook/ceph:v1.13.3
           command: ["rook"]
           args:
             - "multus"

diff --git a/deploy/examples/operator-openshift.yaml b/deploy/examples/operator-openshift.yaml
@@ -682,7 +682,7 @@ spec:
       serviceAccountName: rook-ceph-system
       containers:
         - name: rook-ceph-operator
-          image: rook/ceph:v1.13.2
+          image: rook/ceph:v1.13.3
           args: ["ceph", "operator"]
           securityContext:
             runAsNonRoot: true

diff --git a/deploy/examples/operator.yaml b/deploy/examples/operator.yaml
@@ -607,7 +607,7 @@ spec:
       serviceAccountName: rook-ceph-system
       containers:
         - name: rook-ceph-operator
-          image: rook/ceph:v1.13.2
+          image: rook/ceph:v1.13.3
           args: ["ceph", "operator"]
           securityContext:
             runAsNonRoot: true

diff --git a/deploy/examples/osd-purge.yaml b/deploy/examples/osd-purge.yaml
@@ -28,7 +28,7 @@ spec:
       serviceAccountName: rook-ceph-purge-osd
       containers:
         - name: osd-removal
-          image: rook/ceph:v1.13.2
+          image: rook/ceph:v1.13.3
           # TODO: Insert the OSD ID in the last parameter that is to be removed
           # The OSD IDs are a comma-separated list. For example: "0" or "0,2".
           # If you want to preserve the OSD PVCs, set `--preserve-pvc true`.

diff --git a/deploy/examples/toolbox-job.yaml b/deploy/examples/toolbox-job.yaml
@@ -10,7 +10,7 @@ spec:
     spec:
       initContainers:
         - name: config-init
-          image: rook/ceph:v1.13.2
+          image: rook/ceph:v1.13.3
           command: ["/usr/local/bin/toolbox.sh"]
           args: ["--skip-watch"]
           imagePullPolicy: IfNotPresent
@@ -29,7 +29,7 @@ spec:
               mountPath: /var/lib/rook-ceph-mon
       containers:
         - name: script
-          image: rook/ceph:v1.13.2
+          image: rook/ceph:v1.13.3
           volumeMounts:
             - mountPath: /etc/ceph
               name: ceph-config

diff --git a/deploy/examples/toolbox-operator-image.yaml b/deploy/examples/toolbox-operator-image.yaml
@@ -24,7 +24,7 @@ spec:
       dnsPolicy: ClusterFirstWithHostNet
       containers:
         - name: rook-ceph-tools-operator-image
-          image: rook/ceph:v1.13.2
+          image: rook/ceph:v1.13.3
           command:
             - /bin/bash
             - -c