What problem does it solve? Adding a Flatcar Linux node to a k3s cluster involves immutable-filesystem constraints, overlayfs /etc quirks, and update_engine configuration that fails silently when done the usual way. This Skill provides the exact commands and known pitfalls for joining nodes, auto-configuring updates via DaemonSet, and validating the Nebraska kernel update pipeline end-to-end. ## Core Features & Use Cases - k3s Agent Join: Install k3s on Flatcar via the sysext-aware installer and verify node registration with kubectl. - Nebraska Update Configuration: Use the flatcar-update-configurator DaemonSet and nsenter to write /etc/flatcar/update.conf past the overlayfs restriction, then confirm first check-in in Nebraska logs. - Kernel Pipeline Validation: Triage flatcar-kernel-build Argo workflow failures, verify package registration, and confirm kernel version promotion on the node. - Use Case: You just racked a new Flatcar node (exo-2) and it is not appearing in kubectl get nodes, or update_engine never checks in to Nebraska. Follow the Skill to join the cluster, confirm update.conf, and watch the first processEvent arrive. ## Quick Start Use the flatcar-node-onboarding skill to join my new Flatcar node exo-2 to the k3s cluster and verify it checks in to the Nebraska update server.