feat(verify): ✨ add custom Sigstore trusted root support#2003
Merged
stefanprodan merged 1 commit intoJun 3, 2026
Conversation
matheuscscp
reviewed
Mar 11, 2026
matheuscscp
reviewed
Mar 11, 2026
matheuscscp
reviewed
Mar 11, 2026
pmialon
force-pushed
the
feat/custom-sigstore-trusted-root
branch
2 times, most recently
from
f19c2e3 to
7ea3f5a
Compare
matheuscscp
reviewed
Mar 11, 2026
stefanprodan
added
area/security
pmialon
force-pushed
the
feat/custom-sigstore-trusted-root
branch
from
7ea3f5a to
cd768e2
Compare
Member
|
@pmialon please run |
pmialon
force-pushed
the
feat/custom-sigstore-trusted-root
branch
from
9991fba to
1ed98da
Compare
Member
|
@pmialon please undo the merge. We only accept rebase, so sync your fork with upstream main and rebase your branch. This PR should have a single commit. |
This comment was marked as duplicate.
This comment was marked as duplicate.
pmialon
force-pushed
the
feat/custom-sigstore-trusted-root
branch
from
1ed98da to
a457789
Compare
Author
@stefanprodan done, sorry for the delay. |
pmialon
force-pushed
the
feat/custom-sigstore-trusted-root
branch
from
a457789 to
1ee7959
Compare
Member
Enable signature verification of OCI artifacts against self-hosted Sigstore infrastructure (custom Fulcio CA, self-hosted Rekor instance) by introducing a trustedRootSecretRef field on the verify spec. When set, the controller reads a trusted_root.json from the referenced Secret, extracts the Rekor URL from the transparency log entries, and creates a verifier using the custom trusted material instead of the public Sigstore TUF root. Signed-off-by: Pierre-Gilles Mialon <pierre-gilles.mialon@qube-rt.com>
pmialon
force-pushed
the
feat/custom-sigstore-trusted-root
branch
from
1ee7959 to
bfad0e6
Compare
Member
|
@stefanprodan There's a bug in this PR, HelmChart shares the type with OCIRepository, see the HelmChart CRD YAML changing while no docs or controller code are added (field is ignored). Going to fix this by splitting the type. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enable signature verification of OCI artifacts and Helm charts against self-hosted Sigstore infrastructure (custom Fulcio CA, self-hosted Rekor instance) by introducing a trustedRootSecretRef field on the verify spec.
When set, the controller reads a trusted_root.json from the referenced Secret, extracts the Rekor URL from the transparency log entries, and creates a verifier using the custom trusted material instead of the public Sigstore TUF root.
Changes:
Closes: #1103