Posts

• RE: Xen Orchestra Container Storage Interface (CSI) for Kubernetes

  @koushik you have to use the Helm controller addons for RKE2 to deploy autmatically the Helm chart for the Xen Orchestra CCM with the field spec.bootstrap set to true:

  Field              | Default	| Description
  --------------------------------------------------
  `spec.bootstrap`   | `false`    | Set to True if this chart is needed to bootstrap the cluster (Cloud Controller Manager, etc)
  

  EDIT: I wrote a wiki page with what I've tested https://github.com/vatesfr/xenorchestra-cloud-controller-manager/wiki/Rancher-RKE2

  posted in Infrastructure as Code

  C

  Cyrille
  
• RE: Xen Orchestra Container Storage Interface (CSI) for Kubernetes

  Hi @koushik,
  Having read the RKE2 documentation, I understand that the only difference between the embedded CCM and the Xo CCM is that the latter does not have the ServiceLB LoadBalancer controller. The Xo CCM does everything else that the embedded CCM does (e.g. clearing the uninitilazed taint and setting the node IP) + it set the right providerID.

  Disabling the embedded CCM will "only" result in the loss of the load balancer.

  I would suggest disabling the RKE2 embedded CCM in order to use the Xo CCM as an external Cloud Controller Manager, as described in the RKE2 documentation. You need also to edit the kubelet configuration and set --kubelet-arg=cloud-provider=external.

  You could then use another service to run the load balancer.

  posted in Infrastructure as Code

  C

  Cyrille
  
• RE: Xen Orchestra Container Storage Interface (CSI) for Kubernetes

  @koushik a dit:

  Is there any flag or configuration in the CSI driver to completely bypass the strict CCM/Topology validation logic for non-native cloud setups, or do we have to wait for an update that allows an option like is-the-ccm-mandatory=false?

  The CSI is designed to run with the Xen Orchestra provider ID because it enables the CSI node server to identify the VM on which it is running. This also means that the node server itself has no access to the Xen Orchestra API; only the CSI controller server has access.

  There are no plans to remove this dependency in the next release. Sorry about your issue, we will investigate and see what we can do about that.

  posted in Infrastructure as Code

  C

  Cyrille
  
• RE: Xen Orchestra Container Storage Interface (CSI) for Kubernetes

  @koushik
  I don't kown RKE2. Is it its own CCM which set the node providerID?

  Regarding the CSI, it needs the labels set by the CCM to know the pool topology. Try to enable only the cloud-node-label-sync in the CCM:

  --controllers=cloud-node-label-sync
  

  I'm not sure if that's enough. Maybe you'll have an issue with the provider ID, too

  posted in Infrastructure as Code

  C

  Cyrille
  
• RE: Xen Orchestra Container Storage Interface (CSI) for Kubernetes

  Hi @robfox2, a release candidate version is about to be published. After that, we will wait for feedback before releasing a stable version.
  Keep an eye out for the release blog post on https://xen-orchestra.com/blog/tag/release/

  posted in Infrastructure as Code

  C

  Cyrille
  
• RE: DevOps Megathread: what you need and how we can help!

  Terraform provider v0.41.0

  New release of the Terraform provider for Xen Orchestra : a new xenorchestra_srs data source, a share option on
  xenorchestra_vm to grant team access declaratively, and host_id filtering on xenorchestra_sr. Full release note here.

  Xen Orchestra Golang SDK v1.19.0

  Add share flag for VMs in the v1 SDK and other dependencies bumps. Release note.

  posted in Infrastructure as Code

  C

  Cyrille
  
• RE: [SHARE][PACKER] Exemple d'utilisations de Packer pour déployer un template sur XCP-ng

  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

  posted in French (Français)

  N

  nathanael-h
  
• RE: (kubernetes) Add 'xcp-ng' provider to clusterapi

  @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

  posted in Development

  N

  nathanael-h
  
• RE: DevOps Megathread: what you need and how we can help!

  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

  posted in Infrastructure as Code

  C

  Cyrille
  
• RE: (kubernetes) Add 'xcp-ng' provider to clusterapi

  @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

  posted in Development

  N

  nathanael-h