Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sidero and Proxmox CCM #2

Open
dhess opened this issue Aug 22, 2023 · 1 comment
Open

Sidero and Proxmox CCM #2

dhess opened this issue Aug 22, 2023 · 1 comment

Comments

@dhess
Copy link

dhess commented Aug 22, 2023

Hi! Thanks for this repo, it's very helpful!

I see you're using both Sidero and Proxmox CCM in your configs. We're using CAPI + Sidero to provision bare Proxmox VMs and would like to also use Proxmox CCM, to label the nodes with the necessary Proxmox metadata (e.g., zone == Proxmox node) so that we can use the Proxmox CSI, but as I understand it, both Sidero and Proxmox CCM want to be a node provider, which seems like it shouldn't be possible.

If I'm reading your config correctly, it looks like you don't run Proxmox CCM in your CAPI + Sidero-provisioned clusters (e.g., cluster-0), is that right? So do you run Proxmox CSI in your CAPI + Sidero clusters, and if so, how do you set the necessary labels?

@kubebn
Copy link
Owner

kubebn commented Aug 24, 2023

Hi @dhess, Sidero and CAPI are only used to bootstrap talos clusters on the nodes. Proxmox CCM is used to add some cloud provider logic to the k8s clusters hence Proxmox CSI can be used in conjunction with Proxmox CCM. None of them are used as node providers. You can create nodes whatever way suits you - terraform, ansible, or Proxmox Operator as in this repo.

Yes, you are correct. I am using CCM/CSI in my CAPI + Sidero-provisioned clusters. They are deployed in Management cluster only, for testing purposes. I do not see any issues of adding them to CAPI clusters though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants