Inso CLI Docker container images are signed using cosign
with signatures published to a Docker Hub repository.
This guide provides steps to verify signatures for signed Inso CLI Docker container images in two different ways:
- A minimal example, used to verify an image without leveraging any annotations
- A complete example, leveraging optional annotations for increased trust
For the minimal example, you only need Docker image details, a GitHub repo name, and a GitHub workflow filename.
For the complete example, you need the same details as the minimal example, as well as any of the optional annotations you want to verify:
Shorthand |
Description |
Example Value |
---|---|---|
REPO
|
GitHub repository |
insomnia
|
WORKFLOW_FILENAME
|
GitHub workflow filename |
release-publish.yml
|
WORKFLOW_NAME
|
GitHub workflow name |
Release Publish
|
TAG
|
Docker image tag |
11.3.0
|
Because Kong uses GitHub Actions to build and release, Kong also uses GitHub’s OIDC identity to sign images, which is why many of these details are GitHub-related.