KCNA: pod states after scheduler retries

Question

In a Kubernetes cluster, if the scheduler fails to assign a pod to any node due to insufficient resources, and the pod has a podAffinity rule that cannot be satisfied, what will be the final state of the pod after the scheduler retries for the maximum configured duration?

quizzes.technology · Accepted Answer

The pod will be stuck in a Pending state

quizzes.technology · Answer

The pod will be forcefully run on one of the control plane nodes

quizzes.technology · Answer

The pod will be stuck in a CrashLoopBackOff state

quizzes.technology · Answer

The pod will be stuck in a NotScheduled state

☁️ Free practice test question from: KCNA (KCNA)

In a Kubernetes cluster, if the scheduler fails to assign a pod to any node due to insufficient resources, and the pod has a `podAffinity` rule that cannot be satisfied, what will be the final state of the pod after the scheduler retries for the maximum configured duration?

Question: 344

Question: 280

Question: 347

💬 Discussion and Feedback

Comments