Closed bspaans closed 5 months ago
Thanks @bspaans. I saw that you are willing to submit PRs to contribute to this issue. Would you mind sharing any ETA on this so that we can plan it?
Hi @yizha1, sure, I think I can find some time this week.
Thanks @bspaans for the contribution. I will assign this issue to you.
Hello. Has there been any progress on this?
I'm wondering if you're still on this issue. Please let us know if you're not, so we can reassign it to someone else.
@zachbugay may I know which Cosign scenario you are interested in? Currently Ratify doesn't support public key stored in AKV yet, which is planned for upcoming release v1.2.0
What would you like to be added?
The documentation for "Ratify on AWS" mentions a few steps to get cosign signatures working with Ratify, but this isn't mentioned on the "Ratify on Azure" page. This was a bit of a head-scratcher, because cosign can also use Azure Key Vault (AKV), but creates a Key, instead of a Cert, so ultimately doesn't work with Ratify.
Steps to get Cosign working on Azure:
cosign.key
on the Helm chartAnything else you would like to add?
No response
Are you willing to submit PRs to contribute to this feature?