fairwindsops/goldilocks

Get your resource requests "Just Right"

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 5 minutes ago
Added to GitGenius on September 20th, 2026
Created on April 25th, 2019
Open Issues & Pull Requests: 14 (+0)
GitHub issues: Enabled
Number of forks: 176
Total Stargazers: 3,346 (+0)
Total Subscribers: 33 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 58 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

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

Top labels

  • triage (28)
  • stale (24)
  • enhancement (20)
  • bug (14)
  • pinned (6)
  • good first issue (4)
  • priority: could (4)
  • duplicate (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Goldilocks is a Kubernetes tool that helps teams right-size container resource requests and limits by analyzing actual usage patterns and providing recommendations.

The problem Goldilocks solves is that setting appropriate CPU and memory requests in Kubernetes is difficult without visibility into how applications actually consume resources. Undersized requests lead to pod evictions and performance issues, while oversized requests waste cluster capacity. The tool works by integrating with the Vertical Pod Autoscaler to collect resource usage metrics and generate recommendations for what requests should be. It presents these findings through a web dashboard that makes it easy to review suggestions across workloads and namespaces.

Teams managing Kubernetes clusters who want to optimize resource allocation without manual analysis should consider Goldilocks. It suits environments where you already have metrics collection in place and want to act on that data systematically. The tool is particularly valuable for organizations running many applications where manual tuning would be impractical, or for teams new to Kubernetes who need guidance on reasonable resource values.

Development on the project shows consistent activity with regular commits addressing issues and improvements. The maintainers respond to pull requests and issues, indicating active engagement with the user community. Work spans both bug fixes and feature additions, suggesting the project is maintained beyond initial release. The codebase receives updates that reflect evolving Kubernetes practices and user feedback.