What problem does it solve? Securing a self-hosted RKE2 cluster beyond its hardened defaults requires navigating CIS benchmark profiles, Pod Security Admission, secrets encryption key rotation, SELinux policies, certificate lifecycles, join tokens, and FIPS 140-2 constraints, each with version-specific procedures and manual host-level steps that are easy to miss. ## Core Features & Use Cases - CIS Benchmark Hardening: Enable profile: cis, satisfy host prerequisites (etcd user, sysctl kernel parameters), patch default ServiceAccounts, and configure audit policies and NetworkPolicies. - Secrets Encryption & Key Rotation: Manage at-rest encryption providers (aescbc vs secretbox) and execute modern or classic rke2 secrets-encrypt rotation procedures for single-server and HA clusters. - Certificate & Token Lifecycle: Check and rotate leaf certificates, rotate 10-year CA certificates with rotate-ca, provision custom CAs, and rotate server/agent/bootstrap tokens. - Use Case: A platform engineer preparing an RKE2 v1.30 cluster for a compliance audit uses this Skill to enable CIS mode, apply the sysctl config, set a real audit policy, rotate encryption keys across three HA servers, and verify FIPS-compliant component selection. ## Quick Start Ask how to enable CIS hardening on a new RKE2 cluster, including the etcd user setup, sysctl configuration, and the config.yaml profile setting.