Create an Internal Load Balancer (Lab GSP216)
Task 1. Configure HTTP and health check firewall rules
- Explored the my-internal-app network.
The network my-internal-app with subnet-a and subnet-b along with firewall rules for RDP, SSH, and ICMP traffic have been configured for you.
- Created the HTTP firewall rule.
- Created the health check firewall rules.
Task 2. Configure instance templates and create instance groups
- Configured the first instance template
- Configured the next instance template.
- Created the managed instance groups.
Group 1
Group 2
- Verified the backends.
Notice two instances that start with
instance-group-1andinstance-group-2.These instances are in separate zones and their internal IP addresses are part of the subnet-a and subnet-b CIDR blocks.
Click Create instance.
- After creation of utility-vm, click SSH to launch a terminal and connect.
Note : The curl commands demonstrate that each VM instance lists the Client IP and its own name and location. This will be useful when verifying that the Internal Load Balancer sends traffic to both backends.
Task 3. Configure the Internal Load Balancer
Serach Load balancing and open the page.
Click Create load balancer
Configured the regional backend service
Click on Backend configuration.
- For Health Check, select Create a health check.
Configure the frontend
Click on Frontend configuration.
select subnet-b.
for Internal IP - Under IP address select Create IP address.
- Click on Review and finalize.
- Click on create.
Task 4. Test the Internal Load Balancer
Access the Internal Load Balancer
For utility-vm, click SSH to launch a terminal and connect.
To verify that the Internal Load Balancer forwards traffic, run the following command:
curl 10.10.30.5
Note: As expected, traffic is forwarded from the Internal Load Balancer (10.10.30.5) to the backend.
- Run the same command a couple more times.
In the output, you should be able to see responses from instance-group-1 in Zone and instance-group-2 in the different zone of same region.