kubernetes-on-aws icon indicating copy to clipboard operation
kubernetes-on-aws copied to clipboard

Published 20 hours ago • verified publisher icon zalando-incubator

Introduce Karpenter

Open mikkeloscar opened this issue 3 years ago • 2 comments

Changes needed for introducing Karpenter as an optional autoscaler

This PR is just showing of the Proof of Concept as presented in the demo

mikkeloscar avatar May 19 '22 14:05 mikkeloscar

@mikkeloscar as far as I saw in notification e-mails, this was not properly load tested. We need:

  1. overlap test of without karpenter, to karpenter
  2. ingress controller create/delete/update ALB and NLB
  3. svc type load balancer test.

One open question would be if it makes sense to switch the ingress controller to AWS CNI mode, because it will detect the nodes faster like this.

szuecs avatar May 19 '22 17:05 szuecs

@szuecs you're right, so far there is no decision when to try this out. I demoed it for the team yesterday and I made these PRs to show what was done and to work as a starting point for going forward with this.

This is done in a way where it's only enabled if there are node pools of profile worker-karpenter, so we could even run it next to the skipper-ingress node-pools as a start and skipper-ingress/ingress-controller would have the old behavior. If we see a benefit of karpenter then we could explore the skipper-ingress/ingress-controller use case how you suggest. At least that's how I think about it right now.

mikkeloscar avatar May 20 '22 07:05 mikkeloscar

We are still waiting for this fix to be released. then we will upgrade karpenter version https://github.com/aws/karpenter/issues/3697

myaser avatar Apr 14 '23 09:04 myaser

👍

linki avatar May 09 '23 14:05 linki

👍🏻

myaser avatar May 09 '23 14:05 myaser