Chainguard Container for longhorn-ui-fips

A lightweight, reliable distributed block storage system for 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/longhorn-ui-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 Longhorn FIPS images are FIPS 140-2 compliant variants of the upstream Longhorn. Longhorn is a distributed block storage system for Kubernetes. These images leverage the security features of Chainguard Containers, including minimal attack surface, low-to-zero CVEs, automated nightly builds, high-quality SBOMs, verifiable signatures, and reproducible builds, with the addition of FIPS-validated cryptographic modules.

Longhorn Backing Image Manager Compatibility

• Chainguard's variant of Longhorn Backing Image Manager does not include telnet, as it is not functionally required by Longhorn and the container is designed to remain minimal.
• The backing-image-manager-fips image switches the default key derivation from argon2i to pbkdf2 to maintain FIPS 140-2 compliance.

Available Images

Longhorn is composed of multiple container images. Currently, the following Chainguard Longhorn images are available in fips variant:

• longhorn-share-manager-fips
• longhorn-ui-fips
• backing-image-manager-fips

cgr.dev/ORGANIZATION/longhorn-share-manager-fips:latest
cgr.dev/ORGANIZATION/longhorn-ui-fips:latest
cgr.dev/ORGANIZATION/backing-image-manager-fips:latest

The longhorn-share-manager component provides NFS server functionality to enable ReadWriteMany (RWX) volume access in Longhorn. The longhorn-ui component provides access to the dashboard for ease of administering the longhorn storage system. The backing-image-manager handles creating, synchronizing and deleting backing images stored on a single Longhorn disk.

Getting Started

To deploy Longhorn with Chainguard FIPS images, use the official Longhorn Helm chart with custom values to override the default images.

First, add the Longhorn Helm repository:

helm repo add longhorn https://charts.longhorn.io
helm repo update

Create a custom values file (values-chainguard-fips.yaml) to use Chainguard FIPS images:

image:
  longhorn:
    shareManager:
      repository: cgr.dev/ORGANIZATION/longhorn-share-manager-fips
      tag: latest
    ui:
      repository: cgr.dev/ORGANIZATION/longhorn-ui-fips
      tag: latest
    backingImageManager:
      repository: cgr.dev/ORGANIZATION/backing-image-manager-fips
      tag: latest

Deploy Longhorn with the custom FIPS values:

helm install longhorn longhorn/longhorn \
  --namespace longhorn-system \
  --create-namespace \
  -f values-chainguard-fips.yaml

Documentation and Resources

• Longhorn Docs - https://longhorn.io/docs/
• Longhorn Github - https://github.com/longhorn/longhorn
• Longhorn Share Manager Github - https://github.com/longhorn/longhorn-share-manager
• Longhorn Backing Image Manager Github - https://github.com/longhorn/backing-image-manager

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.