Fixing a kubelet Memory Leak in Kubernetes 1.36 | Blog | HeyOnCall
- How I tracked down a tiny Go lifecycle bug in Kubernetes kubelet which leaked a context on every startPodSync.
- A few weeks ago, I started getting alerts from a tiny Kubernetes cluster: a single-node Kubernetes test cluster, not running any of our production workload.
- I’d recently upgraded this cluster to v1.36, hosted on DigitalOcean’s managed DOKS service.
Unverified
- How I tracked down a tiny Go lifecycle bug in Kubernetes kubelet which leaked a context on every startPodSync.
- A few weeks ago, I started getting alerts from a tiny Kubernetes cluster: a single-node Kubernetes test cluster, not running any of our production workload.
- I’d recently upgraded this cluster to v1.36, hosted on DigitalOcean’s managed DOKS service.
Sources: Heyoncall