# \[Question\] cAdvisor implementation in kubelet

**URL:** <https://discuss.kubernetes.io/t/question-cadvisor-implementation-in-kubelet/22196>\
**Category:** General Discussions\
**Created:** [December 6, 2022, 6:50am UTC](https://discuss.kubernetes.io/t/question-cadvisor-implementation-in-kubelet/22196 "2022-12-06T06:50:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ryysud](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/ryysud/32/11326_2.png) [@ryysud](https://discuss.kubernetes.io/u/ryysud)\
**Post date:** [December 6, 2022, 6:50am UTC](https://discuss.kubernetes.io/t/question-cadvisor-implementation-in-kubelet/22196/1 "2022-12-06T06:50:01Z")

</div>

Hi,

In kubelet, not all metrics of cAdvisor are exposed, but only those in the following option parameters are exposed by default.

- cpu
- memory
- cpuLoad
- diskIO
- network
- app
- process
- oom\_event

> <https://github.com/kubernetes/kubernetes/blob/v1.25.4/pkg/kubelet/cadvisor/cadvisor_linux.go#L86-L95>

The [–enable\_load\_reader](https://github.com/google/cadvisor/blob/v0.46.0/docs/runtime_options.md#cpu) flag in cAdvisor is required to expose `cpuLoad` metrics, but is not configured in kubelet as below:

> <https://github.com/kubernetes/kubernetes/blob/v1.25.4/pkg/kubelet/cadvisor/cadvisor_linux.go#L63-L80>

Currently, those metrics are always 0. Is this the intended implementation?

---

<div class="post-metadata">

**Author:** ![ryysud](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/ryysud/32/11326_2.png) [@ryysud](https://discuss.kubernetes.io/u/ryysud)\
**Post date:** [December 8, 2022, 3:05am UTC](https://discuss.kubernetes.io/t/question-cadvisor-implementation-in-kubelet/22196/2 "2022-12-08T03:05:00Z")

</div>

Is this implemented because we can pass `--enable_load_reader` (deprecated) via kubelet?

> <https://github.com/kubernetes/kubernetes/blob/v1.25.4/cmd/kubelet/app/options/globalflags_linux.go#L53>