Last changed
Get notified of upcoming product changes, critical vulnerability notifications and patches and more.
Sign InSRIOV network device plugin for Kubernetes
Chainguard 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.
Where possible, the sriov-network-device-plugin Chainguard Image is built for compatibility with the official SR-IOV Network Device Plugin image.
The SR-IOV Network Device Plugin facilitates the use of SR-IOV-capable network devices in Kubernetes clusters, enabling high-performance networking for your workloads.
If you're exploring the usage of sriov-network-device-plugin
for the first time, bear in mind that when deploying on a virtual machine like an EC2 instance or a Google Cloud VM these environments often expose only virtual functions (VFs), not physical functions (PFs).
The upstream documentation assumes you have access to PFs and uses the SR-IOV type net-attach-def
. However, for it to function properly, it requires access to the PFs, which is typically available only on bare-metal instances. Therefore, we recommend using a bare-metal instance, such as those offered by IBM Cloud, for full functionality. Alternatively, on VMs, consider using the Host Device CNI, which allows VFs to pass through without requiring direct access to the PFs.
sriov-network-device-plugin
and virtual function passthroughIf 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-only
GPL-2.0-or-later
GPL-3.0-or-later
LGPL-2.1-or-later
MIT
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreement