vl3-scale-from-zero

Test automatic scale from zero

This example shows that vL3-NSEs can be created on the fly on NSC requests. This allows effective scaling for endpoints. The requested endpoint will be automatically spawned on the same node as NSC, allowing the best performance for connectivity.

Run

Create test namespace:

kubectl create ns ns-vl3-scale-from-zero

Deploy NSC and supplier:

kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-scale-from-zero?ref=58a90eb58a3e06f02cbd99c221b35327488025cc

Wait for applications ready:

kubectl wait -n ns-vl3-scale-from-zero --for=condition=ready --timeout=1m pod -l app=nse-supplier-k8s

kubectl wait -n ns-vl3-scale-from-zero --for=condition=ready --timeout=1m pod -l app=nsc-kernel

kubectl wait -n ns-vl3-scale-from-zero --for=condition=ready --timeout=1m pod -l app=nse-vl3-vpp

Find all nscs:

nscs=$(kubectl  get pods -l app=nsc-kernel -o go-template --template="{{range .items}}{{.metadata.name}} {{end}}" -n ns-vl3-scale-from-zero) 
[[ ! -z $nscs ]]

Ping each client by each client:

for nsc in $nscs 
do
    ipAddr=$(kubectl exec -n ns-vl3-scale-from-zero $nsc -- ifconfig nsm-1)
    ipAddr=$(echo $ipAddr | grep -Eo 'inet addr:[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}'| cut -c 11-)
    for pinger in $nscs
    do
        echo $pinger pings $ipAddr
        kubectl exec $pinger -n ns-vl3-scale-from-zero -- ping -c4 $ipAddr
    done
done

Ping each vl3-nse by each client. Note: By default we're using ipam prefix is 169.254.0.0/16 and client prefix len is 24. We also have two vl3 nses in this example. So we are expect to have a two vl3 addresses: 169.254.0.0 and 169.254.1.0 that should be accessible by each client.

for nsc in $nscs 
do
    echo $nsc pings nses
    kubectl exec -n ns-vl3-scale-from-zero $nsc -- ping 169.254.0.0 -c4
    kubectl exec -n ns-vl3-scale-from-zero $nsc -- ping 169.254.1.0 -c4
done

Cleanup

Delete namespace:

kubectl delete ns ns-vl3-scale-from-zero