Resources and performance
CPU throttling
Symptom: latency spikes, slow responses, even though average CPU usage looks low. Cause: CPU limits are enforced as CFS quota per 100 ms period; a multi-threaded burst (GC, JIT, a batch of requests) exhausts the quota early and the container is paused for the rest of the period.
container_cpu_cfs_throttled_periods_total / container_cpu_cfs_periods_total → throttling ratio
Fixes: raise or remove CPU limits for latency-sensitive services (keep realistic requests for fair sharing and scheduling), tune thread pools/GC threads to the CPU allotment.
Evictions
Pods with status Evicted (reason in describe): the kubelet evicted them due to node pressure — memory, ephemeral storage (ephemeral-storage used by logs/emptyDir/container layers), PIDs. BestEffort pods go first, then Burstable pods over their requests. Fix the pressure source (set ephemeral-storage requests/limits, log rotation, memory requests realistic), and clean up evicted pod objects (kubectl delete pod --field-selector=status.phase=Failed -n shop).
HPA not scaling
kubectl get hpa -n shop
kubectl describe hpa orders -n shop
TARGETS <unknown>/70%→ metrics-server missing/broken, or pods have no CPU requests (utilisation is computed relative to requests).ScalingLimited/ at maxReplicas → raisemaxReplicas(and check node capacity).- Custom metrics not found → Prometheus Adapter/KEDA configuration.
- Flapping → tune
behaviorstabilisation windows.
Noisy neighbours
Prevent with: requests/limits on everything (enforced by LimitRange and policy), ResourceQuotas per namespace, PriorityClasses for critical workloads, separate node pools (taints) for heavy or special workloads, and topology spread.