Skip to content

Latest commit

 

History

History
47 lines (35 loc) · 1.32 KB

File metadata and controls

47 lines (35 loc) · 1.32 KB

Test kernel to kernel connection with excluded prefixes

This example shows kernel to kernel example where we excluded 2 prefixes from provided IP prefix range.

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

Requires

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

Run

Create config map with excluded prefixes

kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes/configmap?ref=c91be29099fab1f8376d9ff90c858efd829de35e

Deploy NSC and NSE:

kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes?ref=c91be29099fab1f8376d9ff90c858efd829de35e

Wait for applications ready:

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

Ping from NSC to NSE:

kubectl exec pods/alpine -n ns-exclude-prefixes -- ping -c 4 172.16.1.200

Ping from NSE to NSC:

kubectl exec deployments/nse-kernel -n ns-exclude-prefixes -- ping -c 4 172.16.1.203

Cleanup

Delete ns:

kubectl delete configmap excluded-prefixes-config
kubectl delete ns ns-exclude-prefixes