✨ [build] Add support for darwin/arm64 arch

[dntosas]

Description

More and more users are now using M1 chips for development so publishing
kubebuilder-tools in darwin/arm64 arch will enable them to use the
project natively on their machines without needing to apply custom ways
of solving missing dependencies.

Motivation

Have seen many issues on different projects that utilize kubebuilder regarding missing
binaries in darwin/arm64 arch so I thought to push this. Example Project: operator-sdk, cluster-api, etc.

Fixes

• build kubebuilder-tools for darwin/arm64 #2505
• unable to find a version that was supported for platform darwin/arm64 controller-runtime#1657
• unable to find a version that was supported for platform darwin/arm64 when execute make test controller-runtime#1809

[k8s-ci-robot]

Welcome @dntosas!

It looks like this is your first PR to kubernetes-sigs/kubebuilder 🎉. 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/kubebuilder 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 @dntosas. 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.

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/test-infra repository.

[FillZpp]

/ok-to-test

[camilamacedo86]

That shows great 🥇
We will be able to test/ensure it in the next release.

/approved

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, dntosas

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 [camilamacedo86]

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

[camilamacedo86]

/lgtm

[sbueringer]

One question. Will this only publish the darwin/arm64 kubebuilder binary or also kubebuilder darwin/arm64 tools (https://github.com/kubernetes-sigs/kubebuilder/tree/tools-releases)?
(just asking because I think we want both and I'm not sure how tools is configured)

[dntosas]

One question. Will this only publish the darwin/arm64 kubebuilder binary or also kubebuilder darwin/arm64 tools (https://github.com/kubernetes-sigs/kubebuilder/tree/tools-releases)? (just asking because I think we want both and I'm not sure how tools is configured)

good question ^ maybe we should also update the branch you mentioned?

[camilamacedo86]

Hi @sbueringer and @dntosas,

I could not find a place in https://github.com/kubernetes-sigs/kubebuilder/tree/tools-releases where we should change regards this one. Did you find something?

[camilamacedo86]

/test pull-kubebuilder-e2e-k8s-1-16-15

[camilamacedo86]

/hold
Until we get the answers: #2516 (comment)

[dntosas]

hey @camilamacedo86 !

the README file maybe 😆

other than that, can't see anything more related ^^ let's wait for @sbueringer also if he got any findings

[sbueringer]

Hi @sbueringer and @dntosas,

I could not find a place in https://github.com/kubernetes-sigs/kubebuilder/tree/tools-releases where we should change regards this one. Did you find something?

I did some research about that a while back and only found: https://github.com/kubernetes-sigs/kubebuilder/pull/1992/files#r573150243

xref: kubernetes-sigs/cluster-api#6092 (comment)

[dntosas]

makes sense, as Dockerfile seems to take values for GOOS and GOARCH dynamically from the master branch (?) now ^^

[camilamacedo86]

Hi @dntosas,

Let's move forward here.
I will ping you if it does not work when we try to do the next release

/hold cancel