Knock vs Kubernetes
Side-by-side trajectory, velocity, and editorial themes.
Knock keeps widening from a notifications API into an agent-driven engagement platform
Knock remains a developer-first notifications infrastructure product, but recent releases push past send-a-message plumbing. The last month added warehouse sync for delivery and engagement events, a hosted end-user preference center, dashboard MFA, and faster workflow testing. Data now moves both into Knock (Shopify) and back out to the warehouse.
Two arcs stand out: an agentic control surface — a Slack agent that creates and schedules resources, plus dashboard/CLI/agent parity for building audiences — and a maturing enterprise posture via MFA, the preference center, and warehouse analytics. Knock is positioning as a system of record for customer engagement, not just a delivery layer.
Expect the agent surface to deepen so more resources are manageable conversationally, and more data connectors after Shopify, given the warehouse-sync and dynamic-audiences direction.
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 Knock →
See more alternatives to Kubernetes →