Configure Karpenter| karpenter.sh
Set up a cluster and add Karpenter| karpenter.sh
Understand different ways Karpenter disrupts nodes| karpenter.sh
Understand the key concepts and requirements for network interfaces.| docs.aws.amazon.com
Configure AWS-specific settings with EC2NodeClasses| karpenter.sh
FEATURE STATE: Kubernetes v1.21 [stable] This page shows how to limit the number of concurrent disruptions that your application experiences, allowing for higher availability while permitting the cluster administrator to manage the clusters nodes. Before you begin Your Kubernetes server must be at or later than version v1.21. To check the version, enter kubectl version. You are the owner of an application running on a Kubernetes cluster that requires high availability.| Kubernetes
This guide is for application owners who want to build highly available applications, and thus need to understand what types of disruptions can happen to Pods. It is also for cluster administrators who want to perform automated cluster actions, like upgrading and autoscaling clusters. Voluntary and involuntary disruptions Pods do not disappear until someone (a person or a controller) destroys them, or there is an unavoidable hardware or system software error.| Kubernetes