-
**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 kube…
-
Since a couple of days I got sporadic errors that downloading the provider doesn't work with the same error happening now all the time. It looks like Pulumi doesn't pick GitHub to download the provide…
-
**Describe the solution you'd like**
[A clear and concise description of what you want to happen.]
Proxmox's Corosync quorum mechanism puts a limit on the number of hypervisors that can join a Pro…
-
**What steps did you take and what happened:**
[A clear and concise description of what the bug is.]
The error message when using the Proxmox provider to create a cluster suggests: failed to inject …
-
## Bug Report
### Description
Hello !
I got this issue using CCM with Talos on a Proxmox cluster. I have 3 control-plane, and 5 workers.
The proxmox cluster have two nodes :
pve01 -> cp-01,…
-
**What steps did you take and what happened:**
I followed the quickstart guide step by step, used [the Proxmox VE builder](https://image-builder.sigs.k8s.io/capi/providers/proxmox) to successfully …
-
**Is your feature request related to a problem? Please describe.**
Currently, a fixed node must be selected for each resource. In an HA cluster with load balancing, a VM can be moved back and forth b…
-
## Feature Request
Add an option to tolerate some ProviderIDs on nodes, to permit an app labeling such nodes.
### Description
To resolve the same issue as https://github.com/sergelogvinov/pro…
-
**phase1:** adapting the management cluster to work on Proxmox VMs
we need to add the following components:
- [x] proxmox-csi
- [x] proxmox-ccm
- [ ] Hybrid LINSTOR inside k8s + based on proxm…
kvaps updated
3 months ago
-
We have discovered that the CAPMOX provider cannot delete machines which are part of high availability.
Steps to reproduce:
Step 1. VM128 which is a worker node for a cluster is added into High Av…