✨ Use kustomize new syntax for patches

[mquhuy]

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 #1730

Special notes for your reviewer:
Kustomize version needs to be updated to 5.2.1, as the current version (5.1.1) gets confused with multiple objects in the same patch file (it only understands if the patch file is split so that each object is in one file).

I also updated the kustomize version in ensure_kustomize.sh. Not sure if it's in use though, as I can see that the version is already very old.

[netlify]

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

Name	Link
🔨 Latest commit	83f22d4
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-cluster-api-openstack/deploys/653b5e88e48ff90008e0e820
😎 Deploy Preview	https://deploy-preview-1735--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 site configuration.

[k8s-ci-robot]

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

[lentzi90]

/ok-to-test

[lentzi90]

Looks good! Could you move the apiVersion and kind to the top of the files?

[lentzi90]

Great!
I think we can also update the same in v1alpha6, v1alpha5 and here. Then I think we got rid of all the old syntax 🙂

[lentzi90]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lentzi90, mquhuy

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]

Triggering full e2e since this touches the remediation tests
/test pull-cluster-api-provider-openstack-e2e-full-test

[lentzi90]

It is unclear to me if the test failure is related to the PR
/test pull-cluster-api-provider-openstack-e2e-test

[mdbooth]

/lgtm

[mquhuy]

/unhold