karpenter-provider-aws VS kured

This blog explores how Karpenter and EKS Auto Mode transform Amazon Kubernetes cluster management.

Simplify Data Plane Upgrades: Use Managed Node Groups for automated rolling updates or Karpenter for dynamic node provisioning, making node upgrades easier and less error-prone.

Implement Instance Autoscaling: Configure autoscaling for worker nodes by using Karpenter to adjust resources based on demand dynamically.

A point worth noting is that using the AWS Load Balancer Controller decouples your node management with your cluster management. Let’s say we wanted to use Karpenter for autoscaling instead of the defacto cluster-autoscaler. Karpenter will not use AWS AutoScalingGroups but will instead create standalone EC2 instances based on the Provisioners you define. This means our previous approach of attaching AutoScalingGroups with TargetGroups will not work as the EC2 instances Karpenter manages will not belong to the AutoScalingGroup and therefore not be automatically attached to the TargetGroup. The AWS Load Balancer Controller doesn’t care how the nodes are created; only that they belong to the cluster and match the label selectors defined. Probably we will look into Karpenter again in the near future for our project now that it supports pod anti-affinity, as this was previously a blocker for us.

Built in AWS, Karpenter is a high-performance, flexible, open-source Kubernetes cluster auto-scaler. One of its key features is the ability to launch EC2 instances based on specific workload requirements such as storage, compute, acceleration, and scheduling needs.

Documentación Oficial de Karpenter Post Community AWS - Christian Melendez (AWS) Video Explicativo Karpenter Workshop Karpenter (AWS)

Karpenter is a high-performance Kubernetes cluster autoscaler that dynamically provisions worker nodes to meet the resource demands of unscheduled pods.

Karpenter: https://karpenter.sh/

Dan: Argo CD is the first tool I install. For AWS, I will add Karpenter to manage costs. I will also use Longhorn for on-prem storage solutions, though I'd need ingress. Depending on the situation, I will install Argo CD first and then one of those other two.

Maaaaybe, but it's not really what it's suited for. For the Kubernetes host, I'd recommend you enable auto-updates, and then deploy https://github.com/kubereboot/kured to perform reboots as required (you can have it check alertmanager for current alerts, and only do a reboot during a maintenance window if there are no alerts)

OS patches, which are installed automatically by AKS. If restarts are required, we let https://github.com/weaveworks/kured handle it

kured : automatic restarts of kubernetes nodes

See https://github.com/weaveworks/kured or https://github.com/MnrGreg/kubectl-node-restart

You may want to check this https://github.com/weaveworks/kured It is very useful when updating underlying OS on nodes - allows you detect and restart gracefuly