Last changed
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
SRIOV network device plugin for Kubernetes
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container 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 passthroughChainguard'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:
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.
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.
Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.
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.
Chainguard container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag 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