Are your Kubernetes CPU limits actually being enforced?
CPU limits are one of the first guardrails most teams add to a Kubernetes manifest. Set resources.limits.cpu: 200m, and you can trust that the container will never use more than a fifth of a core…right? That’s not always the case. A CPU limit is a request, not a restriction: the kubelet can ignore it, and if that happens, the container is free to use as much CPU time as it wants.