ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #k3s
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 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.
k3OS provides RAM-only, immutable k3s nodes provisioned from a single k3os.yaml. It is useful for disposable edge and CI workloads, but the project is archived since 2022 with no security updates.
A decision guide for choosing between RKE2 and K3s for Rancher-managed clusters, with a comparison table, trade-off analysis, and a concrete validation workflow.
k3OS made the OS declarative and upgrades atomic — ideas worth keeping. But the project is archived, so here's how to reuse the design with maintained tooling.
Learn how k3OS uses an immutable, read‑only filesystem and YAML‑based configuration to eliminate configuration drift in k3s clusters.
k3OS stripped the Kubernetes node down to an immutable image and a YAML file. Here's why that design decision matters, how node provisioning actually worked, and what to use now that the project is archived.
Learn how to run K3s with its embedded SQLite datastore, verify the setup, perform safe backups, and understand the scalability limits of this lightweight alternative to etcd.
kubernetes
k3os
rancher
sqlite