Replies: 2 comments 3 replies
-
Hey, yeah, we're focusing on bare-metal servers and using KubeVirt to spawn VMs. This means Cozytack covers all infrastructure needs from the very lowest layers (hardware, OS, and hypervisor) up to the highest levels of applications and managed services. |
Beta Was this translation helpful? Give feedback.
-
Thanks for replying. So, would you then agree that CozyStack is not as useful when running in a virtualized environment? For instance, unless you request metal type machines in the cloud, you'll always get a virtual machine. Same with vmware on-prem? I don't think kubevirt can fulfill it's role in that case and you would need to integrate with the vm-provider directly. |
Beta Was this translation helpful? Give feedback.
-
I'm trying to understand how kubevirt runs the tenant worker nodes. As far as I understand a combination of qemu and KVM is used on the worker node to start a VM 'process'.
So, when I install CozyStack on a VM-based management cluster (meaning Talos runs on vms itself), does that mean that the vms (tenant worker nodes) created by kubevirt require nested virtualization to have the full speed benefits? I believe the worker nodes are launched on the management cluster?
Beta Was this translation helpful? Give feedback.
All reactions