Skip to content

Conversation

@tarilabs
Copy link
Member

Description

followup to

Standardize GitHub Actions workflows to use docker/build-push-action for multi-arch builds with metadata, anchore/sbom-action for SPDX SBOM generation, and cosign attestation for signed SBOMs.

Minor note: called KEP 2 since we currently we have KEP 1 under review here.

How Has This Been Tested?

see KEP markdown for details.

we will need to observe the GHA workflow aligned once merged, possibly after a release so to not jeopardize a release's process.

Merge criteria:

  • All the commits have been signed-off (To pass the DCO check)
  • The commits have meaningful messages
  • Automated tests are provided as part of the PR for major new functionalities; testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • [partially] The developer has manually tested the changes and verified that the changes work.
  • Code changes follow the kubeflow contribution guidelines.
  • For first time contributors: Please reach out to the Reviewers to ensure all tests are being run, ensuring the label ok-to-test has been added to the PR.

If you have UI changes

  • The developer has added tests or explained why testing cannot be added.
  • Included any necessary screenshots or gifs if it was a UI change.
  • Verify that UI/UX changes conform the UX guidelines for Kubeflow.

tarilabs and others added 2 commits December 18, 2025 18:42
… workflows

Align all GitHub Actions workflows for container image builds with:
- Multi-arch support (linux/arm64, linux/amd64) via QEMU
- Standardized metadata generation using docker/metadata-action
- Image signing with cosign using digest references
- SBOM generation using anchore/sbom-action (SPDX format)
- SBOM attestation using cosign attest (replacing cosign attach)
- Consistent permissions (id-token, actions, contents)

This ensures all container images are signed and have SBOMs attested
in a cosign-compatible format, improving supply chain security.

Co-Authored-By: Claude <[email protected]>
Signed-off-by: Matteo Mortari <[email protected]>
@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from tarilabs. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Signed-off-by: Matteo Mortari <[email protected]>
Copy link
Member

@ederign ederign left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tarilabs this lgtm, just a minor nitpick. Shall we merge it? Or should we wait for others chime in?

@tarilabs
Copy link
Member Author

tarilabs commented Jan 5, 2026

it was in the Dec 22 meeting, and in the agenda's for today's meeting.

To me we can merge it next week as we're planning to cut a release this week.

@ederign
Copy link
Member

ederign commented Jan 5, 2026

@tarilabs lgtm then, feel free to merge when it's suitable for the release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Adds multi-architecture (arm64/amd64) support for the Model Registry UI Docker images.

2 participants