Skip to content

📖 Docs: Update proposal for scaling from zero for csi driver #13012

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
k8s-ci-robot merged 1 commit into from
Nov 20, 2025
Merged

📖 Docs: Update proposal for scaling from zero for csi driver #13012

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions docs/proposals/20210310-opt-in-autoscaling-from-zero.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -316,6 +316,23 @@ status:
The cluster autoscaler will prefer the annotation on the MachineDeployment and will predict nodes that have a
`kubernetes.io/arch: amd64` label on them.

**CSI driver attach limits and availability**

When a user would like to signal that the node being created from a MachineSet or MachineDeployment will
have a specific CSI driver installed with any volume attach limits, they can use following
annotations to specify that information.

```
kind: <MachineSet or MachineDeployment>
metadata:
annotations:
capacity.cluster-autoscaler.kubernetes.io/csi-driver: "driver1=attach-limit,driver2=attach-limit"
```
Users can specify `attach-limit` of `0` if they merely want to signal presence of CSI driver and
driver does not have any attach limits.
### Security Model
This feature will require the service account associated with the cluster autoscaler to have
Expand Down
Loading