FEATURED STORIES
Kubernetes HPA on Memory: Working Examples, CPU + Memory Combined, and Troubleshooting
You can scale a Deployment on memory with a plain autoscaling/v2 HorizontalPodAutoscaler and no extra tooling: set a Resource metric named memory, give every container a memory request, and have metrics-server running. The manifest below does exactly that. The rest of this article is about what the HPA actually does with that manifest — how the number is computed, what changes when you add CPU next to it, why it scales down slower than you expect, and what every error message in kubectl describe hpa means. apiVersion: autoscaling/v2 kind: HorizontalPodAutoscaler metadata: name: worker-memory namespace: default spec: scaleTargetRef: apiVersion: apps/v1 kind:…
🎙 ON RADAR PODCAST
LATEST STORIES
Kubernetes Features That Hurt in Production: A Framework for Safer Adoption
Why I Built an Investment Tracker That Doesn’t Connect to Your Broker
Kubernetes Namespace Isolation: When Security Boundaries Fail
Lazy-Pulling in Containerd v2: Why Pull Time Isn’t the Right Metric
Beyond GPU Drivers: Custom Node Readiness for Specialized Workloads
Kubernetes Liveness Probe Anti-Patterns: Preventing Cascading Failures