Add e2e test for upgrading v1alpha4 to v1beta1 #1255
Labels
area/testing
kind/feature
Categorizes issue or PR as related to a new feature.
kind/release-blocking
Issues or PRs that need to be closed before the next CAPV release
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
/kind feature
/area testing
/priority important-soon
/milestone v0.8.0
/kind release-blocking
Describe the solution you'd like
With the new upgrade path being enabled for CAPI, we want to add the tests in e2e to upgrade from v1alpha4 to v1beta1
Depends on #1253
The text was updated successfully, but these errors were encountered: