WhatBrokeToday
GTA 6FAQ
Kubernetes

Kubernetes VolumeBinding Filter Cost Scaled with Nodes and CSIStorageCapacity

medium

Is it fixed? Not yet.

Ongoing since Nov 14, 05:05 UTC. First reported Nov 14, 05:05 UTC.

What happened

For pods with an unbound WaitForFirstConsumer PVC using a CSI driver with storageCapacity: true, the VolumeBinding Filter scales inefficiently. It lists all CSIStorageCapacity objects for every node, repeatedly evaluating label selectors until a match is found.

What caused it?

The VolumeBinding filter evaluates capacity checks per node by listing all cluster-wide CSIStorageCapacity objects and iterating through label selectors iteratively.

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

    VolumeBinding Filter cost grows with nodes × CSIStorageCapacity objects

    Source

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    VolumeBinding Filter cost grows with nodes × CSIStorageCapacity objects(opens GitHub issue in a new tab)

    What happened? For a pod with an unbound WaitForFirstConsumer PVC whose CSI driver sets storageCapacity: true, the VolumeBinding Filter calls hasEnoughCapacity for every node. For each node it: lists every CSIStorageCapacity in the cluster with csiStorageCapacityLister.List(labels.Everything()) (L1000); for each object in the PVC's StorageClass with enough capacity, calls metav1.LabelSelectorAsSelector(capacity.NodeTopology) until it finds one that matches the node (L1036-1048). Drivers for…

    by circy9 0upvotes 1comments

FAQ

What happened in the Kubernetes issue?

For pods with an unbound WaitForFirstConsumer PVC using a CSI driver with storageCapacity: true, the VolumeBinding Filter scales inefficiently. It lists all CSIStorageCapacity objects for every node, repeatedly evaluating label selectors until a match is found.

What is affected by the Kubernetes issue?

Kubernetes.

When did the Kubernetes issue start and end?

It started Nov 14, 05:05 UTC and is still ongoing (4 d 23 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.