From e87868c6ab72a3aa39ad9b85d8932a9f135d2ee2 Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Wed, 22 Dec 2021 18:00:15 -0500 Subject: [PATCH] OSDOCS-3040: Check for config drift regularly RN --- release_notes/ocp-4-10-release-notes.adoc | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/release_notes/ocp-4-10-release-notes.adoc b/release_notes/ocp-4-10-release-notes.adoc index c3f4e78791..386e1868b6 100644 --- a/release_notes/ocp-4-10-release-notes.adoc +++ b/release_notes/ocp-4-10-release-notes.adoc @@ -84,6 +84,15 @@ This release adds improvements related to the following components and concepts. [id="ocp-4-10-machine-api"] === Machine API +[id="ocp-4-10-mco-config-drift"] +==== Enhanced configuration drift detection + +With this enhancement, the Machine Config Daemon (MCD) now checks nodes for configuration drift if a filesystem write event occurs for any of the files specified in the machine config and before a new machine config is applied, in addition to node bootup. Previously, the MCD checked for configuration drift only at node bootup. This change was made because node reboots do not occur frequently enough to avoid the problems caused by configuration drift until an administrator can correct the issue. + +Configuration drift occurs when the on-disk state of a node differs from what is configured in the machine config. The Machine Config Operator (MCO) uses the MCD to check nodes for configuration drift and, if detected, sets that node and machine config pool (MCP) to `degraded`. + +For more information on configuration drift, see xref:../post_installation_configuration/machine-configuration-tasks.adoc#machine-config-drift-detection_post-install-machine-configuration-tasks[Understanding configuration drift detection]. + [id="ocp-4-10-nodes"] === Nodes