{product-title} supports both cluster-wide and per-machine configuration via Ignition, which allows arbitrary partitioning and file content changes to the operating system. In general, if a configuration file is documented in {op-system-base-full}, then modifying it via Ignition is supported.
There are two ways to deploy machine config changes:
-
Creating machine configs that are included in manifest files to start up a cluster during
openshift-install. -
Creating machine configs that are passed to running {product-title} nodes via the Machine Config Operator.
Additionally, modifying the reference config, such as
the Ignition config that is passed to coreos-installer when installing bare-metal nodes
allows per-machine configuration. These changes are currently not visible
to the Machine Config Operator.
The following sections describe features that you might want to configure on your nodes in this way.
modules/installation-special-config-butane.adoc modules/installation-special-config-butane-about.adoc modules/installation-special-config-butane-install.adoc modules/installation-special-config-butane-create.adoc
-
For information on Butane, see Creating machine configs with Butane.
-
For information on FIPS support, see Support for FIPS cryptography.