Hello @kiki_adm
Thank you for reaching to Cloudera Community
Regarding the reported behavior where the Pod Count decreased from 54 to 18 after restarting the service, this does not necessarily indicate that pods were actually deleted or that there is an issue with the cluster.
The Pod Count displayed on the dashboard represents the number of pods being returned by the underlying monitoring/metrics query for the configured scope and filters. Therefore, the value can temporarily change after a service restart while the monitoring component is rebuilding or reloading its pod information.
To determine whether this is an actual pod-level issue or only a monitoring/dashboard discrepancy, we recommend first comparing the dashboard value with the actual Kubernetes pod count.
For example:
kubectl get pods -A --no-headers | wc -l
For a specific namespace:
kubectl get pods -n <namespace> --no-headers | wc -l
kubectl get pods -n <namespace>
It is also useful to check the pod status:
kubectl get pods -A
If Kubernetes shows that the expected number of pods are running while the dashboard shows only 18, this would indicate that the issue is likely related to metrics collection, monitoring, or the dashboard query, rather than an actual loss of pods.
Looking forward for your response
