🌱 Add Windows ARM64 in Makefile

[bear-redhat]

Add Windows ARM64 to release

[k8s-ci-robot]

Welcome @bear-redhat!

It looks like this is your first PR to kubernetes-sigs/controller-tools 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/controller-tools has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @bear-redhat. Thanks for your PR.

I'm waiting for a github.com 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.

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.

[sbueringer]

Sorry, wrong button

/ok-to-test

@bear-redhat I assume you tested it and the binary generally works on Windows arm64? (because we will have no way to test it)

[bear-redhat]

@sbueringer heyy thank you for looking into the PR!
I am not sure how to systematically test the binary, but it does generate the executable. I tried to use the envtest with openshift-installer and it seems working.
I missed one part yesterday about the Dockerfile change - etcd current does not release a Windows on ARM64 binary, and I am not sure how to make them generating that binary (seems they are not using GitHub workflow for releasing). Thus, I changed the Dockerfile to download amd64 version of the etcd instead, which will work on Windows on ARM as well.

[sbueringer]

Alright, sounds good. Let's just give it a try.

Can you open a PR like this for the latest Kubernetes 1.35 alpha? So we can test the entire workflow once end to end

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 9379633ac8074e2f7d37599a05fe63a2ec47e85b

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bear-redhat, sbueringer

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

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