Windows EKS Nodes & Quick Scaling

In a <a href="https://medium.com/@bixlerm/scaling-legacy-windows-applications-in-aws-6fa0322ec161" rel="noopener">previous post</a>, I went over the effects of using AWS Warm Pools for legacy windows applications. For Windows EKS Nodes, we take that same concept but “take it up a notch” to leveraging Warm Pools for faster launching of EKS Windows Nodes. Prior to Warm Pools, our servers were built using UserData and took ~20 min to build. Due to this, we set scaling schedules to ramp up in the morning and then back down in the evening as we couldn’t quickly respond to workload demands. This leads to extra costs of over-provisioned nodes when the auto-scaling group can be scaled-in. The challenges of leveraging Warm Pools for EKS Nodes. <a href="https://bixlerm.medium.com/windows-eks-nodes-quick-scaling-b9cf41c2f133">Visit Now</a>