Skip to content

Verification of Argo Rollouts Artifacts


Release Assets

Asset Description
argo-rollouts-checksums.txt Checksums of binaries
argo-rollouts-cli.intoto.jsonl Attestation of CLI binaries & manifiest
dashboard-install.yaml Dashboard install
install.yaml Standard installation method
kubectl-argo-rollouts-darwin-amd64 CLI Binary
kubectl-argo-rollouts-darwin-arm64 CLI Binary
kubectl-argo-rollouts-linux-amd64 CLI Binary
kubectl-argo-rollouts-linux-arm64 CLI Binary
kubectl-argo-rollouts-windows-amd64 CLI Binary
namespace-install.yaml Namespace installation
notifications-install.yaml Notification installation
rollout_cr_schema.json Schema
sbom.tar.gz Sbom
sbom.tar.gz.pem Certificate used to sign sbom
sbom.tar.gz.sig Signature of sbom

Verification of container images

Argo Rollouts container images are signed by cosign using identity-based ("keyless") signing and transparency. Executing the following command can be used to verify the signature of a container image:

cosign verify \
--certificate-identity-regexp \
--certificate-oidc-issuer \ | jq
The command should output the following if the container image was correctly verified:
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": ""
      "image": {
        "docker-manifest-digest": "sha256:519522f8c66c7b4c468f360ebe6c8ba07b8d64f5f948e71ae52c01b9953e1eb9"
      "type": "cosign container image signature"
    "optional": {
      "": "",
      "": "push",
      "": "aa1afcb418fcebcc68b063377c48225f5a9d1511",
      "": "Release",
      "": "argoproj/argo-rollouts",
      "": "refs/tags/v1.5.0",

Verification of container image attestations

A SLSA Level 3 provenance is generated using slsa-github-generator.

The following command will verify the signature of an attestation and how it was issued. It will contain the payloadType, payload, and signature.

cosign verify-attestation --type slsaprovenance \
--certificate-identity-regexp \
--certificate-oidc-issuer \ | jq
The payload is a non-falsifiable provenance which is base64 encoded and can be viewed by using the command below:
cosign verify-attestation --type slsaprovenance \
--certificate-identity-regexp \
--certificate-oidc-issuer \ | jq -r .payload | base64 -d | jq


cosign or slsa-verifier can both be used to verify image attestations. Check the documentation of each binary for detailed instructions.

Verification of CLI artifacts with attestations

A single attestation (argo-rollouts.intoto.jsonl) from each release is provided. This can be used with slsa-verifier to verify that a CLI binary or manifest was generated using Argo Rollouts workflows on GitHub and ensures it was cryptographically signed.

slsa-verifier verify-artifact kubectl-argo-rollouts-linux-amd64 --provenance-path kubectl-argo-rollouts.intoto.jsonl  --source-uri

Verifying an artifact and output the provenance

slsa-verifier verify-artifact kubectl-argo-rollouts-linux-amd64 --provenance-path kubectl-argo-rollouts.intoto.jsonl  --source-uri --print-provenance | jq

Verification of Sbom

cosign verify-blob --signature sbom.tar.gz.sig --certificate sbom.tar.gz.pem \
--certificate-identity-regexp ^ \
--certificate-oidc-issuer  \
 ~/Downloads/sbom.tar.gz | jq

Verification on Kubernetes

Policy controllers


We encourage all users to verify signatures and provenances with your admission/policy controller of choice. Doing so will verify that an image was built by us before it's deployed on your Kubernetes cluster.

Cosign signatures and SLSA provenances are compatible with several types of admission controllers. Please see the cosign documentation and slsa-github-generator for supported controllers.