-
Notifications
You must be signed in to change notification settings - Fork 502
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
Release Process: Write SLSA v0.2 provenance attestations #2375
Conversation
Signed-off-by: Adolfo García Veytia <[email protected]>
Migrate provenance predicate fields to SLSA v0.2 equivalents. Also, reference the DigestSets from the new versioned SLSA package. Signed-off-by: Adolfo García Veytia <[email protected]>
This commit removes the temporary logic to lookup the last commit SHA in favor of the function in the release-sdk `git` package. Signed-off-by: Adolfo García Veytia <[email protected]>
Signed-off-by: Adolfo García Veytia <[email protected]>
This commit addresses nits noted in kubernetes#2273. Signed-off-by: Adolfo García Veytia <[email protected]>
krel arguments recorded in the provenance attestation were recorded with dashes and equal signs: ``` "arguments": { "--branch=": "master", ``` This commit fixes them to record just the name of the parameter. Signed-off-by: Adolfo García Veytia <[email protected]>
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, puerco 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 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR modifies the Kubernetes release process to write its provenance attestations using the latest SLSA 0.2 spec. Except for newer fields in the attestation predicate, content is mostly the same, it just has been migrated from 0.1 to the equivalent 0.2 fields.
This PR also addresses the comments noted in #2273 (/cc @justaugustus )
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
/cc @kubernetes/release-engineering @justaugustus @cpanato
Test runs of the new code:
Stage:
https://console.cloud.google.com/cloud-build/builds;region=global/f464f9a1-dac8-4090-8a00-bd5ae56e72c5?project=kubernetes-release-test
Release:
https://console.cloud.google.com/cloud-build/builds;region=global/bfc36ac7-c558-4f84-95ae-76ca1de6f546?project=kubernetes-release-test
Does this PR introduce a user-facing change?