✨ Implement CRD migration

[okozachenko1203]

What this PR does / why we need it:
Follow-up to: kubernetes-sigs/cluster-api#11889
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

• squashed commits
• if necessary:
  • includes documentation
  • adds unit tests

/hold

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!

Name	Link
🔨 Latest commit	dd809f5
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-cluster-api-openstack/deploys/6902aa15a4c0410008d8afa8
😎 Deploy Preview	https://deploy-preview-2810--kubernetes-sigs-cluster-api-openstack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[k8s-ci-robot]

Hi @okozachenko1203. Thanks for your PR.

I'm waiting for a github.com 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.

[okozachenko1203]

/ok-to-test

[k8s-ci-robot]

@okozachenko1203: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

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.

[lentzi90]

Can you explain what this does and why it is needed?
I thought CRD migration was already implemented in clusterctl, so why now this?

[okozachenko1203]

Can you explain what this does and why it is needed? I thought CRD migration was already implemented in clusterctl, so why now this?

sure, here are references.

kubernetes-sigs/cluster-api#11889
kubernetes-sigs/cluster-api#11894

[lentzi90]

Thank you! Now I understand!
/ok-to-test

[okozachenko1203]

/retest

[okozachenko1203]

/retest

[lentzi90]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lentzi90

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 [lentzi90]

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

[lentzi90]

/cc @smoshiur1237
@adilGhaffarDev have you seen this? We should do the same in CAPM3 also!

[adilGhaffarDev]

@adilGhaffarDev have you seen this? We should do the same in CAPM3 also!
Yes, I will add this on Capm3 side.

[smoshiur1237]

Thanks for this. It looks good to me but I would request to add details in the PR descriptions. Then remove the hold please.
/lgtm

[lentzi90]

/hold cancel