Batuhan Apaydın
Batuhan Apaydın
Hello @colek42 I can take care of this someone if no one is already working on 😊
I will look at it; this is quite an interesting issue.
Hello @lukehinds, as I mentioned above, recently, we've added other key supports for verification by using cosign to Kyverno. As you already know, KMS is one of them, so, I...
I found this but am not sure whether it refers to our problem but this [--k8s-keychain flag](https://github.com/sigstore/cosign/blob/90e2dcfe7b92223221a44b2fc16ade64de09f2c9/cmd/cosign/cli/options/registry.go?_pjax=%23js-repo-pjax-container%2C%20div%5Bitemtype%3D%22http%3A%2F%2Fschema.org%2FSoftwareSourceCode%22%5D%20main%2C%20%5Bdata-pjax-container%5D#L46-L47) seems to help us because I found these two blog posts and all...
nope, but I'll give a hand one more time, this feature really excites me 🙈
seems everything fine but I couldn't make it work 🤦🏻♂️
I'm asking for making it clear, do you want me to try the demo on more time with kyverno 1.6.0-rc3 ? Do I need to do anything other than that...
Hello @ribbybibby, here is the result of verifying my container image stored in public GCP registry against a key stored in GCP KMS: Cosign Verify result ```shell cosign verify -key...
Yep, I noticed that to so, I've updated it as "kyverno", it didn't work also 🥲
kindly ping @ribbybibby 🙋🏻♂️ would you mind sharing your commands with me? Then I'll be able to execute them to test Kyveno v1.6.0 with workload identity feature to verify container...