This example shows that NSC and NSE can work with each other over the SR-IOV kernel connection.
Make sure that you have completed steps from sriov setup.
Deploy ponger:
kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop/ponger?ref=aad7c26ad32fb4c3b515179bbe85d59c811c52f1
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=aad7c26ad32fb4c3b515179bbe85d59c811c52f1
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
Delete ns:
kubectl delete ns ns-sriov-kernel2noop