Repository navigation
docs(operator-guide): verify release image and chart signatures - #657
Conversation
Document cosign verification of the release image and OCI chart with an anchored certificate identity for release.yml tag builds, the SBOM and provenance attestations, and a Kyverno policy using the same identity. Closes #652 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: MaxRink <maximilian.rink@telekom.de>
Output DeltaNo output differences were detected for this PR.
The compare job downloads artifacts only; it does not checkout or execute pull-request code. |
📊 Output Delta ReportNo output differences were detected for this PR. No full diff content was generated for this run. |
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are reported for the release-signature verification documentation update.
No open issues 🎉
What changed in this PR
Adds release-signature verification guidance to Auth Operator’s installation documentation, addressing #652 so consumers can verify published artifacts before deployment.
Changes:
- Documents image and OCI Helm chart verification using cosign with an anchored release-workflow identity and issuer.
- Adds SBOM and provenance verification commands for images and release manifests.
- Provides a Kyverno admission-policy example and guidance on deploying verified image digests.
| File | Description |
|---|---|
| README.md | Links installation instructions to the new verification guide. |
| docs/operator-guide.md | Adds verification commands, identity constraints, and a Kyverno policy example. |
Review effort: Balanced
Security scan reportCommit: Security findings are advisory, not merge blockers. Build, test and licensing checks remain blocking. A successful job is not proof of a clean scan; findings and scanner errors are called out below.
See the linked logs for complete findings and any scanner setup failures. |
Closes #652
Description
Adds "Verify Release Signatures" to the Installation part of
docs/operator-guide.mdand links it from the README. The commands follow whatrelease.ymlactually publishes:release.ymlcosign sign(keyless) on the manifest digestcosign verifycosign signonghcr.io/telekom/charts/auth-operator:<version>cosign verifycosign attest --type spdxjsoncosign verify-attestationactions/attest-build-provenancegh attestation verify oci://…install.yaml,crds.yamlprovenanceactions/attest-build-provenancegh attestation verify <file>All of these use the same anchored identity:
^https://github\.com/telekom/auth-operator/\.github/workflows/release\.yml@refs/tags/v[0-9]+\.[0-9]+\.[0-9]+(-[0-9A-Za-z.-]+)?$together with the issuer
https://token.actions.githubusercontent.com. The tag part mirrors the SemVer guard inrelease.yml.The release notes already contain exact-identity commands for each tag. This section adds the regexp form for policies, the provenance of the manifests, and a Kyverno example.
Cosign v3 stores the signatures as Sigstore bundles in OCI referrers, so the Kyverno
ClusterPolicyneedstype: SigstoreBundle(Kyverno 1.13+). Without it, Kyverno reports "no signatures found" even for a valid release.Type of Change
Testing
The Bash blocks were extracted from the Markdown and run verbatim with cosign v3.1.4, gh, and
VERSION=0.5.0-rc.26. All commands succeed. The image and chart of0.4.0-rc.17and0.5.0-rc.20also verify.Negative checks:
cosign verifyof the unsigned main buildsha-f343a38fails with "no signatures found".cosign verifyandgh attestation verifyof0.5.0-rc.26fail with an identity anchored torefs/heads/main.gh attestation verifyof a modifiedcrds.yamlfails.Kyverno CLI 1.19.2
applywith the policy from the doc:ghcr.io/telekom/auth-operator-foois not matched.refs/heads/mainfails for the release.PSA PSM-12.17
🤖 Generated with Claude Code