aws/karpenter-provider-aws

Karpenter is a Kubernetes Node Autoscaler built for flexibility, performance, and simplicity.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 19 minutes ago
Added to GitGenius on September 8th, 2026
Created on July 9th, 2020
Open Issues & Pull Requests: 511 (+1)
GitHub issues: Enabled
Number of forks: 1,325
Total Stargazers: 7,715 (+0)
Total Subscribers: 80 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 30.4 hours
Mean response time: 19.4 days
90th percentile: 24.4 days
Tracked items: 904

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 98% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "question" is answered fastest, typically in about 16 hours, while "documentation" waits about 3 days. 51% of tracked open issues have had no activity in three months. Only 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 266
New in 7 days: 0
Closed in 7 days: 4
Avg open age: 617 days
Stale 30+ days: 235
Stale 90+ days: 204

Recent activity

Opened in 7 days: 0
Closed in 7 days: 3
Comments in 7 days: 3
Events in 7 days: 5

Top labels

  • bug (372)
  • feature (290)
  • lifecycle/stale (207)
  • lifecycle/closed (195)
  • needs-triage (180)
  • triage/needs-information (176)
  • triage/accepted (142)
  • documentation (101)

Detailed Description

Karpenter is a Kubernetes node autoscaler built for flexibility, performance, and simplicity. It automatically provisions and removes nodes in response to workload demands, watching for unschedulable pods and evaluating their scheduling constraints to determine what infrastructure is needed.

The tool addresses the inefficiency of static node pools and the limitations of traditional cluster autoscalers by taking a workload-driven approach. It observes pods that the Kubernetes scheduler cannot place, examines their resource requests, node selectors, affinities, tolerations, and topology spread constraints, then provisions nodes that satisfy those requirements. When nodes are no longer needed, it removes them to reduce costs. This reactive model eliminates the need to pre-configure node groups and allows the cluster to respond dynamically to actual workload patterns.

Teams running Kubernetes on AWS should consider Karpenter if they want to reduce infrastructure costs while improving scheduling efficiency. It works well for clusters with variable or unpredictable workloads, and for environments where fine-grained control over node provisioning decisions is valuable. The README references a comparison with Kubernetes Cluster Autoscaler, positioning Karpenter as an alternative approach to the same problem.

The project maintains active engagement with its community through a dedicated Slack channel and bi-weekly working group meetings. Development activity shows sustained focus on core functionality, with multiple talks and presentations delivered over time demonstrating ongoing refinement of the tool's capabilities and use cases.