kubevirt-cdi-operator-fips

packaged by Chainguard

Chainguard Container for kubevirt-cdi-operator-fips

FIPS-validated CDI images for persistent storage data import, upload, and cloning for KubeVirt virtual machines.

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/kubevirt-cdi-operator-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 KubeVirt CDI FIPS images are drop-in replacements for the upstream kubevirt/containerized-data-importer images, with a validated redistribution of the OpenSSL FIPS provider module. CDI manages persistent storage data import, upload, and cloning for KubeVirt virtual machines.

oVirt imports through an OvirtVolumePopulator fail: ovirt-populator execs ovirt-img, which neither importer image ships.

FIPS Support

The FIPS variants are built with the go-msft toolchain against the OpenSSL FIPS provider, so all TLS handshakes and application-layer crypto routed through the Go standard library go through the validated module. By default (GODEBUG=cgr_fips=openssl+geomys), a binary falls back to the embedded Go FIPS module if the OpenSSL FIPS provider is unavailable; set GODEBUG=cgr_fips=openssl to make it abort instead.

In kubevirt-cdi-importer-fips, cdi-containerimage-server is dynamically linked against glibc, unlike the static upstream and non-FIPS builds, so pullMethod: node DataVolume imports and DataImportCron polls from FROM scratch or musl-based source containerdisks fail.

For more on FIPS support in Chainguard Images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy.

Available Images

cgr.dev/ORGANIZATION/kubevirt-cdi-operator-fips:latest
cgr.dev/ORGANIZATION/kubevirt-cdi-controller-fips:latest
cgr.dev/ORGANIZATION/kubevirt-cdi-cloner-fips:latest
cgr.dev/ORGANIZATION/kubevirt-cdi-importer-fips:latest
cgr.dev/ORGANIZATION/kubevirt-cdi-apiserver-fips:latest
cgr.dev/ORGANIZATION/kubevirt-cdi-uploadproxy-fips:latest
cgr.dev/ORGANIZATION/kubevirt-cdi-uploadserver-fips:latest

kubevirt-cdi-importer-fips is published from the 1.6 stream onwards. It is the short-lived worker image CDI creates to populate a PVC and also carries the openstack-populator, ovirt-populator, cdi-containerimage-server, cdi-image-size-detection, and cdi-source-update-poller helpers the controller invokes from the same image.

Deployment

CDI is deployed using the CDI operator. Download the upstream operator manifest and replace image references with Chainguard FIPS images:

export CDI_VERSION="vX.X.X"
export ORG="ORGANIZATION"

curl -fsSL "https://github.com/kubevirt/containerized-data-importer/releases/download/${CDI_VERSION}/cdi-operator.yaml" \
  | sed -E \
    -e "s|quay.io/kubevirt/cdi-operator:[^ \"]+|cgr.dev/${ORG}/kubevirt-cdi-operator-fips:latest|g" \
    -e "s|quay.io/kubevirt/cdi-controller:[^ \"]+|cgr.dev/${ORG}/kubevirt-cdi-controller-fips:latest|g" \
    -e "s|quay.io/kubevirt/cdi-cloner:[^ \"]+|cgr.dev/${ORG}/kubevirt-cdi-cloner-fips:latest|g" \
    -e "s|quay.io/kubevirt/cdi-importer:[^ \"]+|cgr.dev/${ORG}/kubevirt-cdi-importer-fips:latest|g" \
    -e "s|quay.io/kubevirt/cdi-apiserver:[^ \"]+|cgr.dev/${ORG}/kubevirt-cdi-apiserver-fips:latest|g" \
    -e "s|quay.io/kubevirt/cdi-uploadproxy:[^ \"]+|cgr.dev/${ORG}/kubevirt-cdi-uploadproxy-fips:latest|g" \
    -e "s|quay.io/kubevirt/cdi-uploadserver:[^ \"]+|cgr.dev/${ORG}/kubevirt-cdi-uploadserver-fips:latest|g" \
  | kubectl apply -f -

kubectl apply -f "https://github.com/kubevirt/containerized-data-importer/releases/download/${CDI_VERSION}/cdi-cr.yaml"

Documentation and Resources

• CDI GitHub Repository
• KubeVirt CDI User Guide
• CDI API Reference

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.