1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
Heroku's $50 Dyno Is Where the Math Flips: A Worked 1-to-5-Dyno Cost Curve Against a Flat Hetzner Box
A Heroku Standard-2X dyno costs $50 a month and the bill scales per process. We price the same web-plus-worker-plus-Postgres topology from one dyno to five against a flat-rate Hetzner box at post-June-2026 prices — and the meter crosses the box at dyno two.
Hetzner Changed Its Storage Box API Under Your Backup Cron: Three Breaks and the Audit Your Automation Owes Itself
Hetzner's Storage Box API now follows Cloud API conventions: snapshot plans require hour and minute, subaccount home directories moved to their own action, and rollback takes a name or ID — with the old fields removed April 21, 2026. Here is the old-vs-new table and the checklist for any backup automation still on the pre-migration shape.
IPVS Is Dying in Kubernetes: Your Migration Timeline From the v1.37 Feature Gate to v1.43 Removal
Kubernetes 1.37 introduces the KubeProxyIPVS feature gate, starting a staged removal that disables IPVS by default in v1.40 and deletes it in v1.43. The full timeline, what breaks at each gate, and a detect-switch-validate recipe for moving self-hosted clusters to nftables mode.
Stop Buying a Control-Plane Machine Per Tenant: What Kamaji's Pod-Based Control Planes Actually Save
Running each tenant's Kubernetes control plane as pods instead of dedicated machines cuts the per-tenant control-plane bill from €7.50 a month to under €2 — starting at about six tenants. A worked Hetzner-priced model of Kamaji's consolidation, its limits, and the isolation tradeoff that decides whether the saving is safe to take.
kro Hits CNCF's 'Adopt' Ring: What Declarative CRD Composition Buys a PaaS Control Plane That Wants to Stop Hand-Writing Operators
CNCF's Q1 2026 Technology Radar put kro in the Adopt ring alongside Helm and Backstage. What declarative CRD composition actually buys a Cluster API-based PaaS — the 40-line RGD that replaces a hand-written expansion controller — and the four layer-on-layer costs to price in first.
Your Scheduler Config Has No Staging Environment: Rehearsing Bin-Packing Changes With kube-scheduler-simulator
Scheduler config changes ship straight to production because a dev cluster cannot reproduce real contention. kube-scheduler-simulator mirrors your fleet's actual nodes and pods so you can replay bin-packing changes and read per-plugin placement verdicts before anything moves.
Controllers Are Cheap to Write Now. Running One Still Isn't
Writing a Kubernetes controller now takes an afternoon thanks to kubebuilder — but each one still costs a replicated deployment, a sized informer cache, and idempotent reconcile logic. A promotion table for six tenant-lifecycle jobs: what a self-hosted PaaS should turn into controllers, and what should stay a script.
Kubernetes 1.36 Resizes Pods In Place — Until It Doesn't: The Two Boundaries Your Autoscaler Still Has to Respect
Kubernetes 1.36 enables pod-level in-place resizing by default, but resizes that cross a QoS class are rejected and memory shrinks below live usage are blocked. What each boundary means and the recreate-not-resize fallback your autoscaler needs.
Kubernetes v1.37's Deprecations Are a Ticking Clock: Audit Your Self-Hosted PaaS Before the Upgrade Window Closes
Kubernetes v1.37 puts dated removal timelines on kube-dns, kube-proxy IPVS mode, and cgroup v1. A concrete sunset table plus six runnable audit checks for your Cluster API fleet's controllers, CRDs, webhooks, and node templates — run them between code freeze and GA, not after reconciliation breaks.