1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own

AWS Load Balancer Controller Goes GA on Gateway API: Why Your Self-Hosted Ingress Bet Just Got Its Strongest Signal Yet
AWS Load Balancer Controller v3.0.0 made Gateway API generally available — the hyperscaler's own controller now targets typed Gateway/HTTPRoute CRDs instead of annotations. What that signals for self-hosted fleets, the four non-portable limits, and an Envoy-vs-Cilium pick table.

Your Buildpack Already Wrote the SBOM — Your Cluster Just Isn't Reading It
Cloud Native Buildpacks already emit a per-layer SBOM with every image, but most fleets never enforce it. Attaching that SBOM as a signed Sigstore attestation and verifying it with an admission controller turns scan-after-deploy into a deny decision before an unapproved image ever shares a node with other tenants.

You Can't Debug What You Can't See: The Agent Audit Trail Your PaaS Needs Before Agents Get Prod Access
CNCF's August 2026 field report says agents don't crash with stack traces — they loop, hallucinate, and burn tokens while dashboards stay green. The three pillars that make agent failures reconstructible, and the six-column audit blueprint to require before any agent touches production.

CAPH Stopped Checking Your Server Type: What Hetzner's Hardware Churn Teaches About Pinning Machine Templates
CAPH v1.0.7 deleted its hardcoded server-type allowlist after Hetzner's October 2025 lineup rework retired types like cx22. A typo'd or retired type now passes kubectl apply and fails later at Hetzner's API — here is the four-part CI discipline that replaces the deleted guardrail.

Cloud Native Buildpacks Just Graduated: Why Your PaaS Build Step Shouldn't Belong to One Vendor
Cloud Native Buildpacks graduated in August 2026 with 535 contributors and 20+ production adopters. Graduation makes CNB the boring, multi-vendor foundation for a fleet's build step — just as Nixpacks' maintenance mode shows what single-vendor builders cost — but build speed still has to be earned with cache locality.

Cloudflare Sandboxes Are GA: Active-CPU Billing vs E2B/Daytona, Repriced Line by Line
Cloudflare's GA Sandbox pricing bills CPU only while it burns and memory while the container stays awake. We run 30,000 bursty agent sessions through the rate card against E2B, Daytona, and Modal, find the break-even near 62% CPU-active, and name what the math can't change: it only runs on Cloudflare.

Your APM Says the Deploy Was Green. The Agent Retried the Migration Three Times
An agent can return HTTP 200 with zero errors while looping, misusing tools, or producing confident nonsense. This is what an OpenTelemetry run trace of an agent-operated deploy actually looks like — and the five telemetry emissions a platform has to produce natively before its first agent-run rollout.

Freeze the Crash: How CRIU Container Checkpoints Turn a Crash-Looping Pod Into a Debuggable Core Dump
One kubelet API call freezes a failing container into a tarball of memory, file descriptors, and process state. What the January 2026 Checkpoint/Restore Working Group means, the exact checkpoint-debug-restore loop, and the four boundaries — TCP sockets, GPUs, sandboxed runtimes, pod-level restore — that still say no.

Your Controller Makes 11 API Calls, Then Goes Quiet: What the controller-runtime Cache Costs a Cluster API Fleet at Scale
A controller-runtime controller's API reads cost almost nothing after startup — one snapshot plus one watch per type. The bill comes due in memory and restart bursts instead: how the Reflector/Indexer pipeline works, the three cache mistakes everyone makes, and a 50/200/500-Machine sizing table for Cluster API fleets.