From 5de4c2a970aa3d5d6c50c85ea49856905c681313 Mon Sep 17 00:00:00 2001 From: Madhu Rajanna Date: Wed, 22 Feb 2023 08:31:35 +0100 Subject: [PATCH] doc: upgrade doc from 3.7 to 3.8 updating upgrade document from 3.7 to 3.8.0 Signed-off-by: Madhu Rajanna --- docs/ceph-csi-upgrade.md | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+), 8 deletions(-) diff --git a/docs/ceph-csi-upgrade.md b/docs/ceph-csi-upgrade.md index d62d1fae05f..491e8aefd7a 100644 --- a/docs/ceph-csi-upgrade.md +++ b/docs/ceph-csi-upgrade.md @@ -9,6 +9,7 @@ - [Upgrading from v3.4 to v3.5](#upgrading-from-v34-to-v35) - [Upgrading from v3.5 to v3.6](#upgrading-from-v35-to-v36) - [Upgrading from v3.6 to v3.7](#upgrading-from-v36-to-v37) + - [Upgrading from v3.7 to v3.8](#upgrading-from-v37-to-v38) - [Upgrading CephFS](#upgrading-cephfs) - [1. Upgrade CephFS Provisioner resources](#1-upgrade-cephfs-provisioner-resources) - [1.1 Update the CephFS Provisioner RBAC](#11-update-the-cephfs-provisioner-rbac) @@ -55,7 +56,7 @@ To avoid this issue in future upgrades, we recommend that you do not use the fuse client as of now. This guide will walk you through the steps to upgrade the software in a cluster -from v3.4 to v3.5 +from v3.7 to v3.8 ### Snapshot-controller and snapshot crd @@ -94,6 +95,11 @@ to upgrade from cephcsi v3.5 to v3.6 ## Upgrading from v3.6 to v3.7 +Refer [upgrade-from-v3.6-v3.7](https://github.com/ceph/ceph-csi/blob/v3.7.2/docs/ceph-csi-upgrade.md) +to upgrade from cephcsi v3.6 to v3.7 + +## Upgrading from v3.7 to v3.8 + **Ceph-csi releases from devel are expressly unsupported.** It is strongly recommended that you use [official releases](https://github.com/ceph/ceph-csi/releases) of Ceph-csi. Unreleased @@ -102,15 +108,15 @@ that will not be supported in the official releases. Builds from the devel branch can have functionality changed and even removed at any time without compatibility support and without prior notice. -**Also, we do not recommend any direct upgrades to 3.7 except from 3.6 to 3.7.** -For example, upgrading from 3.5 to 3.7 is not recommended. +**Also, we do not recommend any direct upgrades to 3.8 except from 3.7 to 3.8.** +For example, upgrading from 3.6 to 3.8 is not recommended. -git checkout v3.7.2 tag +git checkout v3.8.0 tag ```bash git clone https://github.com/ceph/ceph-csi.git cd ./ceph-csi -git checkout v3.7.2 +git checkout v3.8.0 ``` ```console @@ -246,7 +252,7 @@ kubectl delete role cephfs-csi-nodeplugin-psp --ignore-not-found kubectl delete rolebinding cephfs-csi-nodeplugin-psp --ignore-not-found ``` -we have successfully upgraded cephfs csi from v3.6 to v3.7 +we have successfully upgraded cephfs csi from v3.7 to v3.8 ### Upgrading RBD @@ -329,7 +335,7 @@ kubectl delete role rbd-csi-vault-token-review-psp --ignore-not-found kubectl delete rolebinding rbd-csi-vault-token-review-psp --ignore-not-found ``` -we have successfully upgraded RBD csi from v3.6 to v3.7 +we have successfully upgraded RBD csi from v3.7 to v3.8 ### Upgrading NFS @@ -391,7 +397,7 @@ daemonset.apps/csi-nfsplugin configured service/csi-metrics-nfsplugin configured ``` -we have successfully upgraded nfs csi from v3.6 to v3.7 +we have successfully upgraded nfs csi from v3.7 to v3.8 ### CSI Sidecar containers consideration