Building a K8s Operator for a Distributed Database
summary
Kubernetes operator that keeps Aerospike clusters online through live patches, replacing live clusters of tens of nodes and recovering crashed nodes to meet a claimed 100% uptime. Implements an init‑container wipe flag to distinguish new volumes from restarted pods so persistent data is not lost, and a reconcile loop that requeues after each operation (with API response delay) to allow immediate aborts of rolling updates. Notes scale limits: customers with ~half a trillion objects require private hardware and overprovisioning beyond what an operator alone can solve.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:23What is a Kubernetes Operator
- 7:20Aerospike
- 11:24Persistent Data
- 13:23Rolling Updates
- 16:34Large Scale
related talks
16mBuilding a K8s Operator for a Distributed Database
35mOrchestrating Resilient Data: Harnessing the Strength of Kubernetes with Operators
44mDatabases on Kubernetes: Why You Should Care!
29mFlipkart: Scaling Aerospike at Flipkart with Kubernetes
15mHow We Solved the K8s Cluster Communication Challenge
41mDatabases on Kubernetes Using a Custom Operator: Day 1, Day 2, and Beyond
21mStory of a Kubernetes Go Operator
24mWhat a Modern Database Enables
