VM Operator was originally designed to support a specific set of use cases, such as deploying virtual machines to act as Kubernetes nodes. As the scope of VM Operator expanded to include a wider variety of workloads, it became clear the VM Operator API needed to evolve as well. Requirements such as a better user experience, enhanced guest bootstrapping, improved guest network configuration, and augmented status capabilities gave way to the next version of the VM Operator API. This proposal describes the VM Operator API schema version v1alpha2 and its ability to satisfy current workload requirements as well as provide a stable foundation for future API revisions as new use cases emerge.
Please describe the solution you would like.
VM Operator was originally designed to support a specific set of use cases, such as deploying virtual machines to act as Kubernetes nodes. As the scope of VM Operator expanded to include a wider variety of workloads, it became clear the VM Operator API needed to evolve as well. Requirements such as a better user experience, enhanced guest bootstrapping, improved guest network configuration, and augmented status capabilities gave way to the next version of the VM Operator API. This proposal describes the VM Operator API schema version v1alpha2 and its ability to satisfy current workload requirements as well as provide a stable foundation for future API revisions as new use cases emerge.
Please find a link to the proposal entitled VM Operator API v1alpha2: One-Pager.
Is there anything else you would like to add?
NA
Please tell us about your environment.
NA
rpm -qa VMware-wcp
on the vCenter applianceNA
rpm -qa VMware-wcpovf
on the vCenter applianceNA
kubectl version
NA