640 posts tagged with "Kubernetes"
Container orchestration, Cluster API, and self-hosted control planes
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.
KEDA's Queue-Depth Autoscaling vs. Render and Railway's Black-Box Scaling
A practical comparison of KEDA's queue-aware Kubernetes autoscaling with Render and Railway's documented CPU, memory, and replica controls, including a worked worker-backlog example.
Kubernetes Metrics API Is Stable in v1.37: The Contract Agents Need Before Autoscaling Apps
Kubernetes v1.37 makes metrics.k8s.io stable, but stable data is not safe automation. Here is the concrete, tenant-scoped contract a self-hosted PaaS should expose before an AI agent changes replicas.
Kubero vs Porter vs Coolify: What Happens When Your Self-Hosted Heroku Needs a Second Server?
Kubero, Porter, and Coolify all bring Heroku-like deployment to infrastructure you control. This comparison shows where app deployment ends and machine provisioning, replacement, traffic routing, and fleet reconciliation begin.
8% CPU, 69% Overprovisioning: A 30-Minute Kubernetes Fleet Audit
Measure allocatable, requested, and used resources in 30 minutes, then test whether a self-hosted Kubernetes fleet can safely remove a node without sacrificing N-1 resilience.
Before AI Agents Operate Your Platform: The Catalog Hygiene Contract Your IDP Needs
Use a field-level catalog contract, a worked deploy example, and staged authority controls to let AI agents safely operate a self-hosted developer platform.