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/releases.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,18 +12,18 @@ description: This page contains list of supported OpenEBS releases.
12
12
**Release Date: 08 July 2024**
13
13
14
14
OpenEBS is a collection of data engines and operators to create different types of replicated and local persistent volumes for Kubernetes Stateful workloads. Kubernetes volumes can be provisioned via CSI Drivers or using Out-of-tree Provisioners.
15
-
The status of the various components as of v4.1.0 are as follows:
15
+
The status of the various components as of v4.1.1 are as follows:
@@ -99,7 +99,7 @@ The workaround is to delete the old pod so the new pod can get scheduled. Refer
99
99
100
100
## Related Information
101
101
102
-
OpenEBS Release notes are maintained in the GitHub repositories alongside the code and releases. For summary of what changes across all components in each release and to view the full Release Notes, see [OpenEBS Release 4.1](https://github.com/openebs/openebs/releases/tag/v4.1.0).
102
+
OpenEBS Release notes are maintained in the GitHub repositories alongside the code and releases. For summary of what changes across all components in each release and to view the full Release Notes, see [OpenEBS Release 4.1](https://github.com/openebs/openebs/releases/tag/v4.1.1).
103
103
104
104
See version specific Releases to view the legacy OpenEBS Releases.
Copy file name to clipboardExpand all lines: docs/main/user-guides/upgrades.md
+17-16Lines changed: 17 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ description: Upgrade to the latest OpenEBS version.
9
9
---
10
10
11
11
:::important
12
-
Upgrade from OpenEBS 3.x to OpenEBS 4.1.0 is only supported for the below storages installed from OpenEBS 3.x.
12
+
Upgrade from OpenEBS 3.x to OpenEBS 4.1.1 is only supported for the below storages installed from OpenEBS 3.x.
13
13
14
14
- Local PV Hostpath
15
15
- Local PV LVM
@@ -21,15 +21,15 @@ Refer to the [Migration documentation](../user-guides/data-migration/migration-o
21
21
22
22
## Overview
23
23
24
-
This upgrade flow allows the users to upgrade to the latest OpenEBS version 4.1.0 which is a unified installer for three Local Storages (a.k.a Local Engines):
24
+
This upgrade flow allows the users to upgrade to the latest OpenEBS version 4.1.1 which is a unified installer for three Local Storages (a.k.a Local Engines):
25
25
- Local PV HostPath
26
26
- Local PV LVM
27
27
- Local PV ZFS
28
28
29
29
and one Replicated Storage (a.k.a Replicated Engine):
30
30
- Replicated PV Mayastor
31
31
32
-
As a part of upgrade to OpenEBS 4.1.0, the helm chart would install all four engines irrespective of the engine the user was using prior to the upgrade.
32
+
As a part of upgrade to OpenEBS 4.1.1, the helm chart would install all four engines irrespective of the engine the user was using prior to the upgrade.
33
33
34
34
:::info
35
35
During the upgrade, advanced users who are only interested in Local PV Storage, can disable the Replicated PV Mayastor by setting the below option:
@@ -68,16 +68,16 @@ Feel free to reach out via our communication channels.
68
68
69
69
## Local Storage
70
70
71
-
This section describes the Local Storage upgrade from OpenEBS chart 3.x to OpenEBS 4.1.0. 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.
71
+
This section describes the Local Storage upgrade from OpenEBS chart 3.x to OpenEBS 4.1.1. 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.
If the upgrade is 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 be in conflict with the CRDs in 4.1.0 as the chart structure has changed. Hence, they must be disabled.
80
+
If the upgrade is 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 be in conflict with the CRDs in 4.1.1 as the chart structure has changed. Hence, they must be disabled.
81
81
82
82
83
83
- For Upgrade from Local PV LVM, use
@@ -99,25 +99,26 @@ Add both of these options, if your chart has both of these enabled.
99
99
100
100
## Replicated Storage
101
101
102
-
This section describes the Replicated Storage upgrade from OpenEBS Umbrella chart 3.x to OpenEBS 4.1.0.
102
+
This section describes the Replicated Storage upgrade from OpenEBS Umbrella chart 3.x to OpenEBS 4.1.1.
103
103
104
-
1. Start the helm upgrade process with the new chart, i.e. 4.1.0 by using the below command:
104
+
1. Start the helm upgrade process with the new chart, i.e. 4.1.1 by using the below command:
105
105
106
106
:::caution
107
-
Disable the partial rebuild during the upgrade from specific versions of OpenEBS (3.7.0, 3.8.0, 3.9.0 and 3.10.0) to OpenEBS 4.1.0 to ensure data consistency during upgrade. Input the value`--set mayastor.agents.core.rebuild.partial.enabled=false` in the **helm upgrade** command.
107
+
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 upgrade. Upgrades from 4.x onwards to newer version do not require it.
108
108
109
109
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`
4. Once the upgrade process completes, all the volumes and pools should be online.
144
145
145
146
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.
Copy file name to clipboardExpand all lines: docs/versioned_docs/version-4.1.x/releases.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,18 +12,18 @@ description: This page contains list of supported OpenEBS releases.
12
12
**Release Date: 08 July 2024**
13
13
14
14
OpenEBS is a collection of data engines and operators to create different types of replicated and local persistent volumes for Kubernetes Stateful workloads. Kubernetes volumes can be provisioned via CSI Drivers or using Out-of-tree Provisioners.
15
-
The status of the various components as of v4.1.0 are as follows:
15
+
The status of the various components as of v4.1.1 are as follows:
@@ -99,7 +99,7 @@ The workaround is to delete the old pod so the new pod can get scheduled. See th
99
99
100
100
## Related Information
101
101
102
-
OpenEBS Release notes are maintained in the GitHub repositories alongside the code and releases. For summary of what changes across all components in each release and to view the full Release Notes, see [OpenEBS Release 4.1](https://github.com/openebs/openebs/releases/tag/v4.1.0).
102
+
OpenEBS Release notes are maintained in the GitHub repositories alongside the code and releases. For summary of what changes across all components in each release and to view the full Release Notes, see [OpenEBS Release 4.1](https://github.com/openebs/openebs/releases/tag/v4.1.1).
103
103
104
104
See version specific Releases to view the legacy OpenEBS Releases.
Copy file name to clipboardExpand all lines: docs/versioned_docs/version-4.1.x/user-guides/upgrades.md
+17-16Lines changed: 17 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ description: Upgrade to the latest OpenEBS version.
9
9
---
10
10
11
11
:::important
12
-
Upgrade from OpenEBS 3.x to OpenEBS 4.1.0 is only supported for the below storages installed from OpenEBS 3.x.
12
+
Upgrade from OpenEBS 3.x to OpenEBS 4.1.1 is only supported for the below storages installed from OpenEBS 3.x.
13
13
14
14
- Local PV Hostpath
15
15
- Local PV LVM
@@ -21,15 +21,15 @@ See the [migration documentation](../user-guides/data-migration/migration-overvi
21
21
22
22
## Overview
23
23
24
-
This upgrade flow allows the users to upgrade to the latest OpenEBS version 4.1.0 which is a unified installer for three Local Storages (a.k.a Local Engines):
24
+
This upgrade flow allows the users to upgrade to the latest OpenEBS version 4.1.1 which is a unified installer for three Local Storages (a.k.a Local Engines):
25
25
- Local PV HostPath
26
26
- Local PV LVM
27
27
- Local PV ZFS
28
28
29
29
and one Replicated Storage (a.k.a Replicated Engine):
30
30
- Replicated PV Mayastor
31
31
32
-
As a part of upgrade to OpenEBS 4.1.0, the helm chart would install all four engines irrespective of the engine the user was using prior to the upgrade.
32
+
As a part of upgrade to OpenEBS 4.1.1, the helm chart would install all four engines irrespective of the engine the user was using prior to the upgrade.
33
33
34
34
:::info
35
35
During the upgrade, advanced users who are only interested in Local PV Storage, can disable the Replicated PV Mayastor by setting the below option:
@@ -68,16 +68,16 @@ Feel free to reach out via our communication channels.
68
68
69
69
## Local Storage
70
70
71
-
This section describes the Local Storage upgrade from OpenEBS chart 3.x to OpenEBS 4.1.0. 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.
71
+
This section describes the Local Storage upgrade from OpenEBS chart 3.x to OpenEBS 4.1.1. 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.
If the upgrade is 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 be in conflict with the CRDs in 4.1.0 as the chart structure has changed. Hence, they must be disabled.
80
+
If the upgrade is 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 be in conflict with the CRDs in 4.1.1 as the chart structure has changed. Hence, they must be disabled.
81
81
82
82
83
83
- For Upgrade from Local PV LVM, use
@@ -99,25 +99,26 @@ Add both of these options, if your chart has both of these enabled.
99
99
100
100
## Replicated Storage
101
101
102
-
This section describes the Replicated Storage upgrade from OpenEBS Umbrella chart 3.x to OpenEBS 4.1.0.
102
+
This section describes the Replicated Storage upgrade from OpenEBS Umbrella chart 3.x to OpenEBS 4.1.1.
103
103
104
-
1. Start the helm upgrade process with the new chart, i.e. 4.1.0 by using the below command:
104
+
1. Start the helm upgrade process with the new chart, i.e. 4.1.1 by using the below command:
105
105
106
106
:::caution
107
-
Disable the partial rebuild during the upgrade from specific versions of OpenEBS (3.7.0, 3.8.0, 3.9.0 and 3.10.0) to OpenEBS 4.1.0 to ensure data consistency during upgrade. Input the value`--set mayastor.agents.core.rebuild.partial.enabled=false` in the **helm upgrade** command.
107
+
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 upgrade. Upgrades from 4.x onwards to newer version do not require it.
108
108
109
109
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`
4. Once the upgrade process completes, all the volumes and pools should be online.
144
145
145
146
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