Skip to content

Commit

Permalink
chore(upgrade): update upgrade README with 2.7.0 steps
Browse files Browse the repository at this point in the history 
Signed-off-by: shubham <shubham.bajpai@mayadata.io>
  • Loading branch information
@shubham14bajpai @kmova
shubham14bajpai authored and kmova committed Mar 16, 2021
1 parent bf7891a commit cecabdd
Showing 1 changed file with 12 additions and 12 deletions.
24 changes: 12 additions & 12 deletions k8s/upgrades/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ If already using CSPC pools and cStor CSI volumes they can be upgraded from `1.1

This document describes the steps for the following OpenEBS Upgrade paths:

- Upgrade from 1.0.0 or later to a newer release up to 2.6.0
- Upgrade from 1.6.0 or later to a newer release up to 2.7.0

For other upgrade paths of earlier releases, please refer to the respective directories.
Example:
Expand All @@ -38,7 +38,7 @@ The upgrade of OpenEBS is a three step process:

**Note: It is mandatory to make sure to that all OpenEBS control plane
and data plane components are running with the expected version before the upgrade.**
- **For upgrading to the latest release (2.6.0), the previous version should be minimum 1.0.0 **
- **For upgrading to the latest release (2.7.0), the previous version should be minimum 1.6.0 **

**Note: All steps described in this document need to be performed from a
machine that has access to Kubernetes master**
Expand Down Expand Up @@ -119,8 +119,8 @@ the openebs-operator.yaml for your cluster, you will have to download the
desired openebs-operator.yaml and customize it again**

```
#Upgrade to OpenEBS control plane components to desired version. Say 2.6.0
$ kubectl apply -f https://openebs.github.io/charts/2.6.0/openebs-operator.yaml
#Upgrade to OpenEBS control plane components to desired version. Say 2.7.0
$ kubectl apply -f https://openebs.github.io/charts/2.7.0/openebs-operator.yaml
```
### Upgrade using helm chart (using openebs/openebs, openebs-charts repo, etc.,):
Expand All @@ -135,13 +135,13 @@ latest openebs/openebs chart.
- If the default values seem appropriate, you can use the below commands to
update OpenEBS. [More](https://hub.helm.sh/charts/openebs/openebs) details about the specific chart version.
```sh
$ helm upgrade --reset-values <release name> openebs/openebs --version 2.6.0
$ helm upgrade --reset-values <release name> openebs/openebs --version 2.7.0
```
- If not, customize the values into your copy (say custom-values.yaml),
by copying the content from above default yamls and edit the values to
suite your environment. You can upgrade using your custom values using:
```sh
$ helm upgrade <release name> openebs/openebs --version 2.6.0 -f custom-values.yaml`
$ helm upgrade <release name> openebs/openebs --version 2.7.0 -f custom-values.yaml`
```

### Using customized operator YAML or helm chart.
Expand Down Expand Up @@ -172,9 +172,9 @@ backup of the data before starting the below upgrade procedure.
as the new multi-arch images are not pushed to quay.
It can also be used specify any other private repository or airgap prefix in use.
- Before proceeding with the upgrade of the OpenEBS Data Plane components like cStor or Jiva, verify that OpenEBS Control plane is indeed in desired version
You can use the following command to verify components are in 2.6.0:
You can use the following command to verify components are in 2.7.0:
```sh
$ kubectl get pods -n openebs -l openebs.io/version=2.6.0
$ kubectl get pods -n openebs -l openebs.io/version=2.7.0
```
The above command should show that the control plane components are upgrade.
The output should look like below:
Expand Down Expand Up @@ -206,7 +206,7 @@ using Kubernetes Job spec.

The following instructions provide details on how to create your Upgrade Job specs.
Please ensure the `from` and `to` versions are as per your upgrade path. The below
examples show upgrading from 1.12.0 to 2.6.0.
examples show upgrading from 1.12.0 to 2.7.0.

### Upgrade the OpenEBS Jiva PV

Expand Down Expand Up @@ -260,7 +260,7 @@ spec:
- "--from-version=1.12.0"
# --to-version is the version desired upgrade version
- "--to-version=2.6.0"
- "--to-version=2.7.0"
# If the pools and volumes images have the prefix `quay.io/openebs/`
# then please add this flag as the new multi-arch images are not pushed to quay.
Expand Down Expand Up @@ -352,7 +352,7 @@ spec:
- "--from-version=1.12.0"
# --to-version is the version desired upgrade version
- "--to-version=2.6.0"
- "--to-version=2.7.0"
# If the pools and volumes images have the prefix `quay.io/openebs/`
# then please add this flag as the new multi-arch images are not pushed to quay.
Expand Down Expand Up @@ -434,7 +434,7 @@ spec:
- "--from-version=1.12.0"
# --to-version is the version desired upgrade version
- "--to-version=2.6.0"
- "--to-version=2.7.0"
# If the pools and volumes images have the prefix `quay.io/openebs/`
# then please add this flag as the new multi-arch images are not pushed to quay.
Expand Down

0 comments on commit cecabdd

Please sign in to comment.