You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/main/user-guides/upgrades.md
+55-48Lines changed: 55 additions & 48 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,35 +65,26 @@ If you have used helm v3.13 or above to install their chart, and not used helm's
65
65
Feel free to reach out via our [communication channels](../community.md).
66
66
:::
67
67
68
-
69
68
## Local Storage Upgrade
70
69
71
70
The upgrade process for Local PV Hostpath, Local PV LVM, and Local PV ZFS are largely identical, with a few changes in helm values depending on the Local PV Storage variant we are upgrading from.
72
71
73
-
### From 4.x to 4.1.1 or Higher
74
-
75
-
This section describes the Local Storage upgrade from OpenEBS chart 4.x to OpenEBS 4.1.1 or higher.
If upgrading from Local PV LVM or Local PV ZFS storage solution, additional helm values must be specified with the above command to prevent upgrade process conflicts. The installed CRDs in 3.x would conflict with the CRDs in 4.1.1 as the chart structure has changed. Hence, they must be disabled.
87
+
If upgrading from Local PV LVM or Local PV ZFS storage solution, additional helm values must be specified with the above command to prevent upgrade process conflicts. The installed CRDs in 3.x would conflict with the CRDs in 4.2 as the chart structure has changed. Hence, they must be disabled.
97
88
98
89
- For Upgrade from Local PV LVM, use
99
90
@@ -112,24 +103,53 @@ Add both of these options, if your chart has both of these enabled.
112
103
113
104
2. Verify that the CRDs, Volumes, Snapshots, and StoragePools are not affected by the upgrade process.
114
105
106
+
### From 4.x to 4.2
107
+
108
+
This section describes the Local Storage upgrade from OpenEBS chart 4.x to OpenEBS 4.2.
2. Verify that the CRDs, Volumes, Snapshots, and StoragePools are not affected by the upgrade process.
117
+
115
118
## Replicated Storage Upgrade
116
119
117
-
### From 4.x to 4.1.1 or Higher
120
+
:::note
121
+
Downgrades are not supported.
122
+
:::
123
+
124
+
### From 3.x to 4.2
125
+
126
+
This section describes the Replicated Storage upgrade from OpenEBS Umbrella chart 3.x to OpenEBS 4.2.
118
127
119
-
This section describes the Replicated Storage upgrade from OpenEBS Umbrella chart 4.x to OpenEBS 4.1.1 or higher.
128
+
1. Start the helm upgrade process with the new chart, i.e. 4.2 by using the below command:
129
+
130
+
:::caution
131
+
Upgrades from 3.x to 4.x require the option `--set mayastor.agents.core.rebuild.partial.enabled=false` in the **helm upgrade** command to ensure data consistency during the upgrade. Upgrades from 4.x onwards to newer versions do not require it.
120
132
121
-
1. Start the helm upgrade process with the new chart, i.e. 4.1.1 by using the below command:
133
+
This applies to the **kubectl mayastor upgrade** command as well, if you're using the `mayastor/mayastor` chart and not the `openebs/openebs` chart: `kubectl mayastor upgrade --set agents.core.rebuild.partial.enabled=false`
2. Verify that the CRDs, Volumes, Snapshots and StoragePools are unaffected by the upgrade process.
143
+
:::important
144
+
The `--reuse-values` option should not be used with `helm upgrade`, as it may cause the pre-upgrade images to be used instead of the new images. Instead the `--reset-then-reuse-values` option is recommended.
145
+
:::
146
+
147
+
2. Verify that the CRDs, Volumes, Snapshots, and StoragePools are not affected by the upgrade process.
128
148
129
149
3. Start the Replicated Storage upgrade process by using the kubectl mayastor plugin v2.7.1.
4. Once the upgrade process is completed, all the volumes and pools should be online.
153
173
154
-
### From 3.x to 4.1.1
174
+
5. If you have disabled the partial rebuild during the upgrade, re-enable it by adding the value `--set mayastor.agents.core.rebuild.partial.enabled=true` in the upgrade command.
155
175
156
-
This section describes the Replicated Storage upgrade from OpenEBS Umbrella chart 3.x to OpenEBS 4.1.1.
1. Start the helm upgrade process with the new chart, i.e. 4.1.1 by using the below command:
181
+
### From 4.x to 4.2
159
182
160
-
:::caution
161
-
Upgrades from 3.x to 4.x require the option `--set mayastor.agents.core.rebuild.partial.enabled=false` in the **helm upgrade** command to ensure data consistency during the upgrade. Upgrades from 4.x onwards to newer versions do not require it.
183
+
This section describes the Replicated Storage upgrade from OpenEBS Umbrella chart 4.x to OpenEBS 4.2.
162
184
163
-
This applies to the **kubectl mayastor upgrade** command as well, if you're using the `mayastor/mayastor` chart and not the `openebs/openebs` chart: `kubectl mayastor upgrade --set agents.core.rebuild.partial.enabled=false`
164
-
:::
185
+
1. Start the helm upgrade process with the new chart, i.e. 4.2 by using the below command:
165
186
166
187
```
167
-
# Add the option --set mayastor.agents.core.rebuild.partial.enabled=false if
The `--reuse-values` option should not be used with `helm upgrade`, as it may cause the pre-upgrade images to be used instead of the new images. Instead the `--reset-then-reuse-values` option is recommended.
175
-
:::
176
-
177
-
2. Verify that the CRDs, Volumes, Snapshots, and StoragePools are not affected by the upgrade process.
191
+
2. Verify that the CRDs, Volumes, Snapshots and StoragePools are unaffected by the upgrade process.
178
192
179
193
3. Start the Replicated Storage upgrade process by using the kubectl mayastor plugin v2.7.1.
4. Once the upgrade process is completed, all the volumes and pools should be online.
203
217
204
-
5. If you have disabled the partial rebuild during the upgrade, re-enable it by adding the value `--set mayastor.agents.core.rebuild.partial.enabled=true` in the upgrade command.
0 commit comments