k3os config.yaml applies locally but k3s joins with stale token on production cold boot
Symptom A cloud-init-style config.yaml that provisions SSH keys, network settings, and a k3s token works when iteratively rebooted on a local VM, yet the same configuration causes k3s agent nodes to join with an outdated token on first production cold boot. Context k3os processes /var/lib/rancher/k3os/config.yaml (or a boot-time datasource) during early boot
k3s