Skip to content

Commit

Permalink
chore(upgrade): update upgrade README with 1.10.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 May 15, 2020
1 parent 66e6a04 commit 125006a
Showing 1 changed file with 28 additions and 26 deletions.
54 changes: 28 additions & 26 deletions k8s/upgrades/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,15 +4,16 @@

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

- Upgrade from 1.0.0 to any of 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0
- Upgrade from 1.1.0 to any of 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0
- Upgrade from 1.2.0 to any of 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0
- Upgrade from 1.3.0 to any of 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0
- Upgrade from 1.4.0 to 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0
- Upgrade from 1.5.0 to 1.6.0, 1.7.0, 1.8.0, 1.9.0
- Upgrade from 1.6.0 to 1.7.0, 1.8.0, 1.9.0
- Upgrade from 1.7.0 to 1.8.0, 1.9.0
- Upgrade from 1.8.0 to 1.9.0
- Upgrade from 1.0.0 to any of 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.10.0
- Upgrade from 1.1.0 to any of 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.10.0
- Upgrade from 1.2.0 to any of 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.10.0
- Upgrade from 1.3.0 to any of 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.10.0
- Upgrade from 1.4.0 to 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.10.0
- Upgrade from 1.5.0 to 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.10.0
- Upgrade from 1.6.0 to 1.7.0, 1.8.0, 1.9.0, 1.10.0
- Upgrade from 1.7.0 to 1.8.0, 1.9.0, 1.10.0
- Upgrade from 1.8.0 to 1.9.0, 1.10.0
- Upgrade from 1.9.0 to 1.10.0

For other upgrade paths, please refer to the respective directories.
Example, the steps to upgrade from 0.9.0 to 1.0.0 will be under [0.9.0-1.0.0](./0.9.0-1.0.0/).
Expand Down Expand Up @@ -41,6 +42,7 @@ and data plane components are running with expected version before the upgrade.*
- **For upgrading to 1.7.0, the previous version should be 1.0.0 or 1.1.0 or 1.2.0 or 1.3.0 or 1.4.0 or 1.5.0 or 1.6.0**
- **For upgrading to 1.8.0, the previous version should be 1.0.0 or 1.1.0 or 1.2.0 or 1.3.0 or 1.4.0 or 1.5.0 or 1.6.0 or 1.7.0**
- **For upgrading to 1.9.0, the previous version should be 1.0.0 or 1.1.0 or 1.2.0 or 1.3.0 or 1.4.0 or 1.5.0 or 1.6.0 or 1.7.0 or 1.8.0**
- **For upgrading to 1.10.0, the previous version should be 1.0.0 or 1.1.0 or 1.2.0 or 1.3.0 or 1.4.0 or 1.5.0 or 1.6.0 or 1.7.0 or 1.8.0 or 1.9.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 @@ -93,8 +95,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 1.9.0
$ kubectl apply -f https://openebs.github.io/charts/openebs-operator-1.9.0.yaml
#Upgrade to OpenEBS control plane components to desired version. Say 1.10.0
$ kubectl apply -f https://openebs.github.io/charts/openebs-operator-1.10.0.yaml
```

### Upgrade using helm chart (using stable/openebs, openebs-charts repo, etc.,):
Expand All @@ -109,13 +111,13 @@ latest stable/openebs chart.
- If the default values seem appropriate, you can use the below commands to
update OpenEBS. [More](https://hub.helm.sh/charts/stable/openebs) details about the specific chart version.
```sh
$ helm upgrade --reset-values <release name> stable/openebs --version 1.9.0
$ helm upgrade --reset-values <release name> stable/openebs --version 1.10.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> stable/openebs --version 1.9.0 -f custom-values.yaml`
$ helm upgrade <release name> stable/openebs --version 1.10.0 -f custom-values.yaml`
```

### Using customized operator YAML or helm chart.
Expand All @@ -141,9 +143,9 @@ backup of the data before starting the below upgrade procedure.**
**Note: 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 1.9.0:
You can use the following command to verify components are in 1.10.0:
```sh
$ kubectl get pods -n openebs -l openebs.io/version=1.9.0
$ kubectl get pods -n openebs -l openebs.io/version=1.10.0
```

The above command should show that the control plane components are upgrade.
Expand All @@ -166,7 +168,7 @@ OpenEBS maintainers via [Github Issue](https://github.com/openebs/openebs/issues

As you might have seen by now, control plane components and data plane components
work independently. Even after the OpenEBS Control Plane components have been
upgraded to 1.9.0, the Storage Pools and Volumes (both jiva and cStor)
upgraded to 1.10.0, the Storage Pools and Volumes (both jiva and cStor)
will continue to work with older versions.

You can use the below steps for upgrading cstor and jiva components.
Expand All @@ -177,7 +179,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.0.0 to 1.9.0.
examples show upgrading from 1.0.0 to 1.10.0.

### Upgrade the OpenEBS Jiva PV

Expand Down Expand Up @@ -231,14 +233,14 @@ spec:
- "--from-version=1.0.0"
# --to-version is the version desired upgrade version
- "--to-version=1.9.0"
- "--to-version=1.10.0"
# Bulk upgrade is supported from 1.9
# To make use of it, please provide the list of PVs
# as mentioned below
- "pvc-1bc3b45a-3023-4a8e-a94b-b457cf9529b4"
- "pvc-82a2d097-c666-4f29-820d-6b7e41541c11"
# For upgrades lesser than 1.9.0, use
# For upgrades lesser than 1.10.0, use
# '--pv-name=<pv_name> format as
# below commented line
# - "--pv-name=pvc-1bc3b45a-3023-4a8e-a94b-b457cf9529b4"
Expand All @@ -256,7 +258,7 @@ spec:
# the image version should be same as the --to-version mentioned above
# in the args of the job
image: quay.io/openebs/m-upgrade:1.9.0
image: quay.io/openebs/m-upgrade:1.10.0
imagePullPolicy: Always
restartPolicy: OnFailure
---
Expand Down Expand Up @@ -322,14 +324,14 @@ spec:
- "--from-version=1.0.0"
# --to-version is the version desired upgrade version
- "--to-version=1.9.0"
- "--to-version=1.10.0"
# Bulk upgrade is supported from 1.9
# To make use of it, please provide the list of SPCs
# as mentioned below
- "cstor-sparse-pool"
- "cstor-disk-pool"
# For upgrades lesser than 1.9.0, use
# For upgrades lesser than 1.10.0, use
# '--spc-name=<spc_name> format as
# below commented line
# - "--spc-name=cstor-sparse-pool"
Expand All @@ -347,7 +349,7 @@ spec:
# the image version should be same as the --to-version mentioned above
# in the args of the job
image: quay.io/openebs/m-upgrade:1.9.0
image: quay.io/openebs/m-upgrade:1.10.0
imagePullPolicy: Always
restartPolicy: OnFailure
---
Expand Down Expand Up @@ -403,14 +405,14 @@ spec:
- "--from-version=1.0.0"
# --to-version is the version desired upgrade version
- "--to-version=1.9.0"
- "--to-version=1.10.0"
# Bulk upgrade is supported from 1.9
# To make use of it, please provide the list of PVs
# as mentioned below
- "pvc-c630f6d5-afd2-11e9-8e79-42010a800065"
- "pvc-a4aba0e9-8ad3-4d18-9b34-5e6e7cea2eb3"
# For upgrades lesser than 1.9.0, use
# For upgrades lesser than 1.10.0, use
# '--pv-name=<pv_name> format as
# below commented line
# - "--pv-name=pvc-c630f6d5-afd2-11e9-8e79-42010a800065"
Expand All @@ -428,7 +430,7 @@ spec:
# the image version should be same as the --to-version mentioned above
# in the args of the job
image: quay.io/openebs/m-upgrade:1.9.0
image: quay.io/openebs/m-upgrade:1.10.0
imagePullPolicy: Always
restartPolicy: OnFailure
---
Expand Down

0 comments on commit 125006a

Please sign in to comment.