FloatingKernel2Vxlan2Kernel

Floating interdomain kernel2vxlan2kernel example

This example shows that NSC can reach NSE registered in floating registry.

NSC and NSE are using the kernel mechanism to connect to its local forwarder. Forwarders are using the vxlan mechanism to connect with each other.

NSE is registering in the floating registry.

Requires

Make sure that you have completed steps from interdomain

Run

1. Prepare cluster2

Switch to cluster2:

export KUBECONFIG=$KUBECONFIG2

Create test namespace:

NAMESPACE1=($(kubectl create -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/94bde617f7939b9fd990840e80a6f2124e1c8e83/examples/interdomain/usecases/namespace.yaml)[0])
NAMESPACE1=${NAMESPACE1:10}

Create kustomization file:

cat > kustomization.yaml <<EOF
---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

namespace: ${NAMESPACE1}

bases:
- https://github.com/networkservicemesh/deployments-k8s/apps/nse-kernel?ref=94bde617f7939b9fd990840e80a6f2124e1c8e83

patchesStrategicMerge:
- patch-nse.yaml
EOF

Create NSE patch:

cat > patch-nse.yaml <<EOF
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nse-kernel
spec:
  template:
    metadata:
      annotations:
        registration-name: [email protected]
    spec:
      containers:
        - name: nse
          env:
          - name: NSM_NAME
            valueFrom:
              fieldRef:
                fieldPath: metadata.annotations['registration-name']
          - name: NSM_CIDR_PREFIX
            value: 172.16.1.2/31
          - name: NSM_SERVICE_NAMES
            value: [email protected]
EOF

Deploy NSE:

kubectl apply -k .

Find NSE pod by labels:

NSE=$(kubectl get pods -l app=nse-kernel -n ${NAMESPACE1} --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}')
[[ ! -z $NSE ]]

2. Prepare cluster1

Switch to cluster1:

export KUBECONFIG=$KUBECONFIG1

Create test namespace:

NAMESPACE2=($(kubectl create -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/94bde617f7939b9fd990840e80a6f2124e1c8e83/examples/interdomain/usecases/namespace.yaml)[0])
NAMESPACE2=${NAMESPACE2:10}

Create kustomization file:

cat > kustomization.yaml <<EOF
---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

namespace: ${NAMESPACE2}

bases:
- https://github.com/networkservicemesh/deployments-k8s/apps/nsc-kernel?ref=94bde617f7939b9fd990840e80a6f2124e1c8e83

patchesStrategicMerge:
- patch-nsc.yaml
EOF

Create NSC patch:

cat > patch-nsc.yaml <<EOF
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nsc-kernel
spec:
  template:
    spec:
      containers:
        - name: nsc
          env:
            - name: NSM_NETWORK_SERVICES
              value: kernel://[email protected]/nsm-1
EOF

Deploy NSC:

kubectl apply -k .

Wait for applications ready:

kubectl wait --for=condition=ready --timeout=5m pod -l app=nsc-kernel -n ${NAMESPACE2}

Find NSC pod by labels:

NSC=$(kubectl get pods -l app=nsc-kernel -n ${NAMESPACE2} --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}')

3. Ping from NSC to NSE:

Switch to cluster1:

export KUBECONFIG=$KUBECONFIG1

kubectl exec ${NSC} -n ${NAMESPACE2} -- ping -c 4 172.16.1.2

Switch to cluster2:

export KUBECONFIG=$KUBECONFIG2

Ping from NSE to NSC:

kubectl exec ${NSE} -n ${NAMESPACE1} -- ping -c 4 172.16.1.3

Cleanup

1. Cleanup resources for cluster2:

export KUBECONFIG=$KUBECONFIG2

kubectl delete ns ${NAMESPACE1}

2. Cleanup resources for cluster1:

export KUBECONFIG=$KUBECONFIG1

kubectl delete ns ${NAMESPACE2}