Setting up a load balancers
Step 3 : Setting up a load balancers
During initial deployment (i.e., the process that was completed before you began following the instructions in this document), an instance group for Reblaze was created. In this step, you will attach this group to an HTTP/S or TCP load balancing service, as a backend of the service.
This is a three-task process:
Create the load balancer
Create the backend service
Attach the backend (i.e., the Reblaze instance group)
Task 1: Create a load balancer
In your Google cloud console, go to Network services → Load Balancing.
Creating a load balancer
Click on “Create load balancer.” Choose to “Start configuration” on the appropriate type:
The HTTP/S load balancer supports ports 80, 8080, and 443, and is the appropriate type for most Reblaze customers.
If you need non-standard ports, then you will need to use the TCP load balancer instead.
Choosing HTTP/S
Task 2: Create the backend service
Creating a load balancer backend service
Typical Backend Service Example
We recommend creating a health check to ensure that instances are added when appropriate.
Task 3: Create the backend
As shown above, while creating the backend service, a new backend will also be created. This backend is how you attach the Reblaze instance group (created previously) to the backend service.
It is beyond the scope of this document to describe all the possible settings here, but they should be fairly straightforward. More information about Google’s load balancing can be found at https://cloud.google.com/compute/docs/load-balancing/. If you have any questions, feel free to contact us at support@reblaze.com.
When you are finished with the backend setup, choose “Frontend configuration” to change the IP address from “Ephemeral” to the one associated with the backend. You’ll need this IP in the next step.
Task 4: Create HTTPS load balancer
Last updated
