v1beta1 Tracking Issue

[randomvariable]

/kind feature

Describe the solution you'd like

• Bump API version to v1beta1 to match Cluster API Core

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Rough task list

1. Bump controller runtime version to v0.10 and controller tools to v0.7.x #1250

• Do immediately

1. Add v1beta1 types #1251

• Do immediately

1. Refactor v1alpha3 webhooks to convert to v1beta1 hub #1252

• Depends on Add v1beta1 types #1251

1. Add v1alpha4 to v1beta1 conversions #1253

• Depends on Add v1beta1 types #1251

1. Add e2e upgrade test for v1alpha3 to v1beta1 #1254

• Depends on Refactor v1alpha3 webhooks to convert to v1beta1 hub #1252

1. Add e2e test for upgrading v1alpha4 to v1beta1 #1255

• Depends on Add v1alpha4 to v1beta1 conversions #1253

1. Bump clusterctl metadata to v1beta1 #1256

• Depends on Refactor v1alpha3 webhooks to convert to v1beta1 hub #1252
• Depends on Add v1alpha4 to v1beta1 conversions #1253

Related Issues:

• Document the release process for v1beta1 cluster-api#5260
• Document v1alpha4 -> v1beta1 changes for providers in CAPI book cluster-api#5262
• clusterctl v1beta1 should allow upgrades starting from v1alpha3 cluster-api#5269
• Use Controller-Runtime release for CAPI v1beta1/v1.0.0 cluster-api#5277

[randomvariable]

/milestone v0.8.0

[randomvariable]

/area api
/priority important-soon
/kind release-blocking

[k8s-ci-robot]

@randomvariable: The label(s) area/api, kind/release-blocking cannot be applied, because the repository doesn't have them.

In response to this:

/area api
/priority important-soon
/kind release-blocking

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/test-infra repository.

[randomvariable]

/kind release-blocking
/area api

[omniproc]

So, what's left to do here? CAPV v0.8.1 is out as well as CAPI v1.0.0 yet still the metadata iof CAPV sais alphav4? What's blocking? Can we simply rewrite the manifests or are there any breaking changes not yet compatible with v.0.8.1?

[yastij]

@omniproc - we're currently reviewing looking at #1269 then bumping the metadata.yaml, after that we should be able to release v1beta1 support. That should probably happen Tuesday

[MaxRink]

@yastij @randomvariable i guess this can be closed?

[yastij]

yeah