Chainguard Container for tofu-controller

A GitOps OpenTofu and Terraform controller for Flux

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/tofu-controller:latest

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

Compatibility Notes

tofu-controller is composed of multiple images:

• cgr.dev/ORGANIZATION/tofu-controller:latest
• cgr.dev/ORGANIZATION/tofu-controller-runner:latest

The container images are comparable to the official v16.0.0-rc.x pre-release version of tofu-controller and tf-runner images.

Getting Started

To deploy tofu-controller, you can follow the steps below:

Prerequisites

• helm
• flux v2.0+

Before using tofu-controller, you have to install Flux v2.0+ Flux and it's related CRDs were deployed via kubectl through the official install manifests: Flux Releases All example resources are deployed into the flux-system namespace. For more detail about the configurations options you can refer to the official Flux configuration documentation.

Install Flux

1. Install flux operator and related CRDs via kubectl

kubectl apply -f https://github.com/fluxcd/flux2/releases/latest/download/install.yaml

2. Verify CRDs have been established

kubectl wait --for=condition=Established crd --all -n flux-system --timeout=60s

3. Verify all flux related pods are ready

kubectl wait --for=condition=ready -n flux-system pod -l app=helm-controller --timeout=30s
kubectl wait --for=condition=ready -n flux-system pod -l app=image-automation-controller --timeout=30s
kubectl wait --for=condition=ready -n flux-system pod -l app=image-reflector-controller --timeout=30s
kubectl wait --for=condition=ready -n flux-system pod -l app=kustomize-controller --timeout=30s
kubectl wait --for=condition=ready -n flux-system pod -l app=notification-controller --timeout=30s
kubectl wait --for=condition=ready -n flux-system pod -l app=source-controller --timeout=30s

Install tofu-controller via Helm using values.yaml

1. Create a values.yaml, specifying the Chainguard images:

cat <<EOF > values.yaml
# -- Controller-specific configurations
image:
  # -- Controller image repository
  repository: cgr.dev/ORGANIZATION/tofu-controller
  # -- Controller image pull policy
  pullPolicy: IfNotPresent
  # -- Controller image tag
  tag: "latest"

# -- Runner-specific configurations
runner:
  image:
    # -- Runner image repository
    repository: cgr.dev/ORGANIZATION/tofu-controller-runner
    # -- Controller image pull policy
    pullPolicy: IfNotPresent
    # -- Runner image tag
    tag: "latest"
EOF

2. Install the Helm chart for Rancher Fleet using the following command:

helm -n cattle-fleet-system install --create-namespace --wait fleet-crd \
    fleet/fleet-crd
helm -n cattle-fleet-system install --create-namespace --wait fleet \
    fleet/fleet  --values values.yaml

3. Verify that the tofu-controller pod is up and running

kubectl wait --for=condition=ready -n flux-system pod -l app.kubernetes.io/name=tofu-controller --timeout=60s

You should now have Chainguard tofu-controller with a Chainguard tf-runner running in your cluster.

Documentation and Resources

• Tofu-Controller Docs
• Tofu-Controller Helm Chart Docs
• Flux Docs
• Flux Operator Docs

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.