TDV Container Orchestration Architecture
There are two types of TDV Server deployment in a Kubernetes environment:
Single TDV Deployment Mode:
In the single TDV deployment mode, each TDV pod consists of a single TDV container that has the TDV repo, cache and the Server.
There is one external IP exposed to provide access to your single TDV deployment mode pod. That IP can be used to access your TDV pod via port 9400 with any TDV client.
ClusterTDV Deployment Mode:
In the cluster TDV deployment mode, each TDV pod consists of a single TDV container that has the TDV repo, cache and the Server.
There are two external IPs exposed to provide TDV client access and direct TDV pod access for monitoring purposes.
Client External IP
This IP is for TDV clients that need to access the TDV services and do not care which TDV pod that handles the request.
It is connected to a Kubernetes Load Balancer service which means requests will get sent to a random TDV pod.
Monitor External IP
This IP is for TDV clients that need to monitor one specific TDV pod for administrative purposes (e.g. TDV Web Manager, TDV Drill console, etc).
It is connected to a Kubernetes Load Balancer service and only routes requests to a specific TDV pod. One uses the TDV HAProxy service to configure this IP to map to a specific TDV pod.
