lmstack-lora-controller-fips

packaged by Chainguard

Chainguard Container for lmstack-lora-controller-fips

FIPS-enabled Kubernetes operator for the vLLM Production Stack, vLLM's reference system for K8S-native cluster-wide deployment, that manages LoRA adapters, vLLM runtimes, routers and cache servers through CRDs.

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/lmstack-lora-controller-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

This is the FIPS-enabled variant of the Chainguard lmstack-lora-controller image, the Kubernetes operator of the vLLM Production Stack that reconciles the LoraAdapter, VLLMRuntime, VLLMRouter, and CacheServer custom resources. The controller is built with a FIPS-enabled Go toolchain that performs cryptography through the system OpenSSL FIPS provider (the image includes openssl-config-fipshardened), so TLS connections to the Kubernetes API server and the metrics and webhook servers use only FIPS-approved algorithms.

Like the upstream lmcache/lmstack-lora-controller image, the controller binary is available at /manager, and the image runs as the nonroot user (UID 65532) by default. The controller serves health probes on port 8081 (/healthz and /readyz), metrics on port 8443 by default, and webhooks on port 9443.

Getting Started

The LoRA controller is deployed as part of the upstream vllm-stack Helm chart. Install it with this image by overriding the controller image values:

helm repo add vllm-stack https://vllm-project.github.io/production-stack
helm repo update

helm install vllm-stack vllm-stack/vllm-stack \
  --create-namespace --namespace vllm-system \
  --set loraController.enableLoraController=true \
  --set loraController.image.repository=cgr.dev/ORGANIZATION/lmstack-lora-controller-fips \
  --set loraController.image.tag=latest

FIPS Support

The controller binary uses the Go OpenSSL crypto backend and enforces FIPS 140-3 compliant cryptography at the library level. If the FIPS configuration is removed or corrupted, the binary refuses to start rather than falling back to non-approved algorithms.

Documentation and Resources

• vLLM Production Stack GitHub project
• vLLM Production Stack Helm chart
• vLLM Production Stack 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.