Study. uk . com
  1. Home
  2. All questions
  3. Question 547

CKA study material · question 547 of 1000

Immediately after a successful kubeadm init, the CoreDNS Pods sit in Pending. What is the expected explanation?

  1. The control plane node is tainted, so no Pod can schedule anywhere
  2. CoreDNS waits for the first worker node to join
  3. No Pod network add-on has been installed yet
  4. The kube-dns Service has not been created yet
Show the answer

Answer: C. No Pod network add-on has been installed yet

kubeadm is deliberately network-provider-agnostic, so CoreDNS cannot start until a CNI add-on is deployed; a Pending CoreDNS right after init is by design, not a fault.

Source: Creating a cluster with kubeadm (Kubernetes) — Installing a Pod network add-on

Challenge yourself on this topic → Study as cards