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

CKA study material · question 553 of 1000

A kubelet is started with --node-labels=node-role.kubernetes.io/worker= and the node never appears in kubectl get nodes. What happened?

  1. The label was silently dropped and registration continued
  2. NodeRestriction rejected the registration, so the node failed to register at all
  3. The node registered but was immediately deleted by the node controller
  4. The label was converted into a taint, keeping the node hidden
Show the answer

Answer: B. NodeRestriction rejected the registration, so the node failed to register at all

kubeadm enables NodeRestriction, which forbids a kubelet from self-applying restricted labels such as node-role.kubernetes.io/*; attempting it makes registration fail rather than dropping the label.

Source: Creating a cluster with kubeadm (Kubernetes) — Managed node labels

Challenge yourself on this topic → Study as cards