RegionBackendService
A Region Backend Service defines a regionally-scoped group of virtual machines that will serve traffic for load balancing.
To get more information about RegionBackendService, see:
- API documentation
- How-to Guides
Create a RegionBackendService Resource
new RegionBackendService(name: string, args: RegionBackendServiceArgs, opts?: CustomResourceOptions);def RegionBackendService(resource_name, opts=None, affinity_cookie_ttl_sec=None, backends=None, circuit_breakers=None, connection_draining_timeout_sec=None, consistent_hash=None, description=None, failover_policy=None, health_checks=None, load_balancing_scheme=None, locality_lb_policy=None, log_config=None, name=None, network=None, outlier_detection=None, port_name=None, project=None, protocol=None, region=None, session_affinity=None, timeout_sec=None, __props__=None);func NewRegionBackendService(ctx *Context, name string, args RegionBackendServiceArgs, opts ...ResourceOption) (*RegionBackendService, error)public RegionBackendService(string name, RegionBackendServiceArgs args, CustomResourceOptions? opts = null)- name string
- The unique name of the resource.
- args RegionBackendServiceArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- opts ResourceOptions
- A bag of options that control this resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args RegionBackendServiceArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args RegionBackendServiceArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
RegionBackendService Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Programming Model docs.
Inputs
The RegionBackendService resource accepts the following input properties:
- Health
Checks string The set of URLs to HealthCheck resources for health checking this RegionBackendService. Currently at most one health check can be specified, and a health check is required.
- int
Lifetime of cookies in seconds if session_affinity is GENERATED_COOKIE. If set to 0, the cookie is non-persistent and lasts only until the end of the browser session (or equivalent). The maximum allowed value for TTL is one day. When the load balancing scheme is INTERNAL, this field is not used.
- Backends
List<Region
Backend Service Backend Args> The set of backends that serve this RegionBackendService. Structure is documented below.
- Circuit
Breakers RegionBackend Service Circuit Breakers Args Settings controlling the volume of connections to a backend service. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- Connection
Draining intTimeout Sec Time for which instance will be drained (not accept new connections, but still work to finish started).
- Consistent
Hash RegionBackend Service Consistent Hash Args Consistent Hash-based load balancing can be used to provide soft session affinity based on HTTP headers, cookies or other properties. This load balancing policy is applicable only for HTTP connections. The affinity to a particular destination host will be lost when one or more hosts are added/removed from the destination service. This field specifies parameters that control consistent hashing. This field only applies when all of the following are true -
- Description string
An optional description of this resource. Provide this property when you create the resource.
- Failover
Policy RegionBackend Service Failover Policy Args Policy for failovers. Structure is documented below.
- Load
Balancing stringScheme Indicates what kind of load balancing this regional backend service will be used for. A backend service created for one type of load balancing cannot be used with the other(s).
- Locality
Lb stringPolicy The load balancing algorithm used within the scope of the locality. The possible values are - ROUND_ROBIN - This is a simple policy in which each healthy backend is selected in round robin order. LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests. RING_HASH - The ring/modulo hash load balancer implements consistent hashing to backends. The algorithm has the property that the addition/removal of a host from a set of N hosts only affects 1/N of the requests. RANDOM - The load balancer selects a random healthy host. ORIGINAL_DESTINATION - Backend host is selected based on the client connection metadata, i.e., connections are opened to the same address as the destination address of the incoming connection before the connection was redirected to the load balancer. MAGLEV - used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2.- Log
Config RegionBackend Service Log Config Args This field denotes the logging options for the load balancer traffic served by this backend service. If logging is enabled, logs will be exported to Stackdriver. Structure is documented below.
- Name string
Name of the cookie.
- Network string
The URL of the network to which this backend service belongs. This field can only be specified when the load balancing scheme is set to INTERNAL.
- Outlier
Detection RegionBackend Service Outlier Detection Args Settings controlling eviction of unhealthy hosts from the load balancing pool. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- Port
Name string A named port on a backend instance group representing the port for communication to the backend VMs in that group. Required when the loadBalancingScheme is EXTERNAL, INTERNAL_MANAGED, or INTERNAL_SELF_MANAGED and the backends are instance groups. The named port must be defined on each backend instance group. This parameter has no meaning if the backends are NEGs. API sets a default of “http” if not given. Must be omitted when the loadBalancingScheme is INTERNAL (Internal TCP/UDP Load Balancing).
- Project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- Protocol string
The protocol this RegionBackendService uses to communicate with backends. The default is HTTP. NOTE: HTTP2 is only valid for beta HTTP/2 load balancer types and may result in errors if used with the GA API.
- Region string
The Region in which the created backend service should reside. If it is not provided, the provider region is used.
- Session
Affinity string Type of session affinity to use. The default is NONE. Session affinity is not applicable if the protocol is UDP.
- Timeout
Sec int How many seconds to wait for the backend before considering it a failed request. Default is 30 seconds. Valid range is [1, 86400].
- Health
Checks string The set of URLs to HealthCheck resources for health checking this RegionBackendService. Currently at most one health check can be specified, and a health check is required.
- int
Lifetime of cookies in seconds if session_affinity is GENERATED_COOKIE. If set to 0, the cookie is non-persistent and lasts only until the end of the browser session (or equivalent). The maximum allowed value for TTL is one day. When the load balancing scheme is INTERNAL, this field is not used.
- Backends
[]Region
Backend Service Backend The set of backends that serve this RegionBackendService. Structure is documented below.
- Circuit
Breakers RegionBackend Service Circuit Breakers Settings controlling the volume of connections to a backend service. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- Connection
Draining intTimeout Sec Time for which instance will be drained (not accept new connections, but still work to finish started).
- Consistent
Hash RegionBackend Service Consistent Hash Consistent Hash-based load balancing can be used to provide soft session affinity based on HTTP headers, cookies or other properties. This load balancing policy is applicable only for HTTP connections. The affinity to a particular destination host will be lost when one or more hosts are added/removed from the destination service. This field specifies parameters that control consistent hashing. This field only applies when all of the following are true -
- Description string
An optional description of this resource. Provide this property when you create the resource.
- Failover
Policy RegionBackend Service Failover Policy Policy for failovers. Structure is documented below.
- Load
Balancing stringScheme Indicates what kind of load balancing this regional backend service will be used for. A backend service created for one type of load balancing cannot be used with the other(s).
- Locality
Lb stringPolicy The load balancing algorithm used within the scope of the locality. The possible values are - ROUND_ROBIN - This is a simple policy in which each healthy backend is selected in round robin order. LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests. RING_HASH - The ring/modulo hash load balancer implements consistent hashing to backends. The algorithm has the property that the addition/removal of a host from a set of N hosts only affects 1/N of the requests. RANDOM - The load balancer selects a random healthy host. ORIGINAL_DESTINATION - Backend host is selected based on the client connection metadata, i.e., connections are opened to the same address as the destination address of the incoming connection before the connection was redirected to the load balancer. MAGLEV - used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2.- Log
Config RegionBackend Service Log Config This field denotes the logging options for the load balancer traffic served by this backend service. If logging is enabled, logs will be exported to Stackdriver. Structure is documented below.
- Name string
Name of the cookie.
- Network string
The URL of the network to which this backend service belongs. This field can only be specified when the load balancing scheme is set to INTERNAL.
- Outlier
Detection RegionBackend Service Outlier Detection Settings controlling eviction of unhealthy hosts from the load balancing pool. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- Port
Name string A named port on a backend instance group representing the port for communication to the backend VMs in that group. Required when the loadBalancingScheme is EXTERNAL, INTERNAL_MANAGED, or INTERNAL_SELF_MANAGED and the backends are instance groups. The named port must be defined on each backend instance group. This parameter has no meaning if the backends are NEGs. API sets a default of “http” if not given. Must be omitted when the loadBalancingScheme is INTERNAL (Internal TCP/UDP Load Balancing).
- Project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- Protocol string
The protocol this RegionBackendService uses to communicate with backends. The default is HTTP. NOTE: HTTP2 is only valid for beta HTTP/2 load balancer types and may result in errors if used with the GA API.
- Region string
The Region in which the created backend service should reside. If it is not provided, the provider region is used.
- Session
Affinity string Type of session affinity to use. The default is NONE. Session affinity is not applicable if the protocol is UDP.
- Timeout
Sec int How many seconds to wait for the backend before considering it a failed request. Default is 30 seconds. Valid range is [1, 86400].
- health
Checks string The set of URLs to HealthCheck resources for health checking this RegionBackendService. Currently at most one health check can be specified, and a health check is required.
- number
Lifetime of cookies in seconds if session_affinity is GENERATED_COOKIE. If set to 0, the cookie is non-persistent and lasts only until the end of the browser session (or equivalent). The maximum allowed value for TTL is one day. When the load balancing scheme is INTERNAL, this field is not used.
- backends
Region
Backend Service Backend[] The set of backends that serve this RegionBackendService. Structure is documented below.
- circuit
Breakers RegionBackend Service Circuit Breakers Settings controlling the volume of connections to a backend service. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- connection
Draining numberTimeout Sec Time for which instance will be drained (not accept new connections, but still work to finish started).
- consistent
Hash RegionBackend Service Consistent Hash Consistent Hash-based load balancing can be used to provide soft session affinity based on HTTP headers, cookies or other properties. This load balancing policy is applicable only for HTTP connections. The affinity to a particular destination host will be lost when one or more hosts are added/removed from the destination service. This field specifies parameters that control consistent hashing. This field only applies when all of the following are true -
- description string
An optional description of this resource. Provide this property when you create the resource.
- failover
Policy RegionBackend Service Failover Policy Policy for failovers. Structure is documented below.
- load
Balancing stringScheme Indicates what kind of load balancing this regional backend service will be used for. A backend service created for one type of load balancing cannot be used with the other(s).
- locality
Lb stringPolicy The load balancing algorithm used within the scope of the locality. The possible values are - ROUND_ROBIN - This is a simple policy in which each healthy backend is selected in round robin order. LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests. RING_HASH - The ring/modulo hash load balancer implements consistent hashing to backends. The algorithm has the property that the addition/removal of a host from a set of N hosts only affects 1/N of the requests. RANDOM - The load balancer selects a random healthy host. ORIGINAL_DESTINATION - Backend host is selected based on the client connection metadata, i.e., connections are opened to the same address as the destination address of the incoming connection before the connection was redirected to the load balancer. MAGLEV - used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2.- log
Config RegionBackend Service Log Config This field denotes the logging options for the load balancer traffic served by this backend service. If logging is enabled, logs will be exported to Stackdriver. Structure is documented below.
- name string
Name of the cookie.
- network string
The URL of the network to which this backend service belongs. This field can only be specified when the load balancing scheme is set to INTERNAL.
- outlier
Detection RegionBackend Service Outlier Detection Settings controlling eviction of unhealthy hosts from the load balancing pool. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- port
Name string A named port on a backend instance group representing the port for communication to the backend VMs in that group. Required when the loadBalancingScheme is EXTERNAL, INTERNAL_MANAGED, or INTERNAL_SELF_MANAGED and the backends are instance groups. The named port must be defined on each backend instance group. This parameter has no meaning if the backends are NEGs. API sets a default of “http” if not given. Must be omitted when the loadBalancingScheme is INTERNAL (Internal TCP/UDP Load Balancing).
- project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- protocol string
The protocol this RegionBackendService uses to communicate with backends. The default is HTTP. NOTE: HTTP2 is only valid for beta HTTP/2 load balancer types and may result in errors if used with the GA API.
- region string
The Region in which the created backend service should reside. If it is not provided, the provider region is used.
- session
Affinity string Type of session affinity to use. The default is NONE. Session affinity is not applicable if the protocol is UDP.
- timeout
Sec number How many seconds to wait for the backend before considering it a failed request. Default is 30 seconds. Valid range is [1, 86400].
- health_
checks str The set of URLs to HealthCheck resources for health checking this RegionBackendService. Currently at most one health check can be specified, and a health check is required.
- float
Lifetime of cookies in seconds if session_affinity is GENERATED_COOKIE. If set to 0, the cookie is non-persistent and lasts only until the end of the browser session (or equivalent). The maximum allowed value for TTL is one day. When the load balancing scheme is INTERNAL, this field is not used.
- backends
List[Region
Backend Service Backend] The set of backends that serve this RegionBackendService. Structure is documented below.
- circuit_
breakers Dict[RegionBackend Service Circuit Breakers] Settings controlling the volume of connections to a backend service. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- connection_
draining_ floattimeout_ sec Time for which instance will be drained (not accept new connections, but still work to finish started).
- consistent_
hash Dict[RegionBackend Service Consistent Hash] Consistent Hash-based load balancing can be used to provide soft session affinity based on HTTP headers, cookies or other properties. This load balancing policy is applicable only for HTTP connections. The affinity to a particular destination host will be lost when one or more hosts are added/removed from the destination service. This field specifies parameters that control consistent hashing. This field only applies when all of the following are true -
- description str
An optional description of this resource. Provide this property when you create the resource.
- failover_
policy Dict[RegionBackend Service Failover Policy] Policy for failovers. Structure is documented below.
- load_
balancing_ strscheme Indicates what kind of load balancing this regional backend service will be used for. A backend service created for one type of load balancing cannot be used with the other(s).
- locality_
lb_ strpolicy The load balancing algorithm used within the scope of the locality. The possible values are - ROUND_ROBIN - This is a simple policy in which each healthy backend is selected in round robin order. LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests. RING_HASH - The ring/modulo hash load balancer implements consistent hashing to backends. The algorithm has the property that the addition/removal of a host from a set of N hosts only affects 1/N of the requests. RANDOM - The load balancer selects a random healthy host. ORIGINAL_DESTINATION - Backend host is selected based on the client connection metadata, i.e., connections are opened to the same address as the destination address of the incoming connection before the connection was redirected to the load balancer. MAGLEV - used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2.- log_
config Dict[RegionBackend Service Log Config] This field denotes the logging options for the load balancer traffic served by this backend service. If logging is enabled, logs will be exported to Stackdriver. Structure is documented below.
- name str
Name of the cookie.
- network str
The URL of the network to which this backend service belongs. This field can only be specified when the load balancing scheme is set to INTERNAL.
- outlier_
detection Dict[RegionBackend Service Outlier Detection] Settings controlling eviction of unhealthy hosts from the load balancing pool. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- port_
name str A named port on a backend instance group representing the port for communication to the backend VMs in that group. Required when the loadBalancingScheme is EXTERNAL, INTERNAL_MANAGED, or INTERNAL_SELF_MANAGED and the backends are instance groups. The named port must be defined on each backend instance group. This parameter has no meaning if the backends are NEGs. API sets a default of “http” if not given. Must be omitted when the loadBalancingScheme is INTERNAL (Internal TCP/UDP Load Balancing).
- project str
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- protocol str
The protocol this RegionBackendService uses to communicate with backends. The default is HTTP. NOTE: HTTP2 is only valid for beta HTTP/2 load balancer types and may result in errors if used with the GA API.
- region str
The Region in which the created backend service should reside. If it is not provided, the provider region is used.
- session_
affinity str Type of session affinity to use. The default is NONE. Session affinity is not applicable if the protocol is UDP.
- timeout_
sec float How many seconds to wait for the backend before considering it a failed request. Default is 30 seconds. Valid range is [1, 86400].
Outputs
All input properties are implicitly available as output properties. Additionally, the RegionBackendService resource produces the following output properties:
- Creation
Timestamp string Creation timestamp in RFC3339 text format.
- Fingerprint string
Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.
- Id string
- The provider-assigned unique ID for this managed resource.
- Self
Link string The URI of the created resource.
- Creation
Timestamp string Creation timestamp in RFC3339 text format.
- Fingerprint string
Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.
- Id string
- The provider-assigned unique ID for this managed resource.
- Self
Link string The URI of the created resource.
- creation
Timestamp string Creation timestamp in RFC3339 text format.
- fingerprint string
Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.
- id string
- The provider-assigned unique ID for this managed resource.
- self
Link string The URI of the created resource.
- creation_
timestamp str Creation timestamp in RFC3339 text format.
- fingerprint str
Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.
- id str
- The provider-assigned unique ID for this managed resource.
- self_
link str The URI of the created resource.
Look up an Existing RegionBackendService Resource
Get an existing RegionBackendService resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: RegionBackendServiceState, opts?: CustomResourceOptions): RegionBackendServicestatic get(resource_name, id, opts=None, affinity_cookie_ttl_sec=None, backends=None, circuit_breakers=None, connection_draining_timeout_sec=None, consistent_hash=None, creation_timestamp=None, description=None, failover_policy=None, fingerprint=None, health_checks=None, load_balancing_scheme=None, locality_lb_policy=None, log_config=None, name=None, network=None, outlier_detection=None, port_name=None, project=None, protocol=None, region=None, self_link=None, session_affinity=None, timeout_sec=None, __props__=None);func GetRegionBackendService(ctx *Context, name string, id IDInput, state *RegionBackendServiceState, opts ...ResourceOption) (*RegionBackendService, error)public static RegionBackendService Get(string name, Input<string> id, RegionBackendServiceState? state, CustomResourceOptions? opts = null)- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
The following state arguments are supported:
- int
Lifetime of cookies in seconds if session_affinity is GENERATED_COOKIE. If set to 0, the cookie is non-persistent and lasts only until the end of the browser session (or equivalent). The maximum allowed value for TTL is one day. When the load balancing scheme is INTERNAL, this field is not used.
- Backends
List<Region
Backend Service Backend Args> The set of backends that serve this RegionBackendService. Structure is documented below.
- Circuit
Breakers RegionBackend Service Circuit Breakers Args Settings controlling the volume of connections to a backend service. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- Connection
Draining intTimeout Sec Time for which instance will be drained (not accept new connections, but still work to finish started).
- Consistent
Hash RegionBackend Service Consistent Hash Args Consistent Hash-based load balancing can be used to provide soft session affinity based on HTTP headers, cookies or other properties. This load balancing policy is applicable only for HTTP connections. The affinity to a particular destination host will be lost when one or more hosts are added/removed from the destination service. This field specifies parameters that control consistent hashing. This field only applies when all of the following are true -
- Creation
Timestamp string Creation timestamp in RFC3339 text format.
- Description string
An optional description of this resource. Provide this property when you create the resource.
- Failover
Policy RegionBackend Service Failover Policy Args Policy for failovers. Structure is documented below.
- Fingerprint string
Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.
- Health
Checks string The set of URLs to HealthCheck resources for health checking this RegionBackendService. Currently at most one health check can be specified, and a health check is required.
- Load
Balancing stringScheme Indicates what kind of load balancing this regional backend service will be used for. A backend service created for one type of load balancing cannot be used with the other(s).
- Locality
Lb stringPolicy The load balancing algorithm used within the scope of the locality. The possible values are - ROUND_ROBIN - This is a simple policy in which each healthy backend is selected in round robin order. LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests. RING_HASH - The ring/modulo hash load balancer implements consistent hashing to backends. The algorithm has the property that the addition/removal of a host from a set of N hosts only affects 1/N of the requests. RANDOM - The load balancer selects a random healthy host. ORIGINAL_DESTINATION - Backend host is selected based on the client connection metadata, i.e., connections are opened to the same address as the destination address of the incoming connection before the connection was redirected to the load balancer. MAGLEV - used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2.- Log
Config RegionBackend Service Log Config Args This field denotes the logging options for the load balancer traffic served by this backend service. If logging is enabled, logs will be exported to Stackdriver. Structure is documented below.
- Name string
Name of the cookie.
- Network string
The URL of the network to which this backend service belongs. This field can only be specified when the load balancing scheme is set to INTERNAL.
- Outlier
Detection RegionBackend Service Outlier Detection Args Settings controlling eviction of unhealthy hosts from the load balancing pool. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- Port
Name string A named port on a backend instance group representing the port for communication to the backend VMs in that group. Required when the loadBalancingScheme is EXTERNAL, INTERNAL_MANAGED, or INTERNAL_SELF_MANAGED and the backends are instance groups. The named port must be defined on each backend instance group. This parameter has no meaning if the backends are NEGs. API sets a default of “http” if not given. Must be omitted when the loadBalancingScheme is INTERNAL (Internal TCP/UDP Load Balancing).
- Project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- Protocol string
The protocol this RegionBackendService uses to communicate with backends. The default is HTTP. NOTE: HTTP2 is only valid for beta HTTP/2 load balancer types and may result in errors if used with the GA API.
- Region string
The Region in which the created backend service should reside. If it is not provided, the provider region is used.
- Self
Link string The URI of the created resource.
- Session
Affinity string Type of session affinity to use. The default is NONE. Session affinity is not applicable if the protocol is UDP.
- Timeout
Sec int How many seconds to wait for the backend before considering it a failed request. Default is 30 seconds. Valid range is [1, 86400].
- int
Lifetime of cookies in seconds if session_affinity is GENERATED_COOKIE. If set to 0, the cookie is non-persistent and lasts only until the end of the browser session (or equivalent). The maximum allowed value for TTL is one day. When the load balancing scheme is INTERNAL, this field is not used.
- Backends
[]Region
Backend Service Backend The set of backends that serve this RegionBackendService. Structure is documented below.
- Circuit
Breakers RegionBackend Service Circuit Breakers Settings controlling the volume of connections to a backend service. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- Connection
Draining intTimeout Sec Time for which instance will be drained (not accept new connections, but still work to finish started).
- Consistent
Hash RegionBackend Service Consistent Hash Consistent Hash-based load balancing can be used to provide soft session affinity based on HTTP headers, cookies or other properties. This load balancing policy is applicable only for HTTP connections. The affinity to a particular destination host will be lost when one or more hosts are added/removed from the destination service. This field specifies parameters that control consistent hashing. This field only applies when all of the following are true -
- Creation
Timestamp string Creation timestamp in RFC3339 text format.
- Description string
An optional description of this resource. Provide this property when you create the resource.
- Failover
Policy RegionBackend Service Failover Policy Policy for failovers. Structure is documented below.
- Fingerprint string
Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.
- Health
Checks string The set of URLs to HealthCheck resources for health checking this RegionBackendService. Currently at most one health check can be specified, and a health check is required.
- Load
Balancing stringScheme Indicates what kind of load balancing this regional backend service will be used for. A backend service created for one type of load balancing cannot be used with the other(s).
- Locality
Lb stringPolicy The load balancing algorithm used within the scope of the locality. The possible values are - ROUND_ROBIN - This is a simple policy in which each healthy backend is selected in round robin order. LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests. RING_HASH - The ring/modulo hash load balancer implements consistent hashing to backends. The algorithm has the property that the addition/removal of a host from a set of N hosts only affects 1/N of the requests. RANDOM - The load balancer selects a random healthy host. ORIGINAL_DESTINATION - Backend host is selected based on the client connection metadata, i.e., connections are opened to the same address as the destination address of the incoming connection before the connection was redirected to the load balancer. MAGLEV - used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2.- Log
Config RegionBackend Service Log Config This field denotes the logging options for the load balancer traffic served by this backend service. If logging is enabled, logs will be exported to Stackdriver. Structure is documented below.
- Name string
Name of the cookie.
- Network string
The URL of the network to which this backend service belongs. This field can only be specified when the load balancing scheme is set to INTERNAL.
- Outlier
Detection RegionBackend Service Outlier Detection Settings controlling eviction of unhealthy hosts from the load balancing pool. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- Port
Name string A named port on a backend instance group representing the port for communication to the backend VMs in that group. Required when the loadBalancingScheme is EXTERNAL, INTERNAL_MANAGED, or INTERNAL_SELF_MANAGED and the backends are instance groups. The named port must be defined on each backend instance group. This parameter has no meaning if the backends are NEGs. API sets a default of “http” if not given. Must be omitted when the loadBalancingScheme is INTERNAL (Internal TCP/UDP Load Balancing).
- Project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- Protocol string
The protocol this RegionBackendService uses to communicate with backends. The default is HTTP. NOTE: HTTP2 is only valid for beta HTTP/2 load balancer types and may result in errors if used with the GA API.
- Region string
The Region in which the created backend service should reside. If it is not provided, the provider region is used.
- Self
Link string The URI of the created resource.
- Session
Affinity string Type of session affinity to use. The default is NONE. Session affinity is not applicable if the protocol is UDP.
- Timeout
Sec int How many seconds to wait for the backend before considering it a failed request. Default is 30 seconds. Valid range is [1, 86400].
- number
Lifetime of cookies in seconds if session_affinity is GENERATED_COOKIE. If set to 0, the cookie is non-persistent and lasts only until the end of the browser session (or equivalent). The maximum allowed value for TTL is one day. When the load balancing scheme is INTERNAL, this field is not used.
- backends
Region
Backend Service Backend[] The set of backends that serve this RegionBackendService. Structure is documented below.
- circuit
Breakers RegionBackend Service Circuit Breakers Settings controlling the volume of connections to a backend service. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- connection
Draining numberTimeout Sec Time for which instance will be drained (not accept new connections, but still work to finish started).
- consistent
Hash RegionBackend Service Consistent Hash Consistent Hash-based load balancing can be used to provide soft session affinity based on HTTP headers, cookies or other properties. This load balancing policy is applicable only for HTTP connections. The affinity to a particular destination host will be lost when one or more hosts are added/removed from the destination service. This field specifies parameters that control consistent hashing. This field only applies when all of the following are true -
- creation
Timestamp string Creation timestamp in RFC3339 text format.
- description string
An optional description of this resource. Provide this property when you create the resource.
- failover
Policy RegionBackend Service Failover Policy Policy for failovers. Structure is documented below.
- fingerprint string
Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.
- health
Checks string The set of URLs to HealthCheck resources for health checking this RegionBackendService. Currently at most one health check can be specified, and a health check is required.
- load
Balancing stringScheme Indicates what kind of load balancing this regional backend service will be used for. A backend service created for one type of load balancing cannot be used with the other(s).
- locality
Lb stringPolicy The load balancing algorithm used within the scope of the locality. The possible values are - ROUND_ROBIN - This is a simple policy in which each healthy backend is selected in round robin order. LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests. RING_HASH - The ring/modulo hash load balancer implements consistent hashing to backends. The algorithm has the property that the addition/removal of a host from a set of N hosts only affects 1/N of the requests. RANDOM - The load balancer selects a random healthy host. ORIGINAL_DESTINATION - Backend host is selected based on the client connection metadata, i.e., connections are opened to the same address as the destination address of the incoming connection before the connection was redirected to the load balancer. MAGLEV - used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2.- log
Config RegionBackend Service Log Config This field denotes the logging options for the load balancer traffic served by this backend service. If logging is enabled, logs will be exported to Stackdriver. Structure is documented below.
- name string
Name of the cookie.
- network string
The URL of the network to which this backend service belongs. This field can only be specified when the load balancing scheme is set to INTERNAL.
- outlier
Detection RegionBackend Service Outlier Detection Settings controlling eviction of unhealthy hosts from the load balancing pool. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- port
Name string A named port on a backend instance group representing the port for communication to the backend VMs in that group. Required when the loadBalancingScheme is EXTERNAL, INTERNAL_MANAGED, or INTERNAL_SELF_MANAGED and the backends are instance groups. The named port must be defined on each backend instance group. This parameter has no meaning if the backends are NEGs. API sets a default of “http” if not given. Must be omitted when the loadBalancingScheme is INTERNAL (Internal TCP/UDP Load Balancing).
- project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- protocol string
The protocol this RegionBackendService uses to communicate with backends. The default is HTTP. NOTE: HTTP2 is only valid for beta HTTP/2 load balancer types and may result in errors if used with the GA API.
- region string
The Region in which the created backend service should reside. If it is not provided, the provider region is used.
- self
Link string The URI of the created resource.
- session
Affinity string Type of session affinity to use. The default is NONE. Session affinity is not applicable if the protocol is UDP.
- timeout
Sec number How many seconds to wait for the backend before considering it a failed request. Default is 30 seconds. Valid range is [1, 86400].
- float
Lifetime of cookies in seconds if session_affinity is GENERATED_COOKIE. If set to 0, the cookie is non-persistent and lasts only until the end of the browser session (or equivalent). The maximum allowed value for TTL is one day. When the load balancing scheme is INTERNAL, this field is not used.
- backends
List[Region
Backend Service Backend] The set of backends that serve this RegionBackendService. Structure is documented below.
- circuit_
breakers Dict[RegionBackend Service Circuit Breakers] Settings controlling the volume of connections to a backend service. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- connection_
draining_ floattimeout_ sec Time for which instance will be drained (not accept new connections, but still work to finish started).
- consistent_
hash Dict[RegionBackend Service Consistent Hash] Consistent Hash-based load balancing can be used to provide soft session affinity based on HTTP headers, cookies or other properties. This load balancing policy is applicable only for HTTP connections. The affinity to a particular destination host will be lost when one or more hosts are added/removed from the destination service. This field specifies parameters that control consistent hashing. This field only applies when all of the following are true -
- creation_
timestamp str Creation timestamp in RFC3339 text format.
- description str
An optional description of this resource. Provide this property when you create the resource.
- failover_
policy Dict[RegionBackend Service Failover Policy] Policy for failovers. Structure is documented below.
- fingerprint str
Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.
- health_
checks str The set of URLs to HealthCheck resources for health checking this RegionBackendService. Currently at most one health check can be specified, and a health check is required.
- load_
balancing_ strscheme Indicates what kind of load balancing this regional backend service will be used for. A backend service created for one type of load balancing cannot be used with the other(s).
- locality_
lb_ strpolicy The load balancing algorithm used within the scope of the locality. The possible values are - ROUND_ROBIN - This is a simple policy in which each healthy backend is selected in round robin order. LEAST_REQUEST - An O(1) algorithm which selects two random healthy hosts and picks the host which has fewer active requests. RING_HASH - The ring/modulo hash load balancer implements consistent hashing to backends. The algorithm has the property that the addition/removal of a host from a set of N hosts only affects 1/N of the requests. RANDOM - The load balancer selects a random healthy host. ORIGINAL_DESTINATION - Backend host is selected based on the client connection metadata, i.e., connections are opened to the same address as the destination address of the incoming connection before the connection was redirected to the load balancer. MAGLEV - used as a drop in replacement for the ring hash load balancer. Maglev is not as stable as ring hash but has faster table lookup build times and host selection times. For more information about Maglev, refer to https://ai.google/research/pubs/pub44824 This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2.- log_
config Dict[RegionBackend Service Log Config] This field denotes the logging options for the load balancer traffic served by this backend service. If logging is enabled, logs will be exported to Stackdriver. Structure is documented below.
- name str
Name of the cookie.
- network str
The URL of the network to which this backend service belongs. This field can only be specified when the load balancing scheme is set to INTERNAL.
- outlier_
detection Dict[RegionBackend Service Outlier Detection] Settings controlling eviction of unhealthy hosts from the load balancing pool. This field is applicable only when the
load_balancing_schemeis set to INTERNAL_MANAGED and theprotocolis set to HTTP, HTTPS, or HTTP2. Structure is documented below.- port_
name str A named port on a backend instance group representing the port for communication to the backend VMs in that group. Required when the loadBalancingScheme is EXTERNAL, INTERNAL_MANAGED, or INTERNAL_SELF_MANAGED and the backends are instance groups. The named port must be defined on each backend instance group. This parameter has no meaning if the backends are NEGs. API sets a default of “http” if not given. Must be omitted when the loadBalancingScheme is INTERNAL (Internal TCP/UDP Load Balancing).
- project str
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- protocol str
The protocol this RegionBackendService uses to communicate with backends. The default is HTTP. NOTE: HTTP2 is only valid for beta HTTP/2 load balancer types and may result in errors if used with the GA API.
- region str
The Region in which the created backend service should reside. If it is not provided, the provider region is used.
- self_
link str The URI of the created resource.
- session_
affinity str Type of session affinity to use. The default is NONE. Session affinity is not applicable if the protocol is UDP.
- timeout_
sec float How many seconds to wait for the backend before considering it a failed request. Default is 30 seconds. Valid range is [1, 86400].
Supporting Types
RegionBackendServiceBackend
- Group string
The fully-qualified URL of an Instance Group or Network Endpoint Group resource. In case of instance group this defines the list of instances that serve traffic. Member virtual machine instances from each instance group must live in the same zone as the instance group itself. No two backends in a backend service are allowed to use same Instance Group resource. For Network Endpoint Groups this defines list of endpoints. All endpoints of Network Endpoint Group must be hosted on instances located in the same zone as the Network Endpoint Group. Backend services cannot mix Instance Group and Network Endpoint Group backends. When the
load_balancing_schemeis INTERNAL, only instance groups are supported. Note that you must specify an Instance Group or Network Endpoint Group resource using the fully-qualified URL, rather than a partial URL.- Balancing
Mode string Specifies the balancing mode for this backend.
- Capacity
Scaler double A multiplier applied to the group’s maximum servicing capacity (based on UTILIZATION, RATE or CONNECTION). ~>NOTE: This field cannot be set for INTERNAL region backend services (default loadBalancingScheme), but is required for non-INTERNAL backend service. The total capacity_scaler for all backends must be non-zero. A setting of 0 means the group is completely drained, offering 0% of its available Capacity. Valid range is [0.0,1.0].
- Description string
An optional description of this resource. Provide this property when you create the resource.
- Failover bool
This field designates whether this is a failover backend. More than one failover backend can be configured for a given RegionBackendService.
- Max
Connections int The maximum number of connections to the backend cluster. Defaults to 1024.
- Max
Connections intPer Endpoint The max number of simultaneous connections that a single backend network endpoint can handle. Cannot be set for INTERNAL backend services. This is used to calculate the capacity of the group. Can be used in either CONNECTION or UTILIZATION balancing modes. For CONNECTION mode, either maxConnections or maxConnectionsPerEndpoint must be set.
- Max
Connections intPer Instance The max number of simultaneous connections that a single backend instance can handle. Cannot be set for INTERNAL backend services. This is used to calculate the capacity of the group. Can be used in either CONNECTION or UTILIZATION balancing modes. For CONNECTION mode, either maxConnections or maxConnectionsPerInstance must be set.
- Max
Rate int The max requests per second (RPS) of the group. Cannot be set for INTERNAL backend services. Can be used with either RATE or UTILIZATION balancing modes, but required if RATE mode. Either maxRate or one of maxRatePerInstance or maxRatePerEndpoint, as appropriate for group type, must be set.
- Max
Rate doublePer Endpoint The max requests per second (RPS) that a single backend network endpoint can handle. This is used to calculate the capacity of the group. Can be used in either balancing mode. For RATE mode, either maxRate or maxRatePerEndpoint must be set. Cannot be set for INTERNAL backend services.
- Max
Rate doublePer Instance The max requests per second (RPS) that a single backend instance can handle. This is used to calculate the capacity of the group. Can be used in either balancing mode. For RATE mode, either maxRate or maxRatePerInstance must be set. Cannot be set for INTERNAL backend services.
- Max
Utilization double Used when balancingMode is UTILIZATION. This ratio defines the CPU utilization target for the group. Valid range is [0.0, 1.0]. Cannot be set for INTERNAL backend services.
- Group string
The fully-qualified URL of an Instance Group or Network Endpoint Group resource. In case of instance group this defines the list of instances that serve traffic. Member virtual machine instances from each instance group must live in the same zone as the instance group itself. No two backends in a backend service are allowed to use same Instance Group resource. For Network Endpoint Groups this defines list of endpoints. All endpoints of Network Endpoint Group must be hosted on instances located in the same zone as the Network Endpoint Group. Backend services cannot mix Instance Group and Network Endpoint Group backends. When the
load_balancing_schemeis INTERNAL, only instance groups are supported. Note that you must specify an Instance Group or Network Endpoint Group resource using the fully-qualified URL, rather than a partial URL.- Balancing
Mode string Specifies the balancing mode for this backend.
- Capacity
Scaler float64 A multiplier applied to the group’s maximum servicing capacity (based on UTILIZATION, RATE or CONNECTION). ~>NOTE: This field cannot be set for INTERNAL region backend services (default loadBalancingScheme), but is required for non-INTERNAL backend service. The total capacity_scaler for all backends must be non-zero. A setting of 0 means the group is completely drained, offering 0% of its available Capacity. Valid range is [0.0,1.0].
- Description string
An optional description of this resource. Provide this property when you create the resource.
- Failover bool
This field designates whether this is a failover backend. More than one failover backend can be configured for a given RegionBackendService.
- Max
Connections int The maximum number of connections to the backend cluster. Defaults to 1024.
- Max
Connections intPer Endpoint The max number of simultaneous connections that a single backend network endpoint can handle. Cannot be set for INTERNAL backend services. This is used to calculate the capacity of the group. Can be used in either CONNECTION or UTILIZATION balancing modes. For CONNECTION mode, either maxConnections or maxConnectionsPerEndpoint must be set.
- Max
Connections intPer Instance The max number of simultaneous connections that a single backend instance can handle. Cannot be set for INTERNAL backend services. This is used to calculate the capacity of the group. Can be used in either CONNECTION or UTILIZATION balancing modes. For CONNECTION mode, either maxConnections or maxConnectionsPerInstance must be set.
- Max
Rate int The max requests per second (RPS) of the group. Cannot be set for INTERNAL backend services. Can be used with either RATE or UTILIZATION balancing modes, but required if RATE mode. Either maxRate or one of maxRatePerInstance or maxRatePerEndpoint, as appropriate for group type, must be set.
- Max
Rate float64Per Endpoint The max requests per second (RPS) that a single backend network endpoint can handle. This is used to calculate the capacity of the group. Can be used in either balancing mode. For RATE mode, either maxRate or maxRatePerEndpoint must be set. Cannot be set for INTERNAL backend services.
- Max
Rate float64Per Instance The max requests per second (RPS) that a single backend instance can handle. This is used to calculate the capacity of the group. Can be used in either balancing mode. For RATE mode, either maxRate or maxRatePerInstance must be set. Cannot be set for INTERNAL backend services.
- Max
Utilization float64 Used when balancingMode is UTILIZATION. This ratio defines the CPU utilization target for the group. Valid range is [0.0, 1.0]. Cannot be set for INTERNAL backend services.
- group string
The fully-qualified URL of an Instance Group or Network Endpoint Group resource. In case of instance group this defines the list of instances that serve traffic. Member virtual machine instances from each instance group must live in the same zone as the instance group itself. No two backends in a backend service are allowed to use same Instance Group resource. For Network Endpoint Groups this defines list of endpoints. All endpoints of Network Endpoint Group must be hosted on instances located in the same zone as the Network Endpoint Group. Backend services cannot mix Instance Group and Network Endpoint Group backends. When the
load_balancing_schemeis INTERNAL, only instance groups are supported. Note that you must specify an Instance Group or Network Endpoint Group resource using the fully-qualified URL, rather than a partial URL.- balancing
Mode string Specifies the balancing mode for this backend.
- capacity
Scaler number A multiplier applied to the group’s maximum servicing capacity (based on UTILIZATION, RATE or CONNECTION). ~>NOTE: This field cannot be set for INTERNAL region backend services (default loadBalancingScheme), but is required for non-INTERNAL backend service. The total capacity_scaler for all backends must be non-zero. A setting of 0 means the group is completely drained, offering 0% of its available Capacity. Valid range is [0.0,1.0].
- description string
An optional description of this resource. Provide this property when you create the resource.
- failover boolean
This field designates whether this is a failover backend. More than one failover backend can be configured for a given RegionBackendService.
- max
Connections number The maximum number of connections to the backend cluster. Defaults to 1024.
- max
Connections numberPer Endpoint The max number of simultaneous connections that a single backend network endpoint can handle. Cannot be set for INTERNAL backend services. This is used to calculate the capacity of the group. Can be used in either CONNECTION or UTILIZATION balancing modes. For CONNECTION mode, either maxConnections or maxConnectionsPerEndpoint must be set.
- max
Connections numberPer Instance The max number of simultaneous connections that a single backend instance can handle. Cannot be set for INTERNAL backend services. This is used to calculate the capacity of the group. Can be used in either CONNECTION or UTILIZATION balancing modes. For CONNECTION mode, either maxConnections or maxConnectionsPerInstance must be set.
- max
Rate number The max requests per second (RPS) of the group. Cannot be set for INTERNAL backend services. Can be used with either RATE or UTILIZATION balancing modes, but required if RATE mode. Either maxRate or one of maxRatePerInstance or maxRatePerEndpoint, as appropriate for group type, must be set.
- max
Rate numberPer Endpoint The max requests per second (RPS) that a single backend network endpoint can handle. This is used to calculate the capacity of the group. Can be used in either balancing mode. For RATE mode, either maxRate or maxRatePerEndpoint must be set. Cannot be set for INTERNAL backend services.
- max
Rate numberPer Instance The max requests per second (RPS) that a single backend instance can handle. This is used to calculate the capacity of the group. Can be used in either balancing mode. For RATE mode, either maxRate or maxRatePerInstance must be set. Cannot be set for INTERNAL backend services.
- max
Utilization number Used when balancingMode is UTILIZATION. This ratio defines the CPU utilization target for the group. Valid range is [0.0, 1.0]. Cannot be set for INTERNAL backend services.
- group str
The fully-qualified URL of an Instance Group or Network Endpoint Group resource. In case of instance group this defines the list of instances that serve traffic. Member virtual machine instances from each instance group must live in the same zone as the instance group itself. No two backends in a backend service are allowed to use same Instance Group resource. For Network Endpoint Groups this defines list of endpoints. All endpoints of Network Endpoint Group must be hosted on instances located in the same zone as the Network Endpoint Group. Backend services cannot mix Instance Group and Network Endpoint Group backends. When the
load_balancing_schemeis INTERNAL, only instance groups are supported. Note that you must specify an Instance Group or Network Endpoint Group resource using the fully-qualified URL, rather than a partial URL.- balancing
Mode str Specifies the balancing mode for this backend.
- capacity
Scaler float A multiplier applied to the group’s maximum servicing capacity (based on UTILIZATION, RATE or CONNECTION). ~>NOTE: This field cannot be set for INTERNAL region backend services (default loadBalancingScheme), but is required for non-INTERNAL backend service. The total capacity_scaler for all backends must be non-zero. A setting of 0 means the group is completely drained, offering 0% of its available Capacity. Valid range is [0.0,1.0].
- description str
An optional description of this resource. Provide this property when you create the resource.
- failover bool
This field designates whether this is a failover backend. More than one failover backend can be configured for a given RegionBackendService.
- max
Connections float The maximum number of connections to the backend cluster. Defaults to 1024.
- max
Connections floatPer Endpoint The max number of simultaneous connections that a single backend network endpoint can handle. Cannot be set for INTERNAL backend services. This is used to calculate the capacity of the group. Can be used in either CONNECTION or UTILIZATION balancing modes. For CONNECTION mode, either maxConnections or maxConnectionsPerEndpoint must be set.
- max
Connections floatPer Instance The max number of simultaneous connections that a single backend instance can handle. Cannot be set for INTERNAL backend services. This is used to calculate the capacity of the group. Can be used in either CONNECTION or UTILIZATION balancing modes. For CONNECTION mode, either maxConnections or maxConnectionsPerInstance must be set.
- max
Rate float The max requests per second (RPS) of the group. Cannot be set for INTERNAL backend services. Can be used with either RATE or UTILIZATION balancing modes, but required if RATE mode. Either maxRate or one of maxRatePerInstance or maxRatePerEndpoint, as appropriate for group type, must be set.
- max
Rate floatPer Endpoint The max requests per second (RPS) that a single backend network endpoint can handle. This is used to calculate the capacity of the group. Can be used in either balancing mode. For RATE mode, either maxRate or maxRatePerEndpoint must be set. Cannot be set for INTERNAL backend services.
- max
Rate floatPer Instance The max requests per second (RPS) that a single backend instance can handle. This is used to calculate the capacity of the group. Can be used in either balancing mode. For RATE mode, either maxRate or maxRatePerInstance must be set. Cannot be set for INTERNAL backend services.
- max
Utilization float Used when balancingMode is UTILIZATION. This ratio defines the CPU utilization target for the group. Valid range is [0.0, 1.0]. Cannot be set for INTERNAL backend services.
RegionBackendServiceCircuitBreakers
- Connect
Timeout RegionBackend Service Circuit Breakers Connect Timeout Args The timeout for new network connections to hosts. Structure is documented below.
- Max
Connections int The maximum number of connections to the backend cluster. Defaults to 1024.
- Max
Pending intRequests The maximum number of pending requests to the backend cluster. Defaults to 1024.
- Max
Requests int The maximum number of parallel requests to the backend cluster. Defaults to 1024.
- Max
Requests intPer Connection Maximum requests for a single backend connection. This parameter is respected by both the HTTP/1.1 and HTTP/2 implementations. If not specified, there is no limit. Setting this parameter to 1 will effectively disable keep alive.
- Max
Retries int The maximum number of parallel retries to the backend cluster. Defaults to 3.
- Connect
Timeout RegionBackend Service Circuit Breakers Connect Timeout The timeout for new network connections to hosts. Structure is documented below.
- Max
Connections int The maximum number of connections to the backend cluster. Defaults to 1024.
- Max
Pending intRequests The maximum number of pending requests to the backend cluster. Defaults to 1024.
- Max
Requests int The maximum number of parallel requests to the backend cluster. Defaults to 1024.
- Max
Requests intPer Connection Maximum requests for a single backend connection. This parameter is respected by both the HTTP/1.1 and HTTP/2 implementations. If not specified, there is no limit. Setting this parameter to 1 will effectively disable keep alive.
- Max
Retries int The maximum number of parallel retries to the backend cluster. Defaults to 3.
- connect
Timeout RegionBackend Service Circuit Breakers Connect Timeout The timeout for new network connections to hosts. Structure is documented below.
- max
Connections number The maximum number of connections to the backend cluster. Defaults to 1024.
- max
Pending numberRequests The maximum number of pending requests to the backend cluster. Defaults to 1024.
- max
Requests number The maximum number of parallel requests to the backend cluster. Defaults to 1024.
- max
Requests numberPer Connection Maximum requests for a single backend connection. This parameter is respected by both the HTTP/1.1 and HTTP/2 implementations. If not specified, there is no limit. Setting this parameter to 1 will effectively disable keep alive.
- max
Retries number The maximum number of parallel retries to the backend cluster. Defaults to 3.
- connect
Timeout Dict[RegionBackend Service Circuit Breakers Connect Timeout] The timeout for new network connections to hosts. Structure is documented below.
- max
Connections float The maximum number of connections to the backend cluster. Defaults to 1024.
- max
Pending floatRequests The maximum number of pending requests to the backend cluster. Defaults to 1024.
- max
Requests float The maximum number of parallel requests to the backend cluster. Defaults to 1024.
- max
Requests floatPer Connection Maximum requests for a single backend connection. This parameter is respected by both the HTTP/1.1 and HTTP/2 implementations. If not specified, there is no limit. Setting this parameter to 1 will effectively disable keep alive.
- max
Retries float The maximum number of parallel retries to the backend cluster. Defaults to 3.
RegionBackendServiceCircuitBreakersConnectTimeout
- Seconds int
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- Nanos int
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
- Seconds int
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- Nanos int
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
- seconds number
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- nanos number
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
- seconds float
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- nanos float
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
RegionBackendServiceConsistentHash
-
Region
Backend Service Consistent Hash Http Cookie Args Hash is based on HTTP Cookie. This field describes a HTTP cookie that will be used as the hash key for the consistent hash load balancer. If the cookie is not present, it will be generated. This field is applicable if the sessionAffinity is set to HTTP_COOKIE. Structure is documented below.
- Http
Header stringName The hash based on the value of the specified header field. This field is applicable if the sessionAffinity is set to HEADER_FIELD.
- Minimum
Ring intSize The minimum number of virtual nodes to use for the hash ring. Larger ring sizes result in more granular load distributions. If the number of hosts in the load balancing pool is larger than the ring size, each host will be assigned a single virtual node. Defaults to 1024.
-
Region
Backend Service Consistent Hash Http Cookie Hash is based on HTTP Cookie. This field describes a HTTP cookie that will be used as the hash key for the consistent hash load balancer. If the cookie is not present, it will be generated. This field is applicable if the sessionAffinity is set to HTTP_COOKIE. Structure is documented below.
- Http
Header stringName The hash based on the value of the specified header field. This field is applicable if the sessionAffinity is set to HEADER_FIELD.
- Minimum
Ring intSize The minimum number of virtual nodes to use for the hash ring. Larger ring sizes result in more granular load distributions. If the number of hosts in the load balancing pool is larger than the ring size, each host will be assigned a single virtual node. Defaults to 1024.
-
Region
Backend Service Consistent Hash Http Cookie Hash is based on HTTP Cookie. This field describes a HTTP cookie that will be used as the hash key for the consistent hash load balancer. If the cookie is not present, it will be generated. This field is applicable if the sessionAffinity is set to HTTP_COOKIE. Structure is documented below.
- http
Header stringName The hash based on the value of the specified header field. This field is applicable if the sessionAffinity is set to HEADER_FIELD.
- minimum
Ring numberSize The minimum number of virtual nodes to use for the hash ring. Larger ring sizes result in more granular load distributions. If the number of hosts in the load balancing pool is larger than the ring size, each host will be assigned a single virtual node. Defaults to 1024.
-
Dict[Region
Backend Service Consistent Hash Http Cookie] Hash is based on HTTP Cookie. This field describes a HTTP cookie that will be used as the hash key for the consistent hash load balancer. If the cookie is not present, it will be generated. This field is applicable if the sessionAffinity is set to HTTP_COOKIE. Structure is documented below.
- http
Header strName The hash based on the value of the specified header field. This field is applicable if the sessionAffinity is set to HEADER_FIELD.
- minimum
Ring floatSize The minimum number of virtual nodes to use for the hash ring. Larger ring sizes result in more granular load distributions. If the number of hosts in the load balancing pool is larger than the ring size, each host will be assigned a single virtual node. Defaults to 1024.
RegionBackendServiceConsistentHashHttpCookie
RegionBackendServiceConsistentHashHttpCookieTtl
- Seconds int
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- Nanos int
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
- Seconds int
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- Nanos int
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
- seconds number
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- nanos number
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
- seconds float
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- nanos float
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
RegionBackendServiceFailoverPolicy
- Disable
Connection boolDrain On Failover On failover or failback, this field indicates whether connection drain will be honored. Setting this to true has the following effect: connections to the old active pool are not drained. Connections to the new active pool use the timeout of 10 min (currently fixed). Setting to false has the following effect: both old and new connections will have a drain timeout of 10 min. This can be set to true only if the protocol is TCP. The default is false.
- Drop
Traffic boolIf Unhealthy This option is used only when no healthy VMs are detected in the primary and backup instance groups. When set to true, traffic is dropped. When set to false, new connections are sent across all VMs in the primary group. The default is false.
- Failover
Ratio double The value of the field must be in [0, 1]. If the ratio of the healthy VMs in the primary backend is at or below this number, traffic arriving at the load-balanced IP will be directed to the failover backend. In case where ‘failoverRatio’ is not set or all the VMs in the backup backend are unhealthy, the traffic will be directed back to the primary backend in the “force” mode, where traffic will be spread to the healthy VMs with the best effort, or to all VMs when no VM is healthy. This field is only used with l4 load balancing.
- Disable
Connection boolDrain On Failover On failover or failback, this field indicates whether connection drain will be honored. Setting this to true has the following effect: connections to the old active pool are not drained. Connections to the new active pool use the timeout of 10 min (currently fixed). Setting to false has the following effect: both old and new connections will have a drain timeout of 10 min. This can be set to true only if the protocol is TCP. The default is false.
- Drop
Traffic boolIf Unhealthy This option is used only when no healthy VMs are detected in the primary and backup instance groups. When set to true, traffic is dropped. When set to false, new connections are sent across all VMs in the primary group. The default is false.
- Failover
Ratio float64 The value of the field must be in [0, 1]. If the ratio of the healthy VMs in the primary backend is at or below this number, traffic arriving at the load-balanced IP will be directed to the failover backend. In case where ‘failoverRatio’ is not set or all the VMs in the backup backend are unhealthy, the traffic will be directed back to the primary backend in the “force” mode, where traffic will be spread to the healthy VMs with the best effort, or to all VMs when no VM is healthy. This field is only used with l4 load balancing.
- disable
Connection booleanDrain On Failover On failover or failback, this field indicates whether connection drain will be honored. Setting this to true has the following effect: connections to the old active pool are not drained. Connections to the new active pool use the timeout of 10 min (currently fixed). Setting to false has the following effect: both old and new connections will have a drain timeout of 10 min. This can be set to true only if the protocol is TCP. The default is false.
- drop
Traffic booleanIf Unhealthy This option is used only when no healthy VMs are detected in the primary and backup instance groups. When set to true, traffic is dropped. When set to false, new connections are sent across all VMs in the primary group. The default is false.
- failover
Ratio number The value of the field must be in [0, 1]. If the ratio of the healthy VMs in the primary backend is at or below this number, traffic arriving at the load-balanced IP will be directed to the failover backend. In case where ‘failoverRatio’ is not set or all the VMs in the backup backend are unhealthy, the traffic will be directed back to the primary backend in the “force” mode, where traffic will be spread to the healthy VMs with the best effort, or to all VMs when no VM is healthy. This field is only used with l4 load balancing.
- disable
Connection boolDrain On Failover On failover or failback, this field indicates whether connection drain will be honored. Setting this to true has the following effect: connections to the old active pool are not drained. Connections to the new active pool use the timeout of 10 min (currently fixed). Setting to false has the following effect: both old and new connections will have a drain timeout of 10 min. This can be set to true only if the protocol is TCP. The default is false.
- drop
Traffic boolIf Unhealthy This option is used only when no healthy VMs are detected in the primary and backup instance groups. When set to true, traffic is dropped. When set to false, new connections are sent across all VMs in the primary group. The default is false.
- failover_
ratio float The value of the field must be in [0, 1]. If the ratio of the healthy VMs in the primary backend is at or below this number, traffic arriving at the load-balanced IP will be directed to the failover backend. In case where ‘failoverRatio’ is not set or all the VMs in the backup backend are unhealthy, the traffic will be directed back to the primary backend in the “force” mode, where traffic will be spread to the healthy VMs with the best effort, or to all VMs when no VM is healthy. This field is only used with l4 load balancing.
RegionBackendServiceLogConfig
- Enable bool
Whether to enable logging for the load balancer traffic served by this backend service.
- Sample
Rate double This field can only be specified if logging is enabled for this backend service. The value of the field must be in [0, 1]. This configures the sampling rate of requests to the load balancer where 1.0 means all logged requests are reported and 0.0 means no logged requests are reported. The default value is 1.0.
- Enable bool
Whether to enable logging for the load balancer traffic served by this backend service.
- Sample
Rate float64 This field can only be specified if logging is enabled for this backend service. The value of the field must be in [0, 1]. This configures the sampling rate of requests to the load balancer where 1.0 means all logged requests are reported and 0.0 means no logged requests are reported. The default value is 1.0.
- enable boolean
Whether to enable logging for the load balancer traffic served by this backend service.
- sample
Rate number This field can only be specified if logging is enabled for this backend service. The value of the field must be in [0, 1]. This configures the sampling rate of requests to the load balancer where 1.0 means all logged requests are reported and 0.0 means no logged requests are reported. The default value is 1.0.
- enable bool
Whether to enable logging for the load balancer traffic served by this backend service.
- sample
Rate float This field can only be specified if logging is enabled for this backend service. The value of the field must be in [0, 1]. This configures the sampling rate of requests to the load balancer where 1.0 means all logged requests are reported and 0.0 means no logged requests are reported. The default value is 1.0.
RegionBackendServiceOutlierDetection
- Base
Ejection RegionTime Backend Service Outlier Detection Base Ejection Time Args The base time that a host is ejected for. The real time is equal to the base time multiplied by the number of times the host has been ejected. Defaults to 30000ms or 30s. Structure is documented below.
- Consecutive
Errors int Number of errors before a host is ejected from the connection pool. When the backend host is accessed over HTTP, a 5xx return code qualifies as an error. Defaults to 5.
- Consecutive
Gateway intFailure The number of consecutive gateway failures (502, 503, 504 status or connection errors that are mapped to one of those status codes) before a consecutive gateway failure ejection occurs. Defaults to 5.
- Enforcing
Consecutive intErrors The percentage chance that a host will be actually ejected when an outlier status is detected through consecutive 5xx. This setting can be used to disable ejection or to ramp it up slowly. Defaults to 100.
- Enforcing
Consecutive intGateway Failure The percentage chance that a host will be actually ejected when an outlier status is detected through consecutive gateway failures. This setting can be used to disable ejection or to ramp it up slowly. Defaults to 0.
- Enforcing
Success intRate The percentage chance that a host will be actually ejected when an outlier status is detected through success rate statistics. This setting can be used to disable ejection or to ramp it up slowly. Defaults to 100.
- Interval
Region
Backend Service Outlier Detection Interval Args Time interval between ejection sweep analysis. This can result in both new ejections as well as hosts being returned to service. Defaults to 10 seconds. Structure is documented below.
- Max
Ejection intPercent Maximum percentage of hosts in the load balancing pool for the backend service that can be ejected. Defaults to 10%.
- Success
Rate intMinimum Hosts The number of hosts in a cluster that must have enough request volume to detect success rate outliers. If the number of hosts is less than this setting, outlier detection via success rate statistics is not performed for any host in the cluster. Defaults to 5.
- Success
Rate intRequest Volume The minimum number of total requests that must be collected in one interval (as defined by the interval duration above) to include this host in success rate based outlier detection. If the volume is lower than this setting, outlier detection via success rate statistics is not performed for that host. Defaults to 100.
- Success
Rate intStdev Factor This factor is used to determine the ejection threshold for success rate outlier ejection. The ejection threshold is the difference between the mean success rate, and the product of this factor and the standard deviation of the mean success rate: mean - (stdev * success_rate_stdev_factor). This factor is divided by a thousand to get a double. That is, if the desired factor is 1.9, the runtime value should be 1900. Defaults to 1900.
- Base
Ejection RegionTime Backend Service Outlier Detection Base Ejection Time The base time that a host is ejected for. The real time is equal to the base time multiplied by the number of times the host has been ejected. Defaults to 30000ms or 30s. Structure is documented below.
- Consecutive
Errors int Number of errors before a host is ejected from the connection pool. When the backend host is accessed over HTTP, a 5xx return code qualifies as an error. Defaults to 5.
- Consecutive
Gateway intFailure The number of consecutive gateway failures (502, 503, 504 status or connection errors that are mapped to one of those status codes) before a consecutive gateway failure ejection occurs. Defaults to 5.
- Enforcing
Consecutive intErrors The percentage chance that a host will be actually ejected when an outlier status is detected through consecutive 5xx. This setting can be used to disable ejection or to ramp it up slowly. Defaults to 100.
- Enforcing
Consecutive intGateway Failure The percentage chance that a host will be actually ejected when an outlier status is detected through consecutive gateway failures. This setting can be used to disable ejection or to ramp it up slowly. Defaults to 0.
- Enforcing
Success intRate The percentage chance that a host will be actually ejected when an outlier status is detected through success rate statistics. This setting can be used to disable ejection or to ramp it up slowly. Defaults to 100.
- Interval
Region
Backend Service Outlier Detection Interval Time interval between ejection sweep analysis. This can result in both new ejections as well as hosts being returned to service. Defaults to 10 seconds. Structure is documented below.
- Max
Ejection intPercent Maximum percentage of hosts in the load balancing pool for the backend service that can be ejected. Defaults to 10%.
- Success
Rate intMinimum Hosts The number of hosts in a cluster that must have enough request volume to detect success rate outliers. If the number of hosts is less than this setting, outlier detection via success rate statistics is not performed for any host in the cluster. Defaults to 5.
- Success
Rate intRequest Volume The minimum number of total requests that must be collected in one interval (as defined by the interval duration above) to include this host in success rate based outlier detection. If the volume is lower than this setting, outlier detection via success rate statistics is not performed for that host. Defaults to 100.
- Success
Rate intStdev Factor This factor is used to determine the ejection threshold for success rate outlier ejection. The ejection threshold is the difference between the mean success rate, and the product of this factor and the standard deviation of the mean success rate: mean - (stdev * success_rate_stdev_factor). This factor is divided by a thousand to get a double. That is, if the desired factor is 1.9, the runtime value should be 1900. Defaults to 1900.
- base
Ejection RegionTime Backend Service Outlier Detection Base Ejection Time The base time that a host is ejected for. The real time is equal to the base time multiplied by the number of times the host has been ejected. Defaults to 30000ms or 30s. Structure is documented below.
- consecutive
Errors number Number of errors before a host is ejected from the connection pool. When the backend host is accessed over HTTP, a 5xx return code qualifies as an error. Defaults to 5.
- consecutive
Gateway numberFailure The number of consecutive gateway failures (502, 503, 504 status or connection errors that are mapped to one of those status codes) before a consecutive gateway failure ejection occurs. Defaults to 5.
- enforcing
Consecutive numberErrors The percentage chance that a host will be actually ejected when an outlier status is detected through consecutive 5xx. This setting can be used to disable ejection or to ramp it up slowly. Defaults to 100.
- enforcing
Consecutive numberGateway Failure The percentage chance that a host will be actually ejected when an outlier status is detected through consecutive gateway failures. This setting can be used to disable ejection or to ramp it up slowly. Defaults to 0.
- enforcing
Success numberRate The percentage chance that a host will be actually ejected when an outlier status is detected through success rate statistics. This setting can be used to disable ejection or to ramp it up slowly. Defaults to 100.
- interval
Region
Backend Service Outlier Detection Interval Time interval between ejection sweep analysis. This can result in both new ejections as well as hosts being returned to service. Defaults to 10 seconds. Structure is documented below.
- max
Ejection numberPercent Maximum percentage of hosts in the load balancing pool for the backend service that can be ejected. Defaults to 10%.
- success
Rate numberMinimum Hosts The number of hosts in a cluster that must have enough request volume to detect success rate outliers. If the number of hosts is less than this setting, outlier detection via success rate statistics is not performed for any host in the cluster. Defaults to 5.
- success
Rate numberRequest Volume The minimum number of total requests that must be collected in one interval (as defined by the interval duration above) to include this host in success rate based outlier detection. If the volume is lower than this setting, outlier detection via success rate statistics is not performed for that host. Defaults to 100.
- success
Rate numberStdev Factor This factor is used to determine the ejection threshold for success rate outlier ejection. The ejection threshold is the difference between the mean success rate, and the product of this factor and the standard deviation of the mean success rate: mean - (stdev * success_rate_stdev_factor). This factor is divided by a thousand to get a double. That is, if the desired factor is 1.9, the runtime value should be 1900. Defaults to 1900.
- base
Ejection Dict[RegionTime Backend Service Outlier Detection Base Ejection Time] The base time that a host is ejected for. The real time is equal to the base time multiplied by the number of times the host has been ejected. Defaults to 30000ms or 30s. Structure is documented below.
- consecutive
Errors float Number of errors before a host is ejected from the connection pool. When the backend host is accessed over HTTP, a 5xx return code qualifies as an error. Defaults to 5.
- consecutive
Gateway floatFailure The number of consecutive gateway failures (502, 503, 504 status or connection errors that are mapped to one of those status codes) before a consecutive gateway failure ejection occurs. Defaults to 5.
- enforcing
Consecutive floatErrors The percentage chance that a host will be actually ejected when an outlier status is detected through consecutive 5xx. This setting can be used to disable ejection or to ramp it up slowly. Defaults to 100.
- enforcing
Consecutive floatGateway Failure The percentage chance that a host will be actually ejected when an outlier status is detected through consecutive gateway failures. This setting can be used to disable ejection or to ramp it up slowly. Defaults to 0.
- enforcing
Success floatRate The percentage chance that a host will be actually ejected when an outlier status is detected through success rate statistics. This setting can be used to disable ejection or to ramp it up slowly. Defaults to 100.
- interval
Dict[Region
Backend Service Outlier Detection Interval] Time interval between ejection sweep analysis. This can result in both new ejections as well as hosts being returned to service. Defaults to 10 seconds. Structure is documented below.
- max
Ejection floatPercent Maximum percentage of hosts in the load balancing pool for the backend service that can be ejected. Defaults to 10%.
- success
Rate floatMinimum Hosts The number of hosts in a cluster that must have enough request volume to detect success rate outliers. If the number of hosts is less than this setting, outlier detection via success rate statistics is not performed for any host in the cluster. Defaults to 5.
- success
Rate floatRequest Volume The minimum number of total requests that must be collected in one interval (as defined by the interval duration above) to include this host in success rate based outlier detection. If the volume is lower than this setting, outlier detection via success rate statistics is not performed for that host. Defaults to 100.
- success
Rate floatStdev Factor This factor is used to determine the ejection threshold for success rate outlier ejection. The ejection threshold is the difference between the mean success rate, and the product of this factor and the standard deviation of the mean success rate: mean - (stdev * success_rate_stdev_factor). This factor is divided by a thousand to get a double. That is, if the desired factor is 1.9, the runtime value should be 1900. Defaults to 1900.
RegionBackendServiceOutlierDetectionBaseEjectionTime
- Seconds int
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- Nanos int
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
- Seconds int
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- Nanos int
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
- seconds number
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- nanos number
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
- seconds float
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- nanos float
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
RegionBackendServiceOutlierDetectionInterval
- Seconds int
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- Nanos int
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
- Seconds int
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- Nanos int
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
- seconds number
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- nanos number
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
- seconds float
Span of time at a resolution of a second. Must be from 0 to 315,576,000,000 inclusive.
- nanos float
Span of time that’s a fraction of a second at nanosecond resolution. Durations less than one second are represented with a 0
secondsfield and a positivenanosfield. Must be from 0 to 999,999,999 inclusive.
Package Details
- Repository
- https://github.com/pulumi/pulumi-gcp
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
google-betaTerraform Provider.