-
Notifications
You must be signed in to change notification settings - Fork 163
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
Add cosign PKCS11 Support #1229
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure on what the specifics would be, but it would be awesome if the cosign that kpack uses was the version that includes the ability to use a PKCS11 provider, in which the private key for signing is obtained from a local PKCS11 key provider service. We could maybe mount the .so file as a volume to kpack somehow, and then it would reach out to a service/pod running in the cluster.
The text was updated successfully, but these errors were encountered: