The vm-operator-api project provides the object model and generated client libraries for the VM Operator project, which is a part of vSphere's Kubernetes support.
VM Operator allows users to manage the lifecycle of vSphere Virtual Machines using a declarative Kubernetes consumption model and is an integral part of Project Pacific in vSphere 7 with Kubernetes.
The state of VirtualMachine CRDs in a Kubernetes cluster is monitored by built-in controllers which reconcile the CRD specification into real Virtual Machines along with the necessary storage, networking and compute dependencies. The state of the Virtual Machines is reflected back in the VirtualMachine CRD status which can be queried for essential state like IP Address(es).
The use cases of vm-operator-api are currently limited to 3rd party integrations with vSphere with Kubernetes.
In vSphere with Kubernetes it is not currently possible to create new VirtualMachines using this API, but we hope to expand on this functionality over time.
We welcome new contributors who are interested in collaborating on our Kubernetes support for vSphere
More information here
Check out how to get started with vm-operator-api here
Use of the vm-operator-api is currently only supported in vSphere with Kubernetes. However the intention is to make it more widely available as a Kubernetes-native way of interacting with vSphere VMs.
Current list of project maintainers here
Antrea is licensed under the Apache License, version 2.0
Package apis contains Kubernetes API groups.
|Package apis contains Kubernetes API groups.|
+k8s:openapi-gen=true +kubebuilder:object:generate=true +groupName=vmoperator.vmware.com
|+k8s:openapi-gen=true +kubebuilder:object:generate=true +groupName=vmoperator.vmware.com|
Package install installs the API group, making it available as an option to all of the API encoding/decoding machinery.
|Package install installs the API group, making it available as an option to all of the API encoding/decoding machinery.|