Files
Alexey Artamonov e8609ac00d fix(keda): ship the autoscaling dashboard via grafana-operator, not a dead ConfigMap
The database-autoscaling dashboard shipped from the keda package as a ConfigMap
labeled grafana_dashboard: "1" for a Grafana sidecar that cozystack does not run
(no k8s-sidecar anywhere; every dashboard is provisioned by grafana-operator from
the grafana-dashboards image via GrafanaDashboard CRs). It was enabled by default
and never appeared in any Grafana. Move the JSON to dashboards/db/database-autoscaling.json
and register db/database-autoscaling in packages/system/monitoring/dashboards.list,
exactly how db/cloudnativepg and the other managed-db dashboards ship, and drop the
keda ConfigMap, its default-on toggle, and its wrong-mechanism test.

Addresses IvanHunters [MAJOR] review feedback on #3954.

Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>
2026-09-04 23:19:25 +03:00

18 lines
365 B
Plaintext

ingress/controller-detail
ingress/controllers
ingress/namespaces
ingress/vhosts
ingress/vhost-detail
ingress/namespace-detail
db/cloudnativepg
db/maria-db
db/redis
db/database-autoscaling
vm/virtual-machines
kafka/strimzi-kafka
clickhouse/altinity-clickhouse-operator-dashboard
nats/nats-jetstream
nats/nats-server
mongodb/mongodb-overview
mongodb/mongodb-inmemory