<p>I'm running Azure AKS Cluster 1.15.11 with <a href="https://hub.helm.sh/charts/stable/prometheus-operator/8.15.6" rel="nofollow noreferrer">prometheus-operator 8.15.6</a> installed as a helm chart and I'm seeing some different metrics displayed by <a href="https://github.com/kubernetes/dashboard" rel="nofollow noreferrer">Kubernetes Dashboard</a> compared to the ones provided by prometheus Grafana.</p>
<p>An application pod which is being monitored has three containers in it. Kubernetes-dashboard shows that the memory consumption for this pod is ~250MB, standard prometheus-operator <a href="https://grafana.com/grafana/dashboards/12120" rel="nofollow noreferrer">dashboard</a> is displaying almost exactly double value for the memory consumption ~500MB.</p>
<p>At first we thought that there might be some misconfiguration on our monitoring setup. Since prometheus-operator is installed as standard helm chart, Daemon Set for node exporter ensures that every node has exactly one exporter deployed so duplicate exporters shouldn't be the reason.  However, after migrating our cluster to different node pools I've noticed that when our application is running on <strong>user node pool</strong>  instead of <strong>system node pool</strong> metrics does match exactly on both tools. I know that system node pool is running CoreDNS and tunnelfront but I assume these are running as separate components also I'm aware that overall it's not the best choice to run infrastructure and applications in the same node pool.</p>
<p>However, I'm still wondering why running application under <strong>system node pool</strong> causes metrics by prometheus to be doubled?</p>

efomo
<p>I ran into a similar problem (aks v1.14.6, prometheus-operator v0.38.1) where all my values were multiplied by a factor of 3. Turns out you have to remember to remove the extra endpoints called <code>prometheus-operator-kubelet</code> that are created in the <code>kube-system</code>-namespace during install <em>before</em> you remove / reinstall prometheus-operator since Prometheus aggregates the metric types collected for each endpoint.</p>
<p>Log in to the Prometheus-pod and check the status page. There should be as many endpoints as there are nodes in the cluster, otherwise you may have a surplus of endpoints:</p>
<p><img src="https://i.stack.imgur.com/3eYZt.png" alt="Prometheus status page" /></p>
