Menu

Day 11: StatefulSets for Vector Databases — Deploying Milvus or Qdrant in Kubernetes
📰

Day 11: StatefulSets for Vector Databases — Deploying Milvus or Qdrant in Kubernetes

DEV Community: kubernetes·Suresh Kumar Pallapothu·about 21 hours ago
#5qyC7CNO
Reading 0:00
15s threshold

A crashed stateless pod comes back with a random name and a new IP, and nobody minds. A database node that returns with a different identity can break cluster consensus and force expensive re-sharding. A StatefulSet fixes that with stable network identities, ordered operations and automatic per-pod storage.

Identity and storage

Diagram: FIG 1 · Each StatefulSet pod keeps a stable DNS name and its own PersistentVolumeClaim, and pods start in order. A restarted pod comes back as the same member. See the animated version .

Each pod gets a predictable DNS name, such as qdrant-0.qdrant-headless.ai-platform.svc.cluster.local , plus its own PVC. Pods start in order, qdrant-0 then qdrant-1 , and the name survives a restart.

Why Deployments fail databases

Diagram: FIG 2 · Identity, storage and shutdown order all matter to a clustered database. StatefulSets handle each, and Deployments do not. See the animated version .

Identity instability.…

Continue reading — create a free account

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