-
Notifications
You must be signed in to change notification settings - Fork 753
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
Consider moving docker buildx -> ko #2258
Comments
I can try this out. I think we should also remove the |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days |
/not stale |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days |
This seems unviable based on what I have seen today. Today we build multiple binaries into a single image as seen in our |
Thanks for digging into this @jchen6585! From the |
|
What would you like to be added:
Multi-arch image build uses docker buildx and that takes a lot of time. One example - https://github.com/aws/amazon-vpc-cni-k8s/actions/runs/4119775035/jobs/7113817570 , it took 40+ mins and some times more than an hour or so.
AWS LB cntrl moved away from buildx to ko and saw improvements from 2 hrs to 15 mins, we need to evaluate if that would benefit with faster builds for multi-arch images - kubernetes-sigs/aws-load-balancer-controller#2955
Why is this needed:
Faster builds during PR merges. Maybe not urgent but something to POC.
The text was updated successfully, but these errors were encountered: