Chainguard Container for ratify-fips

Artifact Ratification Framework (CNCF Sandbox)

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/ratify-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

Chainguard's ratify container is a lean, Wolfi-based container image. It is functionally equivalent to the upstream Ratity image while maintaining minimal dependencies and enhanced security.

But there are some differences between the upstream and Chainguard's ratify container image:

• The Chainguard image stores the configuration file at /opt/ratify/config.json instead of /.ratify/config.json.
• The plugins in the Chainguard image reside at /opt/ratify/plugins instead of /.ratify/plugins.

Getting Started

In order to deploy Ratify in your Kubernetes cluster, first things first, you need to install the Gatekeeper admission controller. You can follow the Gatekeeper installation guide.

To deploy Gatekeeper, first, you need to add the Gatekeeper Helm repository:

helm repo add gatekeeper https://open-policy-agent.github.io/gatekeeper/charts

You can use Chainguard image for Gatekeeper by setting the image.repository and image.release values in a values.yaml file:

cat > values-gatekeeper.yaml << EOF
image:
  repository: cgr.dev/ORGANIZATION/gatekeeper
  release: latest
EOF

Then, you can install Gatekeeper using the following command:

helm install gatekeeper/gatekeeper  \
    --name-template=gatekeeper \
    --namespace gatekeeper-system --create-namespace \
    --set enableExternalData=true \
    --set validatingWebhookTimeoutSeconds=5 \
    --set mutatingWebhookTimeoutSeconds=2 \
    --set externaldataProviderResponseCacheTTL=10s \
    -f values-gateekeper.yaml

Once Gatekeeper is installed, you can deploy the Ratify admission controller. You can use the Ratify Helm chart to deploy Ratify in your cluster. First, add the Ratify Helm repository:

helm repo add ratify https://notaryproject.github.io/ratify

You can use the Chainguard image for Ratify by setting the image.repository and image.tag values in a values.yaml file:

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

Then install the webhook using the values.yaml file:

NOTE: Do not forget to use the --set-file flag to provide the notation.crt file, which is required for the Ratify webhook to function properly.

  helm install ratify ratify/ratify \
    --namespace gatekeeper-system \
    --set-file notationCerts[0]="./notation.crt" \
    --set featureFlags.RATIFY_CERT_ROTATION=true \
    --set policy.useRego=true \
    -f values.yaml

Then you can follow up the Ratify documentation to configure Ratify constraints to enforce policies on your Kubernetes cluster.

FIPS Support

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

Documentation and Resources

• Ratify Documentation
• Quickstart Guide

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.