<p>I'm trying to figure out why a GKE "Workload" CPU usage is not equivalent to the sum of cpu usage of its pods.</p>

<p>Following image shows a Workload CPU usage.</p>

<p><a href="https://i.stack.imgur.com/b45rT.png" rel="nofollow noreferrer">Service Workload CPU Usage</a></p>

<p>Following images show pods CPU usage for the above Workload.</p>

<p><a href="https://i.stack.imgur.com/pPptu.png" rel="nofollow noreferrer">Pod #1 CPU Usage</a></p>

<p><a href="https://i.stack.imgur.com/UBbEG.png" rel="nofollow noreferrer">Pod #2 CPU Usage</a></p>

<p>For example, at 9:45, the Workload cpu usage was around 3.7 cores, but at the same time Pod#1 CPU usage was around 0.9 cores and Pod#2 CPU usage was around 0.9 cores too. It means, the service Workload CPU Usage should have been around 1.8 cores, but it wasn't.</p>

<p>Does anyone have an idea of this behavior?</p>

<p>Thanks.</p>

Danny Cadavid
<p>On your VM, the node managed by Kubernetes, you have the deployed pods (that you manage) but also several services that run on it for the supervision, the management, the logs ingestion,... A basic description <a href="https://kubernetes.io/docs/tutorials/kubernetes-basics/explore/explore-intro/" rel="nofollow noreferrer">here</a></p>

<p>You can see all these basic services by performing this command <code>kubctl get all --namespace kube-system</code>.</p>

<p>If you have installed additional components, like Istio or Knative, you have additional services and namespaces. All of these get a part of the resources of the node.</p>
