[Feature] Support TUF configuration for private and public Sigstore instances simultaneously #11618
Open
2 tasks done
Labels
enhancement
New feature or request
imageVerify
Image verification support
triage
Default label assigned to all new issues indicating label curation is needed to fully organize.
Milestone
Problem Statement
When kyverno is configured to verify attestations produced from a private GitHub repositories (see this issue), it's not possible to have a ClusterPolicy that verifies images signed using keyless signing from a GitHub Action at the same time.
Solution Description
It would be good to have a way to configure kyverno to allow to override the TUF configuration to the GitHub private Sigstore instance for verification of attestations of artifacts from private repos but that would fallback to the public Sigstore instance when it's verifying image signature. Alternatively, a list of TUF overrides would work.
Alternatives
No response
Additional Context
Kyverno has a values.yaml override like the following :
so I can have a ClusterPolicy that verifies attestations produced by GitHub's private Sigstore instance (see this issue).
Say I also want the ClusterPolicy to verify image signatures that were signed using keyless signing from a GitHub Action by adding this to verifyImages:
When I helm install a chart that uses an image signed the GitHub keyless way way, I see this in logs:
This is because, in the case of keyless image signature verification, the public Sigstore instance is used. How do I configure kyverno so it accepts both the GitHub private Signstore instance (for attestations) as well as the official public one (for image signatures)?
Slack discussion
https://kubernetes.slack.com/archives/CLGR9BJU9/p1720769654925739
Research
The text was updated successfully, but these errors were encountered: