/namespaces dashboard page shows "no namespaces labelled" when running with --on-by-default=true

[xxer10]

What happened?

Running on:
Goldilocks version: chart 10.3.0 / app v4.14.1
Kubernetes version: 1.35 (AKS and EKS)
Helm install with controller.flags.on-by-default: "true"

Description

When Goldilocks is running with --on-by-default=true, the controller correctly
creates VPA objects for every (non-excluded) namespace. However, the /namespaces
page in the dashboard displays "No namespaces are labelled for use by Goldilocks.
Try labelling one with kubectl label ns NAMESPACE_NAME goldilocks.fairwinds.com/enabled=true",
even though the controller is actively analyzing those namespaces and /dashboard
shows their recommendations correctly.

/namespaces only enumerates namespaces with the explicit
goldilocks.fairwinds.com/enabled=true label, leaving the page empty when using
the on-by-default model.

Workaround
Navigate directly to /dashboard, which queries VPA objects (not labels) and
works correctly.

What did you expect to happen?

/namespaces page should enumerate the namespaces that have VPA objects managed
by Goldilocks (which under on-by-default=true is all non-excluded namespaces).

How can we reproduce this?

1. Install Goldilocks via Helm with:

   controller:
     flags:
       on-by-default: "true"
       exclude-namespaces: kube-system,kube-public,kube-node-lease,default,vpa
   

Do NOT label any namespaces with goldilocks.fairwinds.com/enabled
Verify VPA objects exist: kubectl get vpa -A (returns many)
Visit the dashboard root URL that auto-redirects to /namespaces
Page displays "no namespaces labelled" message despite VPA objects existing

Version

chart 10.3.0 / app v4.14.1

Search

• I did search for other open and closed issues before opening this.

Code of Conduct

• I agree to follow this project's Code of Conduct

Additional context

No response