-
Notifications
You must be signed in to change notification settings - Fork 93
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
added cosign and provenance generation #425
Conversation
@sabre1041 ; interested if you've got any feedback on this. i looked at the helm plugin but that didn't seem super active and also required generating pgp keys, which I don't want to have to do as part of this pipeline. |
@ckavili ; happy to have a chat to explain this, if its not clear |
I think we are good! I used |
@garethahealy the goal of the plugin was to provide a bridge for transparency with the existing signing methods of Helm so it could take advantage of Rekor as well as not be tied to OCI to store charts. If neither are necessary, simple sigstore/cosign signing is all you need |
LGTM .. lets try this out @garethahealy ! |
@garethahealy .. think this can be ignored .. https://github.com/redhat-cop/helm-charts/actions/runs/7481237987/job/20362415933 let me merge a renovate one .. see what happens ... |
looks good -- this merge -- provenance generator -- sigstore entry |
ohh very nice! 😍 |
🥳🎉👯♀️ |
Added the ability to generate provenance of how the packaged chart was created by using the GitHub SLSA generator and added the ability to sign the tgz.
tested via this pipeline:
the end result:
if a consumer of the chart, wants to make sure the tgz they've got is the same as the one packaged via the pipeline, they can:
cc: @redhat-cop/day-in-the-life