Xen Orchestra Cloud Controller Manager in development 
Hello everyone 
We publish a development version of a Xen Orchestra Cloud Controller Manager!
It support the controllers cloud-node and cloud-node-lifecycle and add labels to your Kubernetes nodes hosted on Xen Orchestra VMs.
apiVersion: v1
kind: Node
metadata:
labels:
# Type generated base on CPU and RAM
node.kubernetes.io/instance-type: 2VCPU-1GB
# Xen Orchestra Pool ID of the node VM Host
topology.kubernetes.io/region: 3679fe1a-d058-4055-b800-d30e1bd2af48
# Xen Orchestra ID of the node VM Host
topology.kubernetes.io/zone: 3d6764fe-dc88-42bf-9147-c87d54a73f21
# Additional labels based on Xen Orchestra data (beta)
topology.k8s.xenorchestra/host_id: 3d6764fe-dc88-42bf-9147-c87d54a73f21
topology.k8s.xenorchestra/pool_id: 3679fe1a-d058-4055-b800-d30e1bd2af48
vm.k8s.xenorchestra/name_label: cgn-microk8s-recipe---Control-Plane
...
name: worker-1
spec:
...
# providerID - magic string:
# xeorchestra://{Pool ID}/{VM ID}
providerID: xeorchestra://3679fe1a-d058-4055-b800-d30e1bd2af48/8f0d32f8-3ce5-487f-9793-431bab66c115
For now, we have only tested the provider with Microk8s.
What's next?
We will test the CCM with other types of Kubernetes clusters and work on fixing known issues.
Also a modification of the XOA Hub recipe will come to include the CCM.
More label will be added (Pool Name, VM Name, etc.).
Feedback is welcome!
You can install and test the XO CCM, and provide feedback to help improve and speed up the release of the first stable version. This is greatly appreciated 
)