WhatBrokeToday
GTA 6FAQ
Kubernetes

Kubernetes Kubelet Static Pod URL Source Leaks Goroutines

medium

Is it fixed? Not yet.

Ongoing since Nov 1, 10:33 UTC. First reported Nov 1, 10:33 UTC.

What happened

In Kubernetes, NewSourceURL starts a polling goroutine using wait.NeverStop that cannot be stopped and sends updates on an unbuffered channel without reading. Once the context is canceled, the goroutine blocks forever, causing a resource leak in the kubelet.

What caused it?

NewSourceURL in pkg/kubelet/config/http.go uses wait.NeverStop and unbuffered channel sends that block permanently when nothing reads from the channel after the context is canceled.

Source: github.com

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on GitHub issue

    kubelet: static pod URL source goroutine can never be stopped

    Source

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    kubelet: static pod URL source goroutine can never be stopped(opens GitHub issue in a new tab)

    What happened? NewSourceURL in pkg/kubelet/config/http.go starts a polling goroutine that can never be stopped: go wait.Until(func() { config.run(logger) }, period, wait.NeverStop) It also sends on the unbuffered updates channel in three places in extractFromURL (empty data, single pod, pod list) with plain s.updates <- ... sends. Once nothing reads that channel, for example after the kubelet context passed to cfg.Channel(ctx, kubetypes.HTTPSource) is canceled, the goroutine blocks forever.…

    by lyelgate 0upvotes 1comments

FAQ

What happened in the Kubernetes issue?

In Kubernetes, NewSourceURL starts a polling goroutine using wait.NeverStop that cannot be stopped and sends updates on an unbuffered channel without reading. Once the context is canceled, the goroutine blocks forever, causing a resource leak in the kubelet.

What is affected by the Kubernetes issue?

Kubernetes.

When did the Kubernetes issue start and end?

It started Nov 1, 10:33 UTC and is still ongoing (17 d 18 h so far). This page updates as it develops.

How do I get alerts for Kubernetes?

Subscribe to the Kubernetes RSS feed for every new Kubernetes incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Kubernetes is down. Kubernetes feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.