local-nsm-system-restart

Nsm system restart (local case)

This example shows that NSM keeps working after restarting all management resources.

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

Requires

Make sure that you have completed steps from basic.

Run

Deploy NSC and NSE:

kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsm-system-restart?ref=aad7c26ad32fb4c3b515179bbe85d59c811c52f1

Wait for applications ready:

kubectl wait --for=condition=ready --timeout=1m pod -l app=alpine -n ns-local-nsm-system-restart

kubectl wait --for=condition=ready --timeout=1m pod -l app=nse-kernel -n ns-local-nsm-system-restart

Ping from NSC to NSE:

kubectl exec pods/alpine -n ns-local-nsm-system-restart -- ping -c 4 172.16.1.100

Ping from NSE to NSC:

kubectl exec deployments/nse-kernel -n ns-local-nsm-system-restart -- ping -c 4 172.16.1.101

Restart nsm-system:

kubectl delete mutatingwebhookconfiguration nsm-mutating-webhook
kubectl delete ns nsm-system

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

Ping from NSC to NSE:

kubectl exec pods/alpine -n ns-local-nsm-system-restart -- ping -c 4 172.16.1.100

Ping from NSE to NSC:

kubectl exec deployments/nse-kernel -n ns-local-nsm-system-restart -- ping -c 4 172.16.1.101

Cleanup

Delete ns:

kubectl delete ns ns-local-nsm-system-restart