mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2024-09-19 15:09:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: add udgrade from v3.4 to v3.5

Browse Source 
This commit adds the upgrade documentation from v3.4 to v3.5

Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
This commit is contained in:
Humble Chirammal 2022-01-13 11:07:42 +05:30 committed by mergify[bot]
parent dbb523c150
commit b151325871
1 changed files with 15 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/ceph-csi-upgrade.md
View File

@ -6,6 +6,7 @@
- [Snapshot API version support matrix](#snapshot-api-version-support-matrix) - [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.2 to v3.3](#upgrading-from-v32-to-v33)
- [Upgrading from v3.3 to v3.4](#upgrading-from-v33-to-v34) - [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) - [Upgrading CephFS](#upgrading-cephfs)
- [1. Upgrade CephFS Provisioner resources](#1-upgrade-cephfs-provisioner-resources) - [1. Upgrade CephFS Provisioner resources](#1-upgrade-cephfs-provisioner-resources)
- [1.1 Update the CephFS Provisioner RBAC](#11-update-the-cephfs-provisioner-rbac) - [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. fuse client as of now.
This guide will walk you through the steps to upgrade the software in a cluster 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 ### 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 ## 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 **Ceph-csi releases from devel are expressly unsupported.** It is strongly
recommended that you use [official recommended that you use [official
releases](https://github.com/ceph/ceph-csi/releases) of Ceph-csi. Unreleased 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 branch can have functionality changed and even removed at any time without
compatibility support and without prior notice. compatibility support and without prior notice.
**Also, we do not recommend any direct upgrades to 3.4 except from 3.3 to 3.4.** **Also, we do not recommend any direct upgrades to 3.5 except from 3.4 to 3.5.**
For example, upgrading from 3.2 to 3.4 is not recommended. 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 ```bash
git clone https://github.com/ceph/ceph-csi.git git clone https://github.com/ceph/ceph-csi.git
cd ./ceph-csi cd ./ceph-csi
git checkout v3.4.0 git checkout v3.5.0
``` ```
**Note:** While upgrading please Ignore warning messages from kubectl output
```console ```console
Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply 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
Upgrading cephfs csi includes upgrade of cephfs driver and as well as 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 - The pod deletion causes the pods to be restarted and updated automatically
on the node. 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 ### Upgrading RBD
@ -274,7 +280,7 @@ daemonset.apps/csi-rbdplugin configured
service/csi-metrics-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 ### CSI Sidecar containers consideration