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
Build multiplatform images when issue make release-images
#97459
Conversation
@yu2003w: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
Welcome @yu2003w! |
Hi @yu2003w. 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. |
I am not convinced we should always use this pattern |
Hi @fejta , |
/ok-to-test I am primarily concerned about the effect of changing from AKA I would like people to be able to opt-into and then opt-out of this change and not just sending it to everyone immediately. Alternatively I guess you can try and explain me why I shouldn't worry about this change on amd64 :) |
Also are you familiar with |
make release-images
make release-images
/sig release |
make release-images
make release-images
Hi @fejta , |
Signed-off-by: jared <yu2003w@hotmail.com>
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fejta, yu2003w 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 |
@@ -383,7 +383,11 @@ EOF | |||
echo "COPY nsswitch.conf /etc/" >> "${docker_file_path}" | |||
fi | |||
|
|||
"${DOCKER[@]}" build ${docker_build_opts:+"${docker_build_opts}"} -q -t "${docker_image_tag}" "${docker_build_path}" >/dev/null | |||
if [[ "${arch}" == "linux/s390x" || "${arch}" == "linux/ppc64le" ]]; then | |||
DOCKER_CLI_EXPERIMENTAL=enabled "${DOCKER[@]}" buildx build --platform linux/"${arch}" --load ${docker_build_opts:+"${docker_build_opts}"} -q -t "${docker_image_tag}" "${docker_build_path}" >/dev/null |
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.
why aren't we using buildx on all paltforms?
cc @dims @justaugustus @vinayakankugoyal
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.
it seems #97458 was also only solved for the specific list of platforms in the issue?
Currently if you want a multi-arch image for less platforms, you build for the N platforms (in separate invocations) and assemble your own manifest image. That should work. It makes sense to support building for a subset of platforms into a manifest image directly, but I don't think that should special-case two platforms. |
Signed-off-by: jared yu2003w@hotmail.com
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #97458
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: