Editing Rook Storage for Kubernetes (section)

=== Updating Rook ===
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.6.2 is released, the process of updating from v1.6.0 is as simple as running the following:

First get the latest common resources manifests that contain the latest changes for Rook v1.6.

 git clone --single-branch --depth=1 --branch v1.6.2 https://github.com/rook/rook.git
 cd rook/cluster/examples/kubernetes/ceph

If you have deployed the Rook Operator or the Ceph cluster into a different namespace than rook-ceph, see the Update common resources and CRDs section for instructions on how to change the default namespaces in common.yaml.

Then apply the latest changes from v1.6 and update the Rook Operator image.

 kubectl apply -f common.yaml -f crds.yaml
 kubectl -n rook-ceph set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.6.2

As exemplified above, it is a good practice to update Rook-Ceph common resources from the example manifests before any update. The common resources and CRDs might not be updated with every release, but K8s will only apply updates to the ones that changed.

Watch the logs from the operator pod to ensure that nothing is amiss, but that should be it.