Create an NVIDIA nv-ipam IPPool for SR-IOV Networks
Define a valid nv-ipam IPPool and node-aware sizing strategy so SR-IOV workloads can reliably obtain secondary interface IP addresses on Kubernetes.
π‘ Quick Answer: Create one
IPPoolin the same namespace as workloads and NAD, setpoolType: ippool, and choose a subnet/block size combination that fits your node and pod scale.
nv-ipam allocates addresses from IPPool resources. Namespace and sizing must be consistent with your workload.
Example IPPool
apiVersion: nv-ipam.nvidia.com/v1alpha1
kind: IPPool
metadata:
name: tenant-a
namespace: tenant-a
spec:
poolType: ippool
subnet: 10.233.215.96/28
gateway: 10.233.215.97
perNodeBlockSize: 8Apply:
oc apply -f ippool.yamlValidate
oc get ippool -n tenant-aSizing Guidance
/28has 16 addresses total; use small block sizes.perNodeBlockSizemust fit available addresses after gateway/network reservations.- Use larger subnets for larger node counts or high SR-IOV density.
Namespace Rule
Create the pool in the same namespace used by workloads and generated NAD (for example tenant-a).

Recommended
Kubernetes Recipes β The Complete Book100+ production-ready patterns with detailed explanations, best practices, and copy-paste YAML. Everything in one place.
Get the Book βLearn by Doing
CopyPasteLearn β Hands-on Cloud & DevOps CoursesMaster Kubernetes, Ansible, Terraform, and MLOps with interactive, copy-paste-run lessons. Start free.
Browse Courses βπ Deepen Your Skills β Hands-on Courses
Courses by CopyPasteLearn.com β Learn IT by Doing
