rke2-configuration

Configures self-hosted RKE2 servers and agents via config.yaml options and component arguments.

2|Updated Jul 22, 2026
One-click install
npx skills add https://github.com/dydx/rke2-skills --skill rke2-configuration-dydx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rke2-configuration
Source: https://github.com/dydx/rke2-skills/tree/main/skills/rke2-configuration
Command: npx skills add https://github.com/dydx/rke2-skills --skill rke2-configuration-dydx

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about rke2-configuration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure an RKE2 server with config.yaml?▼

Create /etc/rancher/rke2/config.yaml and set keys matching CLI flag names without the leading dashes, such as write-kubeconfig-mode, tls-san, and node-label. Repeatable flags become YAML lists, and changes require a systemctl restart of rke2-server to take effect.

How to pass custom arguments to kube-apiserver or kubelet in RKE2?▼

Use the component argument passthrough lists in config.yaml, such as kube-apiserver-arg, etcd-arg, kube-scheduler-arg, or kubelet-arg, with entries formatted as flag=value strings without leading dashes. Use the + key suffix in drop-in files to append rather than replace existing lists.

How do RKE2 config.yaml.d drop-in files merge values?▼

RKE2 reads config.yaml first, then files in config.yaml.d alphabetically, with the last value winning per key. Append a plus sign to a key, like node-taint+, to append to the accumulated list instead of replacing it.

Can RKE2 run on Windows nodes?▼

Windows nodes are supported as agents only, since rke2 server is Linux-only, and the cluster must use Calico or Flannel as the CNI. Windows agents use the same config file conventions with a native snapshotter default and install via install.ps1.

Why can't I change node labels after RKE2 registration?▼

The node-label and node-taint config options apply only at registration time and cannot be modified later through RKE2. Use kubectl label node or kubectl taint node to change labels and taints after the node has joined.

How do I rotate expired RKE2 certificates?▼

RKE2 certificates expire after 12 months and rotate automatically on restart when expired or within 90 days of expiry. For manual rotation, stop rke2-server, run rke2 certificate rotate, then start the service again; agent certs renew on every agent restart.