694 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
Harbor's Garbage Collection Doesn't Block Your Registry Anymore — So What's the Real Cost Zot Is Actually Solving?
Harbor's registry hasn't gone read-only during garbage collection since 2020 — the real cost of running it against a build-per-deploy pipeline is worker-bound reclaim lag, and here's what Zot's inline GC actually trades for it.
We Took the $828/Year Heroku-to-Render Rails Migration One Hop Further: What Self-Hosted on Hetzner Actually Costs
A developer saved $828/year moving a Rails app from Heroku to Render. We took the same web/worker/Postgres/Redis topology one hop further onto owned Hetzner hardware — real numbers, including the June 2026 Hetzner price hike that complicates the math.
Hetzner Killed the `datacenter` Field on Schedule. CAPH's Provider Code Survived — Its Vendored SDK Didn't Keep Up
Hetzner removed the datacenter field from its Server and Primary IP API on July 1, 2026. A code audit of Cluster API Provider Hetzner found its own logic was never at risk, but its vendored Go client is stuck on a release from before the fix, and the dependency bump has sat in a stalled, CI-failing pull request since June.
Hetzner's Singapore Region Isn't a 2026 Launch — It's a 2026 Repricing: What APAC Self-Hosting Actually Costs
Hetzner's Singapore region launched in 2024, not 2026 — what changed this year is price, not availability. A line-by-line look at the 2026 repricing, the feature gaps versus the EU baseline, and whether Cluster API actually reaches ap-southeast.
Kubernetes' New Node Readiness Controller Closes the 'Pod Scheduled Before the Node Actually Works' Gap
None of CCM, CNI, or CSI natively report a Node Condition NRR can gate on — a worked example wires three NodeReadinessRule manifests into a Hetzner bare-metal bootstrap sequence anyway, and shows why managed EKS/GKE node pools never surface this bug in the first place.
Kamal 2.0's kamal-proxy: How Thin Can a Production PaaS Get Before It Needs Kubernetes?
Kamal 2.0's kamal-proxy runs HEY and Basecamp on nothing but Docker and a YAML file. Here's exactly what's in that box, where its five structural gaps are, and which Cluster API mechanism closes each one.
Kargo Puts Terraform and Kubernetes Behind One Freight Promotion — Does a Self-Hosted PaaS Actually Need That?
Kargo's 2026 Terraform/OpenTofu support bundles infra and app changes into one gated GitOps promotion. Here's a concrete three-question test for whether a Cluster API-managed PaaS actually needs that pattern, run against four real deploy scenarios.
kubectl for AI Agents: What Klaw.sh Reveals About the Layer Between CrewAI and Kubernetes
Klaw.sh borrowed kubectl's verbs for AI agent fleets instead of pods. Here's what layer that actually is, and a concrete verdict on whether a PaaS control plane that already runs Cluster API should absorb it or leave it alone.
Kubernetes 1.36 Splits nodes/proxy Into Nine Permissions — But Exec Still Needs the Keys to Every Container
Kubernetes 1.36 finally splits the kubelet's one catch-all nodes/proxy permission into nine narrower ones — but exec, attach, portforward, and run stay exactly as broad as before. Here's the before/after RBAC migration checklist for a multi-tenant self-hosted PaaS.