This example shows that NSM keeps working after the Registry restart.
NSC and NSE are using the kernel mechanism to connect to its local forwarder.
Make sure that you have completed steps from basic or memory setup.
Deploy NSC and NSE:
kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-before-death?ref=aad7c26ad32fb4c3b515179bbe85d59c811c52f1Wait for applications ready:
kubectl wait --for=condition=ready --timeout=1m pod -l app=alpine -n ns-registry-restartkubectl wait --for=condition=ready --timeout=1m pod -l app=nse-kernel -n ns-registry-restartFind nsc and nse pods by labels:
NSC=$(kubectl get pods -l app=alpine -n ns-registry-restart --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}')NSE=$(kubectl get pods -l app=nse-kernel -n ns-registry-restart --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}')Ping from NSC to NSE:
kubectl exec pods/alpine -n ns-registry-restart -- ping -c 4 172.16.1.100Ping from NSE to NSC:
kubectl exec deployments/nse-kernel -n ns-registry-restart -- ping -c 4 172.16.1.101Find Registry:
REGISTRY=$(kubectl get pods -l app=registry -n nsm-system --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}')Restart Registry and wait for it to start:
kubectl delete pod ${REGISTRY} -n nsm-systemkubectl wait --for=condition=ready --timeout=1m pod -l app=registry -n nsm-systemApply a new client:
kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-after-death?ref=aad7c26ad32fb4c3b515179bbe85d59c811c52f1Wait for a new NSC to start:
kubectl wait --for=condition=ready --timeout=1m pod -l app=alpine-new -n ns-registry-restartPing from new NSC to NSE:
kubectl exec pods/alpine-new -n ns-registry-restart -- ping -c 4 172.16.1.102Ping from NSE to new NSC:
kubectl exec deployments/nse-kernel -n ns-registry-restart -- ping -c 4 172.16.1.103Delete ns:
kubectl delete ns ns-registry-restart