This document provides general information regarding the F5 Integration for Cloud Foundry. For deployment and usage instructions, please refer to the guides below.
The BIG-IP Controller for Cloud Foundry (
cf-bigip-ctlr) lets you use your F5 BIG-IP device as an Application Delivery Controller (ADC) in Cloud Foundry, serving North-South traffic. You can use the BIG-IP Controller with Cloud Foundry or Pivotal Cloud Foundry (PCF).
The BIG-IP Controller is a Docker container-based application that runs on a Cloud Foundry Diego cell.
Once the BIG-IP Controller for Cloud Foundry is running, it
The F5 Integration for Cloud Foundry’s documentation set assumes that you:
The BIG-IP Controller configurations are “global”, meaning a single set of configurations apply to all of the pools/pool members created for Cloud Foundry Routes and Applications. The Cloud Foundry Application Manifest file is the means via which you can identify the BIG-IP policies, profiles, etc., you want to apply.
Some policy and profile configurations only apply to L7 (HTTP) virtual servers. See the cf-bigip-ctlr configuration parameters table for more information.
In Cloud Foundry, the Gorouter component routes all incoming L7 traffic. The TCP Router component routes all incoming L4 traffic. Similarly, the BIG-IP Controller uses Cloud Foundry’s routing tables to direct traffic to the correct virtual machine(s) for a requested application. The BIG-IP Controller watches the NATS bus and Routing API for route updates; when the Controller discovers changes, it configures the BIG-IP device(s) accordingly.
When you deploy a new application with a mapped HTTP route in Cloud Foundry, the BIG-IP Controller automatically creates a BIG-IP pool, pool members, and traffic policy rule for the new route. When you deploy a new application with a mapped TCP route in Cloud Foundry, the BIG-IP Controller automatically creates a BIG-IP virtual server, pool, and pool members for the new route.
You can apply existing BIG-IP health monitors, policies, profiles, and SSL profiles to the virtual server(s) and pools the BIG-IP Controller creates for HTTP routes (these configurations do not apply to objects managed for TCP routes). Likewise, you can select any BIG-IP load balancing mode (applies to both HTTP and TCP pools). Define the cf-bigip-ctlr configuration parameters in your Application Manifest.