Power off, start, or upgrade a load balancer

The Actions menu in a load balancer’s row in the Load Balancers list powers it off, starts it, and upgrades its plan. A powered-off load balancer serves no traffic and keeps all its settings, and it comes back with the same settings when you start it. It also keeps its public IP through powering off, starting, and upgrading. To move to a plan with more vCPU and RAM, power the load balancer off, then upgrade it.

Billing continues while the load balancer is powered off. On hourly billing, the charges stop only when you delete the load balancer; see Delete a load balancer. A committed load balancer is charged for its whole period; see Use committed billing for a load balancer.

Before you begin

• The load balancer has left Creating, Deploying, Upgrading, or Deleting. Actions is available in every other status.
• Your role in the project has the update permission for Load Balancers.
• For an upgrade, the load balancer is on hourly billing. A committed load balancer keeps its plan for the whole committed period.

Power off the load balancer

Powering off stops all traffic through the load balancer until you start it again. Powering off a load balancer whose disk is busy can corrupt its data.

1. In MyAccount, under Compute, click Load Balancers. In the load balancer’s row, open Actions, and click Power Off.
2. Tick I understand the risk, and want to power off the Load Balancer, which ends with the load balancer’s name.
3. Click Power Off.

The load balancer reads Powered off, with Your load balancer is powered off successfully. While it is powered off, you can start it, upgrade it, or delete it. To change its settings, backend groups, or ACL rules, start it first.

Start the load balancer

1. In the load balancer’s row, open Actions, and click Start.
2. Confirm with Start.

Your load balancer is powered on successfully. shows, and the load balancer comes back with the same settings, backend groups, and rules, and serves traffic again.

Upgrade the plan

An upgrade moves the load balancer to a plan with more vCPU and RAM. Its disk keeps its size.

1. Power off the load balancer, and wait until it reads Powered off. While it is running, Upgrade Plan says Your need to power off your LB to upgrade plan.
2. In the load balancer’s row, open Actions, and click Upgrade Plan. Or, on its Info tab, click Upgrade Plan beside Plan Name.
3. Plans lists the plans larger than the current one, with their vCPU, RAM, Storage, and Price. For each plan’s Max Concurrent Connections, see the plan table in Create an Application Load Balancer: Choose the plan.
4. Compare the plans’ vCPU and RAM with your load, then click the plan you want. The upgrade starts as soon as you click it.

The load balancer reads Upgrading, with Your LB plan upgrade is in progress. LB will be upgraded within few minutes. The load balancer comes back with your settings applied.

MyAccount emails the account owner and the project’s members, apart from those with the billing role. The load balancer is then billed at the new plan’s price; see E2E’s pricing page.

The plan list offers only larger plans. To move to a smaller plan, create a new load balancer on it.

Check the load balancer

When the load balancer reads Running again, its Info tab shows the plan under Plan Name and its RAM and vCPU under Configuration. Open its address, and your application opens.

If it stays on Upgrading or Deploying, or an action is refused, see Troubleshooting Load Balancer. To run these actions from a script, see Perform Load Balancer Action in the API reference.