510 posts tagged with "Kubernetes"
Container orchestration, Cluster API, and self-hosted control planes
Your GPUs Are 60% Idle and Kubernetes Says Everything Is Fine
A July 2026 CNCF case study found Kubeflow GPUs ~60% idle with every pod green — a scheduler-vs-network conflict fixed with topology constraints (40% to 85% utilization). The three families of GPU waste, a DCGM-based instrumentation ladder, and the rule for earning your next GPU node.
Kubernetes 1.37 Will Reject Your Static Pods: the kubeadm Audit to Run Before You Upgrade
Kubernetes 1.37 removes the opt-out and has the kubelet refuse any static pod referencing a Secret or ConfigMap. The one-line audit for every control-plane node, the full list of rejected fields, and the hostPath and extraVolumes patterns that replace them.
Kubernetes 2.0 on HN: Why Rivet's Docker Compose Story Ends at the Second Server
A skeptic on HN asked how Docker Compose could be a more reliable, scalable alternative to Kubernetes for Rivet's actor platform. Rivet's own docs supply the answer: the Postgres-plus-NATS second-machine path, the 1,000-actor ceiling, and where K0s fits instead.
Your Coding Agent Needs a Sandbox, Not a StatefulSet: gVisor vs Kata Under Kubernetes' New Sandbox Controller
Kubernetes SIG Apps shipped an upstream Sandbox controller for running untrusted agent code. A practical decision guide: what it replaces, whether gVisor or Kata fits your tenants, and what warm pools cost in idle capacity.
k3s Now, EKS Later? Pricing Ownkube's Graduation Ladder Against Cluster API on Day One
Ownkube lets teams start on hosted compute and graduate the same app into their own AWS account, from free single-node to metered multi-AZ. A priced run of one steady 2-vCPU team workload across every rung — plus what re-surfaces on migration day — against committing to Cluster API on flat hardware from the first deploy.
Docker Is Enough Until the Second Server: Why We Still Bet on Kubernetes
2026's PaaS-first chorus says Docker on one box handles 95% of workloads and Kubernetes is overkill. The verdict table, the Coolify/Dokploy/CapRover facts, and the five things that break at the second server — plus where the backlash is completely right.
Every Pull Request Gets Its Own Environment: The Real Build-vs-Buy Math for Preview Environments
Shared staging lets a team finish 12 of 42 tickets while the rest queue. Preview-per-PR fixes that — the question is whether to build it on a Cluster-API fleet or buy it from Bunnyshell, Uffizzi, or Northflank. First-year totals, the breakeven near 20 concurrent PRs, and the six jobs every solution must cover.
Kubernetes Metrics API Is Stable in v1.37: What a Self-Hosted PaaS Must Expose Before Agents Can Safely Autoscale Apps
Kubernetes 1.37 made the Metrics API stable, but stability doesn't make it safe for an AI agent to autoscale on. Here's the isolation, staleness, and admission contract a self-hosted PaaS needs first.
Coolify's 11 Critical CVEs and 52,890 Exposed Dashboards: What a Single Root Daemon's Blast Radius Actually Looks Like
Coolify disclosed 11 critical CVEs in January 2026 — five rated CVSS 10.0 — with 52,890 dashboards exposed online. Eight months later, here is what changed, what didn't, and why blast radius per CVE is the number that should drive self-hosted PaaS architecture choices.