Karpenter

Karpenter is an open-source node auto-provisioning tool for Kubernetes that dynamically provisions and deprovisions nodes to match pod scheduling requirements.

  • Infrastructure
  • Tools & Utilities
Karpenter is an open-source node auto-provisioning tool for Kubernetes that dynamically provisions and deprovisions nodes to match pod scheduling requirements. It helps operators reduce cluster cost and improve resource utilisation by right-sizing capacity in real time.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

75/100 Good

Maintained
100last commit 14 days ago
Popular
672,267 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
86no serious findings, CI, tests, OpenSSF Scorecard 6.4/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
2,267
Open issues
393
Last commit
2026-11-07
Latest release
v1.15.1
License
Apache-2.0
Activity
steady

Checked 14 days ago - source: GitHub (kubernetes-sigs/karpenter)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Create a NodePool after install Create a NodePool, the Kubernetes object that tells Karpenter what nodes to run, by setting a node class (the cloud-specific node settings) and node requirements. Without this, Karpenter does not know what nodes to create, so it will not scale anything. source
  • Check that the NodePool is ready Use kubectl get nodepools -o wide after creating the NodePool and look for Ready and NodeClassReady status. If those are false, the node class or node settings are not set up correctly, so Karpenter cannot launch nodes. source
  • Limit how many nodes can be replaced Add disruption budgets to your NodePool if you want Karpenter to replace only a certain number of nodes at once. This helps prevent drift (a node no longer matches the desired setup) or expiry (a node has reached its age limit) from interrupting too much work. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where should I report a security issue with Karpenter?

Use the Karpenter security issue reporting process. Do not create a public GitHub issue for it.

Does Karpenter use Kubernetes CRDs to manage node sets?

Yes, Karpenter uses Kubernetes CRDs for managing node sets.

Can Karpenter be used to provision nodes using spot, RIs, and savings plans?

A product that leverages Karpenter to manage EKS can provision and run nodes using spot, RIs, and savings plans. It can also detect unused savings plans.

What common issue areas are documented for troubleshooting the AWS Karpenter Provider?

The documentation covers installation challenges, provisioning problems, deprovisioning issues, and node readiness concerns.

Answers sourced from deepwiki.com, karpenter.sh, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads