Installation and Upgrade Guide > Container Orchestration Using Kubernetes > Pre-Configuration of the Runtime Environment (On-Premises/Private Cloud only): > Deploying TDV as a Cluster Mode Instance
 
Deploying TDV as a Cluster Mode Instance
This section describes how to deploy TDV as a cluster mode using the quick start script.
Refer to the section TDV Container Orchestration Architecture to understand the implementation of TDV Container Orchestration.
Example to run a TDV instance as a Cluster Mode
Run the following command to run TDV as a Cluster Mode:
$ ./run_tdv_helmchart.sh --set tdv.replicas=2,tdv.image=“<REPO_URL>/tdvk8s:8.5,tdv.cluster.externalIPs="{100.20.30.20}",tdv.cluster.loadBalancerSourceRanges="{100.20.30.0/12}"
You will see a log like the one below, indicating the number of pods that will be starting, the number of worker nodes in the cluster, the name of the worker node, and a series of elapsed times. When the pod is ready you will see a message indicating the which pod has started to run.
 
Request to start “2” TDV server pod(s).
Available worker nodes: “3”
Worker node names: “tdv-k8s-1 tdv-k8s-2 tdv-k8s-3”
 
Waiting for TDV Server pod “tdv-0” to start.
............................ (30s elapsed)
............................ (60s elapsed)
............................ (90s elapsed)
........................... (120s elapsed)
........................... (150s elapsed)
........................... (180s elapsed)
........................... (210s elapsed)
........................... (240s elapsed)
........................... (270s elapsed)
............................
TDV pod “tdv-0” is now running after 300s
Run the following command to check the status of a specific pod:
$ kubectl describe pod <pod name> -n tdv
After you see the output of run_tdv_helmchart.sh indicating that the pods and services are ready, then you can use the external IP to access your TDV service. If you want to setup a monitor external IP for one of the TDV pods in your TDV cluster then you have to run “run_tdv_haproxy.sh” to create a service that exposes your TDV pod for access with an external IP. Note that you can only setup one TDV HAProxy service at a time because the service is tied to the TDV pod and requires a unique external IP for its service. Refer to section Installing the TDV HAProxy Service using the Quick Start Script for instructions on using this script “run_tdv_haproxy.sh”.