Hints: crashloopbackoff

Hint 1

The pod is crashing and restarting. Start with logs: - kubectl logs -n grokdevops <pod> --previous - kubectl get events -n grokdevops | grep -i back

Hint 2

Check the exit code to narrow the cause: - Exit 1: application error (check logs for stack trace) - Exit 137: OOMKilled (check memory limits) - Exit 126/127: bad entrypoint/command

Run: kubectl describe pod -n grokdevops <pod> | grep -A5 "Last State"

Hint 3

Common CrashLoop causes: - Missing environment variable or config file -> check ConfigMaps and envFrom - Database/service dependency not available -> check connection strings in logs - Wrong container command -> check deployment spec command/args

Hint 4

Look at kubectl get deployment grokdevops -n grokdevops -o jsonpath='{.spec.template.spec.containers[0]}' for the full container spec. Compare image, command, env, and volumeMounts with what's in devops/helm/values-dev.yaml.