container_cpu_load_d_average_10s remains zero
Author: samvvCreated Sep 8, 2026Updated Sep 8, 2026
Environmental Info: K3s Version: k3s version v1.36.4+k3s1 (4dedb15b) go version go1.26.7
Node(s) CPU architecture, OS, and Version: 1 x64 node on Ubuntu 24.04.4 LTS
Cluster Configuration: One simple node with lots of containers.
Installed are kata-containers and openebs/zfs-localpv.
Describe the bug:
All container_cpu_load_d_average_10s metrics coming from the node's embedded cadvisor return 0. The solution given in #2831 didn't solve anything.
Steps To Reproduce:
- Install K3s using
curl -sfL https://get.k3s.io | sh -s - --service-node-port-range=1000-32767 - Run
curl -k --cert /var/lib/rancher/k3s/server/tls/client-admin.crt --key /var/lib/rancher/k3s/server/tls/client-admin.key https://127.0.0.1:6443/api/v1/nodes/NODE_NAME/proxy/metrics/cadvisor
Expected behavior:
container_cpu_load_d_average_10s should sometimes give other values than 0
Actual behavior:
container_cpu_load_d_average_10s only outputs 0, no matter the time and the container.
Additional context / logs:
Sample metric:
container_cpu_load_average_10s{container="",id="[redacted]",image="docker.io/rancher/mirrored-pause:3.10.2",name="[redacted]",namespace="monitoring",pod="prometheus-0"} 0 1788896689888Source: k3s-io/k3s