Fix failing image-builder targets

[richardcase]

trafficstars

/kind bug

What steps did you take and what happened:

When building AMIs for CAPA there are a number of targets OS's that are failing to build. We need to investigate and decide if we want to fix / support these:

• amazon-2 (error: Failure downloading https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm)
• centos-7 (error: Failure downloading https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm)
• rockylinux-8 (error: amazon-ebs.rockylinux-8: No AMI was found matching filters)

What did you expect to happen:

I expect any supported OS by CAPA to have the AMIs building successfully.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

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

[richardcase]

/help /triage accepted /priority important-soon

[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:

/help /triage accepted /priority important-soon

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.

[phuhung273]

• centos7 already passed EOL -> i think better to drop support
• AL2 is 06/2025 -> nice to have
• rocky linux 8 is 05/2029-> must have

[k8s-triage-robot]

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Deprioritize it with /priority important-longterm or /priority backlog
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted