metacontroller-fips

packaged by Chainguard

Chainguard Container for metacontroller-fips

FIPS-compliant Minimal Metacontroller Image

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/metacontroller-fips:latest

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

Compatibility Notes

The metacontroller-fips image is a drop-in replacement for the upstream metacontroller/metacontroller image. Like all Chainguard Containers, it carries a minimal, distroless design: it includes only metacontroller and its runtime dependencies, ships without a shell or package manager, and runs as a non-root user by default.

FIPS Support

The metacontroller-fips Chainguard Container ships with a validated redistribution of OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Prerequisites

Running metacontroller-fips requires the following:

• A running Kubernetes cluster
• kubectl, configured to communicate with your cluster
• Helm, used to install the upstream chart

Getting Started

Metacontroller is distributed as a Helm chart published as an OCI artifact. To point the chart at the Chainguard FIPS image, first create a values file that overrides the image repository and tag:

cat > values.yaml <<EOF
image:
  repository: cgr.dev/ORGANIZATION/metacontroller-fips
  tag: latest
EOF

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

Install the chart into a dedicated namespace using your values file:

helm install metacontroller \
  oci://ghcr.io/metacontroller/metacontroller-helm \
  --namespace metacontroller --create-namespace \
  --values values.yaml

Metacontroller runs as a single StatefulSet. Confirm that the controller pod reports as ready:

kubectl get pods --namespace metacontroller

NAME               READY   STATUS    RESTARTS   AGE
metacontroller-0   1/1     Running   0          30s

With the controller running, you can register Metacontroller APIs such as CompositeController and DecoratorController to drive your own custom controllers. The upstream examples walk through several complete use cases.

Configuration

The chart exposes the controller's image, replica count, resource limits, and command-line flags through the values file. For example, to run two replicas and set resource requests and limits, extend the values file:

cat > values.yaml <<EOF
image:
  repository: cgr.dev/ORGANIZATION/metacontroller-fips
  tag: latest
replicas: 2
resources:
  requests:
    cpu: 100m
    memory: 128Mi
  limits:
    cpu: 500m
    memory: 512Mi
EOF

Apply the change with helm upgrade. The controller's own flags — log level, discovery interval, and cache-flush interval — are set through the chart's commandArgs value. Refer to the upstream Helm configuration documentation for the complete list of supported values.

Documentation and Resources

• Metacontroller documentation
• Metacontroller API reference
• Chainguard FIPS Images
• Overview of Migrating to Chainguard Containers

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.