mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
32 lines
1.2 KiB
Plaintext
32 lines
1.2 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * edge_computing/day_2_core_cnf_clusters/updating/update-welcome.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="update-introduction_{context}"]
|
|
= Cluster updates for OpenShift clusters
|
|
|
|
[role="_abstract"]
|
|
Updating your cluster is a critical task that ensures that bugs and potential security vulnerabilities are patched.
|
|
Often, updates to cloud-native applications require additional functionality from the platform that comes when you update the cluster version.
|
|
You also must update the cluster periodically to ensure that the cluster platform version is supported.
|
|
|
|
You can minimize the effort required to stay current with updates by keeping up-to-date with EUS releases and upgrading to select important z-stream releases only.
|
|
|
|
[NOTE]
|
|
====
|
|
The update path for the cluster can vary depending on the size and topology of the cluster.
|
|
====
|
|
|
|
The following update scenarios are described:
|
|
|
|
* Control Plane Only updates
|
|
* Y-stream updates
|
|
* Z-stream updates
|
|
|
|
[IMPORTANT]
|
|
====
|
|
Control Plane Only updates were previously known as EUS-to-EUS updates.
|
|
Control Plane Only updates are only viable between even-numbered minor versions of {product-title}.
|
|
====
|