*Remove Kubernetes Volumes
*Reasoning: good dashboard, but not clear how to use it. We have volumes information in Databases on Kubernetes dashaboard as well.

*Remove Pod Status
*Reasoning: also good, but fails to provide insights if the Pod does not have limits set. Also too excessive, we have all this info in Databases on Kubernetes.

*Remove Kubernetes Cluster Summary
*Reasoning: it just duplicates Kubernetes Overview dashboard.

*Rework Kubernetes Overview
*Main changes:

• Rename it to Kubernetes Cluster Overview

• Do not allow to choose "all" clusters as it does not make sense.

• Reorganize the tiles at the top, now they look neat and provide good level of details and structure

• Polish the dashboard so it works with 2 or more clusters properly and also adheres to PMM standards
  Rework Kubernetes DB Cluster
  Main changes:

• Rename to Databases on Kubernetes - we might want to expand it to other operators

• Variables are now dynamic and smart. For example, it will not show you the namespaces where you don't have databases controlled by the Operator

• Remove POD picker. We show information for the cluster

• Provide information about the database and proxy in a separate rows

• Show the limits for CPU and RAM if they are set - allows to quickly understand where utilization is

• Add menus to quickly navigate to another dashboards for more database insights or get help in docs on from Percona

• Polish the dashboard so it works with 2 or more clusters properly and also adheres to PMM standards

https://github.com/percona/grafana-dashboards/pull/1565