What problem does it solve? Configuring networking on self-hosted RKE2 clusters involves many interdependent choices—CNI selection, DNS caching, ingress, dual-stack, Multus, and control-plane load balancing—and misconfiguration leads to broken pod networking, DNS failures, or unreachable API servers. ## Core Features & Use Cases - CNI Selection and Tuning: Compare Canal, Cilium, Calico, and Flannel tradeoffs and customize each via HelmChartConfig manifests, including WireGuard encryption, kube-proxy replacement, and eBPF dataplanes. - DNS, Ingress, and Gateway API: Configure CoreDNS with NodeLocal DNSCache, enable Traefik ingress and Gateway API, and handle Cilium Local Redirect Policy integration. - Advanced Topologies: Set up dual-stack or IPv6-only clusters, Multus with SR-IOV and Whereabouts IPAM, external HAProxy/Keepalived load balancers for the supervisor and API server, and Windows node BGP. - Use Case: When building an HA RKE2 cluster with Cilium kube-proxy replacement, use this Skill to generate the correct config.yaml settings and HelmChartConfig manifests, including the NodeLocal DNSCache Local Redirect Policy workaround. ## Quick Start Ask how to configure a specific RKE2 networking component, such as enabling Cilium with WireGuard encryption or setting up dual-stack networking on a new cluster.