After a failed upgrade, municipal ops must recover API object state from a previously taken etcd snapshot. What does a successful etcd restore primarily recover?
Select an answer to reveal the explanation.
Short Explanation
Restoring etcd is like rolling the cluster’s memory back to the last good save point—Pods, Services, RBAC, the whole API picture that lived in that database. It doesn’t magically rebuild every node’s local disk junk, but it brings back the control plane’s truth. That’s why the snapshot from before the bad upgrade matters.
Full Explanation
An etcd restore returns the API datastore to the contents of the snapshot, recovering objects such as Pods, Deployments, Services, and RBAC as of that point in time. Node-local artifacts like image caches are separate from etcd. Administrators must follow kubeadm/etcd restore procedures so apiserver instances agree on the restored data directory.