Fix Pods Stuck in Pending

easy 10 XP ~6 minHands-on lab

The payouts Deployment in namespace audit was rolled out this morning and none of its Pods has started. The team copied its resource settings from a load-testing environment.

Task

All 3 replicas of Deployment payouts are running and available.
Its container requests 150m CPU and keeps its memory request of 256Mi.
Its container has a CPU limit of 1 and keeps its memory limit of 512Mi.
Deployment fraud-check in the same namespace is not changed.

A practice cluster is running on this machine: start with kubectl get pods -n audit.

About this machine

Ubuntu 24.04 with a private practice cluster: a real Kubernetes API server, scheduler and controllers, and three nodes (controlplane, node01, node02). Containers are simulated, so images never download and kubectl logs/exec are not available. k is an alias for kubectl, with completion. The grader checks the cluster's final state, not the commands you typed.

pending resources requests limits scheduling troubleshooting cka ckad