Provenance Information for calico-calicoctl Images

Provenance information for calico-calicoctl Chainguard Image

All Chainguard Images contain verifiable signatures and high-quality SBOMs (software bill of materials), features that enable users to confirm the origin of each image build and have a detailed list of everything that is packed within.

You’ll need cosign and jq in order to download and verify image attestations.

Registry and Tags for calico-calicoctl Image

Attestations are provided per image build, so you’ll need to specify the correct tag and registry when pulling attestations from an image with cosign.

RegistryTags
cgr.dev/chainguardNo public tags are available for this image.
cgr.dev/chainguard-private3, 3-dev, 3.26, 3.26-dev, 3.26.3, 3.26.3-dev, 3.26.4, 3.26.4-dev, 3.27, 3.27-dev, 3.27.0, 3.27.0-dev, 3.27.2, 3.27.2-dev, 3.27.3, 3.27.3-dev, 3.28, 3.28-dev, 3.28.0, 3.28.0-dev, latest, latest-dev, v3, v3-dev, v3.26, v3.26-dev, v3.26.3, v3.26.3-dev, v3.26.4, v3.26.4-dev, v3.27, v3.27-dev, v3.27.0, v3.27.0-dev, v3.27.2, v3.27.2-dev, v3.27.3, v3.27.3-dev, v3.28, v3.28-dev, v3.28.0, v3.28.0-dev
  • cgr.dev/chainguard - the Public Registry contains our Developer Images, which typically comprise the latest* versions of an image.
  • cgr.dev/chainguard-private - the Private/Dedicated Registry contains our Production Images, which include all versioned tags of an image and special images that are not available in the public registry (including FIPS images and other custom builds).

The commands listed on this page will default to the latest tag, but you can specify a different tag to fetch attestations for.

Verifying calico-calicoctl Image Signatures

The calico-calicoctl Chainguard Images are signed using Sigstore, and you can check the included signatures using cosign.

The cosign verify command will pull detailed information about all signatures found for the provided image.

Public Registry

cosign verify \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  --certificate-identity=https://github.com/chainguard-images/images/.github/workflows/release.yaml@refs/heads/main \
  cgr.dev/chainguard/calico-calicoctl | jq

Private/Dedicated Registry

cosign verify \
--certificate-oidc-issuer=https://token.actions.githubusercontent.com \
--certificate-identity=https://github.com/chainguard-images/images-private/.github/workflows/release.yaml@refs/heads/main \
cgr.dev/chainguard-private/calico-calicoctl | jq

Downloading calico-calicoctl Image Attestations

The following attestations for the calico-calicoctl image can be obtained and verified via cosign:

Attestation TypeDescription
https://slsa.dev/provenance/v1The SLSA 1.0 provenance attestation contains information about the image build environment.
https://apko.dev/image-configurationContains the configuration used by that particular image build, including direct dependencies, user accounts, and entry point.
https://spdx.dev/DocumentContains the image SBOM (Software Bill of Materials) in SPDX format.

To download an attestation, use the cosign download attestation command and provide both the predicate type and the build platform. For example, the following command will obtain the SBOM for the calico-calicoctl image on linux/amd64:

Public Registry

cosign download attestation \
  --platform=linux/amd64 \
  --predicate-type=https://spdx.dev/Document \
  cgr.dev/chainguard/calico-calicoctl | jq -r .payload | base64 -d | jq .predicate

Private/Dedicated Registry

cosign download attestation \
--platform=linux/amd64 \
--predicate-type=https://spdx.dev/Document \
cgr.dev/chainguard-private/calico-calicoctl | jq -r .payload | base64 -d | jq .predicate

By default, this command will fetch the SBOM assigned to the latest tag. You can also specify the tag you want to fetch the attestation from.

To download a different attestation, replace the --predicate-type parameter value with the desired attestation URL identifier.

Verifying calico-calicoctl Image Attestations

You can use the cosign verify-attestation command to check the signatures of the calico-calicoctl image attestations:

Public Registry

cosign verify-attestation \
  --type https://spdx.dev/Document \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  --certificate-identity=https://github.com/chainguard-images/images/.github/workflows/release.yaml@refs/heads/main \
  cgr.dev/chainguard/calico-calicoctl

Private/Dedicated Registry

cosign verify-attestation \
--type https://spdx.dev/Document \
--certificate-oidc-issuer=https://token.actions.githubusercontent.com \
--certificate-identity=https://github.com/chainguard-images/images-private/.github/workflows/release.yaml@refs/heads/main \
cgr.dev/chainguard-private/calico-calicoctl

This will pull in the signature for the attestation specified by the --type parameter, which in this case is the SPDX attestation. You will receive output that verifies the SBOM attestation signature in cosign’s transparency log:

Verification for cgr.dev/chainguard/calico-calicoctl --
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
Certificate subject:  https://github.com/chainguard-images/images/.github/workflows/release.yaml@refs/heads/main
Certificate issuer URL:  https://token.actions.githubusercontent.com
GitHub Workflow Trigger: schedule
GitHub Workflow SHA: da283c26829d46c2d2883de5ff98bee672428696
GitHub Workflow Name: .github/workflows/release.yaml
GitHub Workflow Trigger chainguard-images/images
GitHub Workflow Ref: refs/heads/main
...

Last updated: 2024-05-14 00:46