kubeflow-pipelines-launcher-fips

packaged by Chainguard

Chainguard Container for kubeflow-pipelines-launcher-fips

FIPS-compliant Minimalist Kubeflow Pipelines Images

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-pipelines-launcher-fips:latest

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

Overview

This image group provides FIPS-compliant backend component images that make up a Kubeflow Pipelines v2 deployment, published under the kubeflow-pipelines-*-fips repositories:

The kubeflow-pipelines-launcher-fips image ships the v2 launcher binary, which KFP injects into every pipeline step's Pod to download input artifacts from object storage, run the user's container command, upload output artifacts, and record the execution/artifacts to ML Metadata.

FIPS Support

The kubeflow-pipelines-launcher-fips Chainguard Container ships with the OpenSSL FIPS provider, so the launcher's cryptographic operations — including its TLS connections to the Pipelines API server, ML Metadata, and the object store — use only FIPS-approved algorithms. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

These images are drop-in replacements for the upstream Kubeflow Pipelines component images. Deploy them by applying the upstream kustomize manifests with the image references retargeted to your Chainguard repositories.

Create a kustomization.yaml that pulls the upstream overlay and remaps each component image (replace ORGANIZATION with your Chainguard org, and pin <KFP_VERSION> to the Kubeflow Pipelines release you are deploying):

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
  - github.com/kubeflow/pipelines/manifests/kustomize/env/platform-agnostic?ref=<KFP_VERSION>
images:
  - name: ghcr.io/kubeflow/kfp-launcher
    newName: cgr.dev/ORGANIZATION/kubeflow-pipelines-launcher-fips
  # ...remap the remaining kfp-* component images the same way

Install the cluster-scoped resources, then apply the overlay:

kubectl apply -k "github.com/kubeflow/pipelines/manifests/kustomize/cluster-scoped-resources?ref=<KFP_VERSION>"
kustomize build . | kubectl apply -f -

Verify the deployment once it converges:

kubectl get pods -n kubeflow

Documentation and Resources

For configuration and usage, refer to the upstream documentation:

• Kubeflow Pipelines documentation
• Kubeflow Pipelines source

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.