openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 09:46:53 +01:00
Code Issues Releases Activity

OCPBUGS-31451-rev: Revert vSphere instance support versions

Browse Source
This commit is contained in:
dfitzmau
2024-04-02 15:31:08 +01:00
committed by openshift-cherrypick-robot
parent 23340957e8
commit e3dcbd71db
2 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
modules/installation-vsphere-infrastructure.adoc
View File

@@ -9,8 +9,8 @@
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:
* Version 7.0 Update 3 or later
* Version 8.0 Update 2 or later
* Version 7.0 Update 2 or later
* Version 8.0 Update 1 or later
Both of these releases support Container Storage Interface (CSI) migration, which is enabled by default on {product-title} {product-version}.
@@ -21,8 +21,8 @@ You can host the VMware vSphere infrastructure on-premise or on a link:https://c
|===
|Virtual environment product |Required version
|VMware virtual hardware | 15 or later
|vSphere ESXi hosts | 7.0 Update 3 or later; 8.0 Update 2 or later
|vCenter host | 7.0 Update 3 or later; 8.0 Update 2 or later
|vSphere ESXi hosts | 7.0 Update 2 or later; 8.0 Update 1 or later
|vCenter host | 7.0 Update 2 or later; 8.0 Update 1 or later
|===
[IMPORTANT]
@@ -35,12 +35,12 @@ You must ensure that the time on your ESXi hosts is synchronized before you inst
|Component | Minimum supported versions |Description
|Hypervisor
|vSphere 7.0 Update 3 (or later) or vSphere 8.0 Update 2 (or later) with virtual hardware version 15
|vSphere 7.0 Update 2 (or later) or vSphere 8.0 Update 1 (or later) with virtual hardware version 15
|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.
|Optional: Networking (NSX-T)
|vSphere 7.0 Update 3 or later; vSphere 8.0 Update 2 or later
|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].
|vSphere 7.0 Update 2 or later; vSphere 8.0 Update 1 or later
|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].
|===
[IMPORTANT]

6
modules/vmware-csi-driver-reqs.adoc
View File

@@ -10,8 +10,8 @@
To install the vSphere Container Storage Interface (CSI) Driver Operator, the following requirements must be met:
* VMware vSphere version 7.0 Update 2 or later
* vCenter 7.0 Update 2 or later
* VMware vSphere version: 7.0 Update 2 or later; 8.0 Update 1 or later
* vCenter version: 7.0 Update 2 or later; 8.0 Update 1 or later
* Virtual machines of hardware version 15 or later
* No third-party vSphere CSI driver already installed in the cluster
@@ -26,6 +26,6 @@ You can create a custom role for the Container Storage Interface (CSI) driver, t
[IMPORTANT]
====
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.
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.
====