// Module included in the following assemblies:
//
// * updating/updating_a_cluster/control-plane-only-update.adoc

:_mod-docs-content-type: PROCEDURE
[id="updating-control-plane-only-update_{context}"]
= Performing a Control Plane Only update

[role="_abstract"]
You can perform a Control Plane Only update by pausing all non-`master` machine config pools, performing updates from {product-title} <4.y> to <4.y+1> to <4.y+2>, then unpausing the machine config pools.

Following this procedure reduces the total update duration and the number of times worker nodes are restarted.

.Prerequisites

* You reviewed the release notes for {product-title} <4.y+1> and <4.y+2>.
* You reviewed the release notes and product lifecycles for any layered products and Operator Lifecycle Manager (OLM) Operators. Some products and OLM Operators might require updates either before or during a Control Plane Only update.
* You are familiar with version-specific prerequisites, such as the removal of deprecated APIs, that are required before updating from {product-title} <4.y+1> to <4.y+2>.
* If your cluster uses in-tree vSphere volumes, you updated vSphere to version 7.0u3L+ or 8.0u2+.
+
[IMPORTANT]
====
If you do not update vSphere to 7.0u3L+ or 8.0u2+ before initiating an {product-title} update, known issues might occur with your cluster after the update.
For more information, see link:https://access.redhat.com/node/7011683[Known Issues with OpenShift 4.12 to 4.13 or 4.13 to 4.14 vSphere CSI Storage Migration].
====
