Open mkamsikad2 opened 2 weeks ago
@mkamsikad2 thanks for reporting this, While I tested this before I will go and give it another try to check if upgrading broke the ProxmoxClient.
@mcbenjemaa I have upgraded to Capmox 0.5.1 and have now configured ProxmoxCluster.spec.credentialsRef.namespace
I can now build clusters and perform alpha rollouts. One thing that is still an issue is that all upgraded clusters are in a Failed state.
cluster.cluster.x-k8s.io/capi-management-v2 Failed 66d
cluster.cluster.x-k8s.io/dev1-uk-busi-cl Failed 66d
cluster.cluster.x-k8s.io/mk1-busi-cl Provisioned 4m32s
cluster.cluster.x-k8s.io/test1-uk-busi-cl Failed 60d
NAME CLUSTER READY ENDPOINT
proxmoxcluster.infrastructure.cluster.x-k8s.io/capi-management-v2 capi-management-v2 true {"host":"10.20.1.220","port":6443}
proxmoxcluster.infrastructure.cluster.x-k8s.io/dev1-uk-busi-cl dev1-uk-busi-cl true {"host":"10.10.1.10","port":6443}
proxmoxcluster.infrastructure.cluster.x-k8s.io/mk1-busi-cl mk1-busi-cl true {"host":"10.10.1.150","port":6443}
proxmoxcluster.infrastructure.cluster.x-k8s.io/test1-uk-busi-cl test1-uk-busi-cl true {"host":"10.10.1.30","port":6443}
I'm not sure how to bring the cluster out of a failed state.
What steps did you take and what happened: I upgraded from Capmox 0.4.0 to 0.5.0
clusterctl upgrade apply --core cluster-api:v1.7.2 --bootstrap kubeadm:v1.7.2 --control-plane kubeadm:v1.7.2 --ipam in-cluster:v0.1.0 --infrastructure proxmox:v0.5.0
Following the upgrade the Capmox controller logs the following errors:
E0619 13:51:44.068023 1 controller.go:329] "Reconciler error" err="error getting infra provider cluster or control plane object: No credentials found, ProxmoxCluster missing credentialsRef" controller="proxmoxmachine" controllerGroup="infrastructure.cluster.x-k8s.io" controllerKind="ProxmoxMachine" ProxmoxMachine="default/capi-management-v2-control-plane-qjwxf" namespace="default" name="capi-management-v2-control-plane-qjwxf" reconcileID="2ae9413d-cb8e-4425-9860-e870d84adb5a"
I then added created the required secret and added the secret in ProxmoxCluster.spec.credentialsRef.name
The capmox provider cannot then find the secret and is unable to communicate with proxmox:
What did you expect to happen: I would have expected to upgrade capmox and then have to apply the required secret and add the required value into ProxmoxCluster.spec.credentialsRef.name I then would expect the capmox controller to communicate with proxmox.
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
): 1.28.8/etc/os-release
): ubuntu 24.04