Configuring HAProxy Load Balancer

In the portal, the HA Proxy type load balancer is configured through the controllers page in the load balancer modal.

To get there:

Environments from the main, left-hand navigation.
Select the environment from the first column.
Scroll down to the services tile, and click on the manage tab of the load balancer.
Select the Controllers page.

On the controllers page, the toggle for Enable Custom Config must be enabled to make changes to the load balancer config.

Configuring The Load Balancer - Ingress

The load balancer is configurable directly from the interface. You are able to adjust modes, create specific port configurations, and override timeout settings with ease.

Click the Environments link in the navigation menu to the left.
Select the environment who's load balancer you wish to configure from the list.
Click the "Load Balancer" tab at the top of the page.
Enable "Custom Config" by toggling the switch in the upper right hand corner of the form. This will allow you to override the Cycle defaults with custom settings. Disabling custom config after updating the load balancer will cause it to revert back to Cycle's default config.

Default Config

The load balancer comes with a "default config", which is how it treats all ports (that aren't 80 or customized otherwise). These settings will be applied to all ports that aren't explicitly defined in this configuration. The mode cannot be changed for the default config.

Frontend Options

Frontend configuration options are related to how inbound traffic is treated.

Field	Description
Mode (TCP)	Traffic is forwarded by port without any parsing or additional manipulation.
Mode (HTTP)	Traffic is treated as web traffic. If a LINKED record is configured for a container exposing this port, the domain will be parsed and forwarded to the proper container, allowing multiple services to run on port 80 in the same environment.
Max Connections	The number of simultaneous connections that can be processed at a time.
Client Timeout	The number of seconds the load balancer will wait for a response from a client before disconnecting.
Client Finish Timeout	The number of milliseconds the load balancer will wait for a client to send data when one direction is already closed.
HTTP Keep Alive [HTTP mode only]	The number of milliseconds the load balancer will wait for a new HTTP request to start coming after a response was sent.
HTTP Request Timeout [HTTP mode only]	The number of milliseconds the load balancer will wait for a complete HTTP request.

Backend Options

Backend configuration options are related to how the load balancer handles and routes connections

Field	Description
Balance	How connections are balanced across your container instances.
Server Request Timeout	The number of seconds the load balancer will wait for a response from the container instance. See the HAProxy Docs for more information.
Server Finish Timeout	The number of milliseconds the load balancer will wait for the server to send data when one direction is already closed. See the HAProxy Docs for more information.
Connection Timeout	The number of milliseconds the load balancer will wait for a successful connection to a container instance. See the HAProxy Docs for more information.
Queue Timeout	The number of milliseconds the load balancer will hold connections in a queue when the maximum number of connections has been reached. See the HAProxy Docs for more information.
Tunnel Timeout	The number of milliseconds the load balancer will allow for inactivity on a bidirectional tunnel. See the HAProxy Docs for more information.

Balance Options

Field	Description
Round Robin	Each container instance is used in turns.
Static Round Robin	Each container instance is used in turns, but is faster than Round Robin at the expense of being less dynamic.
Least Connection	Routes traffic to the instance with the least number of active connections.
First	Routes traffic to the first available instance.
Source	The same client IP always reaches the same container instance as long as no instance goes down or up.