kubernetes/autoscaler

Autoscaling components for Kubernetes

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 47 minutes ago
Added to GitGenius on April 7th, 2021
Created on April 12th, 2017
Open Issues & Pull Requests: 317 (+0)
Number of forks: 4,468
Total Stargazers: 8,946 (+0)
Total Subscribers: 130 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.5 hours
Mean response time: 88.6 days
90th percentile: 219.5 days
Tracked items: 819

How this project is maintained

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

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 173
New in 7 days: 8
Closed in 7 days: 1
Avg open age: 369 days
Stale 30+ days: 134
Stale 90+ days: 64

Recent activity

Opened in 7 days: 8
Closed in 7 days: 1
Comments in 7 days: 27
Events in 7 days: 75

Top labels

  • area/cluster-autoscaler (533)
  • kind/bug (424)
  • area/vertical-pod-autoscaler (324)
  • lifecycle/rotten (318)
  • kind/feature (304)
  • triage/accepted (132)
  • area/core-autoscaler (120)
  • needs-triage (85)

Detailed Description

The kubernetes/autoscaler repository contains autoscaling-related components for Kubernetes, written primarily in Go. It serves as the central hub for multiple autoscaling solutions that address different scaling needs within Kubernetes clusters, from node-level adjustments to pod-level resource optimization.

The repository houses four main components. Cluster Autoscaler automatically adjusts the size of a Kubernetes cluster to ensure all pods have placement while eliminating unnecessary nodes, with support for multiple public cloud providers. It reached general availability status with Kubernetes 1.8. Vertical Pod Autoscaler, currently in beta, automatically adjusts CPU and memory requests for running pods. Addon Resizer provides a simplified alternative to vertical pod autoscaling by modifying resource requests based on cluster node count, also in beta status. The repository also includes supported Helm charts for both Cluster Autoscaler and Vertical Pod Autoscaler, facilitating easier deployment and management of these components.

Activity data reveals this is an actively maintained project with significant community engagement.

This interconnectedness reflects the autoscaler's foundational role in Kubernetes infrastructure management and its reliance on core Kubernetes functionality and Go language development.

The project is organized around the Special Interest Group for Autoscaling within the Kubernetes community. Contributors are encouraged to engage through the sig-autoscaling channel on Kubernetes Slack and participate in weekly meetings, with additional information available in the Kubernetes Community Repository.

The classification data indicates the repository spans both horizontal and vertical scaling domains, addressing resource management and workload optimization across cloud-native computing environments. The breadth of autoscaling policies and mechanisms covered makes this repository essential infrastructure for organizations running Kubernetes clusters that require dynamic resource allocation based on demand.