Google Associate Cloud Engineer
Get started today
Ultimate access to all questions.
Ultimate access to all questions.
As a lead DevOps engineer at a cloud-based startup, you've deployed an application on a Google Kubernetes Engine cluster featuring a single preemptible node pool. Upon executing the command kubectl get pods -l app=helloworld, you observe that one of the two replicas in your deployment is in a Running status while the other remains Pending. What could be the underlying cause of this issue?
Explanation:
Option B is correct because a Pod stuck in the Pending state often indicates that the cluster lacks the necessary resources (CPU, memory, or both) to schedule the Pod. This scenario is common when the cluster is under heavy load or not adequately scaled. Option A is incorrect because identical Pods in a deployment would have the same resource requests, making it unlikely for only one to be affected. Option C is incorrect because permission issues would affect all Pods in the deployment, not just one. Option D is incorrect because preemption would affect all Pods on the preempted node, not just one. For more details, refer to ManagedKube and Kubernetes documentation.