/etc, but some software requires additional configuration files there.
Use an EtcFileConfig document to create and manage a user-owned file without adding it to the Talos image.
Each EtcFileConfig document owns one complete file, including its contents and permissions.
Use multiple documents to manage multiple files.
Configure a file
-
Create a patch named
etc-file.patch.yamlwith the file path relative to/etc: -
Replace
<NODE>with the target node IP address, then apply the patch:
/etc/nfsmount.conf with mode 0644.
The mode field uses octal notation and defaults to 0o644 when omitted.
The contents field replaces the complete contents of the file.
For a nested path, set name to a path such as example/config.yaml.
Talos creates missing parent directories and writes content updates atomically, so readers do not observe a partially written file.
Changes are reconciled while Talos is running and do not require a reboot.
Changing contents updates the file, and deleting the document removes the file.
Remove a managed file
-
Create a strategic merge patch named
etc-file-delete.patch.yamlthat deletes the document: -
Replace
<NODE>with the target node IP address, then apply the deletion patch:
/etc/nfsmount.conf when it removes the document from the machine configuration.
Path restrictions
The documentname must be a non-empty local path relative to /etc.
The path:
- Must not include the
/etc/prefix. - Must not be absolute.
- Must not traverse to a parent directory.
- Must not start with
..
resolv.confhostsmachine-idextensions.yamllocaltimeos-releasexattr.conf
apparmor.d/apparmor/ca-certificates/cni/cri/iscsi/kubernetes/lvm/nvme/pki/selinux/ssl/
EtcFileConfig reference for the complete field schema.