<![CDATA[(kubernetes) Add 'xcp-ng' provider to clusterapi]]>Kubernetes, being a declarative approach to infrastructure, has something called 'clusterapi' which allows a kubernetes cluster to be defined as 'yaml'. The yaml file is applied, and after awhile you have the defined kubernetes cluster. Later, the yaml file could be updated to add another node, or change the version of kubernetes, and again, after applying the yaml the existing kubernetes cluster would be updated adding a node or updating the nodes with the specified kubernetes version.

Kubernetes generally has multiple nodes, vms, and so this process requires integration into the vm server environments, this is accomplished through 'providers'.

Perhaps we could get on the roadmap to add an 'xcp-ng' provider:
https://cluster-api.sigs.k8s.io/reference/providers.html

Using this method allows the management of the lifecycle of kubernetes clusters without having to drop out of the world of kubernetes to use a tool such as ansible or terraform.

I noticed there was a clusterapi provider for xenserver for the apache cloudstack project, maybe all the code is there to support xcp-ng and could be pulled out to create an xcp-ng provider not dependent on the apache cloudstack project? https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack

Additionally, having 'xcp-ng' on that list would gain attention as people will look at the list of supported providers and then go google the projects.

]]>https://xcp-ng.org/forum/topic/6747/kubernetes-add-xcp-ng-provider-to-clusterapiRSS for NodeMon, 15 Jun 2026 08:33:26 GMTWed, 28 Dec 2022 17:55:07 GMT60<![CDATA[Reply to (kubernetes) Add 'xcp-ng' provider to clusterapi on Mon, 08 Jun 2026 16:02:46 GMT]]>@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 😉

]]>https://xcp-ng.org/forum/post/106077https://xcp-ng.org/forum/post/106077Mon, 08 Jun 2026 16:02:46 GMT<![CDATA[Reply to (kubernetes) Add 'xcp-ng' provider to clusterapi on Mon, 08 Jun 2026 11:47:42 GMT]]>Expect news in the next XO release

]]>https://xcp-ng.org/forum/post/106070https://xcp-ng.org/forum/post/106070Mon, 08 Jun 2026 11:47:42 GMT<![CDATA[Reply to (kubernetes) Add 'xcp-ng' provider to clusterapi on Mon, 08 Jun 2026 09:05:07 GMT]]>Hi @nathanael-h ,

Do you have any new information about this PoC?
Will you release a preview which can be tested?

Thank you in advance!
Peter

]]>https://xcp-ng.org/forum/post/106064https://xcp-ng.org/forum/post/106064Mon, 08 Jun 2026 09:05:07 GMT<![CDATA[Reply to (kubernetes) Add 'xcp-ng' provider to clusterapi on Tue, 05 May 2026 16:42:51 GMT]]>@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.pnga9596fde-e251-4996-8fc9-3f8e208f9f01-image.jpeg

]]>https://xcp-ng.org/forum/post/105060https://xcp-ng.org/forum/post/105060Tue, 05 May 2026 16:42:51 GMT<![CDATA[Reply to (kubernetes) Add 'xcp-ng' provider to clusterapi on Thu, 29 Dec 2022 09:26:45 GMT]]>Hi,

If someone would build this, it should use Xen Orchestra API, as the central orchestrator, that would make most sense to do it that way 🙂

But yes, if someone want to start working on this, we'll be happy to assist on the API part 🙂

]]>https://xcp-ng.org/forum/post/56559https://xcp-ng.org/forum/post/56559Thu, 29 Dec 2022 09:26:45 GMT