1732 posts tagged with "Self-Hosting"
Running your own PaaS and infrastructure on machines you own
Kubernetes v1.37's Node Lifecycle Conditions: Teaching MachineHealthCheck to Tell 'Draining' Apart From 'Dying'
Kubernetes v1.37 reserves five Node Lifecycle Conditions that finally let a node say 'I'm draining' instead of just going NotReady. What MaintenancePlanned changes for MachineHealthCheck remediation, what MHC already covers, and what a Cluster-API fleet should publish this quarter.
The Gate That Wasn't There: What Nomad's CVE-2026-14891 Teaches About Scheduler Isolation
Nomad 2.0.4 fixed a CVE that let any job submitter land a container in the host's PID, network, or IPC namespaces — because the allow_privileged check was never evaluated. What the bug, its two sibling fixes, and Kubernetes' admission-time enforcement say about choosing a scheduler for untrusting tenants.
Your npm Token Is the Next Supply-Chain Incident: A Tokenless Publishing Playbook for Git-Push Pipelines
npm's OIDC trusted publishing replaces the long-lived NPM_TOKEN with per-run workload identity and automatic provenance. A six-step migration checklist with version floors and failure modes, the 2026 enforcement timeline through January 2027, and what the pattern means for a self-hosted build pipeline.
CPU at 40%, Everything on Fire: What Kubernetes 1.36's PSI Metrics Finally Tell a Bin-Packed Fleet
Kubernetes 1.36 graduates PSI metrics to GA, exposing CPU, memory, and I/O stall percentages per node, pod, and container. Here is what that reveals on a bin-packed fleet, the kernel and cgroup v2 checklist to enable it, and three stall-based queries to run before your next 'utilization looks fine' incident.
Railway vs Vercel vs Cloudflare: What Bursty Builds Really Cost Per Second (and When a Flat Hetzner Node Wins)
Railway, Vercel, and Cloudflare all bill per second but meter different things. A worked recompute at three burst tiers shows where metered builds beat a flat Hetzner node — and where they quietly lose.
Valkey Won the Default: What a git-push PaaS Should Bundle Now That the Redis Fork Became the Safe Choice
Two years after Redis gave up the BSD license, Valkey is the default on major Linux distros and the recommended engine on ElastiCache at 20-33% lower prices. A cost-vs-gain accounting for making it your platform's standard cache, plus the one boundary where Redis still wins.
Ten Platforms, One Accidental Contract: The PORT-and-Start-Script Standard Behind Every Git-Push Deploy
Cedar.js set out to fix Railway deploys and found ten platforms sharing one accidental contract: a build script, a start script, PORT, and dual-stack binding. The full convention, the three-tier platform matrix, and the five ways it silently breaks.
Your AI Budget Will Be Wrong. Your Deploy Bill Doesn't Have to Be
Enterprise surveys say four out of five teams miss their AI spend forecasts. Model inference is inherently unpredictable — but the deploy bill underneath it is a choice. Here is why agent-operated apps belong on flat-rate machines you own.
Japan Just Named the Kubernetes AI Stack: What a Self-Hosted PaaS Should Adopt, Pilot, or Skip
Japan's new CNCF AI Infrastructure SIG names DRA, Kueue, KServe, the Gateway API Inference Extension, and more as one coordinated stack. A concrete adopt-pilot-skip triage for self-hosted PaaS teams: three to adopt now, two to pilot, two stacks to decline, and two watches with dated triggers.