Client Connections
After your servers are up and running, you can connect the client applications. Client connections depend on where they are hosted. Clients running in pods within the same Kubernetes cluster are in-cluster clients. They use a Kubernetes native service infrastructure to connect to Apache Pulsar. Clients hosted outside the Kubernetes cluster, for example, on-premises or a different region, need additional setup.
In-cluster Client Access
For client applications in the same Kubernetes cluster, the connection URL is Client TCP URL on the details card of the capability that you have provisioned. It applies to TIBCO BusinessWorks™ Container Edition or TIBCO Flogo® applications deployed in the same or other data planes inside the same Kubernetes cluster.
This URL uses a Kubernetes service that maps the proxy pods as described in the Apache Pulsar documentation.
Off-cluster Client Access
Enabling Apache Pulsar access for clients running outside the Kubernetes cluster requires setting up a TCP load balancer (or TCP-enabled ingress controller). Vendor instructions are required for this setup as each vendor and load balancer option requires different setup details. For common examples, see the Microsoft Azure documentation and the Amazon Web Services documentation.
The preferred setup uses TLS termination at the load-balancer or ingress controller, and connects to the Apache Pulsar Client TCP service port. You can use this setup to manage publicly rooted certificates of vendors, avoiding the need to distribute certificates to individual pods.