Skip to main content
Use named CRICustomizationConfig documents to customize the CRI containerd configuration. Talos merges each document’s TOML fragment with the physical CRI configuration parts in lexicographical order by name. Applying, updating, or removing a CRICustomizationConfig regenerates the CRI configuration and restarts CRI automatically. A Talos node reboot is not required. The deprecated /etc/cri/conf.d/20-customization.part machine file remains supported during the deprecation period. Talos includes this legacy fragment under the reserved name customization, which a CRICustomizationConfig document cannot use.

Examples

The following examples show common CRI containerd customizations.

Exposing metrics

Patch the machine config by adding the following:
After Talos applies the document and restarts CRI, metrics are available:

Pause image

This change is often required for air-gapped environments, as containerd CRI plugin has a reference to the pause image which is used to create pods, and it can’t be controlled with Kubernetes pod definitions.
Now the pause image is set to registry.k8s.io/pause:3.8:

Disabling NRI plugins

Talos 1.14 enables NRI (Node Resource Interface) for the CRI containerd instance by default. NRI plugins can be deployed without a machine configuration patch, for example plugins from the NRI plugins repository. To restore the previous behavior and disable NRI, add the following configuration document: