Memif2Kernel

Test memif to kernel connection

This example shows that NSC and NSE on the one node can find each other.

NSC is using the memif mechanism to connect to its local forwarder. NSE is using the kernel mechanism to connect to its local forwarder.

Requires

Make sure that you have completed steps from basic or memory setup.

Run

Deploy NSC and NSE:

kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Kernel?ref=34e1f2476dbc21097ab0a50348a966fd58b79985

Wait for applications ready:

kubectl wait --for=condition=ready --timeout=1m pod -l app=nsc-memif -n ns-memif2kernel

kubectl wait --for=condition=ready --timeout=1m pod -l app=nse-kernel -n ns-memif2kernel

Ping from NSC to NSE:

result=$(kubectl exec deployments/nsc-memif -n "ns-memif2kernel" -- vppctl ping 172.16.1.100 repeat 4)
echo ${result}
! echo ${result} | grep -E -q "(100% packet loss)|(0 sent)|(no egress interface)"

Ping from NSE to NSC:

kubectl exec deployments/nse-kernel -n ns-memif2kernel -- ping -c 4 172.16.1.101

Cleanup

Delete ns:

kubectl delete ns ns-memif2kernel