feat: Implement Migration Controller

[rschalo]

Fixes #N/A

Description
To facilitate the v1beta1 to v1 migration, Karpenter introduced conversion webhooks. These webhooks were introduced in patch versions to v0.33.x-v0.37.x along with the 1.0 release. As a result, users are able to upgrade to 1.0 with their existing v1beta1 resources. These resources would be automatically converted by the webhooks so users could upgrade without downtime. Users would then migrate the resources they’re applying (e.g. through pipelines or GitOps solutions) to v1 before the conversion webhooks are dropped at v1.1.

There is a problem when users upgrade to v1.1. Users change the storage version on their CRDs to v1 as part of the v1.0 upgrade, however this only affects newly created resources and resources which have had writes performed against them. It is possible that a user could upgrade to v1.1 while resources are still stored as v1beta1, potentially resulting in data loss.

This PR implements two controllers to perform the write against Karpenter resources and when all resources have been updated, update status.StoredVersions for Karpenter resources to be just v1.

How was this change tested?
Local testing and unit tests.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[k8s-ci-robot]

Hi @rschalo. 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.

[jmdeal]

checkpointing

[njtran]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: njtran, rschalo

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [njtran]

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