openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Merge pull request #40144 from mburke5678/RN-OSDOCS-3040-drift

Browse Source 
OSDOCS-3040: Check for config drift regularly RN
This commit is contained in:
Michael Burke
2022-01-06 14:35:17 -05:00
committed by GitHub
parent 04168bfe9c e87868c6ab
commit f59ec68bd7
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
release_notes/ocp-4-10-release-notes.adoc
View File

@@ -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