-
Notifications
You must be signed in to change notification settings - Fork 119
Closed
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Description
In order to support multiple architecture, we need to provide image in multiple
architecture for the projects's end-to-end tests. This also applies to some images built
in plumbing as we may use them on the target clusters (s390x, arm64, …) and/or during
end-to-end tests.
In an ideal world, we would use tekton to build those (aka dogfooding, …). My initial
search around this mainly ended up around qemu, qemu-user-static and docker (+buildkit).
See
- crazy-max/ghaction-docker-buildx: GitHub Action to set up Docker Buildx
- hello-multiarch/image.yml at master · piwi3910/hello-multiarch
So the questions is how should we proceed:
- Have a quick way of building multi-arch images using github action (as above)
- Have a "middle" solution where we use dogfooding with some DinD, privileged containers
and buildx - Find some way to replicate the github action flow in tekton (ideally without any need to
privileged containers, but I have high doubt that it's possible)
/cc @afrittoli
/kind feature
ghatwala and barthy1
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.