Restore is not recovery until the cluster agrees
Restoring etcd data is one step in Kubernetes recovery; control-plane identity, manifests, endpoints, certificates, and reconciliation still have to agree.
A snapshot answers a narrow question
An etcd snapshot proves that a point-in-time keyspace was captured. A successful restore proves that those keys can be written into a new data directory. Neither result proves that the Kubernetes API can start, authenticate clients, reach the restored member, or reconcile a functioning control plane.
Recovery crosses ownership and configuration boundaries that backups do not: file permissions, member identity, peer and client URLs, static pod manifests, certificates, and the API server's etcd arguments all have to describe the same topology.
Bring components back into agreement
After restoring, verify the data directory owner and the effective manifest mounts before starting components. Confirm endpoint health with the credentials the control plane actually uses. Then verify API availability, authentication, nodes, system workloads, and controllers—not just an etcd health response.
The restored state may include objects whose external dependencies changed after the snapshot: load balancer addresses, certificates, tokens, volumes, or cloud resources. Controllers will act on that older desired state as soon as they return, so recovery includes understanding what they will reconcile.
Test outcomes, not commands
A useful drill defines recovery assertions in advance: the API is reachable through its normal path, privileged and ordinary identities behave correctly, core controllers are healthy, workloads can be scheduled, and critical application data is coherent. The restore command is a procedure; recovery is the demonstrated return of system behavior.