Skip to content

Latest commit

 

History

History
42 lines (31 loc) · 1.15 KB

README.md

File metadata and controls

42 lines (31 loc) · 1.15 KB
Raw

Test kernel to IP to kernel connection

This example shows that NSC and NSE on the different nodes could find and work with each other.

NSC and NSE are using the kernel mechanism to connect to its local forwarder. Forwarders are using the IP payload to connect with each other.

Requires

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

Run

Deploy NSC and NSE:

kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Kernel?ref=aad7c26ad32fb4c3b515179bbe85d59c811c52f1

Wait for applications ready:

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

Ping from NSC to NSE:

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

Ping from NSE to NSC:

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

Cleanup

Delete ns:

kubectl delete ns ns-kernel2ip2kernel