mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2024-12-18 02:50:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: add steps for upgrading from 3.10 to 3.11

Browse Source 
This commit adds steps for upgrading from 3.10
to 3.11.

Signed-off-by: Rakshith R <rar@redhat.com>
This commit is contained in:
Rakshith R 2024-04-01 14:52:04 +05:30 committed by mergify[bot]
parent 0e4991ac8b
commit 04670a8b4d
1 changed files with 13 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -4,7 +4,7 @@
- [Pre-upgrade considerations](#pre-upgrade-considerations) - [Pre-upgrade considerations](#pre-upgrade-considerations)
- [Snapshot-controller and snapshot crd](#snapshot-controller-and-snapshot-crd) - [Snapshot-controller and snapshot crd](#snapshot-controller-and-snapshot-crd)
- [Upgrading from previous releases](#upgrading-from-previous-releases) - [Upgrading from previous releases](#upgrading-from-previous-releases)
- [Upgrading from v3.9 to v3.10](#upgrading-from-v39-to-v310) - [Upgrading from v3.10 to v3.11](#upgrading-from-v310-to-v311)
- [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)
@ -49,7 +49,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.9 to v3.10 from v3.10 to v3.11
### Snapshot-controller and snapshot crd ### Snapshot-controller and snapshot crd
@ -77,8 +77,10 @@ To upgrade from previous releases, refer to the following:
to upgrade from cephcsi v3.7 to v3.8 to upgrade from cephcsi v3.7 to v3.8
- [upgrade-from-v3.8-v3.9](https://github.com/ceph/ceph-csi/blob/v3.9.0/docs/ceph-csi-upgrade.md) - [upgrade-from-v3.8-v3.9](https://github.com/ceph/ceph-csi/blob/v3.9.0/docs/ceph-csi-upgrade.md)
to upgrade from cephcsi v3.8 to v3.9 to upgrade from cephcsi v3.8 to v3.9
- [upgrade-from-v3.9-v3.10](https://github.com/ceph/ceph-csi/blob/v3.10.0/docs/ceph-csi-upgrade.md)
to upgrade from cephcsi v3.9 to v3.10
## Upgrading from v3.9 to v3.10 ## Upgrading from v3.10 to v3.11
**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
@ -88,19 +90,19 @@ 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.10 except from 3.9 to 3.10.** **Also, we do not recommend any direct upgrades to 3.11 except from 3.10 to 3.11.**
For example, upgrading from 3.8 to 3.10 is not recommended. For example, upgrading from 3.8 to 3.11 is not recommended.
**Refer to the Breaking Changes Section in the **Refer to the Breaking Changes Section in the
[release notes](https://github.com/ceph/ceph-csi/releases/tag/v3.10.0) before [release notes](https://github.com/ceph/ceph-csi/releases/tag/v3.11.0) before
proceeding further.** proceeding further.**
git checkout v3.10.0 tag git checkout v3.11.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.10.0 git checkout v3.11.0
``` ```
```console ```console
@ -222,7 +224,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.9 to v3.10 we have successfully upgraded cephfs csi from v3.10 to v3.11
### Upgrading RBD ### Upgrading RBD
@ -286,7 +288,7 @@ daemonset.apps/csi-rbdplugin configured
service/csi-metrics-rbdplugin configured service/csi-metrics-rbdplugin configured
``` ```
we have successfully upgraded RBD csi from v3.9 to v3.10 we have successfully upgraded RBD csi from v3.10 to v3.11
### Upgrading NFS ### Upgrading NFS
@ -348,7 +350,7 @@ daemonset.apps/csi-nfsplugin configured
service/csi-metrics-nfsplugin configured service/csi-metrics-nfsplugin configured
``` ```
we have successfully upgraded nfs csi from v3.9 to v3.10 we have successfully upgraded nfs csi from v3.10 to v3.11
### CSI Sidecar containers consideration ### CSI Sidecar containers consideration