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

CKA study material · question 62 of 1000

Straight after kubeadm init, the CoreDNS Pods sit in Pending and never start. What is the expected cause?

  1. No Pod network add-on has been installed yet
  2. The bootstrap token has expired
  3. The API server has not finished its prechecks
  4. RBAC has not been enabled
Show the answer

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

Cluster DNS cannot start before a CNI Pod network add-on is installed; that 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