Add platform linux/arm

[c0va23]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test

/kind feature

/kind flake

What this PR does / why we need it:

democratic-csi has builds for linux/arm, but that doesn't work out of the box because node-driver-registrar does not provide images for this architecture. Currently, to use democratic-csi and other CSI drivers on the linux/arm platform, you have to use third-party node-driver-registrar builds.

I understand that the linux/arm platform can hardly be called complete for server applications. But first, we have official K8S builds for this platform. Secondly, nodes with such a platform can be used for native CI/CD for low-power devices on linux/arm.

In my case, I use RPI4 with 32 bit Ubuntu to build a compact multimedia server that can be operated on low-power devices.

Which issue(s) this PR fixes:

Fixes #150

Special notes for your reviewer:

linux/arm image tested on RPI4 with host OS Ubuntu 20.04.2 (32bit, https://cdimage.ubuntu.com/releases/20.04.2/release/ubuntu-20.04.2-preinstalled-server-armhf+raspi.img.xz). I tested "node-driver-registrar" with democratic-csi (https://github.com/democratic-csi/democratic-csi) as a volume provider for the Drone CI Kubernetes Runner (https://github.com/drone-runners/drone-runner-kube). The linux/arm build works the same as the linux/amd64 and linux/arm64 builds.

For testing, I created a temporary image for all linux architectures (including arm), which I placed here https://github.com/c0va23/node-driver-registrar/pkgs/container/csi-node-driver-registrar.

Does this PR introduce a user-facing change?:

Added `linux/arm` platform for multiarch image 

[k8s-ci-robot]

Welcome @c0va23!

It looks like this is your first PR to kubernetes-csi/node-driver-registrar 🎉. 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/node-driver-registrar 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 @c0va23. 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.

[c0va23]

/assign @c0va23

[mauriciopoppe]

the folder release-tools comes as a git subtree from https://github.com/kubernetes-csi/csi-release-tools, this PR should probably be there too instead

[msau42]

/ok-to-test

[c0va23]

@mauriciopoppe, thanks for the hint. I will push the changes to the upstream release-tools and push their ships when the changes are merged.

[c0va23]

/hold

[c0va23]

Port changes to kubernetes-csi/csi-release-tools#167

[c0va23]

/unhold

[c0va23]

Update release-tools from csi-release-tools from upstream

[mauriciopoppe]

I saw that the build logs are ok, thanks for adding 32 bit arm support to CSI!
/lgtm
/cc @msau42

[msau42]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: c0va23, msau42

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:

• release-tools/OWNERS [msau42]

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

[andyzhangx]

so next release v2.4.0 would have arm/v7 support?