Repository navigation
Commit eac48b0
committed
fix(kubernetes): match the cloud-controller-manager's providerID to capmox
CAPI pairs a Machine with its Node by matching providerID exactly, and the two
were written in different formats: capmox stamps proxmox://<SMBIOS UUID> on the
ProxmoxMachine, while the controller's default mode emits
proxmox://<region>/<vmid>. Nothing ever matched, so status.nodeRef stayed empty,
the Machine stopped at Provisioned and its MachineDeployment reported ScalingUp
indefinitely — all while the tenant cluster itself ran normally, which is what
made it easy to miss.
The chart already has the mode for this; it was simply left at the default. Note
that the CSI chart spells the same idea `proxmox` and this one spells it
`capmox`, which is why setting one is no reminder to set the other.
Verified by replacing the Machine and watching the replacement converge:
providerID identical on both objects, nodeRef set, phase Running,
MachineDeployment 1/1 with the health check healthy, and a PVC still binding to
a disk attached on the hypervisor.
Signed-off-by: Marian Koreniuk <[email protected]>
Assisted-by: LLM1 parent a460714 commit eac48b0
1 file changed
Lines changed: 10 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
30 | 30 | | |
31 | 31 | | |
32 | 32 | | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
33 | 43 | | |
0 commit comments