@Cyrille
we have RKE@ managing the cluster via its own CCM and seems xenorchestra is not supporting other external CCM providers and it requires XenOrchestra CCM to be mandatory which we cannot do as RKE2 Managing our clusters.
https://github.com/vatesfr/xenorchestra-csi-driver/blob/main/docs/topology.md#is-the-ccm-mandatory
Problem:
AS RKE2 our CCM, we can't run xen CCM and hence below node objects cannot be managed by xen.
topology.k8s.xenorchestra/pool_id = <uuid>
topology.k8s.xenorchestra/host_id = <uuid>
topology.k8s.xenorchestra/pool_name_label = <name>
topology.k8s.xenorchestra/host_name_label = <name>
We tried adding them manually on the nodes, but still the PVC is waiting and complaining
[image: 1787842912050-b45c9e35-7024-4045-9097-2c3846d3a3ab-image-resized.jpeg]
Is there a workaround available for now? or is it something getting released as part of the release cycle?