Tutorials on Open Component Model

Create a Multi-Component Product

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

Overview

Real-world software products rarely consist of a single component. A web platform, for example, might combine a frontend, a backend, shared configuration, and deployment manifests — each versioned independently. The OCM component constructor lets you model this entire hierarchy in a single file, wiring components together with references, attaching provenance metadata, and injecting versions through environment variables.

Understand Credential Resolution

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

Overview

Every time OCM accesses a registry, it resolves credentials automatically. This tutorial walks you through how that resolution works — given a config, which credentials does OCM pick for each request, and why?

Deploy an Application from a Helm Chart with OCM and kro

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

What You’ll Learn

Your application already ships as a Helm chart, and you want its delivery to be just as repeatable: one versioned OCM component that carries the chart, its container image, and the instructions to deploy it. Promote that component from a staging registry to production, or hand it to an air-gapped cluster, and the image references should update themselves. Patching a values file to correct a registry path is exactly what this avoids.

Deploy an Application from Chained RGDs with OCM and kro

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

You have an application to run on Kubernetes. You want to ship it the same way every time: one versioned package that carries the container image and the instructions to run it. When you move that package from a development registry to production, or into an air-gapped cluster, the image references must follow automatically. You should never hand-edit a manifest to fix a registry path.

Working with HTTP Resources

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

Overview

OCM can add a file served over HTTP or HTTPS to a component version using the Wget/v1 type. There is one download engine underneath, with two front doors:

Working with SBOMs

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

A component version tells you which artifacts you deliver. It does not tell you what is inside them. That answer lives in a Software Bill of Materials. Today, SBOMs might be located in various places, and we need a way to unify them and get all of them together to one location. For the why, see Software Bills of Materials.

Working with Resolvers

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

Overview

When a component has references to other components stored in different repositories, the CLI needs to know where to find them. Resolvers map component name patterns to repositories so the CLI can automatically locate referenced components during recursive operations. For a high-level introduction, see the Resolvers concept page. For configuration details and pattern syntax, see the Resolver Configuration Reference.