Из ленты dev.to devops — кратко, чтобы не потерять.
It’s 3 AM. Your PostgreSQL pod crashes. On-call fires. The engineer wakes up, checks the dashboard, and spends 20 minutes figuring out why the payments service is throwing 500s at 100% error rate before they realize — database is down, but payments is still running, hammering connection pools, logging thousands of errors per second, triggering cascading alerts. They scale payments to zero. Problem stops. Recovery begins. That 20 minutes was avoidable. klink would have scaled payments to zero automatically — 30 seconds after the database went down. The Problem Nobody Talks About Kubernetes is excellent at keeping individual services running. Liveness probes, restart policies, resource limits — it’s all there. But Kubernetes has no concept of relationships between workloads . When your datab
Полный текст и контекст у первоисточника: https://dev.to/n0rm4l/your-database-just-died-why-is-everything-still-running-227p