krakend-fips

packaged by Chainguard

Chainguard Container for krakend-fips

A minimal, FIPS-enabled image for KrakenD, a high-performance open source API Gateway that aggregates, transforms, filters, and secures requests to your microservices from a single declarative configuration file.

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/krakend-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 Chainguard krakend-fips image is a FIPS-enabled variant of the upstream KrakenD Community Edition Docker Official Image (docker.io/library/krakend, formerly docker.io/devopsfaith/krakend). The krakend binary is installed at /usr/bin/krakend, and the image keeps the upstream entrypoint (docker-entrypoint.sh), default command (krakend run -c krakend.json), and working directory (/etc/krakend), so existing configuration and invocations continue to work.

The gateway is built with a FIPS-validated Go toolchain and dynamically links the system OpenSSL running under a FIPS-hardened configuration. Like most Chainguard Containers, this image runs as a nonroot user and includes only the minimum set of packages needed to run the gateway. As with the standard image, it runs as uid:gid 65532:65532, whereas the upstream image starts as root and drops to its own krakend user (uid 1000, gid 65533); deployments that assume runAsUser: 1000, a particular fsGroup, or bind-mount ownership tied to uid 1000 must be updated to 65532.

For general usage instructions, including the libc/plugin compatibility note, see the non-FIPS krakend image README.

FIPS Support

This Chainguard Container ships with a validated redistribution of OpenSSL's FIPS provider module, and the krakend binary is built with the go-msft FIPS-validated Go toolchain and dynamically linked against the system OpenSSL. Cryptographic operations run through FIPS 140-3 validated modules. If the OpenSSL FIPS provider cannot be loaded (for example, a corrupted fipsmodule.cnf), the go-msft 1.27 runtime falls back to Go's own embedded FIPS-validated module, so the gateway keeps operating under FIPS-approved cryptography rather than dropping to non-approved algorithms. Setting GODEBUG=cgr_fips=openssl disables that fallback and makes the binary abort instead — which is exactly what this image's FIPS-break test asserts to prove the binary genuinely links the OpenSSL FIPS provider.

For more on FIPS support in Chainguard Containers, refer to the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

Validate and run a configuration by mounting it over the default config path:

# Validate the configuration first.
docker run --rm -v "$(pwd)/krakend.json:/etc/krakend/krakend.json:ro" \
  cgr.dev/ORGANIZATION/krakend-fips:latest check -c /etc/krakend/krakend.json

# Run the gateway (KrakenD listens on port 8080 by default).
docker run --rm -p 8080:8080 \
  -v "$(pwd)/krakend.json:/etc/krakend/krakend.json:ro" \
  cgr.dev/ORGANIZATION/krakend-fips:latest

The gateway exposes a built-in health endpoint at /__health that returns HTTP 200 once it is serving:

curl http://localhost:8080/__health

KrakenD can also be deployed to Kubernetes with the community krakend Helm chart; point the chart's image values at this image.

Documentation and Resources

• KrakenD documentation
• Running KrakenD
• KrakenD Community Edition source
• krakend Helm chart

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.