From cecabdd74cd8d44a9a9461b39be49c813bc2d540 Mon Sep 17 00:00:00 2001
From: shubham
Date: Sun, 14 Mar 2021 11:48:19 +0530
Subject: [PATCH] chore(upgrade): update upgrade README with 2.7.0 steps
Signed-off-by: shubham
---
k8s/upgrades/README.md | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/k8s/upgrades/README.md b/k8s/upgrades/README.md
index 5ae661abf7..cea93a49c2 100644
--- a/k8s/upgrades/README.md
+++ b/k8s/upgrades/README.md
@@ -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:
@@ -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**
@@ -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.,):
@@ -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 openebs/openebs --version 2.6.0
+ $ helm upgrade --reset-values 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 openebs/openebs --version 2.6.0 -f custom-values.yaml`
+ $ helm upgrade openebs/openebs --version 2.7.0 -f custom-values.yaml`
```
### Using customized operator YAML or helm chart.
@@ -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:
@@ -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
@@ -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.
@@ -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.
@@ -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.