Bump Kustomize to v5

[killianmuldoon]

Kustomize released v5.0.0 in February - CAPI should bump the Kustomize version to keep up. Release notes are here.

The following need to be taken care of ahead of and / or alongside the Kustomize bump:

1. Ensure encoding of creationTimestamp is handled correctly. This should be handled in upstream Kustomize - issue here - but if not there are workarounds for CAPI - e.g. patch creationTimestamp on each and every CRD. Reference issue in CAPI.
2. Take care of deprecations: The following have been deprecated:

• vars -> replacements
• bases -> resources
• patchesStrategicMerge -> patches
• patchesJson6902 -> patches

/area dependency

[fabriziopandini]

Let's consider if to wait for a patch release with the fix for creationTimestamp
/triage accepted
/help

[k8s-ci-robot]

@fabriziopandini:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

Let's consider if to wait for a patch release with the fix for creationTimestamp
/triage accepted
/help

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.

[killianmuldoon]

Let's consider if to wait for a patch release with the fix for creationTimestamp

Yeah - I'm watching that issue to see if there's an update. We should consider it a blocker until then IMO.

[james-callahan]

Yeah - I'm watching that issue to see if there's an update. We should consider it a blocker until then IMO.

Should still be able to work through the deprecations in the mean-time.

[sbueringer]

I've opened a related issue to bump controller-tools: #8546

As far as I can tell we should be able to bump kustomize after we bumped controller-tools?

[fabriziopandini]

/kind cleanup
/priority-important-soon

[fabriziopandini]

/priority important-soon

[sbueringer]

Done in #10294

/close

@killianmuldoon Maybe you can double check. But as far as I can telle verything is done (and we now use kustomize v5.3)

[k8s-ci-robot]

@sbueringer: Closing this issue.

In response to this:

Done in #10294

/close

@killianmuldoon Maybe you can double check. But as far as I can telle verything is done (and we now use kustomize v5.3)

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.