Kubernetes CSI Driver for XO new release v0.3.0

nathanael-h

@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

Cyrille

Kubernetes CSI Driver for XO new release v0.3.0

Stable CSI Volume Identity: This decouples Kubernetes volume identity from backend storage lifecycle events (e.g. VDI migration between Storage Repositories)
Topology-Aware Volume Provisioning: Dynamic provisioning now supports topology-aware pool selection.

️ 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

nathanael-h

@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

Cyrille

Xen Orchestra Kubernetes Storage Driver new release v0.2.0

Introducing dynamic provisioning

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

Cyrille

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).

nathanael-h

@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.

More doc here https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-with-a-personal-access-token-classic

nathanael-h

@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

Cyrille

@ThasianXi Thank you for your feedback !

nathanael-h

@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.

Cyrille

Kubernetes CCM for Xen Orchestra v1.0.0-rc.1

We’re shipping v1.0.0-rc.1, our first release candidate on the road to a stable 1.0.0! This RC is feature-complete and ready for real-world use.

Please try it out and share any feedback—bugs, regressions, or usability notes—so we can polish the final release. Thank you for testing and helping us!

https://github.com/vatesfr/xenorchestra-cloud-controller-manager/releases/tag/v1.0.0-rc.1

Golang SDK for Xen Orchestra v1.11.0

SDK v2:

VM and Task services now match the latest REST API.
Host service has been added for host data retrieval.
Integration tests have also been strengthened to boost reliability.

The v2 SDK is gradually becoming our main library for all the other DevOps tools (Kubernetes drivers, Terraform provider…).

There are BREAKING CAHNGES in the v2 SDK, so please read the release notes carefully.
Remember that the v2 SDK is a beta version and can be subject to significant changes. The current semantic versioning we use is mostly for the v1 SDK. When the v2 SDK becomes stable, the major version number will increase.

https://github.com/vatesfr/xenorchestra-go-sdk/releases/tag/v1.11.0

Team - DevOps

Posts

Kubernetes CSI Driver for XO new release v0.3.0

Xen Orchestra Kubernetes Storage Driver new release v0.2.0

Introducing dynamic provisioning

Kubernetes CCM for Xen Orchestra v1.0.0-rc.1

Golang SDK for Xen Orchestra v1.11.0

SDK v2:

Member List