Sanity vs Kubernetes
Side-by-side trajectory, velocity, and editorial themes.
Sanity is quietly wiring its CMS to be operated by agents as much as by humans.
Sanity is shipping on several fronts in parallel: a maturing MCP server and agent tooling, a Media Library growing real asset-management depth, and steady Studio and SDK ergonomics. The recent run is incremental but coherent — richer Media Library metadata and reference tracking, searchable reference fields, and a stream of MCP tool fixes. Nothing here reshapes the product; it is compounding polish on an already broad platform.
The clearest theme is agent-operability. The MCP server, a skills-install CLI command, agent-focused doc quickstarts, and copy-paste commands 'for humans and agents' all point at Sanity treating AI coding agents as a first-class way to drive the CMS. In parallel, Media Library is being built out toward a full DAM, and @sanity/presets is trimming schema boilerplate.
Expect the MCP and agent surface to keep expanding and Media Library to keep gaining DAM-grade features; the presets package suggests more ready-made schema building blocks ahead.
etcd 3.7 lands RangeStream and drops the last of v2store as Headlamp becomes the cluster's UI
The Kubernetes ecosystem is advancing on two fronts at once: the core datastore and the operator-facing UI. etcd 3.7.0 shipped GA with RangeStream, a full switch to v3store-only bootstrap, and a protobuf overhaul that cuts control-plane CPU. In parallel, Headlamp — the sanctioned successor to the now-archived Kubernetes Dashboard — is accumulating a plugin layer (Cluster API, Volcano, Knative) that pulls specialized workflows into one visual interface.
The center of gravity is efficiency in the control plane and consolidation in tooling. etcd's removal of legacy v2store and its feature-gate lifecycle signal a deliberate cleanup that Kubernetes 1.37 will draw on via the EtcdRangeStream gate. Around it, the project is standardizing operator experience on Headlamp rather than a proliferation of one-off dashboards, and formalizing how AI-assisted contributions enter the codebase. This is maintenance-era maturity, not new surface area.
Expect Kubernetes 1.37 to expose RangeStream behind its feature gate and more SIG projects to ship Headlamp plugins as the default visual entry point. The v3.8 line will likely complete the v2store removal by dropping v2 snapshot generation and the --snapshot-count flag.
See more alternatives to Sanity →
See more alternatives to Kubernetes →