-
Notifications
You must be signed in to change notification settings - Fork 99
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 Salsa framework during release to increase the supply-chain security #966
Conversation
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
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.
@jkremser looks awesome!
I suggest reflecting these changes in the dev documentation, also wrt the case when cosign key pair should be regenerated.
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.
@jkremser it looks really really good. Is it possible to have brief contextual documentation for the implementation? Fine to have it as a separate PR.
Signed-off-by: Jirka Kremser <jiri.kremser@gmail.com>
Signed-off-by: Jirka Kremser <jiri.kremser@gmail.com>
✅ Deploy Preview for k8gb-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Signed-off-by: Jirka Kremser <jiri.kremser@gmail.com>
@somaritane I've added the docs, can you "ptal" again? |
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.
@jkremser lgtm now, thank you!
This is how it looks like on my other repo - https://github.com/jkremser/log2rbac-operator/actions/runs/3234735006#summary-8846153907
it relies on 3 new repo secrets:
COSIGN_PRIVATE_KEY
,COSIGN_PUBLIC_KEY
andCOSIGN_PASSWORD
COSIGN_PASSWORD
is a passphrase for the private key. The private key is used for signing the artifacts (container images, provenance files, sboms, checksums). The public key is also part of the repo and is used for verifying the signatures.During the release we push the signatures of container images into container registries so that one can verify the validity of the image. Also some artifacts are published together with the release, check the Assets section on log2rbac release page.
inspired / kudos to https://github.com/philips-labs/slsa-provenance-action/blob/main/.github/workflows/ci.yaml
Signed-off-by: Jirka Kremser jiri.kremser@gmail.com