Kubernetes 1.36's Sharded List and Watch: the N× Watch Tax It Kills, and the Ceiling It Doesn't Touch
Kubernetes 1.36's alpha sharded list and watch cuts sharded-controller stream cost from N× to 1× — but it shards controller fan-out, not etcd. The math, the mechanism, and the operator checklist for self-hosted fleets.
52,000 Stars for Coolify, 32,000 for Dokploy, 15,000 for CapRover: What Star Velocity Says About the Self-Hosted PaaS Market in 2026
Coolify adds roughly a thousand GitHub stars a week, Dokploy has nearly doubled to 36,000, and CapRover sits flat near 15,000. What star velocity plus release pace reveal about consolidation in the single-box PaaS market — and the second-machine ceiling the winner shares with everyone else.
etcd 3.7 RangeStream: What Streaming List Reads Mean for a Cluster API Fleet
etcd 3.7's RangeStream streams large collection reads in chunks instead of buffering whole responses, and Kubernetes 1.37 enables it by default. Here is where the memory win lands on a Cluster API fleet, how to verify it with one metric, and what it does not fix in your controllers' caches.
514 Blueprints vs 354 Apps vs 280+ Services: Why Template Count Is a Vanity Metric That Hides the Single-Box Ceiling
Dokploy lists 514 blueprints, CapRover 354 apps, and Coolify 280+ services. What a template count actually measures — packaged Compose files plus contributor throughput — and the five capabilities no catalog entry provides once one box is not enough.
Northflank Prices the Single-Box Decision: What a Price-Verified Dokploy-vs-Coolify Check Gets Right — and What Neither Panel Answers at Machine Two
Dokploy Cloud is cheaper at exactly one server; Coolify Cloud wins at every size above it — and neither panel provisions, heals, or autoscales machine two. A price-verified walkthrough of Northflank's September 2026 check plus the fleet gap both panels stop at.
Canine vs Coolify vs Dokploy: What the awesome-paas List Doesn't Tell You About the Second Machine
The awesome-paas list puts forty self-hosted platforms in one flat section with no signal about which survive a second machine. A taxonomy of the three architectures underneath — single-box Docker, Swarm multi-server, and attach-to-Kubernetes — worked through Canine, Coolify, and Dokploy.
Coolify's v5 Blueprint Is Public: Does Its Agent-and-Broker Rewrite Narrow the Fleet Gap With Cluster API?
Coolify published its accepted v5 architecture — control plane, gRPC broker, Rust host agent — alongside 62,145 stars and a weekly v4 patch train. A seven-primitive scoreboard shows which fleet gaps the rewrite closes and why machine lifecycle still separates it from Cluster API.
Kubernetes 1.36 In-Place Pod Resize Goes Beta: What Restart-Free Vertical Scaling Replaces in a PaaS Autoscaler
Kubernetes 1.36 graduates in-place vertical scaling for pod-level resources to beta: the kubelet can now grow a running pod's CPU and memory budget without a restart. This post shows the resize operation, the before/after for a PaaS autoscaler, and the beta caveats to clear first.
Nine Years in Beta Is Over: What Kubernetes 1.37's Stable Metrics API Means for Your Autoscaler
Kubernetes 1.37 promotes the metrics.k8s.io API to stable after nearly nine years in beta. What the frozen contract changes for autoscaling and usage metering on self-hosted clusters — plus the HPA gotcha and everything the API still doesn't do.