Running Kubernetes clusters in production is a big undertaking with lots of moving parts. Keeping an eye on all those various parts is no easy task. To make the problem worse, Kubernetes is very distributed and oftentimes self-healing. If something is going wrong in your cluster, it may be intermittent enough (or specific enough) that you won’t see the breakage for quite a while. During that time, of course, your customers or developers may have a degraded or completely broken experience.
