| title: | Configure load balancers |
|---|---|
| description: | Configure load balancers for your Deis Cluster |
For a one-node Deis cluster, there is one router and one controller, so load balancing is unnecessary. You can proceed with the next section: :ref:`configure-dns`.
On a multi-node cluster, however, there are probably multiple routers scheduled to the cluster, and these can potentially move hosts. Therefore, it is recommended that you configure a load balancer to operate in front of the Deis cluster to serve application traffic.
These ports need to be open on the load balancers:
- 80 (for application traffic and for API calls to the controller)
- 2222 (for traffic to the builder)
If you want to configure SSL termination on your load balancer, see :ref:`ssl-endpoints`.
A health check should be configured on the load balancer to send an HTTP request to /health-check at port 80 on all nodes in the Deis cluster. The health check endpoint returns an HTTP 200. This enables the load balancer to serve traffic to whichever hosts happen to be running the deis-router component at any moment.
The Deis provisioning scripts for EC2 automatically create an Elastic Load Balancer for your Deis
cluster. However, ELBs on EC2 have a default timeout of 60 seconds, which will disrupt a git push
when using Deis. You should manually increase this timeout to 1200 seconds to match the timeout
on the router and application unit files.
You'll need to create two load balancers on Rackspace, as follows:
Load Balancer 1
Port 80
Protocol HTTP
Health Monitoring -
Monitor Type HTTP
HTTP Path /health-check
Load Balancer 2
Virtual IP Shared VIP on Another Load Balancer (select Load Balancer 1)
Port 2222
Protocol TCP
The provisioning instructions for Google Compute Engine include steps to create a load balancer. It is not possible to change the timeout of the load balancer in Google Compute Engine at the moment.