Skip to content

Latest commit

 

History

History

Kernel2Kernel_dual_stack

Test kernel to kernel connection

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

NSC and NSE are using the kernel mechanism to connect to its local forwarder.

Run

Deploy NSC and NSE:

kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/Kernel2Kernel_dual_stack?ref=7d9096404c273143d4925deaabb991e705909289

Wait for applications ready:

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

Check connectivity:

kubectl exec pods/alpine -n ns-kernel2kernel-dual-stack -- ping -c 4 2001:db8::

Check connectivity:

kubectl exec deployments/nse-kernel -n ns-kernel2kernel-dual-stack -- ping -c 4 2001:db8::1

Ping from NSC to NSE:

kubectl exec pods/alpine -n ns-kernel2kernel-dual-stack -- ping -c 4 172.16.1.100

Ping from NSE to NSC:

kubectl exec deployments/nse-kernel -n ns-kernel2kernel-dual-stack -- ping -c 4 172.16.1.101

Cleanup

Delete ns:

kubectl delete ns ns-kernel2kernel-dual-stack