Managing Edge Drift with k3OS Immutable Configuration
Eliminate edge node drift using k3OS's immutable root filesystem and declarative config.yaml. Learn how to bake custom configurations into ISOs for zero-touch deployment.
Loading…
ReadMeFeed / Community knowledge
#immutable-os
Real questions. Useful conversations. Find the people who know your stack.
k3osManaging System State with rpm-ostree in Fedora Silverblue
Learn how Fedora Silverblue's rpm-ostree atomic update model prevents system breakage by using immutable root filesystems and staged deployments.
fedoraRunning Immutable Edge Nodes with k3OS: When and How to Leverage Its Read‑Only Root
Learn how k3OS’s read‑only root filesystem enables atomic, rollback‑safe upgrades for edge Kubernetes nodes, and what you must change in your workflow to work within its immutable model.
kubernetesopenSUSE Transactional Updates: Read-Only Root with Btrfs Snapshots
A practical architecture note on openSUSE transactional updates using a read-only root, Btrfs subvolumes and snapper for atomic apply and rollback, with trust boundaries, ops checks and failure modes.
opensusek3os-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 pers