aws/karpenter-provider-aws
Karpenter Provider Aws
karpenter-provider-aws is a Kubernetes node autoscaler and infrastructure provider for AWS. It serves as a node lifecycle manager and cluster cost optimizer that automatically provisions and removes compute instances based on the resource requirements of pending pods.
The project distinguishes itself through advanced AWS spot instance orchestration and price-capacity optimized selection to reduce cloud spend. It minimizes costs by consolidating underutilized nodes and prioritizing spot or reserved instances over on-demand capacity, while proactively migrating workloads before cloud provider interruptions occur.
The provider covers a broad range of capabilities including hardware provisioning for GPUs and bare metal servers, machine image management, and zonal fault tolerance. It manages networking configurations, storage topology alignment, and identity assignment, while implementing disruption guardrails and pacing to maintain application availability during scaling events.
Features
- Cluster Cost Optimizers - Reduces cloud spend by removing empty nodes, consolidating pods, and migrating workloads to cheaper instance variants.
- Compute Node Autoscaling - Automatically provisions and removes cloud compute instances based on the resource demands of pending pods.
- Price-Capacity Optimization - Ranks instance types using current pricing and availability data to minimize spot interruptions and reduce spend.
- Cloud Infrastructure Cost Optimization - Reduces cloud spending by consolidating underutilized nodes and prioritizing cheaper spot or reserved instance types.
- Cloud Node Lifecycle Management - Maintains stability and reduces waste by removing underutilized or expired nodes and coordinating interruption handling.
- AWS Provisioners - Manages EC2 instance lifecycles, machine images, and networking specifically for AWS-based Kubernetes clusters.
- Kubernetes Cluster Autoscalers - Automatically provisions and removes compute instances based on the resource requirements of pending pods.
- Cluster State Reconciliation - Implements continuous processes to align the actual state of the cluster with the desired node pool configuration.
- Node Draining - Ensures workloads are migrated to healthy nodes by draining and shutting down instances gracefully.
- Resource Simulation Selection - Models pod resource requirements against available instance types to select the most cost-effective compute options.
- High Availability Clustering - Distributes compute capacity across availability zones and manages pod disruption budgets to ensure application uptime.
- Instance Type and Mix Policies - Ranks and prioritizes instance types across reserved, spot, and on-demand categories to minimize cloud spend.
- Kubernetes Cluster Management - Rotates nodes to handle configuration drift, automate image upgrades, and enforce maximum node lifetimes.
- Kubernetes Node Lifecycle Management - Handles node expiration, configuration drift, and graceful drainage of instances during cloud interruptions.
- Kubernetes Node Provisioning - Creates and removes compute instances across cloud providers to optimize workload placement and reduce costs.
- Node Lifecycle Recycling - Recycles nodes based on expiration timers, configuration drift, or predicted interruption events to maintain security.
- Price-Capacity Optimized Allocation - Balances infrastructure cost and availability using price-capacity optimized allocation strategies for spot and on-demand capacity.
- Spot Instance Orchestration - Manages interruptible spot instances by processing health events and notifications to migrate workloads.
- Cloud Interruption Handling - Drains nodes proactively by watching for cloud provider interruption events to allow workloads to migrate.
- Infrastructure Interruption Handling - Processes cloud health events and spot notifications to migrate workloads before instances are reclaimed.
- Capacity Consolidation - Minimizes infrastructure costs by replacing underutilized nodes with fewer or cheaper instances.
- Automated Node Rotation - Automatically replaces nodes when newer machine images are available or when current nodes drift from the desired configuration.
- Infrastructure Disruption Pacing - Controls the pace of node replacements by restricting the number of disruptions and defining allowed windows.
- Capacity-Type Workload Distribution - Splits pods across on-demand and spot instances using defined ratios and topology spread constraints.
- Cloud Block Storage Provisioning - Defines block device mappings and instance-store volume handling for provisioned cloud nodes.
- Topology Alignment - Launches nodes in specific availability zones to ensure compatibility with existing zonal storage volumes.
- Attribute-Based Provisioning - Selects the most appropriate instance types by matching requirements against hardware attributes like CPU, memory, and storage.
- Cloud Resource Discovery - Defines cluster endpoints and cloud-provider settings to identify and connect to the target environment.
- Capacity-Based Node Drainage - Drains nodes preemptively based on capacity block expiration to ensure graceful termination before hardware reclamation.
- Mixed Capacity Orchestration - Combines dynamic and fixed compute capacity by operating alongside static node groups or other autoscalers.
- Node Pool Segmentation - Creates isolated sets of nodes for different teams or workloads using labels and scheduling constraints.
- Node Retirement - Drains and terminates nodes automatically after they reach a predefined maximum lifetime.
- Custom Node Images - Defines the operating system and boot images for new nodes using configurable image families and custom images.
- Workload Isolation - Separates team or application requirements using distinct node pools with specific operating systems and instance types.
- Label-Based Node Segregation - Segregates workload subsets onto different nodes by applying pod-specific key-value pairs during launch.
- Hardware Accelerator Provisioning - Launches nodes with specific hardware accelerators based on resource requests in the workload manifest.
- Hardware Constraint Configurations - Allows restricting provisioned instances to specific architectures, instance families, or specialized hardware like GPUs and bare metal servers.
- Drift Detection - Replaces nodes when the actual state differs from the desired configuration defined in the node pool.
- Instance Placement Policies - Controls latency and fault isolation by assigning nodes to specific placement groups using diverse distribution strategies.
- Kubelet Resource Reservations - Adjusts kubelet arguments including reserved resources and memory or disk eviction thresholds for stability.
- GPU Node Provisioners - Launches compute instances with hardware accelerators based on workload resource requests.
- Machine Image Resolution - Dynamically retrieves and selects the most compatible operating system images for provisioning new cluster nodes.
- Storage-Aware Zonal Placement - Matches node launch locations to the availability zones of existing persistent volumes to ensure storage compatibility.
- Network Configurations - Manages subnet selection, security group attachments, and high-performance network interface configurations for nodes.
- Node Scheduling Constraints - Applies temporary startup taints to new nodes to prevent pod scheduling until networking and agents are ready.
- Preemption Disruption Protections - Prevents voluntary termination of critical workloads using pod disruption budgets and annotations during node consolidation.
- Availability Budget Protection - Prevents node replacement if the action would breach pod disruption budgets to ensure applications remain healthy.
- Node Disruption Blocking - Prevents specific nodes from being selected for voluntary disruption using protective metadata annotations.
- Pod Disruption Control - Prevents the eviction of specific pods during voluntary disruption using disruption budgets or metadata annotations.
- Reserved Capacity Allocation - Allocates specific capacity reservations or blocks to ensure guaranteed compute availability for critical workloads.
- Zonal Traffic Shifting - Improves cluster recovery by moving traffic and scaling operations across availability zones using zonal shift controls.
- Workload Placement Policies - Implements pod-level scheduling constraints using taints and tolerations to restrict where workloads run on cluster nodes.
- Capacity Prioritization - Prioritizes the use of pre-purchased capacity via IDs or tags before falling back to on-demand or spot instances.
- Instance-Level IAM Assignments - Specifies the identity role or instance profile that provisioned nodes assume.
- Disruption - Maintains cluster stability by capping the percentage of nodes that can be voluntarily disrupted simultaneously.
- Provisioning Constraints - Limits node creation to specific zones and architectures to ensure workloads run on compatible hardware.
- Node Health Tracking - Tracks the launch, registration, and initialization status of nodes to identify provisioning failures.
- System Repair Tools - Automatically replaces nodes with failing hardware based on cloud provider repair policies.
- Cluster Provisioning - Node autoscaler built for flexibility and performance.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
