ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #k3os
Learn how k3OS’s immutable root filesystem and overlay partition enable atomic, verifiable upgrades and eliminate OS drift in Kubernetes edge nodes.
k3OS can auto‑join a k3s cluster using a pre‑configured token and TLS certs. This guide details the minimal design, trust boundaries, operational checks, failure modes, and when the setup needs to evolve.
k3OS uses a cloud‑config file to declaratively set networking, users, SSH keys, and k3s arguments at boot. This guide shows a concrete example, how to verify the changes, and common pitfalls to avoid when working with k3OS’s immutable root filesystem.
Discover how Mirantis’ k3OS rolling update service lets you upgrade your Kubernetes cluster with minimal downtime. Learn the workflow, a step‑by‑step example, and key trade‑offs to keep your production environment secure and up to date.
k3OS loaded its entire root filesystem into RAM and kept state on a separate disk partition. Here is how that split works, what it costs in memory, and why the project is now a reference architecture rather than a deployment target.
k3OS replaces manual node setup with a declarative YAML file read at boot. Learn how the k3os.yaml mechanism works, how to apply k3s flags, and why direct filesystem edits disappear on reboot.
k3OS uses a cloud‑init‑style config.yaml to turn a bare‑metal node into a fully unattended, Kubernetes‑managed machine. This post shows how to supply the file, a working example, and the trade‑offs of using an archived distribution.
k3os turns a whole Kubernetes node into one YAML file: hostname, SSH keys, and k3s role applied automatically on first boot. Here's how cloud-config provisioning works, with a two-node example and the caveats that matter.
Learn how a single k3os cloud‑config YAML can define hostname, SSH access, and k3s agent settings for reproducible, version‑controlled edge node deployments.
k3s
kubernetes