From d1cc7186a33195283637f4c83e050b67567d0e1f Mon Sep 17 00:00:00 2001 From: panigs7 Date: Fri, 25 Feb 2022 04:52:51 -0500 Subject: [PATCH] Operator docs changes to update versions references --- content/docs/csidriver/installation/operator/_index.md | 10 +++++----- content/docs/csidriver/release/operator.md | 2 +- content/docs/csidriver/upgradation/drivers/operator.md | 2 +- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/content/docs/csidriver/installation/operator/_index.md b/content/docs/csidriver/installation/operator/_index.md index 5c11ccaad5..8ceab18249 100644 --- a/content/docs/csidriver/installation/operator/_index.md +++ b/content/docs/csidriver/installation/operator/_index.md @@ -50,21 +50,21 @@ If you have installed an old version of the `dell-csi-operator` which was availa #### Full list of CSI Drivers and versions supported by the Dell CSI Operator | CSI Driver | Version | ConfigVersion | Kubernetes Version | OpenShift Version | | ------------------ | --------- | -------------- | -------------------- | --------------------- | -| CSI PowerMax | 1.7 | v6 | 1.19, 1.20, 1.21 | 4.6, 4.7 | | CSI PowerMax | 2.0.0 | v2.0.0 | 1.20, 1.21, 1.22 | 4.6 EUS, 4.7, 4.8 | | CSI PowerMax | 2.1.0 | v2.1.0 | 1.20, 1.21, 1.22 | 4.8, 4.8 EUS, 4.9 | -| CSI PowerFlex | 1.5 | v5 | 1.19, 1.20, 1.21 | 4.6, 4.7 | +| CSI PowerMax | 2.2.0 | v2.2.0 | 1.21, 1.22, 1.23 | 4.8, 4.8 EUS, 4.9 | | CSI PowerFlex | 2.0.0 | v2.0.0 | 1.20, 1.21, 1.22 | 4.6 EUS, 4.7, 4.8 | | CSI PowerFlex | 2.1.0 | v2.1.0 | 1.20, 1.21, 1.22 | 4.8, 4.8 EUS, 4.9 | -| CSI PowerScale | 1.6 | v6 | 1.19, 1.20, 1.21 | 4.6, 4.7 | +| CSI PowerFlex | 2.2.0 | v2.2.0 | 1.21, 1.22, 1.23 | 4.8, 4.8 EUS, 4.9 | | CSI PowerScale | 2.0.0 | v2.0.0 | 1.20, 1.21, 1.22 | 4.6 EUS, 4.7, 4.8 | | CSI PowerScale | 2.1.0 | v2.1.0 | 1.20, 1.21, 1.22 | 4.8, 4.8 EUS, 4.9 | -| CSI Unity | 1.6 | v5 | 1.19, 1.20, 1.21 | 4.6, 4.7 | +| CSI PowerScale | 2.2.0 | v2.2.0 | 1.21, 1.22, 1.23 | 4.8, 4.8 EUS, 4.9 | | CSI Unity | 2.0.0 | v2.0.0 | 1.20, 1.21, 1.22 | 4.6 EUS, 4.7, 4.8 | | CSI Unity | 2.1.0 | v2.1.0 | 1.20, 1.21, 1.22 | 4.8, 4.8 EUS, 4.9 | -| CSI PowerStore | 1.4 | v4 | 1.19, 1.20, 1.21 | 4.6, 4.7 | +| CSI Unity | 2.2.0 | v2.2.0 | 1.21, 1.22, 1.23 | 4.8, 4.8 EUS, 4.9 | | CSI PowerStore | 2.0.0 | v2.0.0 | 1.20, 1.21, 1.22 | 4.6 EUS, 4.7, 4.8 | | CSI PowerStore | 2.1.0 | v2.1.0 | 1.20, 1.21, 1.22 | 4.8, 4.8 EUS, 4.9 | +| CSI PowerStore | 2.2.0 | v2.2.0 | 1.21, 1.22, 1.23 | 4.8, 4.8 EUS, 4.9 |
diff --git a/content/docs/csidriver/release/operator.md b/content/docs/csidriver/release/operator.md index 06f5f4a65d..037e24091f 100644 --- a/content/docs/csidriver/release/operator.md +++ b/content/docs/csidriver/release/operator.md @@ -5,7 +5,7 @@ description: Release notes for Dell CSI Operator ## Release Notes - Dell CSI Operator 1.7.0 ->**Note:** There will be a delay in certification of Dell CSI Operator 1.6.0 and it will not be available for download from the Red Hat OpenShift certified catalog right away. The operator will still be available for download from the Red Hat OpenShift Community Catalog soon after the 1.6.0 release. +>**Note:** There will be a delay in certification of Dell CSI Operator 1.7.0 and it will not be available for download from the Red Hat OpenShift certified catalog right away. The operator will still be available for download from the Red Hat OpenShift Community Catalog soon after the 1.7.0 release. ### New Features/Changes diff --git a/content/docs/csidriver/upgradation/drivers/operator.md b/content/docs/csidriver/upgradation/drivers/operator.md index 78ab08b226..0add7dac64 100644 --- a/content/docs/csidriver/upgradation/drivers/operator.md +++ b/content/docs/csidriver/upgradation/drivers/operator.md @@ -6,7 +6,7 @@ tags: weight: 1 Description: Upgrade Dell CSI Operator --- -To upgrade Dell CSI Operator from v1.2.0/v1.3.0 to v1.4.0/v1.5.0/v1.6.0, perform the following steps. +To upgrade Dell CSI Operator from v1.2.0/v1.3.0 to v1.4.0/v1.5.0/v1.6.0/v1.7.0, perform the following steps. Dell CSI Operator can be upgraded based on the supported platforms in one of the 2 ways: 1. Using script (for non-OLM based installation) 2. Using Operator Lifecycle Manager (OLM)