Transport on Open Component Model

Configure Registry Credentials

Mon, 01 Jan 0001 00:00:00 +0000

Goal

Configure OCM to authenticate against multiple OCI registries — pinning explicit credentials for specific registries while using Docker config as a catch-all fallback.

Transfer Component Versions

Mon, 01 Jan 0001 00:00:00 +0000

Goal

Move a component version from a source OCM repository to a target OCM repository with the default ocm transfer cv workflow. This is the base procedure that every other transfer guide builds on.

Transfer Components across an Air Gap

Mon, 01 Jan 0001 00:00:00 +0000

Start from the base transfer guide

This guide builds on Transfer Component Versions. Read it first for the default ocm transfer cv workflow, credentials, and verification; the steps below only add the air-gap transport via a CTF archive.

Replicate Component Versions with the Controller

Mon, 01 Jan 0001 00:00:00 +0000

Goal

Use the OCM Kubernetes controller to transfer a component version, together with the full graph of components it references (if recursion is enabled), from one OCM repository to another. The transfer re-runs automatically whenever the source Component resolves to a new version.

Download Resources

Mon, 01 Jan 0001 00:00:00 +0000

Goal

Download resources from a component version using the OCM CLI. Learn how to fetch specific resources, optionally transform them to their native format, and save them to your local filesystem.

Download SBOMs

Mon, 01 Jan 0001 00:00:00 +0000

Complete the pack guide first

This guide continues from Add SBOMs. It assumes the /tmp/ocm-sbom-tutorial workspace and the ./transport-archive CTF from that guide already exist, with a linked SBOM on the ocm-cli resource and the podinfo image carrying a BuildKit attestation. Complete it before running the steps below.

Pull OCI Artifacts Natively

Mon, 01 Jan 0001 00:00:00 +0000

Complete the pack guide first

This guide continues from Add OCI Artifacts. It assumes you already built the component versions from that guide — an embedded OCI image layout, an externally referenced image, and an ORAS-fetched layout — each sitting in a local ./transport-archive CTF. Complete it before running the steps below.

Configure HTTP Behaviour

Mon, 01 Jan 0001 00:00:00 +0000

Control the HTTP behaviour OCM uses when talking to OCI registries and Helm repositories — globally and per-host — so that slow, flaky, or restricted networks do not cause silent hangs, premature failures, or surprise certificate errors.

Upload OCI Images

Mon, 01 Jan 0001 00:00:00 +0000

Start from the base transfer guide

This guide builds on Transfer Component Versions. Read it first for the default ocm transfer cv workflow, credentials, and verification; the steps below only add the OCI uploader configuration.

Upload to a Custom Target

Mon, 01 Jan 0001 00:00:00 +0000

Start from the base transfer guide

This guide builds on Transfer Component Versions. Read it first for the default ocm transfer cv workflow, credentials, and verification; the steps below only add routing resources to a custom upload target during transfer.

Upload to JFrog Artifactory

Mon, 01 Jan 0001 00:00:00 +0000

Start from the base transfer guide

This guide specializes the default transfer workflow for JFrog Artifactory targets. If you have not transferred a component version before, read Transfer Component Versions first, then return here to route resources into Artifactory repositories.

Upload to Sonatype Nexus

Mon, 01 Jan 0001 00:00:00 +0000

Start from the base transfer guide

This guide specializes the default transfer workflow for Sonatype Nexus targets. If you have not transferred a component version before, read Transfer Component Versions first, then return here to route resources into Nexus hosted repositories.