Parks staff see pods on one rack fail to obtain network interfaces while other racks work, and the CNI DaemonSet shows unhealthy pods only on that rack. What is the right troubleshooting focus?
Select an answer to reveal the explanation.
Short Explanation
CNI agents ride along as a DaemonSet—one per node—so a single sick rack usually means those nodes' CNI pods or host net, not a whole-cluster etcd rebuild.
Full Explanation
Container networking plugins typically deploy node agents as DaemonSets. When only one rack's pods fail networking and CNI pods are unhealthy there, investigation should focus on those nodes' CNI agents, logs, and host firewall/routes. etcd quorum loss, blanket NetworkPolicy deletion, and scheduler scaling are not the first correct focus for localized CNI DaemonSet failure.