Multi-NIC CNI on Multi-Cloud
| Multi-NIC CNI Features | IBM Cloud | Bare Metal | AWS | Azure (tentative) |
|---|---|---|---|---|
| Single definition for multiple attachments - dynamic interface discovery - policy-based NIC selection |
✓ | ✓ | ✓ | ✓ |
| CIDR/IP management | ✓ | * | * | ✓ |
| L3 Route configuration | ✓ | X | X | ✓ |
✓: beneficial
*: optional (e.g., replacable by whereabout, aws-vpc-cni IPAM)
X: non-beneficial as using L2
Operator Installation
Multi-NIC CNI Operator for supporting multi-cloud is under developing from v1.1.0. The pre-release bundle is available on alpha and beta channel on Openshift OKD OperatorHub.
Please check latest release.
MultiNICNetwork Deployment
IBM Cloud, Azure
- IPVLAN L3
kubectl apply -f config/samples/multinicnetwork/ipvlanl3.yaml
BareMetal
-
IPVLAN L2 with whereabout IPAM
kubectl apply -f config/samples/multinicnetwork/ipvlanl2.yaml -
SR-IoV with Multi-NIC IPAM ( from v1.2.0 )
kubectl apply -f config/samples/multinicnetwork/sriov.yaml -
Mellanox Host Device without IPAM ( from v1.2.0 )
kubectl apply -f config/samples/multinicnetwork/mellanox_hostdevice.yaml -
IPVLAN L2 with unmanaged HostInterface ( from v1.2.1 )
kubectl apply -f config/samples/multinicnetwork/ipvlanl2_unmanaged.yaml
AWS
- IPVLAN L2 with AWS-VPC-connecting IPAM ( from v1.1.0 )
kubectl apply -f config/samples/multinicnetwork/awsipvlan.yaml
Connection Check
see check connection.