Two-Year Deployment Mindset on a StatefulSet Cost a Team a Morning of Data Recovery
A engineering team ran a three-node message broker as a Kubernetes StatefulSet for two years while applying Deployment-style operational habits, including overnight scale-downs to cut costs. The incident occurred when an automated scale-down raced with a node replacement, causing a pod to return with an empty volume after its PVC was reclaimed under an unreviewed policy. This left two broker members with conflicting partition ownership, requiring hours of manual data reconciliation. The team resolved the issue by removing scale-down automation, setting reclaim policy to Retain, using the broker's own admin commands for member removal, and configuring rolling updates with a readiness probe that verifies cluster membership. The key takeaway was that StatefulSet pods carry distinct identities and roles, meaning orchestration for stateful workloads must follow the application's own lifecycle rather than generic container management patterns.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in