Skip to content

Latest commit

 

History

History
49 lines (37 loc) · 1.28 KB

README.md

File metadata and controls

49 lines (37 loc) · 1.28 KB

Test SR-IOV kernel connection

This example shows that NSC and NSE can work with each other over the SR-IOV kernel connection.

Requires

Make sure that you have completed steps from sriov setup.

Run

Deploy ponger:

kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop/ponger?ref=2e62a2c11180b72bf57fca60e04562a9fe17c1ae

Wait for applications ready:

kubectl -n ns-sriov-kernel2noop wait --for=condition=ready --timeout=1m pod -l app=ponger

Wait for the ponger configuration to be applied:

kubectl -n ns-sriov-kernel2noop exec deploy/ponger -- ip a | grep "172.16.1.100"

Deploy NSC and NSE:

kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop?ref=2e62a2c11180b72bf57fca60e04562a9fe17c1ae

Wait for applications ready:

kubectl -n ns-sriov-kernel2noop wait --for=condition=ready --timeout=1m pod -l app=nsc-kernel
kubectl -n ns-sriov-kernel2noop wait --for=condition=ready --timeout=1m pod -l app=nse-noop

Ping from NSC to NSE:

kubectl -n ns-sriov-kernel2noop exec deployments/nsc-kernel -- ping -c 4 172.16.1.100

Cleanup

Delete ns:

kubectl delete ns ns-sriov-kernel2noop