fix(download): Correct Youki download URL for arm64 architecture

[burxtx]

This PR fixes an issue with downloading Youki on systems where Ansible reports the architecture as arm64, such as Apple Silicon Macs. The youki_download_url was using {{ ansible_architecture }} directly, which results in arm64 in the URL. However, Youki's release artifacts use aarch64 for this architecture, leading to a "404 Not Found" error when trying to download the component.

What type of PR is this?

/kind bug

What this PR does / why we need it:
This change introduces a conditional to map arm64 to aarch64 for both the youki_download_url and the local destination file path (downloads.youki.dest), resolving the download failure.

Which issue(s) this PR fixes:

Fixes #12950

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Fixed youki download URL for Apple Silicon Mac's arm64 architecture

[k8s-ci-robot]

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

[tico88612]

/ok-to-test

[tico88612]

Hey @burxtx, could you write the release note?

[burxtx]

Hey @burxtx, could you write the release note?

OK, release-note added.

[yankay]

Thanks @burxtx
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: burxtx, yankay

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [yankay]

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

[VannTen]

We already have the mapping in the other direction (host_architecture)( Which btw seems weird because I think ansible_arch can have the values used as key there).

Can you please instead add a dict alt_arch (or something like that) and use that (

alt_arch:
  arch1: alt_arch_name
  ...

There is one in

kubespray/scripts/component_hash_update/src/component_hash_update/download.py

Lines 45 to 50 in 4245ddc

	arch_alt_name = {
	"amd64": "x86_64",
	"arm64": "aarch64",
	"ppc64le": None,
	"arm": None,
	"no_arch": None,

but it's not in YAML.

[k8s-ci-robot]

Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found 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.

[burxtx]

We already have the mapping in the other direction (host_architecture)( Which btw seems weird because I think ansible_arch can have the values used as key there).

Can you please instead add a dict alt_arch (or something like that) and use that (

alt_arch:
  arch1: alt_arch_name
  ...

There is one in

kubespray/scripts/component_hash_update/src/component_hash_update/download.py

Lines 45 to 50 in 4245ddc

	arch_alt_name = {
	"amd64": "x86_64",
	"arm64": "aarch64",
	"ppc64le": None,
	"arm": None,
	"no_arch": None,

but it's not in YAML.

@VannTen Thanks for the review, I also noticed the _host_architecture_groups, maybe we need a new dict to resolve the "reverse mapping". I've moved the alt architecture name mapping into "_alt_arch_name".

[VannTen]

One comment (also, no need to rebase / merge unless the bot detect a conflict, but if you need to , you should do something like git rebase master from your branch.

[VannTen]

Don't bother with that, this would only mask errors.
just setup the dict, and if you can have one entry for each supported arch for youki that should be enough.
Then just use alt_arch_name[ansible_architecture] directly on use site.