kubeflow-trainer-controller-manager-fips

packaged by Chainguard

Chainguard Container for kubeflow-trainer-controller-manager-fips

FIPS-enabled Kubeflow Trainer (v2) controller-manager for distributed AI/ML model training on Kubernetes

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/kubeflow-trainer-controller-manager-fips:latest

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

Overview

Kubeflow Trainer is a Kubernetes-native project for distributed training and fine-tuning of AI/ML models (including LLMs) on Kubernetes clusters. This image provides the FIPS-enabled Kubeflow Trainer v2 controller-manager, which reconciles TrainJob, TrainingRuntime, and ClusterTrainingRuntime resources.

Compatibility Notes

This image is a drop-in replacement for the upstream ghcr.io/kubeflow/trainer/trainer-controller-manager image with FIPS-mode cryptography swapped in: same /manager entrypoint at /, same 65532 nonroot user, same SSL_CERT_FILE default. The upstream Helm chart works unchanged — only the image.registry / image.repository values need retargeting to your Chainguard org.

• Chainguard publishes the v2 Trainer controller-manager (the successor to the deprecated v1 training-operator). Upstream v1 charts and CRDs are not compatible.

FIPS Support

• The Go binary is built with go-fips-md5 and links against OpenSSL via the CGO opensslcrypto backend, so cryptographic operations (webhook TLS, admission signature verification, HTTPS to the Kubernetes API) run through the FIPS 140-3 provider shipped in openssl-provider-fips-3.4.0.
• The image bundles openssl-config-fipshardened, which sets /etc/ssl/openssl.cnf to require the FIPS provider at process start.
• HMAC keys shorter than 112 bits (14 bytes) are rejected by the OpenSSL FIPS provider; any outbound TLS/authentication paths driven by user-supplied secrets must use keys/passphrases of at least 14 bytes.

Getting Started

Install the upstream Helm chart with the image pointed at your Chainguard registry. The chart installs the JobSet controller it depends on by default (jobset.install: true); set it to false when JobSet is already present in the cluster.

cat > values.yaml <<EOF
image:
  registry: cgr.dev
  repository: ORGANIZATION/kubeflow-trainer-controller-manager-fips
  tag: latest
EOF
helm install kubeflow-trainer oci://ghcr.io/kubeflow/charts/kubeflow-trainer \
  --namespace kubeflow-system --create-namespace --values values.yaml

Replace the ORGANIZATION placeholder with your Chainguard Registry organization name.

Configuration

The controller runs as a nonroot user (UID 65532) and launches /manager at container start. The following environment variable is set by default:

• SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt — points the Go controller at the Wolfi CA bundle for verifying webhook and Kubernetes API TLS connections.

Documentation and Resources

• Kubeflow Trainer documentation
• Upstream repository

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.