k3os-node-agent configuration persistence limits

The k3os architecture utilizes an immutable operating system design to ensure consistency across Kubernetes nodes. While the k3os-node-agent manages system state transitions and configuration applications, the root filesystem is designed to be read-only to prevent configuration drift.

There is a technical uncertainty regarding how the node agent handles persistent custom configuration files that must survive an image-based system update. Since package-level updates are replaced by full image swaps, standard filesystem modifications are lost upon reboot.

• How does the k3os-node-agent distinguish between transient state and persistent configuration during an image replacement?
• What are the documented mechanisms for injecting persistent node-specific metadata into the immutable core without violating the immutability constraint?