Damiano Donati
Damiano Donati
/remove-lifecycle stale
@adammw this will need rebasing
/cherry-pick release-2.4
/test pull-cluster-api-provider-aws-e2e /test pull-cluster-api-provider-aws-e2e-eks
Kicked the tests again now that CI seems to be working again. If tests are green are we happy for this to merge? @r4f4 @richardcase @AndiDog ?
/test pull-cluster-api-provider-aws-e2e-eks
The [EKS e2e failures](https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_cluster-api-provider-aws/5093/pull-cluster-api-provider-aws-e2e-eks/1849186934245560320) are not related to this PR, as I can see them In a no-op PR as well [here](https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/5179#issuecomment-2434713158).
The failure looks limited to `pull-cluster-api-provider-gcp-conformance-ci-artifacts`. Do you think it is related to the change in this PR or something broke it even before this? @cpanato
@richardcase this is fixed by #5133 right? Should we close this as resolved?
> @damdo - i think maybe we should leave it open until there is a release with the new AMI account in it. wdyt? Sounds reasonable yeah.