Migrate to vm-operator v1alpha2 APIs

[sbueringer]

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]

cc @srm09 @randomvariable

[randomvariable]

/lifecycle frozen

[chrischdi]

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).

[randomvariable]

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

[randomvariable]

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

[chrischdi]

Let's split this into two PRs:

• migrating the controller and main go module
  • ✨ vm-operator: migrate to v1alpha2 #3029
• migrating the e2e test part
  • 🌱 test: migrate to vm-operator v1alpha2 #3032

[chrischdi]

/close

🎉

[k8s-ci-robot]

@chrischdi: Closing this issue.

In response to this:

/close

🎉

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.