Support for Cosign verification with keys managed in KMS

[yizha1]

What would you like to be added?

Currently users can only configure Cosign verification with a public key from a file path. In enterprise context, normally users create and manage key in a Key Management System (KMS). Cosign supports different KMS provider, for example AKV as a provider, and verification with a KMS.

This issue asks for support Cosign verification with keys that are managed in KMS, like AKV. Users can easily configure KMS name/address, authentication and keys used for verification without the need to download the key to a file first and then configure a file path.

Anything else you would like to add?

No response

Are you willing to submit PRs to contribute to this feature?

• Yes, I am willing to implement it.