// Module included in the following assemblies:
//
// * scalability_and_performance/ztp_far_edge/ztp-vdu-validating-cluster-tuning.adoc

:_mod-docs-content-type: REFERENCE
[id="ztp-recommended-cluster-mc-crs_{context}"]
= Recommended cluster MachineConfig CRs for {sno} clusters

[role="_abstract"]
Check that the `MachineConfig` custom resources (CRs) that you extract from the `ztp-site-generate` container are applied in the cluster. The CRs can be found in the extracted `out/source-crs/extra-manifest/` folder.

The following `MachineConfig` CRs from the `ztp-site-generate` container configure the cluster host:

.Recommended {ztp} MachineConfig CRs
[cols=2*, options="header"]
|====
|MachineConfig CR
|Description

a|`01-container-mount-ns-and-kubelet-conf-master.yaml`

`01-container-mount-ns-and-kubelet-conf-worker.yaml`
|Configures the container mount namespace and kubelet configuration.

a|`03-sctp-machine-config-master.yaml`

`03-sctp-machine-config-worker.yaml`
|Loads the SCTP kernel module. These `MachineConfig` CRs are optional and can be omitted if you do not require this kernel module.

a|`06-kdump-master.yaml`

`06-kdump-worker.yaml`
|Configures kdump crash reporting for the cluster.

a|`07-sriov-related-kernel-args-master.yaml`
|Configures SR-IOV kernel arguments in the cluster.

a|`08-set-rcu-normal-master.yaml`

`08-set-rcu-normal-worker.yaml`
|Disables `rcu_expedited` mode after the cluster has rebooted.

a|`99-crio-disable-wipe-master.yaml`

`99-crio-disable-wipe-worker.yaml`
|Disables the automatic CRI-O cache wipe following cluster reboot.

a|`99-sync-time-once-master.yaml`

`99-sync-time-once-worker.yaml`
|Configures the one-time check and adjustment of the system clock by the Chrony service.

a|`enable-crun-master.yaml`

`enable-crun-worker.yaml`
|Enables the `crun` OCI container runtime.

a|`extra-manifest/enable-cgroups-v1.yaml`

`source-crs/extra-manifest/enable-cgroups-v1.yaml`
|Enables cgroups v1 during cluster installation and when generating {rh-rhacm} cluster policies.
|====

[NOTE]
====
In {product-title} 4.14 and later, you configure workload partitioning with the `cpuPartitioningMode` field in the `ClusterInstance` CR.
====
