-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Use docker buildx for the build-image. #99080
Conversation
Hi @vinayakankugoyal. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/cc @BenTheElder |
We need to be ensuring a buildx builder exists, the first point in that issue needs fixing before this one. |
5870bea
to
19fb35d
Compare
19fb35d
to
73d68e5
Compare
/test pull-kubernetes-cross |
@vinayakankugoyal: Cannot trigger testing until a trusted user reviews the PR and leaves an 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. |
73d68e5
to
338ba25
Compare
/ok-to-test |
/test pull-kubernetes-bazel-test |
/test pull-kubernetes-cross |
/test all |
1.21 or 1.22 ? need rebase for conflicts. |
6060524
to
9df100b
Compare
9df100b
to
086cdfb
Compare
Since code freeze for 1.21 is already in effect, 1.22. |
Thanks Done! |
/test pull-kubernetes-unit |
@BenTheElder - do we wan't to make this change? I believe we are using buildx for docker builds for other images already. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
buildx is already a hard requirement for building a Kubernetes release since at least v1.21.0
/test pull-kubernetes-node-e2e-containerd [new job that is stuck pending because it was added while this PR was inactive I think] |
pull-kubernetes-node-e2e-containerd passed, @BenTheElder can you /lgtm when you get a chance? Thanks! |
bah, in some repos github approve is lgtm + approve with prow |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, vinayakankugoyal The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/triage accepted |
/retest |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Switch to using docker buildx for the build-image. We want to consistently use buildx everywhere as highlighted in #98908.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: