You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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: