Skip to content

Karpenter Best Practices

Best Practices

  • Lock down AMIs in production clusters
  • Use Karpenter for workloads with changing capacity needs
  • Consider other autoscaling projects when you need features that are still being developed in Karpenter.
  • Run the Karpenter controller on EKS Fargate or on a worker node that belongs to a node group
  • No custom launch templates support with Karpenter
  • Exclude instance types that do not fit your workload
  • Enable Interruption Handling when using Spot
  • Amazon EKS private cluster without outbound internet access