Skip to content

Commit 3844a16

Browse files
committed
OCPBUGS-31451-rev: Revert vSphere instance support versions
1 parent 6c4afc4 commit 3844a16

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

modules/installation-vsphere-infrastructure.adoc

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,8 @@
99

1010
You must install an {product-title} cluster on one of the following versions of a VMware vSphere instance that meets the requirements for the components that you use:
1111

12-
* Version 7.0 Update 3 or later
13-
* Version 8.0 Update 2 or later
12+
* Version 7.0 Update 2 or later
13+
* Version 8.0 Update 1 or later
1414
1515
Both of these releases support Container Storage Interface (CSI) migration, which is enabled by default on {product-title} {product-version}.
1616

@@ -21,8 +21,8 @@ You can host the VMware vSphere infrastructure on-premise or on a link:https://c
2121
|===
2222
|Virtual environment product |Required version
2323
|VMware virtual hardware | 15 or later
24-
|vSphere ESXi hosts | 7.0 Update 3 or later; 8.0 Update 2 or later
25-
|vCenter host | 7.0 Update 3 or later; 8.0 Update 2 or later
24+
|vSphere ESXi hosts | 7.0 Update 2 or later; 8.0 Update 1 or later
25+
|vCenter host | 7.0 Update 2 or later; 8.0 Update 1 or later
2626
|===
2727

2828
[IMPORTANT]
@@ -35,12 +35,12 @@ You must ensure that the time on your ESXi hosts is synchronized before you inst
3535
|Component | Minimum supported versions |Description
3636

3737
|Hypervisor
38-
|vSphere 7.0 Update 3 (or later) or vSphere 8.0 Update 2 (or later) with virtual hardware version 15
38+
|vSphere 7.0 Update 2 (or later) or vSphere 8.0 Update 1 (or later) with virtual hardware version 15
3939
|This hypervisor version is the minimum version that {op-system-first} supports. For more information about supported hardware on the latest version of {op-system-base-full} that is compatible with {op-system}, see link:https://catalog.redhat.com/hardware/search[Hardware] on the Red Hat Customer Portal.
4040

4141
|Optional: Networking (NSX-T)
42-
|vSphere 7.0 Update 3 or later; vSphere 8.0 Update 2 or later
43-
|At a minimum, vSphere 7.0 Update 3 or vSphere 8.0 Update 2 is required for {product-title}. For more information about the compatibility of NSX and {product-title}, see the Release Notes section of VMware's link:https://docs.vmware.com/en/VMware-NSX-Container-Plugin/index.html[NSX container plugin documentation].
42+
|vSphere 7.0 Update 2 or later; vSphere 8.0 Update 1 or later
43+
|At a minimum, vSphere 7.0 Update 2 or vSphere 8.0 Update 1 is required for {product-title}. For more information about the compatibility of NSX and {product-title}, see the Release Notes section of VMware's link:https://docs.vmware.com/en/VMware-NSX-Container-Plugin/index.html[NSX container plugin documentation].
4444
|===
4545

4646
[IMPORTANT]

modules/vmware-csi-driver-reqs.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@
1010

1111
To install the vSphere Container Storage Interface (CSI) Driver Operator, the following requirements must be met:
1212

13-
* VMware vSphere version 7.0 Update 2 or later
14-
* vCenter 7.0 Update 2 or later
13+
* VMware vSphere version: 7.0 Update 2 or later; 8.0 Update 1 or later
14+
* vCenter version: 7.0 Update 2 or later; 8.0 Update 1 or later
1515
* Virtual machines of hardware version 15 or later
1616
* No third-party vSphere CSI driver already installed in the cluster
1717
@@ -26,6 +26,6 @@ You can create a custom role for the Container Storage Interface (CSI) driver, t
2626

2727
[IMPORTANT]
2828
====
29-
Installing an {product-title} cluster in a vCenter is tested against a full list of privileges as described in the "Required vCenter account privileges" section. By adhering to the full list of privileges, you can reduce the possibility of unexpected and unsupported behaviors that might occur when creating a custom role with a set of restricted privileges.
29+
Installing an {product-title} cluster in a vCenter is tested against a full list of privileges as described in the "Required vCenter account privileges" section. By adhering to the full list of privileges, you can reduce the possibility of unexpected and unsupported behaviors that might occur when creating a custom role with a set of restricted privileges.
3030
====
3131

0 commit comments

Comments
 (0)