kuberay-apiserver-fips

packaged by Chainguard

Chainguard Container for kuberay-apiserver-fips

A FIPS-compliant REST/gRPC API server for managing Ray clusters on 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/kuberay-apiserver-fips:latest

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

FIPS Compliance

The kuberay-apiserver-fips Chainguard Container ships with a FIPS-validated cryptographic module. The image is built with Chainguard's FIPS-enabled Go toolchain, ensuring all TLS and cryptographic operations use FIPS 140-2 validated implementations.

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

This FIPS variant is designed for environments requiring FIPS 140-2 compliance. For standard deployments without compliance requirements, use the non-FIPS kuberay-apiserver image.

Compatibility Notes

Chainguard's kuberay-apiserver-fips image is a FIPS-compliant variant of the upstream kuberay/apiserver image. Key differences:

• Built with a FIPS-validated Go toolchain for all cryptographic operations
• Includes openssl-config-fipshardened for enforced FIPS mode
• Runs as non-root user (65532:65532) by default
• Built on a minimal Chainguard base rather than scratch
• Requires the kuberay-operator to be deployed in the cluster for RayCluster CR reconciliation

The apiserver exposes a gRPC server on port 8887 and an HTTP gateway on port 8888 that translate API calls into RayCluster, RayJob, and RayService custom resource operations against the Kubernetes API.

Getting Started

The KubeRay APIServer requires the KubeRay operator to be running in the cluster. You can install both using Helm.

Add the KubeRay Helm repository:

helm repo add kuberay https://ray-project.github.io/kuberay-helm/
helm repo update

Install the KubeRay operator (prerequisite):

helm install kuberay-operator kuberay/kuberay-operator \
    --create-namespace \
    --namespace kuberay-system

Install the KubeRay APIServer with the Chainguard FIPS image:

helm install kuberay-apiserver kuberay/kuberay-apiserver \
    --namespace kuberay-system \
    --set image.repository=cgr.dev/ORGANIZATION/kuberay-apiserver-fips \
    --set image.tag=latest

Validation

Once deployed, verify the apiserver is running and healthy:

kubectl wait --for=condition=Available -n kuberay-system deployment/kuberay-apiserver --timeout=120s
kubectl port-forward -n kuberay-system svc/kuberay-apiserver-service 8888:8888 &
curl -s http://localhost:8888/healthz

You can also verify the Swagger UI is accessible at http://localhost:8888/swagger-ui/ and the API spec at http://localhost:8888/swagger/cluster.swagger.json.

Documentation and Resources

• KubeRay APIServer Documentation
• KubeRay Helm Charts
• KubeRay Operator Documentation
• Ray Documentation
• Chainguard FIPS Images Guide

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.