WIP: 🌱 ClusterAPI v1.11 v1beta2

[toby-archer-tr]

What type of PR is this?
/kind api-change

What this PR does / why we need it:
Taking a stab at refactoring cluster-api-aws v1beta2 resources, based on the new v1.11+ v1beta2 cluster-api resources, along with following API contract changes around status' and the use of k8s conditions.

Which issue(s) this PR fixes
Fixes #

Special notes for your reviewer:

• I would love to break this down to smaller, iterative PRs, but couldn't see through the entanglement to find a strategy, would appreciate any input.
• Alignment is needed on the implementation of v1beta1 -> v1beta2 conditions conversions. The closest I have gotten so far is by annotating the Conditions field with +k8s:conversion-gen=false and attempting to wire in a custom conversion; however the conversion-gen is proving a little tricky. My first approach was to provide a conversion for the v1alpha1.Condition -> metav1.Condition but as both packages are external, this doesn't work. I have not found any example or guidance on this, so far.
• Run through all status changes, ensuring correct assumptions of removing Ready, introduction of *InitializationStatus and the uses of those in the controllers are correct.
• Align/standardize on conditions, as per the proposal

Checklist:

• squashed commits
• includes documentation
• includes emoji in title
• adds unit tests
• adds or updates e2e tests

Release note:

TBD...

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[linux-foundation-easycla]

• ❌ - login: @toby-archer-tr / name: Toby Archer . The commit (a7024a9, dbd3660) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign ankitasw for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @toby-archer-tr. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[richardcase]

Thanks for this @toby-archer-tr .

We have #5624 that has started this.

[richardcase]

Lets discuss on slack. Feel free to ping me.

[k8s-ci-robot]

PR needs rebase.

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.