Skip to content

Commit 0a1bc0d

Browse files
committed
docs(capi): correct the reason capmox stays on v0.7
capmox v0.8 still serves v1alpha1 for its machine and cluster CRDs through a conversion webhook, so the v1alpha1 templates the kubernetes-nodes chart renders would still be accepted. What holds capmox back is the move to the v1beta2 contract and v1alpha2 storage, which has not been tried against those templates and should land together with in-cluster IPAM v1.1. Suggested-by: Marian Koreniuk <[email protected]> Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <[email protected]>
1 parent f2a6117 commit 0a1bc0d

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

  • packages/system/capi-providers-infraprovider-proxmox/templates

‎packages/system/capi-providers-infraprovider-proxmox/templates/providers.yaml‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,10 @@ metadata:
55
spec:
66
# https://github.com/ionos-cloud/cluster-api-provider-proxmox
77
#
8-
# Pinned to the v0.7 series: v0.8 moves capmox to its v1alpha2 API, and the
9-
# kubernetes-nodes chart still renders ProxmoxMachineTemplate at v1alpha1.
10-
# Moving past v0.7 means migrating those objects first.
8+
# Pinned to the v0.7 series. v0.8 moves capmox to the v1beta2 contract and
9+
# stores v1alpha2. v1alpha1 is still served through conversion, but that has
10+
# not been tested with the kubernetes-nodes templates, and in-cluster IPAM
11+
# should move to v1.1 at the same time. Bump the two together.
1112
version: v0.7.7-infraprovider-proxmox
1213
configSecret:
1314
name: {{ .Values.credentialsSecretName | quote }}

0 commit comments

Comments
 (0)