Welcome!

• Yes, I've searched similar issues on GitHub and didn't find any.

What did you do?

The release binaries have armv7, (e.g https://github.com/traefik/traefik/releases/download/v3.5.0-rc1/traefik_v3.5.0-rc1_linux_armv7.tar.gz) but the alpine dockerfiles only check the platforms for:

• armhf
• aarch64
• x86_64
• riscv64
• s390x
• ppc64le

Similar past discussion here

What were you expecting?

There is a 1:1 mapping of the arch of release binaries to the arch of the official docker image.

arm32v7 is listed as an "official" architecture.

In alpine, apk --print-arch outputs armv7 , so the dockerfile template should have this case
armv7) arch="$apkArch" ;; \

What version are you using?

Impacts all released versions, but discovered using 3.3.6

https://github.com/k3s-io/k3s/blob/master/manifests/traefik.yaml#L31
K3s is using rancher's mirrored repository as a downstream to the official traefik image on dockerhub. rancher/mirrored-library-traefik:3.3.6

I have built my own image by modifying the dockerfile with this addition
armv7) arch="$apkArch" ;; \ and was able to deploy traefik on my k3s cluster.

What is your environment & configuration?

Note my issue is not related to k3s or helm! I assume when this is fixed upstream here, rancher will update their mirror images.

k3s cluster installed from alpine edge repo

k3s version v1.33.1+k3s1 (AlpineLinux)
go version go1.24.3

https://github.com/k3s-io/k3s/blob/master/manifests/traefik.yaml#L31

Charts:

• traefik-34.2.1+up34.2.0 v3.3.2
• traefik-crd-34.2.1+up34.2.0 v3.3.2

Raspberry PI 2 model B

• uname -a

  Linux pi2 6.12.31-0-rpi #1-Alpine SMP Thu May 29 23:21:07 UTC 2025 armv7l GNU/Linux

• apk --print-arch

  armv7

If applicable, please paste the log output in DEBUG level

N/A