These are the frequently asked questions for Vultr Load Balancer.
The Vultr Load Balancer is a fully managed solution designed to distribute incoming traffic across multiple backend servers to ensure high availability and reliability of your applications. It simplifies traffic management by automating the distribution process and offering several features.
Vultr Load Balancers support two algorithms:
Yes, Vultr Load Balancers allow you to configure internal firewall rules similar to Vultr’s stand-alone Firewall. These rules can restrict traffic based on IPs or ranges. You can set firewall rules on the Add Load Balancer page and the Networking menu of the Manage Load Balancer page.
Forwarding rules map a Load Balancer port to an Instance port. You can configure rules for HTTP, HTTPS, or TCP protocols. For instance, you might forward HTTP port 80 on the load balancer to port 8000 on the instances. You can create up to 15 forwarding rules.
Metrics are available on the Metrics tab of the Manage Load Balancer page after the load balancer has been running for a few minutes. Metrics provide insights into performance and health.
The VPC Network option allows you to forward traffic via a Virtual Private Cloud (VPC) instead of the public network if your instances are attached to a VPC. Changing the network interface will briefly disrupt connections.
The default interval between health checks is 15 seconds. You can adjust this interval when configuring health checks on the Add Load Balancer page or the Health Checks menu of the Manage Load Balancer page.
When setting firewall rules on a Vultr Load Balancer, ports 65300 to 65310 are reserved for internal use by the load balancer and cannot be configured for traffic forwarding.
You can create a maximum of 15 forwarding rules for each Load Balancer.
If an instance fails health checks:
The Vultr API provides endpoints to: