Signed Images

A signed build: every command of one Go module built into an image by ko and pushed, every image signed by digest with cosign using a key held in a vault, and every signature verified, in one run that fails unless all three happened for all of them. ko's part is @dataverket/ko-images without its assertion: describe, then one build per command, each recorded with its digest. cosign's part takes those digests from this run's image records, never from an input, so what is signed is exactly what was

Signed manifests: ko resolve renders the manifests in files with every ko:// reference built from the Go module in dir, pushed to repo and pinned by digest; cosign signs every image built in that run by digest with a key held in a vault, attests the rendered manifests onto each of them as a custom predicate, and verifies both the signatures and the attestations; the run fails unless all of it happened for every image built. The images come from this run's resolution record, never from an input,

Verify every image a rendered manifest file names: ko resolve over files, pushing nothing, lists every image pinned by digest in them, and cosign verify checks each one against a public key, with the required annotations when any are given; the run fails unless every image is pinned and every one verifies. Read-only: nothing is pushed anywhere. Made to gate a deploy: run it on the manifests a signed build rendered before anything applies them. ko resolve is the image lister, so dir must be a Go

A signed release: a directory of rendered manifests becomes one OCI artifact in the registry, pushed with flux push artifact, tagged with the commit, signed by digest with cosign using a key held in a vault, with the rendered manifests attested onto it, and both verified; the run fails unless all of it happened. ko resolve over the directory, pushing nothing, lists every image pinned by digest in it as this run's resolution record; release.json is built from that record, environment, revision, s

A base image mirrored by digest after a quarantine, verified keyless upstream and signed with our key: the upstream tag in ref is resolved to its digest on the base-image-watch model, whose digest record carries firstSeenAt forward while the digest stays the same, so the daily @dataverket/base-image-watch and this workflow share one watch; an assertion refuses a digest first seen less than minimumAgeDays ago and says when it may be mirrored; cosign verifies the upstream digest keyless, against t

Verify a signed release before anything moves: the artifact's tag is resolved to its digest with crane, and everything after uses that digest; cosign verifies the artifact's signature and its custom attestation against a public key; release.json is read out of the artifact's layer with crane blob; and every image it lists is verified by repository and digest against the same key. The run fails unless the artifact verified, the attestation verified, the release was read, it lists at least one ima

Promote a verified release by retag: @dataverket/verify-release runs first as a nested workflow, with the artifact's tag resolved to its digest, the artifact's signature and attestation verified against a public key, release.json read out of it and every image it lists verified; then crane tag points the channel tag, such as current, at the digest that was verified, and crane digest reads the channel back; the run fails unless the channel now holds exactly that digest. Nothing is rebuilt, copied

Mirror every image a verified release lists into another registry, with its signatures: @dataverket/verify-release runs first as a nested workflow, with the artifact's tag resolved to its digest, its signature and attestation verified against a public key, release.json read out of it and every image it lists verified; then crane copy copies each image by its digest from release.json to <registry>/<namespace>/<source registry>/<path>:<tag>, the source repository kept whole and the tag the release