STAC-22594 Documented how to verify signature of docker images - #404
Merged
Merged
Conversation
✅ Deploy Preview for suse-obs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
viliakov
reviewed
Aug 26, 2026
viliakov
reviewed
Aug 26, 2026
viliakov
reviewed
Aug 26, 2026
viliakov
reviewed
Aug 27, 2026
viliakov
reviewed
Aug 27, 2026
|
|
||
| Signing is keyless: there is no public key file to download or manage. Instead, each signature is backed by a short-lived certificate tied to the GitHub Actions job that produced it, and a public, tamper-evident record of the signing event. | ||
|
|
||
| Image signing was added to our build pipeline recently. Images published before this was rolled out do not carry a signature — verifying one of those tags fails with `no signatures found`, which does not indicate a problem with the image itself. If you rely on signature verification, pull a current tag. |
Contributor
There was a problem hiding this comment.
Suggested change
| Image signing was added to our build pipeline recently. Images published before this was rolled out do not carry a signature — verifying one of those tags fails with `no signatures found`, which does not indicate a problem with the image itself. If you rely on signature verification, pull a current tag. | |
| Image signing was introduced for platform images in release vX.Y.Z and for agent images in release vA.B.C.. Images published before this was rolled out do not carry a signature — verifying one of those tags fails with `no signatures found`, which does not indicate a problem with the image itself. If you rely on signature verification, pull a current tag. |
|
|
||
| == Overview | ||
|
|
||
| {stackstate-product-name} container images are cryptographically signed during the build pipeline using https://www.sigstore.dev/[Sigstore] keyless signing (`cosign`). Verifying a signature confirms that an image was genuinely built by our CI from a specific source repository, workflow, and branch or tag — before you pull it into a cluster. |
Contributor
There was a problem hiding this comment.
Suggested change
| {stackstate-product-name} container images are cryptographically signed during the build pipeline using https://www.sigstore.dev/[Sigstore] keyless signing (`cosign`). Verifying a signature confirms that an image was genuinely built by our CI from a specific source repository, workflow, and branch or tag — before you pull it into a cluster. | |
| {stackstate-product-name} container images are cryptographically signed during the build pipeline using link:https://www.sigstore.dev/[Sigstore] keyless signing (`cosign`). Verifying a signature confirms that an image was genuinely built by our CI from a specific source repository, workflow, and branch or tag — before you pull it into a cluster. |
akashraj4261
approved these changes
Sep 7, 2026
akashraj4261
approved these changes
Sep 15, 2026
…tures.adoc Co-authored-by: Vladimir Iliakov <vladimir.iliakov@suse.com>
Co-authored-by: Vladimir Iliakov <vladimir.iliakov@suse.com>
Co-authored-by: Akash Raj <akash.raj@suse.com>
LukaszMarchewka
force-pushed
the
STAC-25594-doc-how-to-verify-signature
branch
from
September 16, 2026 08:09
85ee972 to
73593d5
Compare
Collaborator
$ cosign verify \
--certificate-oidc-issuer=https://token.actions.githubusercontent.com \
--certificate-identity-regexp='^https://github.com/StackVista/.*' \
registry.rancher.com/suse-observability/stackstate-ui:2.11.1
Verification for registry.rancher.com/suse-observability/stackstate-ui:2.11.1 --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
[{"critical":{"identity":{"docker-reference":"registry.rancher.com/suse-observability/stackstate-ui:2.11.1"},"image":{"docker-manifest-digest":"sha256:6eb468d98c7d995aba410267e6da1d91a24b4ec0f2c8f57ba2b60cf536c8ce0f"},"type":"https://sigstore.dev/cosign/sign/v1"},"optional":{}}]
$ cosign verify \
--certificate-oidc-issuer=https://token.actions.githubusercontent.com \
--certificate-identity-regexp='^https://github.com/StackVista/.*' \
registry.rancher.com/suse-observability/stackstate-k8s-agent:158e1098
Verification for registry.rancher.com/suse-observability/stackstate-k8s-agent:158e1098 --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
[{"critical":{"identity":{"docker-reference":"registry.rancher.com/suse-observability/stackstate-k8s-agent:158e1098"},"image":{"docker-manifest-digest":"sha256:35e66696a1bdc0d470e0d11d7711e426548a09d31190bdd94cd1350b464dc839"},"type":"https://sigstore.dev/cosign/sign/v1"},"optional":{}}] |
l4zy0n3
approved these changes
Sep 16, 2026
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
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.
No description provided.