dask-kubernetes-fips

packaged by Chainguard

Chainguard Container for dask-kubernetes-fips

Native Kubernetes integration for Dask (FIPS)

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/dask-kubernetes-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

Chainguard's Dask Kubernetes FIPS image is comparable to the dask/dask-kubernetes-operator image maintained by Dask, but rebuilt on Chainguard OS against FIPS-hardened OpenSSL. It is also a drop-in replacement for the upstream dask/dask image (ghcr.io/dask/dask:latest) for worker pods, so a single FIPS image can back both the operator deployment and the worker pods of a DaskCluster.

The image runs the same kopf-driven operator and reconciles the same DaskCluster, DaskWorkerGroup, and DaskJob CRDs as upstream, but the runtime differs in a few ways that may matter when migrating:

• Non-root by default. The container runs as user dask (uid 1000, gid 1000); the upstream image runs as root. If you mount volumes or write files at runtime, ensure they are writable by uid 1000 or set securityContext.runAsUser accordingly.
• Python 3.10, not 3.8.13. Upstream pins an end-of-life'd Python 3.8.13; the Chainguard image ships Python 3.10. Any custom wheels installed alongside the operator must be compatible with 3.10.
• No shell wrapper. Upstream invokes the operator via ["/bin/sh", "-c", "kopf run -m dask_kubernetes.operator --verbose --all-namespaces"]. The Chainguard image has no shell — the entrypoint is kopf run -m dask_kubernetes.operator.controller directly (the same controller code path) and the default args add a liveness HTTP endpoint at http://0.0.0.0:8080/healthz so Kubernetes can probe the operator without exec-ing into the container.
• Minimal runtime. No shell, no package manager, no build toolchain. kubectl exec ... -- /bin/bash will not work; use the -dev variant for debugging.
• Dedicated venv on PATH / PYTHONPATH. The operator and its dependencies live under /usr/share/dask-kubernetes/ (PATH prefixed with /usr/share/dask-kubernetes/bin, PYTHONPATH set to the venv's site-packages). Upstream installs into the system Python — plugins copied to /usr/local/lib/python*/site-packages will not be picked up; install them into /usr/share/dask-kubernetes/lib/python3.10/site-packages instead.
• FIPS-specific kopf patch. kopf's make_suffix in _cogs/configs/conventions.py uses hashlib.blake2b to generate a 4-byte non-cryptographic suffix for long Kubernetes annotation storage keys. BLAKE2b is not FIPS-approved, so this image replaces the call with hashlib.sha256(...).digest()[:4] (FIPS-approved, same 4-byte digest width). Behavior is equivalent; the suffix bytes differ from upstream's, so do not assume kopf storage keys are byte-identical to a non-FIPS deployment.

See upstream's Dask Kubernetes documentation for operator configuration and CRD reference, and Chainguard FIPS Documentation for the FIPS-hardened OpenSSL details.

FIPS Support

This FIPS-compliant image includes the OpenSSL FIPS provider and is built with FIPS-validated cryptographic modules. Key FIPS features include:

• FIPS-validated OpenSSL provider - Uses OpenSSL FIPS provider for cryptographic operations
• Approved algorithms only - Restricted to FIPS-approved cryptographic algorithms
• FIPS mode enforcement - Cryptographic operations automatically use FIPS-validated modules

Getting Started

Install the operator

helm repo add dask https://helm.dask.org
helm install dask-k8s-operator dask/dask-kubernetes-operator \
  --set image.name=cgr.dev/ORGANIZATION/dask-kubernetes-fips \
  --set image.tag=latest \
  --create-namespace -n dask-operator

Verify it's running: kubectl get pods -n dask-operator

To get started with a dask cluster and scale it run this python snippet:

from dask_kubernetes.operator import KubeCluster
cluster = KubeCluster(
  name="my-dask-cluster",
  image="cgr.dev/ORGANIZATION/dask-kubernetes-fips:latest"
)
cluster.scale(10)

You can see the dask worker nodes created above:

kubectl get daskcluster -n default
kubectl get pods -l dask.org/cluster-name=my-dask-cluster

Documentation and Resources

• Official Dask Kubernetes documentation
• Default values.yaml file for Dask Kubernetes
• Chainguard FIPS Documentation

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.