Configuring TCP Routing in PAS
This topic describes how to enable the TCP routing feature in a Pivotal Application Service (PAS) deployment.
Breaking Change: If you have mutual TLS app identity verification enabled, Envoy only recognizes communications from the Gorouter. Therefore, TCP no longer works.
TCP Routing enables applications and services to be run on PCF that require inbound requests on non-HTTP protocols. Before enabling TCP Routing, review the Pre-Deployment Steps that describe required networking infrastructure changes.
TCP Routing is disabled by default. To enable this feature, go to Networking and select Enable TCP Routing.
In TCP Router IPs, enter the IP address(es) you would like assigned to the TCP Routers. The addresses must be within your subnet CIDR block. These will be the same IP addresses you configured your load balancer with in Pre-Deployment Steps, unless you configured DNS to resolve the TCP domain name directly to an IP you’ve chosen for the TCP router. You can enter multiple values as a comma-delimited list or as a range. For example,
For TCP Routing Ports, enter a single port or a range of ports for the load balancer to forward to. This field does not accept a comma-delimited list. If you configured AWS for PCF manually, enter
1024-1123which corresponds to the rules you created for
- To support multiple TCP routes, Pivotal recommends allocating multiple ports.
- To allocate a list of ports rather than a range:
- Enter a single port in the TCP Routing Ports field.
- After deploying PAS, follow the directions in Configuring a List of TCP Routing Ports to add TCP routing ports using the cf CLI.
If you are deploying PCF to AWS, Azure or GCP, add the name of your load balancer to TCP Router job of the Resource Config page of the PAS tile. For more information, see the PCF installation documentation for you IaaS.
If you want to disable TCP routing after enabling it, click Select this option if you prefer to enable TCP Routing at a later time.
Manually remove the TCP routing domain.