fix: ensure consistent Docker image manifest format across releases#22172
fix: ensure consistent Docker image manifest format across releases#22172kairosci wants to merge 1 commit into
Conversation
|
Hi @kairosci. Thanks for your PR. I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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-sigs/prow repository. |
814a476 to
d900152
Compare
kubernetes-prow
Bot
added
github_actions
|
/assign @ahrtr |
d900152 to
f58b0c6
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: kairosci The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
…releases Disable SBOM and provenance in buildx, add manifest type verification, and add GitHub Actions workflow to build images deterministically in CI instead of locally on release persons' machines. Signed-off-by: Alessio Attilio <attilio.alessio@protonmail.com>
f58b0c6 to
30f3470
Compare
2 participants
Move Docker image builds from local release scripts to a GitHub Actions workflow so every release uses the same Docker/buildx version, eliminating the mediaType inconsistency across different release persons' machines. The workflow triggers on release published, downloads release binaries, builds multi-arch images with buildx (--sbom=false --provenance=false), verifies the manifest is a multi-platform list/index, and tests the images before pushing to gcr.io and quay.io.
Fixes #21007