ARM64 support for MaaS

[kreeuwijk]

Change description

This PR adds the ability to generate Ubuntu 22.04/24.04 ARM64 images.

The work is inspired by this work from @ader1990. While that PR was never merged, this PR generalizes the approach and ensures no impact to existing workflows.

• Is this change including a new Provider or a new OS? (y/n) N

Related issues

• Provides a generic solution for AARCH64 / ARM64 CAPI image build for Ubuntu 22.04 #1142, which could be adopted into the qemu builds (this PR only implements it for maas builds)

Additional context

images/capi/packer/maas/README.md has been updated to detail the build steps fully for both AMD64 and ARM64.

Acknowledgements

Kudos to @blik616287 for helping out with the Ansible filtering

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: kreeuwijk / name: Kevin Reeuwijk (f3af927)

[k8s-ci-robot]

Hi @kreeuwijk. 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.

Details

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.

[drew-viles]

/ok-to-test

[kreeuwijk]

pull-azure-sigs has no relevance to the PR

[vasartori]

I don't have ARM64 hardware available to test this PR. However, based on my review, this PR will not break anything for amd64 builds.
I am starting tests on amd64 right now.

[ader1990]

Thanks for spearheading this work!

[vasartori]

Tested! Everything seems to work well on amd64.
/lgtm

[vasartori]

/approve

[kreeuwijk]

@vasartori for completeness: I used an AWS Graviton instance (m7g.metal) to test this in ARM64. The changes allowed me to generate CAPI images for Ubuntu 22.04 and 24.04. I also tested deploying a CAPI cluster through MaaS (using Spectro Cloud Palette) with the ARM64 Ubuntu 22.04 + Kubernetes 1.33.5 image and that worked.

I did find a bug in MaaS itself though, which has been reported here

[vasartori]

@kreeuwijk Would you mind squashing the commits please?

[kreeuwijk]

@vasartori Commits squashed

[vasartori]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vasartori
Once this PR has been reviewed and has the lgtm label, please assign jsturtevant for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vasartori]

@drew-viles could you help us to merge this PR?

[drew-viles]

/retest

[vasartori]

/retest

[k8s-ci-robot]

@kreeuwijk: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-azure-vhds	f3af927	link	true	/test pull-azure-vhds
pull-azure-sigs	f3af927	link	false	/test pull-azure-sigs

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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. I understand the commands that are listed here.

[drew-viles]

So in principle I've no issues with merging this. My only concern is it'll cause issues with the azure tests moving forward. This is where my knowledge of the repo and subsequent prow usage falters tbh. I'm going to ask @mboersma if he can chip in on how we can target it in a way that skips the azure checks. I'm sure there is as there are some build that only use Azure for example, and they only run those checks.