1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/machine_configuration/index.adoc

64 lines
3.6 KiB
Plaintext

:_mod-docs-content-type: ASSEMBLY
:context: machine-config-overview
[id="machine-config-index"]
= Machine configuration overview
include::_attributes/common-attributes.adoc[]
toc::[]
There are times when you need to make changes to the operating systems running on {product-title} nodes. This can include changing settings for network time service, adding kernel arguments, or configuring journaling in a specific way.
Aside from a few specialized features, most changes to operating systems on {product-title} nodes can be done by creating what are referred to as `MachineConfig` objects that are managed by the Machine Config Operator. For example, you can use the Machine Config Operator (MCO) and machine configs to manage update to systemd, CRI-O and kubelet, the kernel, Network Manager and other system features.
Tasks in this section describe how to use features of the Machine Config Operator to configure operating system features on {product-title} nodes.
[IMPORTANT]
====
NetworkManager stores new network configurations to `/etc/NetworkManager/system-connections/` in a key file format.
Previously, NetworkManager stored new network configurations to `/etc/sysconfig/network-scripts/` in the `ifcfg` format. Starting with RHEL 9.0, RHEL stores new network configurations at `/etc/NetworkManager/system-connections/` in a key file format. The connections configurations stored to `/etc/sysconfig/network-scripts/` in the old format still work uninterrupted. Modifications in existing profiles continue updating the older files.
====
include::modules/understanding-machine-config-operator.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* xref:../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc#about-ovn-kubernetes[About the OVN-Kubernetes network plugin]
include::modules/machine-config-overview.adoc[leveloffset=+1]
include::modules/architecture-machine-config-pools.adoc[leveloffset=+2]
include::modules/machine-config-node-drain.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* xref:../machine_configuration/index.adoc#about-machine-config-operator_machine-config-overview[About the Machine Config Operator]
* xref:../machine_configuration/machine-config-node-disruption.adoc#machine-configs-configure[Using node disruption policies to minimize disruption from machine config changes]
* xref:../support/troubleshooting/troubleshooting-operator-issues.adoc#troubleshooting-disabling-autoreboot-mco_troubleshooting-operator-issues[Disabling the Machine Config Operator from automatically rebooting]
include::modules/machine-config-drift-detection.adoc[leveloffset=+1]
include::modules/checking-mco-status.adoc[leveloffset=+1]
include::modules/checking-mco-node-status.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources
* xref:../machine_configuration/mco-coreos-layering.adoc#coreos-layering-configuring-on_mco-coreos-layering[About on-cluster image mode]
* xref:../nodes/clusters/nodes-cluster-enabling-features.adoc#nodes-cluster-enabling-features[Enabling features using feature gates]
include::modules/checking-mco-node-status-configuring.adoc[leveloffset=+2]
[id="machine-config-operator-certificates_{context}"]
== Understanding Machine Config Operator certificates
Machine Config Operator certificates are used to secure connections between the Red Hat Enterprise Linux CoreOS (RHCOS) nodes and the Machine Config Server. For more information, see xref:../security/certificate_types_descriptions/machine-config-operator-certificates.adoc#cert-types-machine-config-operator-certificates[Machine Config Operator certificates].
include::modules/checking-mco-status-certs.adoc[leveloffset=+2]