Menu

The one replica that leaks while its siblings stay flat
📰

The one replica that leaks while its siblings stay flat

DEV Community: kubernetes·SelimBF·6 days ago
#JmPGEwPR
#devtokubernetes#devto#dev#ruptura#version
Reading 0:00
15s threshold

Prefer video? The 4-minute overview above covers the whole idea.

Your Deployment runs five replicas. Four of them hold steady at 300 MiB. One climbs a little every minute.

On your dashboard, the average memory of the Deployment barely moves. Your alert on "memory above 90% of the limit" stays silent. Then that one pod is OOMKilled , restarts, and starts climbing again.

This is one of the failures that averages and global thresholds are built to miss. Here is how Ruptura , an open-source operator for Kubernetes and OpenShift, catches it, along with its close cousin: the release that leaks.

Why averages hide the leak

A Deployment-level metric is usually a sum or an average across pods. One replica growing while the others stay flat moves that number by a fifth of the growth.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.