hostname field in k3os v0.12.0 cloud-config requires two boots to apply
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
k3s