-
Notifications
You must be signed in to change notification settings - Fork 111
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
Multi-architecture build of e2e and plumbing images #592
Comments
Can first versions of the mentioned images be built using the fastest way? I guess it would be github actions. Just to unblock "other arch support" activities.. |
@barthy1 yeah, @afrittoli said the same during our productivity working group 👼 |
@vdemeester I'd like to suggest the first candidate for multi-arch build here is |
One more idea, for future extensions. We can use Tekton task to start Github action - https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#workflow_dispatch :) |
Is there any cloud provider we could have access to ? (IBM, Google or others), where we can just spin up a VM there, inject our build script from a tekton task and get back the multi arch build ? I understand that Github may seem easy to implement but I think we have the opportunity to show that tekton can be the right CI tool for this kind of workflow and not having to leverage another CI provider for it. |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
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. |
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
anddocker
(+buildkit).See
So the questions is how should we proceed:
and buildx
privileged containers, but I have high doubt that it's possible)
/cc @afrittoli
/kind feature
The text was updated successfully, but these errors were encountered: