mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
52 lines
2.1 KiB
Plaintext
52 lines
2.1 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * machine_management/control_plane_machine_management/cpmso-managing-machines.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="cpmso-feat-replace_{context}"]
|
|
= Replacing a control plane machine
|
|
|
|
To replace a control plane machine in a cluster that has a control plane machine set, you delete the machine manually. The control plane machine set replaces the deleted machine with one using the specification in the control plane machine set custom resource (CR).
|
|
|
|
.Prerequisites
|
|
|
|
* If your cluster runs on {rh-openstack-first} and you need to evacuate a compute server, such as for an upgrade, you must disable the {rh-openstack} compute node that the machine runs on by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ openstack compute service set <target_node_host_name> nova-compute --disable
|
|
----
|
|
+
|
|
For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.1/html/configuring_the_compute_service_for_instance_creation/assembly_managing-instances_managing-instances#proc_preparing-to-migrate_migrating-instances[Preparing to migrate] in the {rh-openstack} documentation.
|
|
|
|
.Procedure
|
|
|
|
. List the control plane machines in your cluster by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get machines \
|
|
-l machine.openshift.io/cluster-api-machine-role==master \
|
|
-n openshift-machine-api
|
|
----
|
|
|
|
. Delete a control plane machine by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc delete machine \
|
|
-n openshift-machine-api \
|
|
<control_plane_machine_name> <1>
|
|
----
|
|
<1> Specify the name of the control plane machine to delete.
|
|
+
|
|
[NOTE]
|
|
====
|
|
If you delete multiple control plane machines, the control plane machine set replaces them according to the configured update strategy:
|
|
|
|
* For clusters that use the default `RollingUpdate` update strategy, the Operator replaces one machine at a time until each machine is replaced.
|
|
|
|
* For clusters that are configured to use the `OnDelete` update strategy, the Operator creates all of the required replacement machines simultaneously.
|
|
|
|
Both strategies maintain etcd health during control plane machine replacement.
|
|
==== |