Real-world scenarios. Timed challenges. XP rewards. This is where training becomes mastery.
KUBERNETESQuest 14 of 38+350 XP
Debug the CrashLoopBackOff
Your production API pod keeps restarting. The on-call alert fired 10 minutes ago and SLA breach is imminent. Use the clues from the logs to identify and fix the root cause.
⏱ 05:00 remaining
$ kubectl get pods -n production
NAME READY STATUS RESTARTS AGE
api-deploy-7d9b8c-xk2p 0/1 CrashLoopBackOff 12 8m
db-sts-0 1/1 Running 0 2d
$ kubectl logs api-deploy-7d9b8c-xk2p --previous
Error: cannot connect to database: connection refused
postgres://db-service:5432/appdb unreachable
Retrying 3/3... giving up.
$ kubectl get svc -n production
NAME TYPE CLUSTER-IP PORT(S)
api-svc ClusterIP 10.96.0.10 80/TCP
(no db-service found)
What is the most likely root cause?
Quest 14 / 38
KUBERNETESQuest 15 of 38+280 XP
Fix the ImagePullBackOff
A new deployment is stuck in ImagePullBackOff. The team just pushed a new image to a private registry. Identify why the pod cannot pull the image.
⏱ 04:00 remaining
$ kubectl describe pod webapp-7f8b-abc -n staging
Events:
Failed to pull image "myregistry.io/webapp:v2.1": unauthorized: authentication required