chainloop-control-plane-migrations

packaged by Chainguard

Chainguard Container for chainloop-control-plane-migrations

Chainloop provides SDLC evidence store and policy engine for your Software Supply Chain attestations, SBOMs, VEX, SARIF, and provenance metadata.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/chainloop-control-plane-migrations:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

Chainguard's Chainloop image group consists of four container images that work together to provide an SLSA level 3 provenance-compliant control plane and evidence store for Software Supply Chain attestations:

cgr.dev/ORGANIZATION/chainloop-control-plane
cgr.dev/ORGANIZATION/chainloop-artifact-cas
cgr.dev/ORGANIZATION/chainloop-cli
cgr.dev/ORGANIZATION/chainloop-control-plane-migrations

These images are comparable to the upstream Chainloop images and can be used as drop-in replacements.

Key components:

• control-plane: Main control plane service for managing workflows and attestations
• artifact-cas: Content Addressable Storage (CAS) service for artifacts and attestation metadata
• cli: Command-line interface for interacting with Chainloop
• control-plane-migrations: Database migration tool using Atlas for schema management

All Chainguard Chainloop images run as non-root user (uid/gid 1001).

Getting Started

Chainloop components are typically deployed together in a Kubernetes cluster using the official Helm chart. The following example demonstrates how to deploy Chainloop using Chainguard's container images.

Prerequisites

• A Kubernetes cluster (1.23+)
• Helm 3.x installed
• kubectl configured to communicate with your cluster

Helm Chart Installation

The following is an example of deploying Chainloop with the official Helm chart using Chainguard's images:

helm install chainloop \
  oci://ghcr.io/chainloop-dev/charts/chainloop \
  --namespace chainloop \
  --create-namespace \
  --set controlplane.image.repository=cgr.dev/ORGANIZATION/chainloop-control-plane \
  --set controlplane.image.tag=latest \
  --set cas.image.repository=cgr.dev/ORGANIZATION/chainloop-artifact-cas \
  --set cas.image.tag=latest \
  --set controlplane.migration.image.repository=cgr.dev/ORGANIZATION/chainloop-control-plane-migrations \
  --set controlplane.migration.image.tag=latest

Be sure to replace ORGANIZATION with the name used for your organization's private repository within the Chainguard registry.

Note: The above example uses default settings which include built-in PostgreSQL. For production deployments, you'll need to configure external OIDC authentication, secrets backend (Vault/AWS/GCP/Azure), and optionally an external database. Refer to the upstream chart documentation for complete configuration options.

Using the CLI

You can use the Chainloop CLI to interact with your deployment. Configure it to point to your instance:

chainloop config save \
  --control-plane api.cp.chainloop.example.com:443 \
  --artifact-cas api.cas.chainloop.example.com:443

The CLI image (chainloop-cli) can also be used in CI/CD pipelines or container-based workflows:

# Example: Running CLI in a container for attestation workflows
docker run --rm -v $(pwd):/workspace \
  cgr.dev/ORGANIZATION/chainloop-cli:latest \
  attestation add --value /workspace/sbom.json

Configuration

Chainloop components can be configured through Helm chart values or environment variables. Common configuration options include:

Control Plane:

• CHAINLOOP_DATABASE_URL: PostgreSQL connection string
• CHAINLOOP_CAS_SERVER: Artifact CAS service endpoint
• CHAINLOOP_AUTH_*: Authentication provider settings

Artifact CAS:

• CAS_SERVER_DATABASE_URL: Database connection for metadata storage
• CAS_BACKEND: Storage backend configuration (S3, GCS, local filesystem)

CLI:

• CHAINLOOP_API_URL: Control plane API endpoint
• CHAINLOOP_TOKEN: Authentication token

Refer to the Chainloop Helm chart documentation for a complete list of configuration options.

Available Images

Documentation and Resources

For more information about Chainloop, please refer to:

• Chainloop Official Documentation
• Chainloop GitHub Repository
• Getting Started Tutorial

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.