Kubemark density test failing because kubelet doesn't have a ClusterDNS #18056
Labels
area/kubelet
area/test
area/test-infra
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
The Kubemark Jenkins Density tests started failing around 2:14pm PST today. Looking at test logs, it seems all pods are scheduled, but remain in "Pending" state forever. Digging into the container logs, found all the containers with similar error of the format:
"kubelet does not have ClusterDNS IP configured and cannot create Pod using ClusterFirst policy."
Still investigating.
The text was updated successfully, but these errors were encountered: