Kernel2Memif

Test kernel to memif connection

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

NSC is using the kernel mechanism to connect to its local forwarder. NSE is using the memif 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/Kernel2Memif?ref=34e1f2476dbc21097ab0a50348a966fd58b79985

Wait for applications ready:

kubectl wait --for=condition=ready --timeout=1m pod -l app=alpine -n ns-kernel2memif

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

Ping from NSC to NSE:

kubectl exec pods/alpine -n ns-kernel2memif -- ping -c 4 172.16.1.100

Ping from NSE to NSC:

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

Cleanup

Delete ns:

kubectl delete ns ns-kernel2memif