You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Customer created a ticket ( https://solo-io.zendesk.com/agent/tickets/5239 ). Upstream dashboards in grafana do not get created when using watchNamespaceSelectors in Settings. I was able to reproduce this issue in my environment as well.
``
Expected Behavior
Defining watchNamespaceSelectors should find namespaces and add dynamic dashboards.
Steps to reproduce the bug
Installed gloo ( 1.18.2 ) , where no watchNamespaceSelectors is defined in Settings.
Added a static upstream , which is accepted from Gloo.
The text was updated successfully, but these errors were encountered:
chris530
changed the title
watchNamespaceSelectors does not pick up dynamic dashboards in grafana.
watchNamespaceSelectors does not create dynamic dashboards in grafana.
Jan 24, 2025
Gloo Edge Product
Enterprise
Gloo Edge Version
v1.18.2
Kubernetes Version
v1.31
Describe the bug
Customer created a ticket ( https://solo-io.zendesk.com/agent/tickets/5239 ). Upstream dashboards in grafana do not get created when using watchNamespaceSelectors in Settings. I was able to reproduce this issue in my environment as well.
``
Expected Behavior
Defining watchNamespaceSelectors should find namespaces and add dynamic dashboards.
Steps to reproduce the bug
Installed gloo ( 1.18.2 ) , where no watchNamespaceSelectors is defined in Settings.
Added a static upstream , which is accepted from Gloo.
Logging into grafana, a upstream dashboard was created.
I reinstall gloo with same steps. Then label namespace.
Confirmed label selector is working
Added label selector to settings.
Waiting awhile, ( also restarted observability pod ). upstream dashboard never gets created.
NOTE: If I remove the watchNamespaceSelectors in Settings , the dashboard gets immediately created in grafana.
Additional Environment Detail
Gloo 1.18.2
K8s 1.31
EKS
Additional Context
Followed these steps
https://docs.solo.io/gloo-edge/main/operations/upgrading/faq/
https://docs.solo.io/gloo-edge/main/installation/advanced_configuration/multiple-gloo-installs/#specify-namespaces-to-watch-for-kuberenetes-services-and-gloo-gateway-crs
The text was updated successfully, but these errors were encountered: