The first part of this blog is to integrate Avi GSLB with Tanzu Service Mesh (TSM)

My Avi controller stays in a private network so it is not reachable from TSM Avi Connector. So I have to use “Connect via a proxy” option to establish the connectivity from TSM to Avi Controller.

VMware have implemented WebSockets proxy on all of the client Kubernetes clusters onboarded into TSM for this purpose. In this way, Tanzu Service Mesh can connect to the Avi controller through the client cluster, which should have connectivity to the Avi controller as well. Let us get our hands dirty now.

Step 1: Add Proxy Location label to my two clusters in TSM

<aside> 💡 Due to a known bug, you can’t add the label via TMC UI if the clusters have been onboard TMC.

</aside>

Step 2: Add Avi Integration

After the account was added. We will see the below:

Step 3. We need to create a TSM DNS config to use the account that defined in step 2.

After the DNS account was created. The DNS integration status changed to CONNECTED.