-
Notifications
You must be signed in to change notification settings - Fork 8
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
Interaction with Sidero #45
Comments
Hello, i did not try Sidero, i cannot say how it works. But i see here two ways to solve this idea.
If you familiar with terraform, there are two examples exist https://github.com/kubebn/talos-proxmox-kaas (good documented) and https://github.com/sergelogvinov/terraform-talos/tree/main/proxmox |
Yes, I’ve seen https://github.com/kubebn/talos-proxmox-kaas and it even uses Sidero and CAPI, it’s just not clear to me how it works with the Proxmox CCM as well :) |
Hi, thanks for this project, it looks like it might be a great fit for our use case (also running Kubernetes clusters on a Proxmox cluster).
As background, we’ve just gotten a CAPI management cluster up and running via the Talos bootstrap, control plane, and infrastructure CAPI providers (the latter via Sidero). To create a new cluster, we currently need to:
clusterctl
via the Sidero provider.This works well enough, but it sounds like this CCM, combined with https://github.com/CRASH-Tech/proxmox-operator to create the QEMU VMs via a manifest, could eliminate at least step 1 above.
We would like for the new cluster procedure to be something like:
Qemu
CRDs viaproxmox-operator
.clusterctl
via the Sidero provider.Sorry for the dumb question, as I’m just figuring this stuff out, but as I understand it both Sidero and this CCM will be
Node
providers, so it’s not clear whether this will work. Will Sidero and this CCM both be able to label the nodes?The text was updated successfully, but these errors were encountered: