Disable boot image management
You can disable the boot image management feature so that the Machine Config Operator (MCO) no longer manages or updates the boot image in the affected machine sets. For example, you could disable this feature for the worker nodes in order to use a custom boot image that you do not want changed.
|
|
If you are updating an Microsoft Azure or VMware vSphere cluster from OpenShift Container Platform 4.21 to 4.22, and you have not configured the To allow the update, perform one of the following tasks:
|
You disable the boot image management feature for the control plane or worker machine sets in your cluster by editing the MachineConfiguration object.
|
|
The following table lists the platforms on which boot image management is available:
For all other platforms, the MCO does not automatically update the boot image with each cluster update. Images from the Google Cloud Marketplace or AWS Marketplace are not automatically updated. For clusters where automatic updates are disabled or not supported, you can manually update the boot image on your cluster. See "Manually updating the boot image" for information. The method to update or specify the image varies by platform. |
Disabling this feature does not rollback the nodes or machine sets to the originally-installed boot image. The machine sets retain the boot image version that was present when the feature was disabled and is not updated if the cluster is upgraded to a new OpenShift Container Platform version in the future. This feature has no effect on existing nodes.
If boot image management is disabled, you must update the boot image version that is used by the boot image skew enforcement feature to ensure that the boot image is current for your cluster. For more information, see "Boot image skew enforcement".
After disabling the feature, you can re-enable the feature at any time. For more information, see "Enabling updated boot images".
-
Edit the
MachineConfigurationobject, namedcluster, by using the following command::$ oc edit MachineConfiguration cluster -
Disable the feature for some or all of your machine sets by making one or both of the following changes:
-
Disable the feature for nodes in the worker machine sets by adding the following parameters:
apiVersion: operator.openshift.io/v1 kind: MachineConfiguration metadata: name: cluster spec: # ... managedBootImages: machineManagers: - apiGroup: machine.openshift.io resource: machinesets selection: mode: Nonewhere:
spec.managedBootImages-
Specifies the parameters for the boot image management feature.
spec.managedBootImages.machineManagers.apiGroup-
Specifies the API group. This must be
machine.openshift.io. spec.managedBootImages.machineManagers.resource-
Specifies that the
selection.modeparameter applies to worker nodes when a value ofmachinesetsis set. spec.managedBootImages.machineManagers.selection.mode-
When
None, specifies that the feature is disabled for the specified machine sets.
-
Disable the feature for nodes in the control plane machine sets by adding the following parameters:
apiVersion: operator.openshift.io/v1 kind: MachineConfiguration metadata: name: cluster spec: # ... managedBootImages: machineManagers: - apiGroup: machine.openshift.io resource: controlplanemachinesets selection: mode: Nonewhere:
spec.managedBootImages-
Specifies the parameters for the boot image management feature.
spec.managedBootImages.machineManagers.apiGroup-
Specifies the API group. This must be
machine.openshift.io. spec.managedBootImages.machineManagers.resource-
Specifies that the
selection.modeparameter applies to control plane nodes when a value ofcontrolplanemachinesetsis set. spec.managedBootImages.machineManagers.selection.mode-
When
None, specifies that the feature is disabled for the specified machine sets.
-
-
View the current state of the boot image management feature by using the following command to view the machine configuration object:
$ oc get machineconfiguration cluster -o yamlExample machine set with the boot image referencekind: MachineConfiguration metadata: name: cluster # ... status: conditions: - lastTransitionTime: "2025-05-01T20:11:49Z" message: Reconciled 2 of 4 MAPI MachineSets | Reconciled 0 of 0 CAPI MachineSets | Reconciled 0 of 0 CAPI MachineDeployments reason: BootImageUpdateConfigurationUpdated status: "True" type: BootImageUpdateProgressing - lastTransitionTime: "2025-05-01T19:30:13Z" message: 0 Degraded MAPI MachineSets | 0 Degraded CAPI MachineSets | 0 CAPI MachineDeployments reason: BootImageUpdateConfigurationUpdated status: "False" type: BootImageUpdateDegraded managedBootImagesStatus: machineManagers: - apiGroup: machine.openshift.io resource: controlplanemachinesets selection: mode: None - apiGroup: machine.openshift.io resource: machinesets selection: mode: Allwhere:
status.managedBootImagesStatus.machineManagers.selection.mode-
Specifies that the boot image management feature is disabled when set to
None. In this example, the boot image management feature is disabled for control plane machine sets and enabled for worker machine sets.