EKS Retype EC2 Optimize Manually
AWS Resource Type:
Amazon EKS, Amazon EC2
This finder identifies EKS clusters that can be optimized by using Karpenter to manage autoscaling of your EKS cluster. Karpenter is an open-source node provisioning project which can dramatically improve the efficiency and cost of running workloads on EKS. In addition, this finder recommends retyping opportunities for the underlying EC2 instances to more modern, cost-effective architectures and generations (without changing the actual instance sizes). Recommendations include migrating instances to Graviton, AMD, and the newest generation of the current instance type.
Criteria for identifying the opportunity:
This finder identifies non-Spot EC2 instances running in an active EKS cluster and checks to see if Karpenter is running on the cluster.
Potential savings (range in % on annual basis):
Savings will vary depending on the recommendation. Karpenter savings can vary based on your workload and cluster size. Typical Graviton migrations can result in as much as 40% price performance improvement when migrating from x86-based instances.
What happens when the Fixer is executed?
There is no automated fixer with this finder. The finder presents recommendations on how to install Karpenter and how to manually retype instances in the target EKS cluster. Users will report back once the manual actions have been taken so that savings can be computed after the recommendations are implemented.
Is it possible to rollback once CloudFix implements the fixer?
Yes, however rollback would be a manual process and would be the responsibility of the user to track the previous state of the cluster before making modifications.
Can CloudFix implement the fix automatically once I accept the recommendation?
No, this is a manual fix that must be executed by the user.
Does this fix require downtime?
Installing Karpenter does not require downtime. Retyping the underlying EC2 instances does.