Making Karpenter More Reliable at Scale: Removing Its Dependency on CoreDNS

How Freshworks evolved its Karpenter bootstrap architecture across 400+ EKS clusters — and what it’s paying off now. by Ebin Gladson At Freshworks, our applications run on AWS EKS. A while back, we moved from Cluster Autoscaler to Karpenter, and the switch paid off in several concrete ways: ~37% faster node provisioning Tighter bin-packing of EC2 nodes across the fleet Real, ongoing cost savings…

This is an excerpt. The full article continues at Freshworks.