Using Your Own Load Balancer

This guide describes how to use your own load balancer and forward traffic to your Elastic Runtime router IP address.

Pivotal Cloud Foundry (PCF) deploys with a single instance of HAProxy for use in lab and test environments. Production environments should use a highly-available customer-provided load balancing solution that does the following:

  • Provides load balancing to each of the PCF Router IPs
  • Supports SSL termination with wildcard DNS location
  • Adds appropriate x-forwarded-for and x-forwarded-proto HTTP headers to incoming requests
  • (Optional) Supports WebSockets

Note: Application logging with Loggregator requires WebSockets. To use another logging service, see the Using Third-Party Log Management Services topic.

Prerequisites

To integrate your own load balancer with PCF, you must ensure the following:

  • WebSocket connections are not blocked for Loggregator functionality.
  • The load balancer must be able to reach the Gorouter IP addresses.

Follow the instructions below to use your own load balancer.

Step 1: Deploy PCF Installation VM

Deploy a PCF Installation virtual machine. See the topic Deploying Operations Manager to vSphere for more information.

Step 2: Register PCF IP Address

In your load balancer, register the IP addresses that you assigned to PCF.

Step 3: Configure Pivotal Ops Manager and Ops Manager Director

Configure your Pivotal Operations Manager and Ops Manager Director as described in Installing Pivotal Cloud Foundry, then add Elastic Runtime.

Do not click Install after adding Elastic Runtime.

Step 4: Configure Networking

Complete the Networking configuration page in Elastic Runtime. Load balancer configuration in Elastic Runtime varies depending on which IaaS you are using for PCF. See the configuration procedure for your deployment IaaS:

Step 5: Finalize Changes

  1. Return to the Ops Manager Installation Dashboard

  2. Click Install.

Create a pull request or raise an issue on the source for this page in GitHub