mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
OCPBUGS-44063: Removing RHEL 9.2 update requirement 4.15+
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
2e96f203dc
commit
42afa1283b
@@ -242,7 +242,7 @@ For {product-title} version 4.18, RHCOS is based on RHEL version 9.4, which upda
|
||||
* IBM Power architecture requires Power 9 ISA
|
||||
* s390x architecture requires z14 ISA
|
||||
|
||||
For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/9.0_release_notes/index#architectures[RHEL Architectures].
|
||||
For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/9.2_release_notes/index#architectures[Architectures] ({op-system-base} documentation).
|
||||
====
|
||||
|
||||
ifdef::azure[]
|
||||
|
||||
@@ -44,7 +44,7 @@ You must ensure that the time on your ESXi hosts is synchronized before you inst
|
||||
|
||||
|CPU micro-architecture
|
||||
|x86-64-v2 or higher
|
||||
|OpenShift 4.13 and later are based on RHEL 9.2 host operating system which raised the microarchitecture requirements to x86-64-v2. See the link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/9.0_release_notes/index#architectures[RHEL Microarchitecture requirements documentation]. You can verify compatibility by following the procedures outlined in link:https://access.redhat.com/solutions/7052996[this KCS article].
|
||||
|{product-title} version 4.13 and later are based on the {op-system-base} 9.2 host operating system, which raised the microarchitecture requirements to x86-64-v2. See link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/9.2_release_notes/index#architectures[Architectures] in the {op-system-base} documentation.
|
||||
|===
|
||||
|
||||
[IMPORTANT]
|
||||
|
||||
@@ -14,16 +14,6 @@ To do: Remove this comment once 4.13 docs are EOL.
|
||||
|
||||
Learn more about administrative tasks that cluster admins must perform to successfully initialize an update, as well as optional guidelines for ensuring a successful update.
|
||||
|
||||
[id="rhel-micro-architecture-update-requirements"]
|
||||
== {op-system-base} 9.2 micro-architecture requirement change
|
||||
|
||||
{product-title} is now based on the {op-system-base} 9.2 host operating system. The micro-architecture requirements are now increased to x86_64-v2, Power9, and Z14. See the link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/9.0_release_notes/index#architectures[RHEL micro-architecture requirements documentation]. You can verify compatibility before updating by following the procedures outlined in this link:https://access.redhat.com/solutions/7052996[KCS article].
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
Without the correct micro-architecture requirements, the update process will fail. Make sure you purchase the appropriate subscription for each architecture. For more information, see link:https://access.redhat.com/products/red-hat-enterprise-linux#addl-arch[Get Started with Red Hat Enterprise Linux - additional architectures]
|
||||
====
|
||||
|
||||
[id="kube-api-removals_{context}"]
|
||||
== Kubernetes API removals
|
||||
|
||||
|
||||
Reference in New Issue
Block a user