Goldilocks

Goldilocks is a Kubernetes utility that recommends starting-point resource requests and limits for your workloads.

  • Infrastructure
  • Monitoring & Logging
  • Tools & Utilities
Goldilocks is a Kubernetes utility that recommends starting-point resource requests and limits for your workloads. It creates Vertical Pod Autoscalers in recommendation mode and displays suggestions in a dashboard, helping operators right-size container resources without changing live workloads.

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.

71/100 Good

Maintained
95last commit 1 day ago
Popular
713,367 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
67no serious findings, 10 minor, CI, tests, OpenSSF Scorecard 6.3/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
3,367
Open issues
13
Last commit
2026-11-20
Latest release
v4.16.4
License
Apache-2.0
Activity
rising

Checked today - source: GitHub (FairwindsOps/goldilocks)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Use Helm and create the goldilocks namespace Use Helm (a package installer for Kubernetes) to add the Fairwinds stable repo, create the goldilocks namespace, and install the chart into that namespace. Skipping the repo or namespace can break the install because Helm cannot find the chart or the app ends up in the wrong place. source
  • If using manifests, apply both parts If you are not using Helm, create the goldilocks namespace and then apply both the controller and dashboard manifests from the hack/manifests folder. You need both parts: the controller analyzes workloads, while the dashboard shows the recommendations. source
  • Skip the one-off CLI for first install The standalone goldilocks CLI is not the normal way to run Goldilocks, because it is scoped to one namespace at a time. It also does not clean up VPA objects (Kubernetes autoscaling resources), so it can leave leftovers behind. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Goldilocks generate resource request and limit recommendations by itself?

No. The FAQ says Goldilocks does not do any recommending of resource requests/limits by itself.

Where can users get Fairwinds open-source community support for Goldilocks?

Fairwinds documentation points users to the Fairwinds Open Source Slack community for chat.

Where are Goldilocks issues and development contributions handled?

They are handled in the GitHub issues and contribution workflow for the FairwindsOps/goldilocks repository.

Answers sourced from github.com, goldilocks.docs.fairwinds.com, insights.docs.fairwinds.com

Community

Collected 48 days ago - public community threads