Inside the VM Service, you'll find where you can manage the components, namely the VM Images (Content Libraries) and VM Classes (t-shirt sizes). The vSphere side of the VM Service is very straight forward, it is created as part of your vSphere with Tanzu namespaces once you enable the service in the new Workload Management "Services" tab:įor more details on setting up VM Service - check out the documentation here. ![]() So, let's have a look at each of these components in detail and see what makes it all tick! VM Service in vSphere The vSphere side is built right into vCenter, it allows you to manage VM Images (Content Libraries) and VM Classes (VM sizing), the Kubernetes side is called VM Operator which creates and services the Kubernetes Custom Resources (CRs/CRDs), which we'll get into later, and tells K8s how to talk to vSphere.Īdditionally, we are happy to announce that we are releasing the VM Operator as a completely open-source component on GitHub, and you can find that here. VM Service is made up of two components, a vSphere side component and a Kubernetes side component. VM Service allows Kubernetes users to provision VMs and their guest OSes declaratively, that is to say in a desired-state manner, just like anything else that is managed by Kubernetes. ![]() This is our first release of VM Service and the VM Operator (v1alpha1) so we would very much appreciate your feedback in helping to shape the future of this feature! VM Service has a whole bunch of goodies inside from declarative Kubernetes CRD based VM provisioning, automatic load balancing across multiple VMs, industry standard cloud-init based guest OS customisation for dev users all the way to administrative controls for VM Images and VM Classes (think t-shirt sizing) for the vSphere administrator. I am happy to introduce the VM Service and VM Operator, these two components work in unison on vSphere with Tanzu to offer Kubernetes users a VM provisioning workflow, never before seen on vSphere. With vSphere 7.0 U2a we will be changing that. However, the way in which VMs have historically been provisioned is somewhat the antithesis of what desired state and Kubernetes stands for, which makes those parts of a solution much less attractive overall than converting everything to containers. VMware as a company has always done something very well, Virtual Machines - and we believe, as well as the wider community that modern applications will not exist in isolation as Kubernetes-only apps, rather they will be made up of a mixture of containers, functions, VMs and as-a-service offerings.
0 Comments
Leave a Reply. |