This repo contains modules to perform load balancing on Google Cloud Platform (GCP) using Google Cloud Load Balancing.
If you want to quickly spin up a HTTP Load Balancer with multiple backends, you can run the example that is in the root of this repo. Check out the http-multi-backend example documentation for instructions.
This repo has the following folder structure:
-
root: The root folder contains an example of how to deploy a HTTP Load Balancer with multiple backends. See http-multi-backend example documentation for the documentation.
-
modules: This folder contains the main implementation code for this Module.
The primary modules are:
- http-load-balancer is used to create an HTTP(S) External Load Balancer using global forwarding rules.
- internal-load-balancer is used to create an Internal TCP/UDP Load Balancer using internal forwarding rules.
-
examples: This folder contains examples of how to use the submodules.
-
test: Automated tests for the submodules and examples.
Cloud Load Balancing is a fully distributed, software-defined, managed service for all your traffic. It is not an instance or device based solution, so you won’t be locked into physical load balancing infrastructure or face the HA, scale and management challenges inherent in instance based LBs. Cloud Load Balancing features include:
- HTTP(S) Load Balancing: HTTP(S) load balancing can balance HTTP and HTTPS traffic across multiple backend instances, across multiple regions.
- Network TCP/UDP Load Balancing: load balance external traffic.
- Internal TCP/UDP Load Balancing: load balance internal traffic.
- Seamless Autoscaling: Autoscaling helps your applications gracefully handle increases in traffic and reduces cost when the need for resources is lower.
- Cloud CDN Integration: Enabling Cloud CDN for HTTP(S) Load Balancing for optimizing application delivery for your users.
- Stackdriver Logging: Stackdriver Logging for load balancing logs all the load balancing requests sent to your load balancer.
You can learn more about Cloud Load Balancing in the official documentation.
This Module and its Submodules are maintained by Gruntwork. Read the Gruntwork Philosophy document to learn more about how Gruntwork builds production grade infrastructure code. If you are looking for help or commercial support, send an email to support@gruntwork.io.
Gruntwork can help with:
- Setup, customization, and support for this Module.
- Modules and submodules for other types of infrastructure, such as VPCs, Docker clusters, databases, and continuous integration.
- Modules and Submodules that meet compliance requirements, such as HIPAA.
- Consulting & Training on GCP, AWS, Terraform, and DevOps.
Contributions are very welcome! Check out the Contribution Guidelines for instructions.
This Module follows the principles of Semantic Versioning. You can find each new release, along with the changelog, in the Releases Page.
During initial development, the major version will be 0 (e.g., 0.x.y
), which indicates the code does not yet have a
stable API. Once we hit 1.0.0
, we will make every effort to maintain a backwards compatible API and use the MAJOR,
MINOR, and PATCH versions on each release to indicate any incompatibilities.
Please see LICENSE.txt for details on how the code in this repo is licensed.