WhatBrokeToday
GTA 6FAQ
Kubernetes

Kubernetes PodGC Force Deletes Replacement Pods Due to Missing UID Precondition

high

Is it fixed? Not yet.

Ongoing since Nov 13, 10:59 UTC. First reported Nov 13, 10:59 UTC.

What happened

PodGC in Kubernetes force deletes same-named replacement pods because its delete operation has no UID precondition and uses a zero grace period. This occurs when the StatefulSet controller deletes a pod in a terminal phase and recreates it under the same name.

What caused it?

markFailedAndDeletePodWithCondition in pkg/controller/podgc/gc_controller.go performs deletions by name without a UID precondition or grace period, and skips the UID-pinned status patch for pods already in a terminal phase.

No verified workaround yet

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

Official fix

Timeline

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

    PodGC can force delete a same-named replacement pod because its delete has no UID precondition

    Source

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    PodGC can force delete a same-named replacement pod because its delete has no UID precondition(opens GitHub issue in a new tab)

    What happened? markFailedAndDeletePodWithCondition in pkg/controller/podgc/gc_controller.go force deletes pods by name, with a zero grace period and no UID precondition. The pods come from PodGC's informer cache. For pods that are already in a terminal phase (Succeeded/Failed), the UID-pinned status patch is skipped, so nothing ties the delete to the pod PodGC actually observed. The StatefulSet controller deletes a pod in a terminal phase and recreates it under the same name…

    by shirzady1934 0upvotes 1comments

FAQ

What happened in the Kubernetes issue?

PodGC in Kubernetes force deletes same-named replacement pods because its delete operation has no UID precondition and uses a zero grace period. This occurs when the StatefulSet controller deletes a pod in a terminal phase and recreates it under the same name.

What is affected by the Kubernetes issue?

Kubernetes.

When did the Kubernetes issue start and end?

It started Nov 13, 10:59 UTC and is still ongoing (5 d 17 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.