This example shows that NSC and NSE on the one node can find each other.
NSC and NSE are using the kernel
mechanism to connect to its local forwarder.
Diagram:
Make sure that you have completed steps from memory setup.
Deploy NSC and NSE:
kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Kernel2Kernel?ref=34e1f2476dbc21097ab0a50348a966fd58b79985
Wait for applications ready:
kubectl wait --for=condition=ready --timeout=1m pod -l app=alpine -n ns-kernel2kernel
kubectl wait --for=condition=ready --timeout=1m pod -l app=nse-kernel -n ns-kernel2kernel
Ping from NSC to NSE:
kubectl exec pods/alpine -n ns-kernel2kernel -- ping -c 4 172.16.1.100
Ping from NSE to NSC:
kubectl exec deployments/nse-kernel -n ns-kernel2kernel -- ping -c 4 172.16.1.101
Delete ns:
kubectl delete ns ns-kernel2kernel