This is a classic production trap.
Root cause
readinessProbe ≠ livenessProbe
Most people use only one.
Correct pattern
Daily micro-tips for C#, SQL, performance, and scalable backend engineering.
This is a classic production trap.
Root cause
readinessProbe ≠ livenessProbe
Most people use only one.
Correct pattern
livenessProbe:
httpGet:
path: /health/live
port: 80
readinessProbe:
httpGet:
path: /health/ready
port: 80
Why this matters
Liveness = should I restart?
Readiness = should I receive traffic?
If your app is warming caches or reconnecting DBs,
traffic arrives too early → silent failures.