karpenter VS buildpacks-jvm

Karpenter, is a cluster autoscaling solution that, for the moment, only works with AWS infrastructure, but helps you increase the number of nodes automatically depending on your Pods requirements.

I have a few EKS clusters that are running cluster-autoscaler, and I'd like to replace it with Karpenter. When reading through the documentation this stood out to me:

Karpenter: since we are talking about EKS maybe this kind of autoscaling is worth your time.

Karpenter

This post demonstrates a proof-of-concept implementation that uses Kubernetes to execute code in response to an event here is API request. The workflow is powered by Keda (Kubernetes Event-driven Autoscaling) which scales out the kubernetes pods bases on incoming events such as SQS messages. After keda scaleout pods which are in pending state, Karpenter (Just-in-time Nodes for Any Kubernetes Cluster) bases on provisioners to decide scaleout more nodes

Here is the GitHub repo of the tool, and I wrote an article about it if you're interested.

When searching for a cluster autoscaler for EKS, I found out about Karpenter. It's an open-source Kubernetes native node autoscaler developed by AWS.

💡 Karpenter.sh takes a more intelligent, faster approach to autoscaling and improve availability on AWS.

karpenter Helm Release - Installation of karpenter using Helm chart.

Karpenter is an open-source project by AWS that improves the efficiency and cost of running workloads on Kubernetes clusters (not just EKS, it's designed to have support for multiple cloud providers).

They may already have, looks like that archived repository has been replaced with: https://github.com/heroku/heroku-buildpack-java

which doesn't even use go.

And they'd like you to even move away from that replacement to an ever newer replacement: https://github.com/heroku/buildpacks-jvm