Answer-first summary for fast verification
Answer: Too many Pods are already running in the cluster, and there are not enough resources left to schedule the pending Pod.
The correct answer is B. When a Pod is in a Pending state, it often means that there are insufficient resources (CPU, memory) in the cluster to schedule the Pod. In this scenario, given that there is a single preemptible node pool, resource constraints are the most likely cause, as preemptible nodes may be frequently reclaimed by Google, reducing the available resources and preventing the Pod from being scheduled.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You have set up a Google Kubernetes Engine (GKE) cluster that includes a single preemptible node pool. Within this cluster, you have deployed a Deployment configured to maintain 2 replicas of a specific Pod. After a few minutes, you check the status of your Pods using kubectl and notice that one of them is still in the Pending status. What is the most likely reason for this behavior?
A
The pending Pod's resource requests are too large to fit on a single node of the cluster.
B
Too many Pods are already running in the cluster, and there are not enough resources left to schedule the pending Pod.
C
The node pool is configured with a service account that does not have permission to pull the container image used by the pending Pod.
D
The pending Pod was originally scheduled on a node that has been preempted between the creation of the Deployment and your verification of the Pods' status. It is currently being rescheduled on a new node.
No comments yet.