WhatBrokeToday
GTA 6FAQ
Kubernetes

Kubernetes APF queueSet Panics Due to Premature Removal of Lingering Requests

high

Is it fixed? Not yet.

Ongoing since Nov 12, 07:35 UTC. First reported Nov 12, 07:35 UTC.

What happened

In Kubernetes, a lingering request holding seats during its AdditionalLatency is prematurely removed from its queue's executing requests in finishRequestLocked, causing a panic or fairness corruption when its seats are later released.

What caused it?

The queueSet implementation removes a request from the executing requests set immediately upon finishing its main service, even though the request still holds seats that are only released later via a deferred EventAfterDuration callback.

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

    APF queueSet removes an excess queue while a lingering request still holds seats in it, then panics or corrupts fairness when that request's seats are released

    Source

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    APF queueSet removes an excess queue while a lingering request still holds seats in it, then panics or corrupts fairness when that request's seats are released(opens GitHub issue in a new tab)

    What happened? In staging/src/k8s.io/apiserver/pkg/util/flowcontrol/fairqueuing/queueset/queueset.go, a request that has finished its main service but still holds seats during its AdditionalLatency (a "lingering" request, e.g. a mutating request whose work estimate reserves seats for its watch fan-out) is removed from its queue's set of executing requests immediately in finishRequestLocked, while the release of its seats is deferred to an EventAfterDuration callback that fires when the…

    by bodapatisaikrishna 0upvotes 1comments

FAQ

What happened in the Kubernetes issue?

In Kubernetes, a lingering request holding seats during its AdditionalLatency is prematurely removed from its queue's executing requests in finishRequestLocked, causing a panic or fairness corruption when its seats are later released.

What is affected by the Kubernetes issue?

Kubernetes.

When did the Kubernetes issue start and end?

It started Nov 12, 07:35 UTC and is still ongoing (6 d 21 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.