Home / Companies / Cockroach Labs / Blog / Post Details
Content Deep Dive

Introducing the CockroachDB Kubernetes Operator

Blog post from Cockroach Labs

Post Details
Company
Date Published
Author
Ethan Shmargad
Word Count
1,095
Company Posts That Month
3
Language
English
Hacker News Points
-
Post removed?
No
Summary

Cockroach Labs has launched a production-ready CockroachDB Kubernetes Operator that provides Kubernetes-native, CockroachDB-aware lifecycle management for self-hosted deployments, replacing operational scripts and manual procedures commonly required with StatefulSets. Based on an operator used to manage more than 600 CockroachDB Cloud clusters for nearly three years, it automates deployment, rolling upgrades, health-aware scaling, certificate rotation, storage management, observability, and multi-region configuration through custom resources and separate cluster- and node-level reconciliation. The operator supports TLS options, declarative SQL initialization, zero-downtime upgrades, storage expansion, WAL failover, CMEK, physical cluster replication, Helm, GitOps, private registries, and air-gapped environments. Adding a region can be performed through a declarative configuration change while CockroachDB manages cross-region data distribution and consistency. Existing users of the legacy public operator or StatefulSet Helm charts can migrate through an opt-in automated controller that replaces nodes individually, verifies cluster health, preserves disks and certificates, maintains application availability, and supports rollback. The legacy operator and StatefulSet charts will remain supported until CockroachDB 27.3, expected in summer 2027, followed by a 12-month maintenance period without new features or support for version 27.3 and later, after which they will reach end of life.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Kubernetes 21 634 79 44 -75%
Observability 2 625 152 84 -84%
Platform Engineering 1 154 51 23 -88%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.