liveBook · Manning

Artifact identity

As explained in Kargo in Action

Artifact identity is the information that uniquely specifies a deployable artifact version, including identifiers such as a digest and provenance data.

Artifact identity pins the exact versions moving through a delivery pipeline. A tag helps people recognize an artifact, but can be reassigned; its digest, and a Git commit’s SHA, identify specific content. In Kargo, a Freight records that identity for an immutable bundle of artifacts. section 1.3.3 section 3.2.2

A Freight makes artifact identity operational:

  • A Warehouse creates Freight when it discovers new artifact versions; people do not author Freight by hand. section 3.2.2
  • Its origin identifies the Warehouse, while its tag is for readability and its digest is the image identity. section 3.2.2
  • A Freight can bundle an image, chart, and Git version so a Stage advances a coherent set together. section 3.2.2

When a tag changes

Suppose tag 1.2.0 is reassigned to a different image after a Freight is created. The Freight still points to the original digest, so a promoted version remains unambiguous. That stable reference helps prevent production from silently diverging from what was tested in pre-production. section 3.2.2 section 1.3.3

Listing 3.2 A Freight object as Kargo creates it (illustrative, not for authoring)
apiVersion: kargo.akuity.io/v1alpha1
kind: Freight
metadata:
  name: 7b2f9a8e3c1d5f4a6b8e9c0d2f1a5b7c    # #1
  namespace: demo
spec:
  origin:
    kind: Warehouse
    name: demo-app                           # #2
  images:
  - repoURL: ghcr.io/kargobook/demo-app
    tag: 1.2.0                               # #3
    digest: sha256:a3b9e7f2c1d4f8a2b6c4e1d7   # #4

Use the illustrative Freight object to locate its origin, human-readable tag, and digest; it shows a controller-created resource, not a manifest to author. section 3.2.2

How Kargo in Action covers it

How deep it goes
Defines tag-versus-digest identity and explains immutable, multi-artifact Freight bundles, without detailing digest internals.
Examples
Uses a repushed image tag and an image-chart-Git bundle to illustrate stable identity and coordinated advancement.
What you can do after
Evaluate whether a promoted version refers to specific artifact content rather than a mutable tag.
How it connects
Connects Kargo Freight and Warehouse resources with promotion, GitOps, CI/CD, and delivery lineage.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kargo in Action. The section links point to the parts of the book it draws on.