Kubernetes incidents: first 10
From reading Pod states to image pulls, rolling updates, resource limits, and node failures.
0/10
1A pod is Running and one Service still has no endpointsBeginner6 minFree2Organizing the first checkpoints for a CrashLoopBackOff PodBeginner18 minFree3ImagePullBackOff caused by a missing private registry credentialBeginner17 minFree4OOMKilled: a container keeps restarting after hitting its memory limitBeginner15 minFree5A readiness probe path typo keeps the rolling update from finishingBeginner16 minFree6A CoreDNS pod is healthy and one namespace still resolves old namesBeginner6 minFree7HPA stays idleBeginner16 minFree8Pods get Evicted in bulkIntermediate18 minFree9NetworkPolicy allows the app service but blocks CoreDNS resolutionIntermediate18 minFree10A node goes NotReady after a rebootIntermediate16 minFree
A problem counts as done once you submit it. The goal is to write your answer in full and compare it with the model answer, regardless of the keyword score. Log in to track submitted problems as progress.