How EMP Works
EMP consolidates your EKS worker nodes on a pool of EC2 metal, replacing some or all existing workers with Elastic VMs (EVMs) running on AWS metal.
New EVM workers will be created based on Kubernetes scheduling requests, but they will be placed on existing pool of metal, till the metal nodes start running out of capacity.
So the workers may not be fully utilized, but underlying metal will be. And this is what you will pay for.
Scale & Rebalance with Live Migration
EMP monitors EVM resource utilization and dynamically scales AWS metal instances only when existing pool or metal is running out of utilized capacity.
EMP also auto rebalances EVMs across the bare metal pool, live migrating EVMs under the hood. So when existing metal nodes start to utilize all of their capacity, EMP will rebalance EVMs to other metal nodes.
EMP vs Existing Tools
Outcomes | EMP | Karpenter | CloudHealth | Cloudability | CloudZero | Kubecost |
---|---|---|---|---|---|---|
Improve resource efficiency using over-provisioning | ||||||
Rebalance and consolidate without pod disruption | ||||||
Eliminate changes to pod requests and limits | ||||||
Optimize usage via bin packing | ||||||
Cost visibility | ||||||
Resource tagging | ||||||
Cost allocation |