1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
CNCF's Platform Engineering 2.0 Five Pillars: Grading a Self-Hosted PaaS Against the AI-Era Scorecard
CNCF's July 2026 Platform Engineering 2.0 framework sets five AI-era pillars. We grade a Cluster-API-managed, Render-compatible self-hosted PaaS against each one — one pass, two partials, two gaps — and map the honest upgrade path.
Docker Hub's 2026 Pricing Squeeze: What Self-Hosting a Registry Cache Actually Saves Your CI Pipeline
Docker Hub's 2026 free tier is 10 pulls/hour unauthenticated and 40/hour on Personal, with roughly 10x overage past paid plan limits. A line-by-line cost model shows a real CI pipeline paying $160–300/month on Docker Hub versus under €12 for a self-hosted pull-through cache — and exactly where the crossover sits.
Docker Hub Almost Cut You to 40 Pulls an Hour: The Math for Sizing Your Own Registry Cache
Docker's walked-back 10/40-per-hour limits were a preview, not a false alarm: a 15-developer team with ephemeral CI runners and a 12-node cluster hits today's enforced 100/200-per-6-hour buckets on an ordinary Tuesday. The full pull ledger, the tipping-point formula, and how to size and wire a registry cache — registry:2 or Harbor — into a Cluster API fleet.
GAMMA Extends Your HTTPRoutes East-West: Does a Self-Hosted PaaS Need a Service Mesh, or Just the Ingress Layer It Already Owns?
GAMMA lets the HTTPRoute objects a PaaS already provisions for ingress govern east-west traffic too — retries, timeouts, and canary splits without a service mesh. A capability map, worked YAML, real mesh cost numbers, and a decision framework for self-hosted platforms.
Kubernetes 1.36 Ships User Namespaces to GA: What Rootless Containers Change for Multi-Tenant PaaS Isolation
Kubernetes 1.36 graduates user namespaces to GA, remapping container root to an unprivileged host UID. What that changes for packing multiple tenants on shared bare metal — the CVEs it defuses, the version matrix your fleet must clear, and the shared-kernel risks it does not fix.
Your Cluster Runs at 8% CPU: Bin-Packing Defaults for a Self-Hosted Fleet That Can't Return Capacity
Cast AI's 2026 report puts average Kubernetes CPU utilization at 8% and memory at 20%. On elastic cloud that's an expensive bill; on owned hardware it's capacity you already paid for and can't return. Concrete request/limit defaults, a bin-packing scheduler config, and a worked Hetzner-vs-cloud cost delta.
Kubernetes v1.36 Ships Admission Policies That Can't Be Deleted: Closing the Bootstrap Window in Your Fleet's Guardrails
Kubernetes v1.36's manifest-based admission control loads policies from files before the API server serves its first request — undeletable via any RBAC. What it forecloses for a multi-tenant self-hosted PaaS, and the Cluster API bootstrap sequencing that makes guardrails live before the first tenant pod.
Railway's July 2026 US East Outage: What One ISP's Bad Route Cost Every App — and What Owning the Network Costs Instead
One carrier's backbone degradation left every app in Railway's US East zone degraded for over four hours — including 20 minutes with no internet route at all. A worked breakdown of what the outage cost and what owning your own network path actually costs, from a €40 Hetzner box to a full ASN with dual transit.
Render Says Buildpacks Beat Your Dockerfile by 75%. Can Nixpacks or Paketo Match That on Your Own Hardware?
Render's 75% faster-builds claim is standard Cloud Native Buildpacks layer caching, and both Paketo and Nixpacks reproduce it on hardware you own. What the number actually measures, the exact cache-image and cache-key commands for a fleet of ephemeral builders, and the five cache policies a shared build node platform needs.