No Arm support for the livenessprobe and csi-provisioner images

[stuart-c-moore]

What happened:

When trying to run the csi-driver-nfs on an Arm system (Raspberry Pi):

Failed to pull image "k8s.gcr.io/sig-storage/livenessprobe:v2.1.0": rpc error: code = NotFound desc = failed to pull and unpack image "k8s.gcr.io/sig-storage/livenessprobe:v2.1.0": no match for platform in manifest: not found

Failed to pull image "k8s.gcr.io/sig-storage/csi-provisioner:v2.1.0": rpc error: code = NotFound desc = failed to pull and unpack image "k8s.gcr.io/sig-storage/csi-provisioner:v2.1.0": no match for platform in manifest: not found

What you expected to happen:

Image should be pulled successfully on arm platforms

How to reproduce it:

On a Raspberry Pi4, Running Raspbian OS 10 (Buster), using the latest version of k3s:

sudo helm repo add csi-driver-nfs https://raw.githubusercontent.com/kubernetes-csi/csi-driver-nfs/master/charts
sudo helm install csi-driver-nfs csi-driver-nfs/csi-driver-nfs --namespace kube-system

Anything else we need to know?:

Environment:

• CSI Driver version: latest
• Kubernetes version (use kubectl version): 1.20.6 (k3s.io)
• OS (e.g. from /etc/os-release): Raspbian GNU/Linux 10 (buster)
• Kernel (e.g. uname -a): Linux pik3s-s01 5.10.17-v7l+ #1403 SMP Mon Feb 22 11:33:35 GMT 2021 armv7l GNU/Linux
• Hardware: Raspberry Pi 4 Model B 8GB

[andyzhangx]

according to kubernetes-csi/livenessprobe#89 (comment), k8s.gcr.io/sig-storage/livenessprobe:v2.1.0 already supports ARM

[stuart-c-moore]

So, apparently not:

 $ sudo docker pull k8s.gcr.io/sig-storage/livenessprobe:v2.1.0
v2.1.0: Pulling from sig-storage/livenessprobe
no matching manifest for linux/arm/v7 in the manifest list entries

$ sudo docker pull k8s.gcr.io/sig-storage/csi-provisioner:v2.1.0
v2.1.0: Pulling from sig-storage/csi-provisioner
no matching manifest for linux/arm/v7 in the manifest list entries

Should this issue be moved to the livenessprobe and csi-provisioner repos?

[andyzhangx]

cc @msau42

[msau42]

When I inspect the image, I do see arm64 manifests:

$ gcrane manifest k8s.gcr.io/sig-storage/csi-provisioner:v2.1.0
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
   "manifests": [
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 739,
         "digest": "sha256:dc17308d5e6405307a4c6dc3d019013beecde77818473e428bf2d3b89a7af751",
         "platform": {
            "architecture": "amd64",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 739,
         "digest": "sha256:a2127f719d22f9605eaf730f7a204244c270b5f0a390d69be6eab34d7eedbd78",
         "platform": {
            "architecture": "arm64",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 739,
         "digest": "sha256:0fc862566d4033d992a44f899f61661c1aff1a20cbabc3c6c948d0e6d00be965",
         "platform": {
            "architecture": "ppc64le",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 739,
         "digest": "sha256:6569f5a4627582b5552bec5401d30289715d2194bd322eeed9ed4bfaf2fbd836",
         "platform": {
            "architecture": "s390x",
            "os": "linux"
         }
      }
   ]

[stuart-c-moore]

ah, I'm not using arm64 though, I'm using armv7. Arm64 support for Raspberry Pi's is still in beta, hence being stuck on armv7 for a while.

Are there any plans to support this?

[msau42]

Our build platforms are listed in https://github.com/kubernetes-csi/csi-release-tools/blob/master/prow.sh#L83. If you would like to help test and add armv7 builds that would be greatly appreciated.

[stuart-c-moore]

I'm happy to test any new armv7 images, however I have no experience the the build process used in that repo.

Is it just a case of adding linux arm -arm to prow.sh in a PR? (I assume the architecture name is arm, looking at https://golang.org/doc/install/source.

Would it really be as simple as stuart-c-moore/csi-release-tools#1 ?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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.