High performance, scalable load balancing on Google Cloud Platform. Scale your applications on Google Compute Engine from zero to full-throttle with Google Cloud Load Balancing, with no pre-warming needed. Distribute your load-balanced compute resources in single or multiple regions, close to your users and to meet your high availability requirements. Cloud Load Balancing can put your resources behind a single anycast IP and scale your resources up or down with intelligent Autoscaling.
Pattern | Trigger Node | Attribute | Condition | Argument |
---|---|---|---|---|
RESTAPIs | DiscoveredCloudAPIResultList | discovery_method | = | Google.Compute.ForwardingRules.List |
RESTAPIs | Comments |
---|---|
Google.Compute.GlobalForwardingRules.List | |
Google.Compute.TargetHttpProxies.List | |
.Google.Compute.TargetHttpsProxies.List | |
Google.Compute.UrlMaps.List | |
Google.Compute.BackendServices.List | |
Google.Compute.RegionBackendServices.List | |
Google.Compute.TargetPools.List |
NodeKind | Attribute | Default value/Comments |
---|---|---|
LoadBalancerService | type | Google Load Balancer |
key | <id> | |
name | <name> | |
cloud | true | |
project | ||
project_name | ||
availability_zones | ||
port | ||
protocol | ||
scheme | ||
ip_version | ||
ip_addr | ||
network | ||
subnetwork |
NodeKind | Attribute | Default value/Comments |
---|---|---|
LoadBalancerPool | type | Google Backend Service |
key | <id> | |
name | <name> | |
cloud | true | |
project | ||
project_name | ||
availability_zones | ||
port | ||
protocol | ||
network | ||
subnetwork | ||
session_affinity | ||
failover_ratio | ||
connection_draining | ||
protocol | ||
port_name | ||
enable_CDN | ||
scheme | ||
timeout_sec | ||
affinity_cookie_ttl_sec | ||
description | ||
max_utilization | ||
capacity_scaler | ||
balancing_mode |
NodeKind | Attribute | Default value/Comments |
---|---|---|
LoadBalancerMember | ||
name | <name> | |
cloud | true | |
project | ||
project_name |
Testing
This pattern was tested against a live installation .
Most information used to develop the pattern came from analyzing a live installation of the product.
There are no known open issues with this pattern.