Verify Signed Kubernetes Artifacts

FEATURE STATE: Kubernetes v1.26 [beta]

Before you begin

These instructions are for Kubernetes 1.26. If you want to check the integrity of components for a different version of Kubernetes, check the documentation for that Kubernetes release.

You will need to have the following tools installed:

  • cosign (install guide)
  • curl (often provided by your operating system)

Verifying binary signatures

The Kubernetes release process signs all binary artifacts (tarballs, SPDX files, standalone binaries) by using cosign's keyless signing. To verify a particular binary, retrieve it together with its signature and certificate:



for FILE in "${FILES[@]}"; do
    curl -sSfL --retry 3 --retry-delay 3 "$URL/$FILE" -o "$FILE"

Then verify the blob by using cosign:

cosign verify-blob "$BINARY" --signature "$BINARY".sig --certificate "$BINARY".cert

Verifying image signatures

For a complete list of images that are signed please refer to Releases.

Let's pick one image from this list and verify its signature using the cosign verify command:


Verifying images for all control plane components

To verify all signed control plane images, please run this command:

curl -Ls$(curl -Ls | grep 'PackageName:' | awk '{print $2}' > images.txt
while IFS= read -r image
  COSIGN_EXPERIMENTAL=1 cosign verify "$image"
done < "$input"

Once you have verified an image, specify that image by its digest in your Pod manifests as per this example: registry-url/image-name@sha256:45b23dee08af5e43a7fea6c4cf9c25ccf269ee113168c19722f87876677c5cb2 .

For more information, please refer to Image Pull Policy section.

Verifying Image Signatures with Admission Controller

For non-control plane images ( e.g. conformance image) , signatures can also be verified at deploy time using sigstore policy-controller admission controller. To get started with policy-controller here are a few helpful resources:

Last modified November 11, 2022 at 9:22 AM PST: Add documentation about signed Kubernetes artifacts (f8a2d2319a)