-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No more arm32v7 images available after v0.12.1 #1136
Comments
This seems related to tektoncd/pipeline#4059 and tektoncd/pipeline#3717. I think when we updated the release pipeline, we used the same platforms that pipelines was built for. It should be easy enough to add However I don't think there is much of a use case for releasing triggers for linux/arm without also doing the same for pipelines :) |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
@imjasonh recently brought back building arm v7 images for Pipelines (tektoncd/pipeline#4331) given that precent maybe we can bring it back here as well? |
/remove-lifecycle stale |
Pipelines now supports arm, we should prioritize fixing this in triggers especially because the fix should be relatively simple. /assign dibyom |
Until release v0.12.1, arm32v7 images were available.
See manifests here: https://console.cloud.google.com/gcr/images/tekton-releases/GLOBAL/github.com/tektoncd/triggers/cmd/controller@sha256:96a63ec6d0cc0871d7dfea9d831b6da20df474bbdcbd01caf62f488e2d682db4/details?tab=info
Available platform architectures were: amd64, arm, arm64, ppc64le, s390x
Starting from v0.13.0, no more arm32v7 images were available.
See manifests here: https://console.cloud.google.com/gcr/images/tekton-releases/GLOBAL/github.com/tektoncd/triggers/cmd/controller@sha256:58baa0aa0eaca368b8090bcb6e88024847d14df2952cdfe7f22be6132a7732c9/details?tab=info
Available platform architectures were: amd64, arm64, ppc64le, s390x
So arm32v7 users are currently blocked in v0.12.1, not possibility to upgrade to next releases.
The text was updated successfully, but these errors were encountered: