1. Node Group Sizing Fewer large nodes vs. many small ones. Textbooks don't cover...
1. Node Group Sizing
Fewer large nodes vs. many small ones. Textbooks don't cover this.
We ran 10 nodes, 32 CPU each. Seemed efficient.
Problem: One node dies, 320 CPU worth of workloads need to reschedule. Cluster autoscaler couldn't handle it. Pods sat pending for 10 minutes.
We switched to 20 nodes, 16 CPU each. Same total capacity.
Introduction One of the most misleading situations in Kubernetes is when a pod keeps...
Learn how to implement Kubernetes pod autoscaling to ensure efficient resource utilization and high availability in your…
Part 2 of 7 — The Mac Kubernetes Lab: A Production-Mirror Setup from Scratch. Previously in Part 1:...
Most engineers talk about Kubernetes like it's something you set up once and forget. I set it up five...
How to leverage Kubernetes 1.36's new pod-level resource managers and in-place vertical scaling to optimize infrastructure costs…
Using Kubernetes is a love-hate relationship. Love, because before it, deploying to production was...
