Water-utility admins still rely on kubectl get componentstatuses during outages, but results are confusing on modern clusters. What is the better troubleshooting approach?
Select an answer to reveal the explanation.
Short Explanation
componentstatuses is yesterday's clipboard. On modern clusters, look at the actual control-plane pods, their logs, and health endpoints—the live scene—not the legacy summary card.
Full Explanation
The ComponentStatus API is deprecated and often misleading on current clusters. Operators should verify kube-apiserver, etcd, scheduler, and controller-manager via their static pods or manifests, logs, and healthz/livez/readyz style endpoints. Relying solely on kubectl get cs, or substituting an Ingress probe for etcd health, is not sound modern practice.