verified on version: 4.7.0-0.nightly-2021-03-22-025559 I created 3 kubeletconfig CR, and when delete a kubeletconfig CR, the changes on the node rolls back to the previous kubelet config CR. $ oc get mc NAME GENERATEDBYCONTROLLER IGNITIONVERSION AGE 00-master b8a2aeb8f5a4d6c22773dc814cc9c6d3e5b85705 3.2.0 16h 00-worker b8a2aeb8f5a4d6c22773dc814cc9c6d3e5b85705 3.2.0 16h 01-master-container-runtime b8a2aeb8f5a4d6c22773dc814cc9c6d3e5b85705 3.2.0 16h 01-master-kubelet b8a2aeb8f5a4d6c22773dc814cc9c6d3e5b85705 3.2.0 16h 01-worker-container-runtime b8a2aeb8f5a4d6c22773dc814cc9c6d3e5b85705 3.2.0 16h 01-worker-kubelet b8a2aeb8f5a4d6c22773dc814cc9c6d3e5b85705 3.2.0 16h 99-master-generated-registries b8a2aeb8f5a4d6c22773dc814cc9c6d3e5b85705 3.2.0 16h 99-master-ssh 3.2.0 17h 99-worker-generated-kubelet b8a2aeb8f5a4d6c22773dc814cc9c6d3e5b85705 3.2.0 30m 99-worker-generated-kubelet-1 b8a2aeb8f5a4d6c22773dc814cc9c6d3e5b85705 3.2.0 16m 99-worker-generated-kubelet-2 b8a2aeb8f5a4d6c22773dc814cc9c6d3e5b85705 3.2.0 21s $ oc get kubeletconfig NAME AGE custom-kubelet-gc 24m custom-kubelet-performance 54m set-cpu-manager 40m
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.4 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:0957