Skip to main content
The base containerd configuration expects to merge in any additional configs present in /etc/cri/conf.d/20-customization.part.

Examples

Exposing metrics

Patch the machine config by adding the following:
Once the server reboots, metrics are now 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:

Set CDI plugin Spec Dirs to writable directories

By default Containerd configures CDI to read discovered hardware devices from ["/etc/cdi", "/var/run/cdi"]. Since /etc is not writable in Talos, CDI does not work for Dynamic Resource Allocation out of the box. To be able to use CDI and DRA modify the cdi spec dirs to writable locations like so:
Also change the cdi spec dirs configuration in your Dynamic Resource Allocation driver, since it needs to place the discovered hardware device specs in these folders.

Enabling NRI plugins

By default, Talos disables NRI plugins in containerd, as they might have security implications. However, if you need to enable them, you can do so by adding the following configuration:
After applying the configuration, the NRI plugins can be deployed, for example plugins from this repository.