Last changed
Get notified of upcoming product changes, critical vulnerability notifications and patches and more.
Sign InChainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.
This image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard registry.
KServe enables the scalable deployment of machine learning models in Kubernetes. It provides mechanisms for model versioning, monitoring, and autoscaling, and is built on top of Kubernetes' extensibility features, such as custom resource definitions (CRDs) and operators.
This deployment includes the following critical KServe components:
You can install KServe components using Helm charts. Below are instructions for deploying KServe with Chainguard images.
KServe relies on Custom Resource Definitions (CRDs) to manage model serving resources.
To deploy KServe with Chainguard images, use the following Helm commands:
For detailed installation configurations, refer to the KServe Helm chart values.yaml.
Inference tests are critical to validating KServe's model serving capabilities. After deploying KServe, you can run inference tests to confirm that the deployed models are working as expected. For more info
The following example creates an inference service that uses the iris-sklearn
model:
This service will download the model using the storage-initializer, and KServe will expose the model for inference requests.
Once the inference service is running, you can send inference requests to validate the model's predictions:
Use the following command to send a test prediction request:
You should receive a response like this:
This confirms that the inference service is functioning correctly.
If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.
Chainguard Images are a collection of container images designed for security and minimalism.
Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.
The main features of Chainguard Images include:
-dev
VariantsAs mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev
variant which does include a shell and package manager.
Although the -dev
image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev
variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.
That being said, it’s worth noting that -dev
variants of Chainguard Images are completely fine to run in production environments. After all, the -dev
variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.
To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.
Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:
Apache-2.0
GCC-exception-3.1
GPL-2.0-or-later
GPL-3.0-or-later
LGPL-2.1-or-later
MIT
MPL-2.0
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreement