It’s Complicated: Relationships Between Objects In OCI Registries
summary
Working group defines an artifact manifest with subject field to link non-image blobs to an image and adds a reference API (referrers) that returns an image index of manifests referencing a digest, supports filtering by artifactType and pagination via Link headers. Demos use oras and regctl; fallback uses a client-created digest tag that stores an image index so non-supporting registries can participate today. Change is merged into the OCI specs; registries and conformance tests still need implementation.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:57The Problem Statement
- 3:151 Problem, 2 Parts
- 8:07People start to do things anyway
- 10:05Forming a working group
- 12:30The Proposal Process
- 13:48The Submitted Proposals
- 15:39The Voting Process
- 16:20Landing Proposal E
- 18:31Image Spec
- 23:03Distribution Spec
related talks
44mModifying the Immutable: Attaching Artifacts to OCI Images
36mModifying the Immutable: Attaching Artifacts to OCI Images
40mDistributing Supply Chain Artifacts with OCI & ORAS Artifacts
05mORAS: Create and Distribute a Multi-platform Image with Secu...
36mContainer Images & Security 101: 5 Need to Know Facts
29mBuilding Signing, Distributing SPDX SBOMs as Artifact Reference Type
23mPanel: Expanding Argo CD Content Management Using OCI Artifacts
10mLightning Talk: OCI Images for More Than Containers, Jon Johnson, Google
