Densify: K8s: Autoscaling + Karpenter Optimization
There is a common thought that when you implement technologies like HPA and Karpenter, you are also taking care of optimization. The reality is that autoscaling is not optimizing. It is important to allow for scaling up and down but in the absence of resource optimization, you will never be in the most cost effective state. In fact, autoscaling can actually make you less efficient than with a more static configuration.
Join us to learn about strategies that are the best of both worlds.
On September 19, we will cover 3 reasons autoscaling does not equal optimization:
- In most cases autoscalers don’t optimize pod requests and limits
- Autoscaling unoptimized pods or nodes simply amplifies the issue
- Even autoscaling solutions that optimize container sizes have opaque algorithms and fail to account for historical trends
Who would this benefit?
- FinOps Practitioners with responsibility for K8s
- GKE, AKS, EKS Platform Owners
- OpenShift Platform Owners
- Cloud Platform Owners
- SRE’s concerned about cost
You don’t want to miss this exciting session – register now!