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.
Make sure that you have completed steps from basic or memory or ipsec mechanism setup.
Deploy NSC and NSE:
kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Kernel?ref=0e8c3ce7819f0640d955dc1136a64ecff2ae8c56
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
Delete ns:
kubectl delete ns ns-kernel2ip2kernel