After a control-plane disk fills, city operators find the API server unreachable and the kube-apiserver static pod missing under /etc/kubernetes/manifests. What should they recognize first?
Select an answer to reveal the explanation.
Short Explanation
On kubeadm, the apiserver is more like a sticky note on the node's fridge—the manifest in /etc/kubernetes/manifests—than a regular Deployment. Lose that file (disk fill can wipe or block it) and kubelet stops recreating the API.
Full Explanation
Kubeadm control-plane components are static pods watched by kubelet from /etc/kubernetes/manifests. If the kube-apiserver manifest is missing or unreadable after disk pressure, kubelet will not run the apiserver, causing API outages. Restoring the static pod manifest (and free disk) is the correct recovery class. The apiserver is not a scaled Deployment, not a CoreDNS child, and not expected to vanish during etcd compaction.