tofu-controller-fips

Fips

Infra

Stig

Updated 9 hours ago

Tofu-Controller-FIPS Overview

Secure your stack with a FIPS-validated, hardened Tofu-Controller image freshly-built by Minimus. Minimus images always include the most up-to-date package version for all packages and dependencies contained in the image.

Tofu-Controller lets platform teams manage cloud and on-premises infrastructure through the same GitOps workflow already used for application deployments — an OpenTofu or Terraform configuration is committed to Git, and the controller plans, applies, and continuously reconciles it against a live Kubernetes cluster through Flux. It supports adopting GitOps at whatever pace fits an environment: fully automate provisioning end-to-end, manage just part of an existing resource, enforce a known Terraform state without making changes, or run drift detection alone to flag configuration drift before deciding whether to act. Use this image when you need to meet the requirements for FIPS-validated cryptographic protection.

FIPS 140-3 Certification

This image is FIPS-validated to ensure its cryptographic operations meet the Federal Information Processing Standards (FIPS) required for secure government and regulated environments. Its core cryptographic modules are validated under the NIST Cryptographic Module Validation Program (CMVP) and comply with the FIPS 140-3 standard.

To verify that the FIPS 140-3 provider is configured and active, follow the instructions in the FIPS compliance tab.

Try It Out

For a quick test, print the help menu:

docker run --rm reg.mini.dev/tofu-controller-fips --help

Tofu-Controller can be deployed via a Helm chart. See the related charts tab to get started.

Technical Considerations

The Tofu-Controller-FIPS image provided by Minimus is a FIPS-validated, slim, security-hardened alternative to the public image from GitHub Container Registry. The images are largely interchangeable, with a few differences as noted below.

Tofu-Controller FIPS built by Minimus:

Runs as non-root by default (uid 65532), matching the public image's default non-root user.
Drill down on the version specification tab to see the default user, listening ports, entrypoint, volumes, environment variables, etc.

The Payoff

A hardened, minimal image that will remain more secure for the long run and accrue vulnerabilities at a slower rate.

See the risk reduction dashboard for a detailed CVE comparison over the past 30 days.
Review the compliance report to see the default hardening and security configurations for the image.

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.