WhatBrokeToday
GTA 6FAQ
Kubernetes

Kubernetes PersistentVolumeClaimUnusedSinceTime Causes 409 Conflicts on Resize

medium

Is it fixed? Not yet.

Ongoing since Nov 19, 07:16 UTC. First reported Nov 19, 07:16 UTC.

What happened

In Kubernetes clusters with the PersistentVolumeClaimUnusedSinceTime feature gate enabled, resizing an unreferenced Bound PVC causes 409 conflicts and continuous failure loops between the external-resizer and PVC protection controller during resize finalization.

What caused it?

Under active investigation. No report has identified a root cause yet.

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

    PersistentVolumeClaimUnusedSinceTime causes persistent 409 conflicts between external-resizer and PVC protection controller during resize finalization

    Source

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    PersistentVolumeClaimUnusedSinceTime causes persistent 409 conflicts between external-resizer and PVC protection controller during resize finalization(opens GitHub issue in a new tab)

    What happened? In a cluster with the PersistentVolumeClaimUnusedSinceTime feature gate enabled (Beta, on by default in Kubernetes 1.37), resizing a Bound PVC that is not referenced by any Pod causes external-resizer to fail repeatedly when writing the final resize status back to the PVC. The VolumeResizeSuccessful event is emitted normally, but external-resizer then continuously reports VolumeResizeFailed with the following error: Mark PVC "..." as resize finished failed: can't patch status of…

    by changshuchao 0upvotes 2comments

FAQ

What happened in the Kubernetes issue?

In Kubernetes clusters with the PersistentVolumeClaimUnusedSinceTime feature gate enabled, resizing an unreferenced Bound PVC causes 409 conflicts and continuous failure loops between the external-resizer and PVC protection controller during resize finalization.

What is affected by the Kubernetes issue?

Kubernetes (versions: 1.37). Also affected at the same time: DigitalOcean.

When did the Kubernetes issue start and end?

It started Nov 19, 07:16 UTC and is still ongoing (1 d 2 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.