Kubernetes Kubelet Re-runs Terminated Ephemeral Containers
Is it fixed? Not yet.
Ongoing since Oct 30, 21:25 UTC. First reported Oct 30, 21:25 UTC.
What happened
The Kubernetes Kubelet incorrectly restarts terminated ephemeral containers if their runtime container is removed, because it only checks if the runtime still contains a container with that name during pod syncs.
What caused it?
The kubelet decides whether to start an ephemeral container solely by checking if the runtime still has a container with that name. When an exited container is removed from the runtime, the next pod sync triggers the ephemeral container to start again.
Source: github.com
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on GitHub issue
Kubelet re-runs terminated ephemeral containers when their runtime container is removed
Source
Evidence
1 report · 1 GitHubShow
- [1]GitHub First reportKubelet re-runs terminated ephemeral containers when their runtime container is removed(opens GitHub issue in a new tab)
/kind bug /sig node /area kubelet Problem The kubelet decides whether to start an ephemeral container only by checking whether the runtime still has a container with that name (computePodActions): // Ephemeral Containers are never restarted if podStatus.FindContainerStatusByName(c.Name) == nil { changes.EphemeralContainersToStart = append(changes.EphemeralContainersToStart, i) } If the exited container is removed from the runtime, the next pod sync starts the ephemeral container again and…
by tallclair 0upvotes 11comments
FAQ
What happened in the Kubernetes issue?
The Kubernetes Kubelet incorrectly restarts terminated ephemeral containers if their runtime container is removed, because it only checks if the runtime still contains a container with that name during pod syncs.
What is affected by the Kubernetes issue?
Kubernetes.
When did the Kubernetes issue start and end?
It started Oct 30, 21:25 UTC and is still ongoing (19 d 7 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.