kacerr/cluster-autoscaler-with-capi
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

lab1: autoscaler min/max and capacity annotations on lab1-workers (Step 5)

Browse Source 
kubectl diff against the live cluster shows only the six annotations.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
kacerr
2026-09-27 11:26:55 +02:00
co-authored by Claude Opus 5.5
parent 9fb8a8dcc1
commit 1d0b669d07
2 changed files with 21 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/phase-1-proxmox-capi.md
+12 -1
View File
@@ -159,9 +159,20 @@ metadata:
capacity.cluster-autoscaler.kubernetes.io/maximum-pods: "110"
```
They are part of `MachineDeployment/lab1-workers` in [configs/capi/lab1.yaml](../configs/capi/lab1.yaml);
re-apply the file (the only diff is these annotations; `replicas` isn't in the manifest, so it
stays as is):
```bash
export KUBECONFIG=~/.kube/lab-mgmt.kubeconfig
kubectl diff -f configs/capi/lab1.yaml # expect only the six annotations on lab1-workers
kubectl apply -f configs/capi/lab1.yaml
```
Capacity annotations are required for scale-from-zero because CAPMOX does not publish
`status.capacity`. They must match the `ProxmoxMachineTemplate`; add `.../labels` and `.../taints`
annotations if pods target the group by selector/toleration.
annotations if pods target the group by selector/toleration. They have no effect until
cluster-autoscaler runs (Step 6).
## Step 6 — cluster-autoscaler