Cluster Autoscaler

Kubernetes Cluster Autoscaler is a component that automatically adjusts worker nodes in autoscaling groups so cluster operators keep pod capacity while…

  • Infrastructure
  • Tools & Utilities
Kubernetes Cluster Autoscaler is a component that automatically adjusts worker nodes in autoscaling groups so cluster operators keep pod capacity while removing unneeded nodes.

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.

76/100 Good

Maintained
100last commit 0 days ago
Popular
799,007 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
9,007
Open issues
331
Last commit
2026-11-21
Latest release
vertical-pod-autoscaler-chart-0.17.0
License
Apache-2.0
Activity
rising

Checked today - source: GitHub (kubernetes/autoscaler)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Add the cluster library to your project In your Podfile, add the line pod "Cluster", then run your normal project setup so it is downloaded. This gets the library your app needs; without it, the app can't build or show grouped map markers. source
  • Create a ClusterManager and set its delegate Make a ClusterManager and assign your map screen or controller as its delegate. This lets the library know where to send updates when locations change; if you skip it, new markers or cluster changes may not appear. source
  • Add locations and tell the map what to draw Add each location as an annotation to the manager, and in your map delegate return the cluster or pin view for those annotations. Without these views, the map has no instructions for what a cluster or marker should look like. source
  • Install Cluster Autoscaler Deploy the Cluster Autoscaler Helm chart with a supported cloud-provider configuration, because it manages cloud autoscaling groups. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How does Cluster Autoscaler decide when to add nodes?

It periodically checks for pending pods and increases the cluster size if that makes sense and the scaled-up cluster stays within user-provided constraints.

Can I control whether DaemonSet pods are evicted?

Cluster Autoscaler may evict DaemonSets based on its cluster-wide configuration, but desired behavior can be specified on a per-pod basis.

Can Cluster Autoscaler scale self-hosted GitLab runners running on spot instances?

A user reports that automatic scaling works well for self-hosted GitLab runners on Kubernetes with spot instances if the Cluster Autoscaler is configured properly.

What can break an autoscaling node pool after virtual machine scale set changes?

Deleting the virtual machine scale set attached to the cluster can cause Cluster Autoscaler to fail. It can also cause problems when provisioning nodes and pods.

Answers sourced from github.com, github.com, learn.microsoft.com, www.reddit.com

Community

Collected 48 days ago - public community threads