6.3.5. Deploy NVMesh Pods

Deploying the pods implementing NVMesh is typically done using the following command from the nvmesh-operator directory mentioned in the previous sections.

kubectl apply -f deploy/samples/nvmesh/nvmesh_v1_AKS_tcp.yaml

or as follows if the repository has not been cloned:

kubectl apply -f https://raw.githubusercontent.com/Excelero/nvmesh-k8s-operator/v0.8.0/deploy/samples/nvmesh/nvmesh_v1_AKS_tcp.yaml

The built-in sample deploys using PremiumSSD managed disks for storing system configuration information.
Other than changing the cluster name, it is recommended to contact Excelero Technical Support for any other changes.

Verify the pods have started using the following command. It may take a few minutes.

kubectl get pods --watch

or using

watch -d kubectl get pods -o wide

Sample output:

server:~/AKS_example/openshift-operator$ kubectl get pods
NAME                               READY   STATUS    RESTARTS   AGE
mongo-0                            1/1     Running   0          33m
nvmesh-client-dp84f                1/1     Running   0          85s
nvmesh-client-tj9pw                1/1     Running   0          98s
nvmesh-client-zvmq2                1/1     Running   0          92s
nvmesh-csi-controller-0            4/4     Running   0          33m
nvmesh-csi-node-driver-2rgtx       2/2     Running   0          85s
nvmesh-csi-node-driver-92cn6       2/2     Running   0          92s
nvmesh-csi-node-driver-98v9b       2/2     Running   0          98s
nvmesh-management-0                1/1     Running   0          33m
nvmesh-mcs-agent-ffbls             2/2     Running   0          91s
nvmesh-mcs-agent-kdtsq             2/2     Running   0          85s
nvmesh-mcs-agent-ltx7q             2/2     Running   0          98s
nvmesh-operator-8548f59f4c-n4cmg   1/1     Running   0          33m
nvmesh-target-kk8gh                3/3     Running   0          73s
nvmesh-target-vcbd9                3/3     Running   0          61s
nvmesh-target-zpmbt                3/3     Running   0          67s