[e2e] Tests are failing on main

[richardcase]

/kind bug

What steps did you take and what happened:

The e2e tests are failing on main before it gets to anything to do with the AMIs. Looking at the error its failing when running kustomize here: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/test/e2e/shared/suite.go#L79

The error is:

Error: trouble configuring builtin PatchTransformer with config: `
patch: platform-kustomization.yaml
`: unable to parse SM or JSON patch from [platform-kustomization.yaml]

I created a PR (see #5164) to just run the e2e on main.

What did you expect to happen:

I'd expect the e2e to get past this point.

Anything else you would like to add:

I don't see what has changed in this area, the upstream function (see this: https://github.com/kubernetes-sigs/cluster-api/blob/main/test/framework/kubernetesversions/template.go#L71) hasn't changed in years.

Environment:

• Cluster-api-provider-aws version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[richardcase]

/triagae accepted
/priority critical-urgent
/help
/milestone v2.7.0
/kind release-blocker

[k8s-ci-robot]

@richardcase:
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:

/triagae accepted
/priority critical-urgent
/help
/milestone v2.7.0
/kind release-blocker

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.

[k8s-ci-robot]

@richardcase: The label(s) kind/release-blocker cannot be applied, because the repository doesn't have them.

In response to this:

/triagae accepted
/priority critical-urgent
/help
/milestone v2.7.0
/kind release-blocker

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]

/triage accepted