Specifying hypervisor type in CKS

[Joann Mõndresku <jo...@wavecom.ee.INVALID>]

Hello. 

We have a situation where we have 2 different hypervisor clusters in a zone. 
When trying to deploy a Kubernetes cluster in it, it defaults to KVM with no option to change. 
Is there a way to specify hypervisor used for creating the Kubernetes cluster? 


Lugupidamisega / Best regards, 

Joann Mõndresku 



Süsteemiadministraator | Systems Administrator | joann@wavecom.ee 

WaveCom AS | ISO 9001, 27001 & 27017 Certified DC and Cloud services 
Endla 16, Tallinn 10142 | www.wavecom.ee | www.facebook.com/wavecom.ee 

Re: Specifying hypervisor type in CKS

[Bernardo De Marco Gonçalves <be...@gmail.com>]

Hello, Joann

As Wei mentioned, specifying a hypervisor when creating a k8s cluster is
currently not directly possible. However, it is possible to address this
use case by using host tags.

The first step to achieve that would be to tag each host according to its
hypervisor. For instance, tag KVM hosts with the "kvm" tag, VMware hosts
with the "vmware" tag, and so on. Next, it would be required to create
compute offerings matching each of these tags.

Therefore, when deploying a cluster, the Management Server will provision
the cluster nodes on the hosts matching the selected compute offering's
tag. When the offering does not have any tags, the VMs deployment may be
performed in any host and, thus, the changes will not affect the deployment
of VMs with non-tagged offerings.

Furthermore, it is important to mention that the deployment of k8s clusters
in an environment with multiple clusters of different hypervisors has some
inconsistencies, see https://github.com/apache/cloudstack/issues/10783. The
Management Server does not consider the possibility of Apache CloudStack
clusters being disabled and, as a consequence of that, may try to deploy a
k8s cluster VM in a KVM host using the VMware system VM template, and
vice-versa. Therefore, if the Apache CloudStack environment happens to have
disabled clusters, the usage of host tags would be a workaround to mitigate
this bug.

Best regards,
Bernardo De Marco Gonçalves (bernardodemarco)

Em sex., 16 de mai. de 2025 às 11:06, Wei ZHOU <us...@gmail.com>
escreveu:

> Currently it is not supported.
>
> There are some enhancements for CKS in the PR
> https://github.com/apache/cloudstack/pull/9102
> It will be merged into 4.21
>
>
>
> Kind regards,
> Wei
>
>
>
> On Fri, May 16, 2025 at 2:37 PM Joann Mõndresku <jo...@wavecom.ee.invalid>
> wrote:
>
> > Hello.
> >
> > We have a situation where we have 2 different hypervisor clusters in a
> > zone.
> > When trying to deploy a Kubernetes cluster in it, it defaults to KVM with
> > no option to change.
> > Is there a way to specify hypervisor used for creating the Kubernetes
> > cluster?
> >
> >
> > Lugupidamisega / Best regards,
> >
> > Joann Mõndresku
> >
> >
> >
> > Süsteemiadministraator | Systems Administrator | joann@wavecom.ee
> >
> > WaveCom AS | ISO 9001, 27001 & 27017 Certified DC and Cloud services
> > Endla 16, Tallinn 10142 | www.wavecom.ee | www.facebook.com/wavecom.ee
> >
>

Re: Specifying hypervisor type in CKS

[Wei ZHOU <us...@gmail.com>]

Currently it is not supported.

There are some enhancements for CKS in the PR
https://github.com/apache/cloudstack/pull/9102
It will be merged into 4.21



Kind regards,
Wei



On Fri, May 16, 2025 at 2:37 PM Joann Mõndresku <jo...@wavecom.ee.invalid>
wrote:

> Hello.
>
> We have a situation where we have 2 different hypervisor clusters in a
> zone.
> When trying to deploy a Kubernetes cluster in it, it defaults to KVM with
> no option to change.
> Is there a way to specify hypervisor used for creating the Kubernetes
> cluster?
>
>
> Lugupidamisega / Best regards,
>
> Joann Mõndresku
>
>
>
> Süsteemiadministraator | Systems Administrator | joann@wavecom.ee
>
> WaveCom AS | ISO 9001, 27001 & 27017 Certified DC and Cloud services
> Endla 16, Tallinn 10142 | www.wavecom.ee | www.facebook.com/wavecom.ee
>