Support make container on arm64 architecture

[wangzihao3]

Signed-off-by: wangzihao [email protected]

What type of PR is this?
/kind feature

What this PR does / why we need it:
Add support for multi-arch
Which issue(s) this PR fixes:

Fixes #381

Special notes for your reviewer:
use Kunpeng920(arm) and Xeon 6148(x86) to test building.
Does this PR introduce a user-facing change?:

- Replace gcr.io/distroless/static:latest with BASE_IMAGE in Dockerfile. And judge the arch in build.make, set BASE_IMAGE to discolix/static:latest when ARCH is arm64.

[k8s-ci-robot]

Welcome @Wangzihao18!

It looks like this is your first PR to kubernetes-csi/external-provisioner 🎉. 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-csi/external-provisioner 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 @Wangzihao18. Thanks for your PR.

I'm waiting for a kubernetes-csi 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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Wangzihao18
To complete the pull request process, please assign saad-ali
You can assign the PR to them by writing /assign @saad-ali in a comment when ready.

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

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

[wangzihao3]

/assign @saad-ali

[wangzihao3]

Sorry, I am not very familiar with raising PRs, it seems I modify the contents in the dictionary release-tools and the make test can't pass. And it shows

### test-subtree:./release-tools/verify-subtree.sh release-tools
Directory 'release-tools' contains non-upstream changes:

commit 45723afa1d3cd459a25f4df60bba03ffb86dffa5 (HEAD -> arm-test, origin/arm-test)

What should I do to make it pass? thanks!
Should I go to csi-release-tools repo to modify the contents in the dictionary release-tools?

[Pensu]

@Wangzihao18 Yeah, the release-tool directory comes from csi-release-tools repo. I believe you need to modify that repo and then those changes can be updated here.

[msau42]

/ok-to-test

[wangzihao3]

/retest

[k8s-ci-robot]

@Wangzihao18: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pull-kubernetes-csi-external-provisioner-unit	a8e6acf	link	/test pull-kubernetes-csi-external-provisioner-unit

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.

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

[wangzihao3]

Thanks! Happy new year @Pensu . I have raised a PR in the csi-release-tools repo.kubernetes-csi/csi-release-tools#59. Is that right?

[Pensu]

Thanks! Happy new year @Pensu . I have raised a PR in the csi-release-tools repo.kubernetes-csi/csi-release-tools#59. Is that right?

Hey, thanks @Wangzihao18. A very happy new year to you too! Yeah, that looks good. Thanks.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.