From 9e7c3c9a7c4b772f6844b65d9868ffe3f5cfffa0 Mon Sep 17 00:00:00 2001 From: Humble Chirammal Date: Thu, 13 Jan 2022 11:07:42 +0530 Subject: [PATCH] doc: add udgrade from v3.4 to v3.5 This commit adds the upgrade documentation from v3.4 to v3.5 Signed-off-by: Humble Chirammal (cherry picked from commit b15132587164c408f1717e1c8b3938692059df50) --- docs/ceph-csi-upgrade.md | 24 +++++++++++++++--------- 1 file changed, 15 insertions(+), 9 deletions(-) diff --git a/docs/ceph-csi-upgrade.md b/docs/ceph-csi-upgrade.md index 0bc8b5905..6d759b288 100644 --- a/docs/ceph-csi-upgrade.md +++ b/docs/ceph-csi-upgrade.md @@ -6,6 +6,7 @@ - [Snapshot API version support matrix](#snapshot-api-version-support-matrix) - [Upgrading from v3.2 to v3.3](#upgrading-from-v32-to-v33) - [Upgrading from v3.3 to v3.4](#upgrading-from-v33-to-v34) + - [Upgrading from v3.4 to v3.5](#upgrading-from-v34-to-v35) - [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) @@ -43,7 +44,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.3 to v3.4 +from v3.4 to v3.5 ### Snapshot-controller and snapshot crd @@ -67,6 +68,11 @@ to upgrade from cephcsi v3.2 to v3.3 ## Upgrading from v3.3 to v3.4 +Refer [upgrade-from-v3.3-v3.4](https://github.com/ceph/ceph-csi/blob/v3.4.0/docs/ceph-csi-upgrade.md) +to upgrade from cephcsi v3.3 to v3.4 + +## Upgrading from v3.4 to v3.5 + **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 @@ -75,23 +81,23 @@ 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.4 except from 3.3 to 3.4.** -For example, upgrading from 3.2 to 3.4 is not recommended. +**Also, we do not recommend any direct upgrades to 3.5 except from 3.4 to 3.5.** +For example, upgrading from 3.3 to 3.5 is not recommended. -git checkout v3.4.0 tag +git checkout v3.5.0 tag ```bash git clone https://github.com/ceph/ceph-csi.git cd ./ceph-csi -git checkout v3.4.0 +git checkout v3.5.0 ``` -**Note:** While upgrading please Ignore warning messages from kubectl output - ```console Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply ``` +**Note:** While upgrading please Ignore above warning messages from kubectl output + ### Upgrading CephFS Upgrading cephfs csi includes upgrade of cephfs driver and as well as @@ -208,7 +214,7 @@ For each node: - The pod deletion causes the pods to be restarted and updated automatically on the node. -we have successfully upgraded cephfs csi from v3.3 to v3.4 +we have successfully upgraded cephfs csi from v3.4 to v3.5 ### Upgrading RBD @@ -274,7 +280,7 @@ daemonset.apps/csi-rbdplugin configured service/csi-metrics-rbdplugin configured ``` -we have successfully upgraded RBD csi from v3.3 to v3.4 +we have successfully upgraded RBD csi from v3.4 to v3.5 ### CSI Sidecar containers consideration