easy5 pts · first answer countskubernetestroubleshooting

CrashLoopBackOff

kubectl get pods shows a pod in CrashLoopBackOff. What does that status mean?

A.The pod cannot be scheduled because no node has enough CPUB.The container image cannot be pulled from the registryC.The container keeps starting and exiting, and the kubelet waits longer between each restartD.The pod is being deleted by the cluster autoscaler

← A process vanished overnight Logs from the crashed container →