3a6df3b544
This removes the default dashboards from the Grafana chart and instead places them in the values_overrides directory, similar to what was done for the Prometheus rules. As Grafana dashboards will likely be heavily dependent upon end-user needs, the old default dashboard configs should only be used as a reference instead of opinionated defaults that are difficult to override. The previous defaults made using specialized labels for dashboard variables difficult, as they were making dangerous assumptions about deployed namespaces and host fqdns. By removing the defaults entirely, end users can define their own dashboards to meet their specialized needs Change-Id: I7def8df68371deda0b75a685363c8a73b818dd45 Signed-off-by: Steve Wilkerson <sw5822@att.com> |
||
|---|---|---|
| .. | ||
| bin | ||
| configmap-bin.yaml | ||
| configmap-etc.yaml | ||
| deployment.yaml | ||
| ingress-grafana.yaml | ||
| job-db-init-session.yaml | ||
| job-db-init.yaml | ||
| job-db-session-sync.yaml | ||
| job-image-repo-sync.yaml | ||
| job-set-admin-user.yaml | ||
| network_policy.yaml | ||
| pod-helm-tests.yaml | ||
| secret-admin-creds.yaml | ||
| secret-db-session.yaml | ||
| secret-db.yaml | ||
| secret-ingress-tls.yaml | ||
| secret-prom-creds.yaml | ||
| service-ingress.yaml | ||
| service.yaml | ||