Skip to content

Hints: probe-failure

Hint 1

The pod is running but not ready. Check events: - kubectl describe pod -n grokdevops <pod> | grep -i probe

Hint 2

It's a readiness or liveness probe issue. Check the probe configuration: - kubectl get deployment grokdevops -n grokdevops -o jsonpath='{.spec.template.spec.containers[0].readinessProbe}' | python3 -m json.tool - Is the path correct? Is the port correct?

Hint 3

The probe path is likely wrong (e.g., /nonexistent instead of /health). Check: - kubectl exec -n grokdevops <pod> -- wget -qO- http://localhost:8000/health - Was the probe path changed by a Helm upgrade or chaos script?

Hint 4

Fix: patch the readiness probe path back to /health: kubectl patch deployment grokdevops -n grokdevops --type=json -p='[{"op":"replace","path":"/spec/template/spec/containers/0/readinessProbe/httpGet/path","value":"/health"}]'