From e31532eb2523290e6cb4975395b2ff3c4b50a911 Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Wed, 16 Jul 2025 14:12:05 -0400 Subject: [PATCH] MCO OCL correct an annotation --- modules/coreos-layering-configuring-on-remove.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/coreos-layering-configuring-on-remove.adoc b/modules/coreos-layering-configuring-on-remove.adoc index 85b8cc74a129..349d4000c637 100644 --- a/modules/coreos-layering-configuring-on-remove.adoc +++ b/modules/coreos-layering-configuring-on-remove.adoc @@ -10,4 +10,4 @@ To prevent the custom layered images from taking up excessive space in your regi The credentials provided by the registry push secret that you added to the `MachineOSBuild` object must grant the permission for deleting an image from the registry. If the delete permission is not provided, the image is not removed when you delete the `MachineOSBuild` object. -Note that the custom layered image is not deleted if the image is either currently in use on a node or is desired by the nodes, as indicated by the `machineconfiguration.openshift.io/currentConfig` or `machineconfiguration.openshift.io/desiredConfig` annotation on the node. +The custom layered image is not deleted if the image is either currently in use on a node or is desired by the nodes, as indicated by the `machineconfiguration.openshift.io/currentImage` or `machineconfiguration.openshift.io/desiredImage` annotations on the node, which are added to the node when you create the `MachineOSConfig` object.