Bonjour @bvivi57 merci pour le partage, le tuto est très détaillé, et me semble bien juste, bravo !
Hâte de voir la suite, mais aussi j'ai très envie de te proposer de tester la Kubernetes Cluster API pour Xen Orchestra, https://github.com/vatesfr/cluster-api-provider-vates/ c'est tout neuf, mais ça devrait t'aider à créer des clusters Kubernetes, et au-delà à les gérer (mise à jour, ajout/suppression de node, etc.) ping @devops
@pszelestey Hi, yes, we've pushed an initial commit and a few more here https://github.com/vatesfr/cluster-api-provider-vates/ it is moging every day. Ping us in Matrix/Discord devops if you want to chat live while trying 
️ Migration required from v0.2.0 to v0.3.0
Full release note: https://github.com/vatesfr/xenorchestra-csi-driver/releases/tag/v0.3.0
@lknite Hello, sorry if replying in this old thread looks odd... but I wanted to share that we are starting to work on supporting Cluster API.
We have an internal proof of concept:
/home/nathanael/Images/Captures d’écran/Capture d’écran du 2026-05-05 17-12-22.png
The latest CSI driver release introduces dynamic provisioning: by creating a Kubernetes storage class that references the XO CSI driver and sets the poolId parameter, you can then create a PVC and pod using that storage class, and Xen Orchestra will automatically provision new VDIs into the default SR of the chosen pool, to satisfy the requested volumes.
Your feedback on the CSI driver is welcome! Which features would you like to see? How would you like to use the driver and storage classes?
https://github.com/vatesfr/xenorchestra-csi-driver/releases/tag/v0.2.0
Hi,
Thank you for the feedback
There was an error in the Makefile used to build the Docker image for the CSI. The name was incorrect... The fix that we pushed a month ago didn't trigger the CI 
I manually ran the CI to rebuild the edge image with the correct name, which is now available at ghcr.io/vatesfr/xenorchestra-csi-driver:edge
I delete the wrong one (ghcr.io/vatesfr/xenorchestra-csi:edge).
@ThasianXi Hello, thanks for the report. It looks like the pull image step fails. Can you test that the token generated from Github is working and allows to pull the image.
Maybe a simple test on a docker install could ease the verification:
docker login ghcr.io -u USERNAME -p TOKEN
docker pull ghcr.io/vatesfr/xenorchestra-csi:v0.0.1
Also note that only "Classic" persona access token are supported.
@ThasianXi Nice, thanks 
For now no other question related to the CCM. But I would be very interesting if you have some feedback about the CSI Driver. We'll work on this in the coming weeks. https://github.com/vatesfr/xenorchestra-csi-driver
@ThasianXi Thank you for your feedback ! 
@ThasianXi Thank you very much for this detailed feedback! Did you deployed the CCM on a new cluster or an existing? My question is to know if you relied on the CCM to initialize the nodes.