Proposed PR series, prepared 2026-11-13.
Related change: kubernetes/autoscaler#10680, which makes Azure TargetSize report zero without an error for a missing VMSS.
Add deterministic coverage for this sequence:
Proposed PR series, prepared 2026-11-13.
Related change: kubernetes/autoscaler#10680, which makes Azure TargetSize report zero without an error for a missing VMSS.
Add deterministic coverage for this sequence:
The clearest direction was to start with a lean alpha built around a PostFilter plugin, minimizing changes to existing scheduling behavior. A major architectural clarification was that sharing scheduling logic and guaranteeing that a simulated placement remains available are two different problems.
This chronological summary is based on an automated transcript of a roughly 53-minute discussion. Timestamps are approximate; proposed designs and scheduling targets are not finalized API decisions or release commitments.
The proposed flow was to evaluate potential capacity after ordinary scheduling and preemption fail. The scheduler could determine synchronously whether a pod fits a prospective NodeClaim, while the actual infrastructure provisioning remains asynchronous.
The central question was how to make node autoscaling a native Kubernetes capability without preserving a second, divergent scheduling implementation. Participants debated how much architectural work belongs in the MVP and which follow-ups would make it useful enough to adopt.
This is a chronological summary from an automated transcript. Timestamps are approximate; proposals and preferences below should not be read as finalized API decisions or release commitments.
The opening question was whether provisioning should initially run through kube-scheduler's PostFilter extension point, or whether the MVP should already introduce broader framework changes. Participants discussed starting work in the 1.39 cycle.
The discussion focused on what Kubernetes scheduling primitives workload controllers need for AI workloads. Most topics ended with requirements or possible approaches - not finalized API decisions.
Controllers need to preserve capacity and placement during operations such as rolling updates, rather than letting other queued workloads take the freed resources. Participants distinguished hard reservations from soft reservations, where other, preemptible workloads could temporarily use the capacity. The immediate need was to establish concrete use cases before choosing the mechanism.
Why do English countries (England, Canada, The United States, Australia) have such a high incidence of inventing sports, both for their own amusement, and those that are exported around the world: the many types of football (association football for export; Canadian Football, American Football, and Australian Rules Football for local amusement), Rugby, Cricket, regulated Horse Racing, Baseball, Tennis, Badminton, Ice Hockey, Basketball, Volleyball. Why don't English colonies of non-"English" (meaning generally Anglo-Saxon-dominant peoples) peoples invent sports, and instead adopt the English ones (for example India with cricket, African nations with football, Hong Kong with horse racing, badminton, and football)? Why didn't non-English colonies adopt their non-English rulers' sports, but instead also adopted the English sport (Argentina and Brazil adopting football, for example)? Is there something unique about English culture that suggests a predeliction for inventing rules-based athletic games that othe
| #!/usr/bin/env python3 | |
| """ | |
| Count commits per cloud provider in kubernetes/autoscaler's | |
| cluster-autoscaler/cloudprovider/ tree over a given time window. | |
| How it works | |
| ------------ | |
| GitHub's REST Commits API supports two filters we exploit: | |
| - `path` : restrict to commits that touched files under this path | |
| - `since` : ISO-8601 timestamp lower bound |
Here's what Cluster Autoscaler will do in your scenario, end‑to‑end. The behavior is entirely driven by the fact that the Kubernetes Node objects still exist (kubelet stops, but the API server retains them) and the Azure cloud provider does not surface VM power state to CA.
CA buckets every node every loop in clusterstate.go (updateReadinessStats). The buckets are mutually exclusive:
Issue #4561 by @yuchen-ecnu proposes adding federation capability to KubeRay so that a single logical RayCluster can span multiple Kubernetes clusters. The core motivation:
| Here are my two talks: | |
| The first one will be a joint session w/ GKE (and fellow SIG Autoscaling TL) describing the OSS CA and our plans to make significant changes in 2026. | |
| The tl;dr is that GOOG will be investing significantly in the OSS CA to correct a decade of forking and blackbox dev. | |
| This is directly due to investments that we have made in the SIG to modernize the OSS surface area, release process, E2E tests, etc. | |
| - https://maintainersummiteu2026.sched.com/event/2EWf1/cluster-autoscaler-evolution-kuba-tuznik-google-jack-francis-microsoft |