CockroachDB vs Kubernetes
Side-by-side trajectory, velocity, and editorial themes.
CockroachDB is on a metronome — every six weeks an Innovation or Regular release, no fireworks in the entries themselves.
What we can see is purely cadence: v25.2, v25.4, v26.1, v26.2, v26.3 stacking up on a steady rotation between Innovation and Regular tracks. The entries are version stubs with no payload, so any feature-level analysis would be inference from the release programme rather than the data here.
Cockroach Labs is committed to its dual-track model — Innovation releases for new capabilities, Regular releases for the LTS-style path enterprises consume. The fact that v26 is already at .3 suggests they shipped on schedule across H1 2026 without slipping.
The next observable entry will be a v26.4 Regular release in mid-to-late summer 2026. Without entry content to read, no confident feature predictions are warranted from these data points alone.
Kubernetes 1.36 leans into AI/ML scheduling and control-plane scaling.
The 1.36 cycle is graduation-heavy, with PSI metrics, declarative validation, and volume group snapshots all promoted to GA. Alongside that, the project is making architectural moves around workload scheduling (a new PodGroup API), API-server safety (Mixed Version Proxy on by default), and very-large-cluster scaling (server-side sharded list and watch in alpha). Etcd 3.7 has hit beta in parallel.
Kubernetes is repositioning the control plane for two pressures at once: AI/ML batch workloads, where gang scheduling and DRA are becoming first-class concerns, and very-large clusters, where the control plane itself needs to shard. The pattern across this cycle is consolidation — old experimental scaffolding is reaching GA or being removed (ExternalIPs), while new APIs land with explicit separation of static template from runtime state. Less feature sprawl, more API hygiene.
Expect 1.37 to push server-side sharded watch toward beta and to keep extending DRA's reach into native resources like memory and networking. Workload-aware scheduling will likely accumulate scheduler-plugin-level coordination patterns next, with downstream batch frameworks starting to converge on the PodGroup shape.
See more alternatives to CockroachDB →
See more alternatives to Kubernetes →