@@ -95,11 +95,11 @@ With this upgrade guide, there are a few notes to consider:
9595
9696Unless otherwise noted due to extenuating requirements, upgrades from one patch release of Rook to
9797another are as simple as updating the common resources and the image of the Rook operator. For
98- example, when Rook v1.18.2 is released, the process of updating from v1.18.0 is as simple as running
98+ example, when Rook v1.18.3 is released, the process of updating from v1.18.0 is as simple as running
9999the following:
100100
101101``` console
102- git clone --single-branch --depth=1 --branch v1.18.2 https://github.com/rook/rook.git
102+ git clone --single-branch --depth=1 --branch v1.18.3 https://github.com/rook/rook.git
103103cd rook/deploy/examples
104104```
105105
@@ -111,7 +111,7 @@ Then, apply the latest changes from v1.18, and update the Rook Operator image.
111111
112112``` console
113113kubectl apply -f common.yaml -f crds.yaml -f csi-operator.yaml
114- kubectl -n rook-ceph set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.18.2
114+ kubectl -n rook-ceph set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.18.3
115115```
116116
117117As exemplified above, it is a good practice to update Rook common resources from the example
@@ -146,7 +146,7 @@ In order to successfully upgrade a Rook cluster, the following prerequisites mus
146146## Rook Operator Upgrade
147147
148148The examples given in this guide upgrade a live Rook cluster running ` v1.17.8 ` to
149- the version ` v1.18.2 ` . This upgrade should work from any official patch release of Rook v1.17 to any
149+ the version ` v1.18.3 ` . This upgrade should work from any official patch release of Rook v1.17 to any
150150official patch release of v1.18.
151151
152152Let's get started!
@@ -173,7 +173,7 @@ by the Operator. Also update the Custom Resource Definitions (CRDs).
173173Get the latest common resources manifests that contain the latest changes.
174174
175175``` console
176- git clone --single-branch --depth=1 --branch v1.18.2 https://github.com/rook/rook.git
176+ git clone --single-branch --depth=1 --branch v1.18.3 https://github.com/rook/rook.git
177177cd rook/deploy/examples
178178```
179179
@@ -212,7 +212,7 @@ The largest portion of the upgrade is triggered when the operator's image is upd
212212When the operator is updated, it will proceed to update all of the Ceph daemons.
213213
214214``` console
215- kubectl -n $ROOK_OPERATOR_NAMESPACE set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.18.2
215+ kubectl -n $ROOK_OPERATOR_NAMESPACE set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.18.3
216216```
217217
218218### ** 3. Update Ceph CSI Custom Images **
@@ -236,16 +236,16 @@ watch --exec kubectl -n $ROOK_CLUSTER_NAMESPACE get deployments -l rook_cluster=
236236```
237237
238238As an example, this cluster is midway through updating the OSDs. When all deployments report ` 1/1/1 `
239- availability and ` rook-version=v1.18.2 ` , the Ceph cluster's core components are fully updated.
239+ availability and ` rook-version=v1.18.3 ` , the Ceph cluster's core components are fully updated.
240240
241241``` console
242242Every 2.0s: kubectl -n rook-ceph get deployment -o j...
243243
244- rook-ceph-mgr-a req/upd/avl: 1/1/1 rook-version=v1.18.2
245- rook-ceph-mon-a req/upd/avl: 1/1/1 rook-version=v1.18.2
246- rook-ceph-mon-b req/upd/avl: 1/1/1 rook-version=v1.18.2
247- rook-ceph-mon-c req/upd/avl: 1/1/1 rook-version=v1.18.2
248- rook-ceph-osd-0 req/upd/avl: 1// rook-version=v1.18.2
244+ rook-ceph-mgr-a req/upd/avl: 1/1/1 rook-version=v1.18.3
245+ rook-ceph-mon-a req/upd/avl: 1/1/1 rook-version=v1.18.3
246+ rook-ceph-mon-b req/upd/avl: 1/1/1 rook-version=v1.18.3
247+ rook-ceph-mon-c req/upd/avl: 1/1/1 rook-version=v1.18.3
248+ rook-ceph-osd-0 req/upd/avl: 1// rook-version=v1.18.3
249249rook-ceph-osd-1 req/upd/avl: 1/1/1 rook-version=v1.17.8
250250rook-ceph-osd-2 req/upd/avl: 1/1/1 rook-version=v1.17.8
251251```
@@ -257,13 +257,13 @@ An easy check to see if the upgrade is totally finished is to check that there i
257257# 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
258258This cluster is not yet finished:
259259 rook-version=v1.17.8
260- rook-version=v1.18.2
260+ rook-version=v1.18.3
261261This cluster is finished:
262- rook-version=v1.18.2
262+ rook-version=v1.18.3
263263```
264264
265265### ** 5. Verify the updated cluster**
266266
267- At this point, the Rook operator should be running version ` rook/ceph:v1.18.2 ` .
267+ At this point, the Rook operator should be running version ` rook/ceph:v1.18.3 ` .
268268
269269Verify the CephCluster health using the [ health verification doc] ( health-verification.md ) .
0 commit comments