Kueue v0.20.0 landed on 30 September 2026, and it is not a routine minor. The Kueue maintainers use the .0 of each minor to graduate feature gates and retire API surface, and this one does both at once: kueue.x-k8s.io/v1beta1 is no longer served — the API directory still contains the types, but only as conversion stubs marked +kubebuilder:unservedversion, so any client, GitOps manifest, or CI pipeline still pinned to v1beta1 breaks on the spot. Around that headline sit twelve feature gates that silently flipped to Beta-on, four quota-accounting bypasses that got fixed (meaning your quotas were quietly wrong until now), and a fair-sharing accounting change that alters admission order for any ClusterQueue using UsageBasedAdmissionFairSharing.

This is a field guide, not a release-notes paraphrase. Every gate name, default value, and API field below was verified against the v0.20.0 source tree — the feature-gate registry in pkg/features/kube_features.go, the config defaulting in apis/config/v1beta2/defaults.go, and the scheduler's admission path in pkg/scheduler/scheduler.go. If you run Kueue in production — and in 2026, if you run AI training or batch on Kubernetes, you either run Kueue or something shaped like it — the sequence below is what gets you from v0.19 to v0.20 without an incident review.

TL;DR

  • The API break is real and immediate: v0.20.0 stops serving kueue.x-k8s.io/v1beta1 entirely. Storage moved to v1beta2 back in v0.16; serving is now v1beta2-only. Run the migration script before the upgrade, not after, and audit every pipeline that kubectl-applies Kueue YAML.
  • Twelve gates flipped to Beta, enabled by default — including WorkloadPriorityClassDefaulting (every unlabeled workload now gets the default priority class), AdmissionFairSharingAnchorAtQuotaReservation (fair-sharing accounting starts at quota reservation, not admission), and LWSImmutableGroupSize (LeaderWorkerSet group size becomes immutable while Kueue-managed).
  • Four quota bypasses closed — LWS group-size scaling, Spark cores/memoryOverhead under-reservation, negative-request quota credit, and Job parallelism-over-completions early release. If your quotas "felt tight" before, they were lying: these bugs let workloads run beyond quota.
  • WaitForPodsReady is on by default since v0.19 (30-minute timeout, 30-minute recovery). If you upgraded 0.18 → 0.19 and skipped that note, v0.20 is your forced reckoning: the escape hatch gate DisableWaitForPodsReady is deprecated with removal planned in 0.21.
  • Upgrade order that works: pre-flight audit → migration script → canary ClusterQueue → controller roll → watch kueue_cluster_queue_status and AFS metrics → unbake v1beta1 from CI. Detailed runbook below.

If you want the concepts rather than the migration — how priority, fair sharing, cohorts, and DRA quota fit together for LLM fleets — read our GPU scheduling for LLM workloads guide first; this piece assumes you know what a ClusterQueue is and picks up at the version you are now running.

The Structural Shift: This Is a Versioned-Kubernetes-API Retirement, Not a Config Bump

Most Kueue upgrades are boring. You bump the Helm chart, the controller image rolls, CRDs apply server-side, done. v0.20.0 is different for one structural reason: Kueue's CRDs are now single-serving-version. The Kubernetes API deprecation policy governs how served versions are retired, and Kueue's v1beta1 has reached the end of that runway. Concretely, from the v0.20.0 source tree: apis/kueue/v1beta1/ still exists, but every type file carries +kubebuilder:unservedversion — the generated CRD no longer lists v1beta1 in spec.versions[].served, so the API server itself rejects requests for it. This is not a deprecation warning; it is a hard 404 on the version string.

Storage vs serving matters here. Since v0.16.0, new objects are stored as v1beta2, and the release notes of that cycle told everyone to run the migration script. The script (hack/migrate-to-v1beta2.sh) performs a no-op update on every existing Kueue object, forcing each through the conversion webhook so etcd ends up holding v1beta2. Objects never touched by that script sit in etcd as v1beta1 storage with a conversion webhook keeping them readable — until the serving version goes away and the conversion path breaks with it. v0.20.0 is the release where that debt comes due: an unmigrated object becomes unreadable to any v1beta2-only client, and the migration script can no longer list objects via v1beta1 by default (its --kubectl-get-api-version flag exists for exactly this stranded state, defaulting to v1beta1 for clusters "just after upgrade to Kueue 0.16+" — read the script's help before assuming).

The second structural shift is quieter and, in practice, more disruptive: the default-on gate graduation batch. Kueue's pattern is to flip alpha gates to Beta-on in .0 releases. Verified from pkg/features/kube_features.go in the v0.20.0 tree, the gates that became Default: true, PreRelease: Beta in v0.20 include:

AdmissionFairSharingAnchorAtQuotaReservation   # AFS accounting anchor moves to quota reservation
DeploymentJobUIDLabel                            # Workload of Deployment-managed Pod carries Deployment UID
FlavorFungibilityPreserveScanProgress           # retry workloads across flavors, not just the first one
HighMaxParallelismWithinReconcile               # 8 -> 32 concurrent API updates per reconcile
LWSImmutableGroupSize                          # leaderWorkerTemplate.size immutable while Kueue-managed
MultiKueueKubeConfigPathValidation              # kubeconfig path refs restricted to /etc/multikueue/kubeconfigs/
MultiKueueOrchestratedPreemption                # coordinated preemption across worker clusters
MultiKueueRemoteSpecSync                       # in-place Ray Serve config updates forwarded to workers
MultiKueueReuseClientConnectionConfigForWorkers # QPS/Burst reuse for worker-cluster clients
PodGroupSchedulingShapeOrdering                 # deterministic flavor assignment for Pod groups
PodIntegrationCountSucceededPodsAsReady         # succeeded pods count as ready for PodsReady
RecomputeAssignmentUponPreemptionTargetsOverlap # hero-workload starvation fix, in-cycle recompute
RejectUpdatesToCQWithInvalidOnFlavors           # reject CQ updates referencing invalid flavor names
SkipAncestorCheckForDeletedWorkloads            # GC not blocked by "workload owner not found"
SchedulingEquivalenceHashingIgnorePodSetName    # PodSet names ignored in equivalence hashing
TASCacheTopologyTree                            # cached topology trees between cycles
TASGroupedPodSetSlicing                         # LWS leader grouped + workers sliced
TASNodeFeasibilityForAllLevels                  # per-node feasibility at every topology level
TASPartialSlices                                # PodSet counts not a multiple of slice size
UnadmittedWorkloadsObservability                # granular pending reasons in QuotaReserved condition
WorkloadPriorityClassDefaulting                 # default WorkloadPriorityClass auto-assigned
WorkloadValidateResourcesAreNonNegative        # negative resource requests rejected at validation
WorkloadValidationForPodSetMetadata             # invalid PodSet template metadata rejected at admission
EnforceProvisioningPodTemplateContents          # divergent PodTemplate specs replaced with Kueue-derived