What problem does it solve? RKE2 clusters are configured through a YAML config file with hundreds of options, flag-to-YAML mapping rules, drop-in file merging, and component argument passthrough, which is error-prone to set up from memory. This Skill provides accurate guidance for configuring RKE2 servers and agents without digging through full CLI references. ## Core Features & Use Cases - Config file mechanics: Explains /etc/rancher/rke2/config.yaml conventions, flag-to-YAML mapping, drop-in files in config.yaml.d, and the + append suffix for merging lists. - Server and agent options: Covers tokens, TLS SANs, networking CIDRs, CNI and ingress selection, etcd snapshots and S3 backups, CIS profiles, cloud provider settings, and node labels/taints. - Component customization: Documents kube-apiserver/etcd/scheduler/kubelet argument passthrough, extra mounts, environment variables, resource limits, containerd config.toml.tmpl templating, certificate rotation, and HTTP proxy setup. - Use Case: When joining a new agent to an HA cluster, you get the exact minimal config (server URL, token, node-ip) plus guidance on registration-time labels and rejoining after losing /etc/rancher/node. ## Quick Start Ask the AI to generate an RKE2 server config.yaml with specific TLS SANs, node labels, and kubelet arguments for your cluster.