You can use the tasks in this section to create MachineConfig objects that modify files, systemd unit files, and other operating system features running on {product-title} nodes. For more ideas on working with machine configs, see content related to updating SSH authorized keys, verifying image signatures, enabling SCTP, and configuring iSCSI initiatornames for {product-title}.
{product-title} supports Ignition specification version 3.4. You should base all new machine configs you create going forward on Ignition specification version 3.4. If you are upgrading your {product-title} cluster, any existing machine configs with a previous Ignition specification will be translated automatically to specification version 3.4.
There might be situations where the configuration on a node does not fully match what the currently-applied machine config specifies. This state is called configuration drift. The Machine Config Daemon (MCD) regularly checks the nodes for configuration drift. If the MCD detects configuration drift, the MCO marks the node degraded until an administrator corrects the node configuration. A degraded node is online and operational, but, it cannot be updated. For more information on configuration drift, see Understanding configuration drift detection.
|
Tip
|
Use the following "Configuring chrony time service" procedure as a model for how to go about adding other configuration files to {product-title} nodes. |
modules/cnf-disable-chronyd.adoc modules/nodes-nodes-kernel-arguments.adoc modules/rhcos-enabling-multipath-day-2.adoc
-
See Enabling multipathing with kernel arguments on RHCOS for more information about enabling multipathing during installation time.