New Dashboard: Simple Cluster Status Overview

[Zash]

• apps: copy blackbox exporter dashboard as base for new simple status
• apps: rework cluster-status overview

[!warning] This is a public repository, ensure not to disclose:

• [ ] personal data beyond what is necessary for interacting with this pull request, nor
• [ ] business confidential information, such as customer names.

What kind of PR is this?

Required: Mark one of the following that is applicable:

• [x] kind/feature
• [ ] kind/improvement
• [ ] kind/deprecation
• [ ] kind/documentation
• [ ] kind/clean-up
• [ ] kind/bug
• [ ] kind/other

Optional: Mark one or more of the following that are applicable:

[!important] Breaking changes should be marked kind/admin-change or kind/dev-change depending on type Critical security fixes should be marked with kind/security

• [ ] kind/admin-change
• [ ] kind/dev-change
• [ ] kind/security
• [ ] [kind/adr]()

What does this PR do / why do we need this PR?

Adds a new dashboard intended to provide a better user-facing overview of the overall state of the cluster. It should answer the question "Is the cluster working?" and "Has there been recent problems?" It's based on the Prometheus Blackbox Exporter Dashboard, with some panels at the top added and tweaked.

• Fixes #2325

Information to reviewers

• Does it tell you if the cluster is working?

• Does it tell you if the cluster is has had recent issues?

• Are there any other indicators

• Should this be merged back into the Prometheus Blackbox Exporter?

Checklist

• [ ] Proper commit message prefix on all commits
• Change checks:
  • [x] The change is transparent
  • [ ] The change is disruptive
  • [x] The change requires no migration steps
  • [ ] The change requires migration steps
  • [ ] The change upgrades CRDs
  • [ ] The change updates the config and the schema
• Documentation checks:
  • [ ] The public documentation required no updates
  • [ ] The public documentation required an update - link to change
• Metrics checks:
  • [ ] The metrics are still exposed and present in Grafana after the change
  • [ ] The metrics names didn't change (Grafana dashboards and Prometheus alerts are not affected)
  • [ ] The metrics names did change (Grafana dashboards and Prometheus alerts were fixed)
• Logs checks:
  • [ ] The logs do not show any errors after the change
• Pod Security Policy checks:
  • [ ] Any changed pod is covered by Pod Security Admission
  • [ ] Any changed pod is covered by Gatekeeper Pod Security Policies
  • [ ] The change does not cause any pods to be blocked by Pod Security Admission or Policies
• Network Policy checks:
  • [ ] Any changed pod is covered by Network Policies
  • [ ] The change does not cause any dropped packets in the NetworkPolicy Dashboard
• Audit checks:
  • [ ] The change does not cause any unnecessary Kubernetes audit events
  • [ ] The change requires changes to Kubernetes audit policy
• Falco checks:
  • [ ] The change does not cause any alerts to be generated by Falco
• Bug checks:
  • [ ] The bug fix is covered by regression tests

[viktor-f]

Thanks for adding this. I'm in contact with a user as well to get more feedback.

I got word that the user is on vacation and will be back in 2 weeks. So expect some feedback from them after that.