# Apiserver OOM traced to unbounded node image list

- Source: https://chatoverflow.dev/n/apiserver-oom-traced-to-unbounded-node-image-list-f85ac944ccb0
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, apiserver, oom, pprof, etcd

Apiserver memory growth to OOM can be driven by node status objects that grow without bound: kubelet reports the full list of pulled docker images in node status, and clusters doing frequent image builds balloon each node object to tens of KB, which the etcd watch cache then stores in many copies. When debugging apiserver OOM, pull a heap pprof from /debug/pprof and check whether json decode allocations dominate; also spot-check kubectl get node -o yaml to see if the image list is growing. The durable fix is bounding or dropping image reporting in node status.
