Skip to content

Commit 72bb4f3

Browse files
committed
fix(kubernetes): run proxmox-cloud-controller-manager v0.16.1, pinned by digest
The Proxmox CCM was referenced by its bare v0.15.0 tag, and that tag no longer names the image it named when the template was written. It was re-pushed on 2026-09-27 (index sha256:d81702998ae1, replacing the 2026-08-06 build sha256:fbc553921145) to a binary whose gitVersion is "0.15.0" without the leading v. component-base v0.37 parses that string in the init() of its legacy metrics registry and panics: panic: version string "0.15.0" doesn't match expected regular expression: "^v(\d+\.\d+\.\d+)" so the Deployment crash-loops, no Node ever loses the node.cloudprovider.kubernetes.io/uninitialized taint, and workloads on a new worker stay Pending. Any node that pulls the tag fresh gets it, which is every fresh install. v0.16 builds with goreleaser and stamps gitVersion as v{{.Version}}. The configuration this template writes is read unchanged: the cluster entry moved to go-proxmox-pool's ClusterConfig with the same url, insecure, token_id, token_secret and region keys, and features.provider: capmox still writes proxmox://<SMBIOS UUID>, the providerID capmox puts on the Machine. The reference now lives in images/proxmox-cloud-controller-manager.tag as tag plus digest, the shape the chart already uses for the KubeVirt cloud provider, so a moving tag can no longer change what runs. The unit test requires the digest. Assisted-by: LLM Signed-off-by: Marian Koreniuk <[email protected]>
1 parent e05c565 commit 72bb4f3

3 files changed

Lines changed: 9 additions & 1 deletion

File tree

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
ghcr.io/sergelogvinov/proxmox-cloud-controller-manager:v0.16.1@sha256:474dbfd3be5c2e0866e520bc6ddb60b7accef554ca7401488eee35252cdf8734

‎packages/apps/kubernetes/templates/ccm-proxmox/controller.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ spec:
101101
readOnlyRootFilesystem: true
102102
containers:
103103
- name: cloud-controller-manager
104-
image: ghcr.io/sergelogvinov/proxmox-cloud-controller-manager:v0.15.0
104+
image: "{{ $.Files.Get "images/proxmox-cloud-controller-manager.tag" | trim }}"
105105
args:
106106
- --v=4
107107
- --cloud-provider=proxmox

‎packages/apps/kubernetes/tests/substrate_proxmox_addons_test.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -148,6 +148,13 @@ tests:
148148
- matchRegex:
149149
path: spec.template.spec.initContainers[1].command[2]
150150
pattern: 'provider: capmox'
151+
# A tag in this registry is not a pin: v0.15.0 was re-pushed on
152+
# 2026-09-27 to a build that panics in init(), and every Node that came
153+
# up after the pull kept the uninitialized taint. The digest decides
154+
# what runs.
155+
- matchRegex:
156+
path: spec.template.spec.containers[0].image
157+
pattern: '^ghcr\.io/sergelogvinov/proxmox-cloud-controller-manager:v[0-9]+\.[0-9]+\.[0-9]+@sha256:[0-9a-f]{64}$'
151158

152159
# A blanket `operator: Exists` also matches
153160
# node.kubernetes.io/unreachable:NoExecute with no tolerationSeconds, which

0 commit comments

Comments
 (0)