ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
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.
Learn how to automate k3OS node bootstrapping using a cloud‑config file so the node joins a k3s cluster without manual intervention.
Goal: Ensure that the hostname specified in a k3os cloud‑config is available to the k3s service during the first boot so that nodes register with Rancher using the correct identifier without requiring a manual reboot or cfg apply. Constraint: In k3os v0.12.0 the hostname key is handled by systemd‑hostname after network‑online.target, while k3s.service starts
k3os reads most configuration from a cloud-config file at /var/lib/rancher/k3os/config.yaml , and that file can be supplied in more than one way. A locally installed node usually has it embedded on disk; a PXE or cloud-booted production node may instead fetch it from a remote URL named by kernel command-line parameters such as k3os.mode and its datasource op
kubernetes
k3s
rancher