This section includes a diagram that explains the architecture of each TBSP node.
A Kubernetes Deployment manages all TBSP Pods in this application. Each Pod runs a single instance of TBSP.
All Pods are behind a Service object. This TBSP application is meant to be an internal database, and access to the TBSP instances is not authenticated by default. The TBSP service is also not exposed to external traffic. If you want to expose TBSP outside your cluster, you must configure authentication and other layers of protection, such as firewalls.
You can use the TBSP Service to discover the current number of Pods and their addresses.