kacerr/cluster-autoscaler-with-capi
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
9 Commits 1 Branch 0 Tags
57f58f1fc5f362b3cc7edaf6eb5cd08c95887355
Commit Graph
4 Commits
Author SHA1 Message Date
kacerrandClaude Opus 5.5 aaa1ed64e2 Use data instead of stringData for capmox-variables Secret 
stringData is never stored, so kubectl apply reported "configured" on
every run and the capi play was never changed=0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-09-27 10:35:26 +02:00
kacerrandClaude Opus 5.5 605d6ebf0d Accept cloud-init rc 2 (recoverable errors) in the k3s play 
PVE's cloud-init user-data triggers a deprecation warning that makes
`cloud-init status --wait` exit 2 even though provisioning succeeded.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-09-27 09:40:28 +02:00
kacerrandClaude Opus 5.5 bfc0a9e15d Fix mgmt VM nameserver argument; record first vm run 
mgmt_dns is a list, passed to qm create as one space-separated argument.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-09-27 09:31:57 +02:00
kacerrandClaude Opus 5.5 66d61b21fc Add Ansible playbook for the management cluster (step 1) 
VM from Ubuntu cloud image on pv1-1, pinned k3s, cert-manager and
cluster-api-operator via k3s HelmChart CRs, CAPI providers as operator CRs,
kubeconfig fetch + cluster-inspector kubeconfig. Lint passes (production).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-09-27 01:02:50 +02:00