ci: first cut on signing images with Cosign#4483
Merged
erikgb merged 1 commit intoweaveworks:mainfrom Jan 10, 2025
Merged
Conversation
casibbald
approved these changes
Jan 10, 2025
This was referenced Jan 10, 2025
This was referenced Jan 15, 2025
This was referenced Jan 26, 2025
This was referenced Feb 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes
What changed?
Adds keyless signing (and verification) of images to the PR workflow. We obviously want to sign our release images, but let's start somewhere. The work here is based on this blog post. This might need a couple of iterations, but we have to start somewhere. The blog states that the file workflow file must be named
*keyless.yaml. Let's find out. 😉Why was this change made?
Supply chain attacks are a serious challenge for the software industry, and image signing can help.
How was this change implemented?
How did you validate the change?
Release notes
Documentation Changes