What problem does it solve? RKE2 cluster operators need reliable guidance for backing up and restoring Kubernetes datastore state, whether using embedded etcd, embedded SQLite, or external databases like MySQL, PostgreSQL, or etcd, especially during disaster recovery and quorum-loss events. ## Core Features & Use Cases - Snapshot Management: Configure scheduled and on-demand etcd snapshots with retention, compression, and S3-compatible object store replication via flags or a Kubernetes Secret. - Disaster Recovery Runbooks: Step-by-step cluster-reset restore procedures for single-server and multi-server clusters, including restores from S3, restores to new hosts with the original token, and quorum-loss recovery. - Datastore Selection Guidance: Compare embedded etcd, embedded SQLite, and external etcd/MySQL/MariaDB/PostgreSQL options, including HA support, quorum math, and connection endpoint formats. - Use Case: An operator loses quorum on a three-server RKE2 cluster. Use this Skill to run the cluster-reset restore on one node, wipe peer db directories, rejoin the remaining servers, and clean up stale Node resources. ## Quick Start Ask how to restore an RKE2 cluster from an etcd snapshot stored in S3 after losing quorum on a multi-server cluster.