cluster-api-provider-vsphere icon indicating copy to clipboard operation
cluster-api-provider-vsphere copied to clipboard
verified publisher icon kubernetes-sigs

Migrate to vm-operator v1alpha2 APIs

Open sbueringer opened this issue 2 years ago • 5 comments

CAPV today is using vm-operator v1alpha1 APIs. There is ongoing work on v1alpha2 APIs.

v1alpha2 APIs are not ready yet, so for now there is nothing to do. Also when v1alpha2 is the default in vm-operator v1alpha1 will continue to work for some time.

One reason to migrate earlier could be if CAPV needs any new functionalities which are only available via v1alpha2.

sbueringer avatar Jul 31 '23 11:07 sbueringer

cc @srm09 @randomvariable

sbueringer avatar Jul 31 '23 11:07 sbueringer

/lifecycle frozen

randomvariable avatar Jul 31 '23 11:07 randomvariable

Also depends on which versions we need to support + how far it needs to be backwards compatible :-)

(So there won't be cherry-picks for this).

chrischdi avatar Jul 31 '23 11:07 chrischdi

When we do this, let's make sure we're exposing all of the options like boot device size, etc...

randomvariable avatar Feb 15 '24 20:02 randomvariable

Also, v1alpha2 is ready now, so i guess we can upgrade the description.

randomvariable avatar Feb 15 '24 20:02 randomvariable