[UPCOMING FEATURE] Reduce your cloud cost with spot instances + Karpenter autoscaler - Looking for beta testers!


TLDR; we are looking for beta testers for a new feature to reduce the cost of your non-production clusters (Karpenter + spot instances).

We have been working over the past quarter to improve the way the cluster node autoscaler behaves and, in particular, we plan to move out from the AWS cluster autoscaler and migrate to Karpenter (a new autoscaler developed by AWS).

I’ll try to sum up here the advantages of using Karpenter as autoscaler:

  • allocation optimizations: Karpenter optimizes the workload allocation on your cluster nodes. More in detail, it looks at the number of CPU/RAM needed by all your applications and finds the best cost-effective combination of instance types to run your applications. Moreover, you can run your cluster with only 1 or 2 instances (today the minimum is 3)
  • Spot instances: if the feature is enabled, Karpenter will provision EC2 spot instances to run your applications, strongly reducing your EC2 cost (more info on EC2 spot instances here). If no spot instances are available, it will fall back to the standard on-demand EC2 instances (the same instances we provision today).

Looking for beta testers!

We are looking for beta testers to validate our feature before making it available to everyone.

We have only a few pre-requisite to participate:

  • the cluster should NOT run critical workloads (no production, we are still in a beta phase :slight_smile: ). The best would be a cluster running ephemeral environments or staging/dev environments.
  • it’s a one-way feature activation: once we switch your cluster to use Karpenter, there’s no turning back (if you want to go back to the previous setup, you’ll have to create a new cluster from scratch and clone the environments there)
  • proactively report any problem you may find while using the new autoscaler or ideas you have in mind to improve these two features.

If you want to participate, feel free to contact us on intercom or direct message me here on the forum.



Just for record:

I stress-tested Karpenter and EKS with Qovery (I’m co-founder). I’m impressed by Karpenter and to me, it’s a game-changer tool for everyone using EKS / Kubernetes. It must definitely replace the default node autoscaler that is really basic and makes people using EKS waste money!

1 Like