- Resource: BackendService
- JSON representation
- Backend
- BalancingMode
- Preference
- Protocol
- FailoverPolicy
- LoadBalancingScheme
- ConnectionDraining
- IAP
- CdnPolicy
- CacheKeyPolicy
- CacheMode
- NegativeCachingPolicy
- BypassCacheOnRequestHeader
- LogConfig
- OptionalMode
- SecuritySettings
- AWSV4Signature
- LocalityLoadBalancingPolicy
- ConsistentHashLoadBalancerSettings
- HttpCookie
- CircuitBreakers
- OutlierDetection
- Subsetting
- Policy
- ConnectionTrackingPolicy
- TrackingMode
- ConnectionPersistenceOnUnhealthyBackends
- CompressionMode
- LocalityLoadBalancingPolicyConfig
- Policy
- CustomPolicy
- IpAddressSelectionPolicy
- UsedBy
- HttpCookie
- Methods
Resource: BackendService
Represents a Backend Service resource.
A backend service defines how Google Cloud load balancers distribute traffic. The backend service configuration contains a set of values, such as the protocol used to connect to backends, various distribution and session settings, health checks, and timeouts. These settings provide fine-grained control over how your load balancer behaves. Most of the settings have default values that allow for easy configuration if you need to get started quickly.
Backend services in Google Compute Engine can be either regionally or globally scoped.
For more information, see Backend Services.
JSON representation |
---|
{ "kind": string, "id": string, "creationTimestamp": string, "name": string, "description": string, "selfLink": string, "backends": [ { object ( |
Fields | |
---|---|
kind |
[Output Only] Type of resource. Always
for backend services. |
id |
[Output Only] The unique identifier for the resource. This identifier is defined by the server. |
creation |
[Output Only] Creation timestamp in RFC3339 text format. |
name |
Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression |
description |
An optional description of this resource. Provide this property when you create the resource. |
self |
[Output Only] Server-defined URL for the resource. |
backends[] |
The list of backends that serve this BackendService. |
health |
The list of URLs to the healthChecks, httpHealthChecks (legacy), or httpsHealthChecks (legacy) resource for health checking this backend service. Not all backend services support legacy health checks. See Load balancer guide. Currently, at most one health check can be specified for each backend service. Backend services with instance group or zonal NEG backends must have a health check. Backend services with internet or serverless NEG backends must not have a health check. |
timeout |
The backend service timeout has a different meaning depending on the type of load balancer. For more information see, Backend service settings. The default is 30 seconds. The full range of timeout values allowed goes from 1 through 2,147,483,647 seconds. This value can be overridden in the PathMatcher configuration of the UrlMap that references this backend service. Not supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true. Instead, use
. |
port |
Deprecated in favor of
. The TCP port to connect on the backend. The default value is
. For internal passthrough Network Load Balancers and external passthrough Network Load Balancers, omit
. |
protocol |
The protocol this BackendService uses to communicate with backends. Possible values are HTTP, HTTPS, HTTP2, TCP, SSL, UDP or GRPC. depending on the chosen load balancer or Traffic Director configuration. Refer to the documentation for the load balancers or for Traffic Director for more information. Must be set to GRPC when the backend service is referenced by a URL map that is bound to target gRPC proxy. |
fingerprint |
Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking. This field will be ignored when inserting a BackendService. An up-to-date fingerprint must be provided in order to update the
, otherwise the request will fail with error
. To see the latest fingerprint, make a
request to retrieve a BackendService. A base64-encoded string. |
port |
A named port on a backend instance group representing the port for communication to the backend VMs in that group. The named port must be defined on each backend instance group. This parameter has no meaning if the backends are NEGs. For internal passthrough Network Load Balancers and external passthrough Network Load Balancers, omit
. |
enable |
If
, enables Cloud CDN for the backend service of a global external Application Load Balancer. |
session |
Type of session affinity to use. The default is
. Only
and
are supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true. For more details, see: Session Affinity. |
affinity |
Lifetime of cookies in seconds. This setting is applicable to Application Load Balancers and Traffic Director and requires GENERATED_COOKIE or HTTP_COOKIE session affinity. If set to
, the cookie is non-persistent and lasts only until the end of the browser session (or equivalent). The maximum allowed value is two weeks (
). Not supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true. |
region |
[Output Only] URL of the region where the regional backend service resides. This field is not applicable to global backend services. You must specify this field as part of the HTTP request URL. It is not settable as a field in the request body. |
failover |
Requires at least one backend instance group to be defined as a backup (failover) backend. For load balancers that have configurable failover: Internal passthrough Network Load Balancers and external passthrough Network Load Balancers. |
load |
Specifies the load balancer type. A backend service created for one type of load balancer cannot be used with another. For more information, refer to Choosing a load balancer. |
connection |
|
iap |
The configurations for Identity-Aware Proxy on this resource. Not available for internal passthrough Network Load Balancers and external passthrough Network Load Balancers. |
cdn |
Cloud CDN configuration for this BackendService. Only available for specified load balancer types. |
custom |
Headers that the load balancer adds to proxied requests. See Creating custom headers. |
custom |
Headers that the load balancer adds to proxied responses. See Creating custom headers. |
security |
[Output Only] The resource URL for the security policy associated with this backend service. |
edge |
[Output Only] The resource URL for the edge security policy associated with this backend service. |
log |
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. |
security |
This field specifies the security settings that apply to this backend service. This field is applicable to a global backend service with the loadBalancingScheme set to INTERNAL_SELF_MANAGED. |
locality |
The load balancing algorithm used within the scope of the locality. The possible values are:
This field is applicable to either: If
is not configured—that is, if session affinity remains at the default value of
—then the default value for
is
. If session affinity is set to a value other than
, then the default value for
is
. Only
and
are supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true. |
consistent |
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 is only applicable when
is set to
or
. This field is applicable to either:
|
circuit |
|
outlier |
Settings controlling the ejection of unhealthy backend endpoints from the load balancing pool of each individual proxy instance that processes the traffic for the given backend service. If not set, this feature is considered disabled. Results of the outlier detection algorithm (ejection of endpoints from the load balancing pool and returning them back to the pool) are executed independently by each proxy instance of the load balancer. In most cases, more than one proxy instance handles the traffic received by a backend service. Thus, it is possible that an unhealthy endpoint is detected and ejected by only some of the proxies, and while this happens, other proxies may continue to send requests to the same unhealthy endpoint until they detect and eject the unhealthy endpoint. Applicable backend endpoints can be:
Applicable backend service types can be:
Not supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true. |
network |
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
. |
subsetting |
|
connection |
Connection Tracking configuration for this BackendService. Connection tracking policy settings are only available for external passthrough Network Load Balancers and internal passthrough Network Load Balancers. |
max |
Specifies the default maximum duration (timeout) for streams to this service. Duration is computed from the beginning of the stream until the response has been completely processed, including all retries. A stream that does not complete in this duration is closed. If not specified, there will be no timeout limit, i.e. the maximum duration is infinite. This value can be overridden in the PathMatcher configuration of the UrlMap that references this backend service. This field is only allowed when the
of the backend service is
. |
compression |
Compress text responses using Brotli or gzip compression, based on the client's Accept-Encoding header. |
service |
URL to
resource. Can only be set if load balancing scheme is EXTERNAL, EXTERNAL_MANAGED, INTERNAL_MANAGED or INTERNAL_SELF_MANAGED and the scope is global. |
service |
URLs of
resources. Can only be set if load balancing scheme is INTERNAL_SELF_MANAGED. If set, lists of backends and health checks must be both empty. |
locality |
A list of locality load-balancing policies to be used in order of preference. When you use localityLbPolicies, you must set at least one value for either the localityLbPolicies[].policy or the localityLbPolicies[].customPolicy field. localityLbPolicies overrides any value set in the localityLbPolicy field. For an example of how to use this field, see Define a list of preferred policies. Caution: This field and its children are intended for use in a service mesh that includes gRPC clients only. Envoy proxies can't use backend services that have this configuration. |
ip |
Specifies a preference for traffic sent from the proxy to the backend (or from the client to the backend for proxyless gRPC). The possible values are:
This field is applicable to either:
|
metadatas |
Deployment metadata associated with the resource to be set by a GKE hub controller and read by the backend RCTH |
used |
[Output Only] backendServices.list of resources referencing given backend service. |
strong |
Describes the HTTP cookie used for stateful session affinity. This field is applicable and required if the
is set to
. |
Backend
Message containing information of one individual backend.
JSON representation |
---|
{ "description": string, "group": string, "balancingMode": enum ( |
Fields | |
---|---|
description |
An optional description of this resource. Provide this property when you create the resource. |
group |
The fully-qualified URL of an instance group or network endpoint group (NEG) resource. To determine what types of backends a load balancer supports, see the Backend services overview. You must use the fully-qualified URL (starting with ) to specify the instance group or NEG. Partial URLs are not supported. |
balancing |
Specifies how to determine whether the backend of a load balancer can handle additional traffic or is fully loaded. For usage guidelines, see Connection balancing mode. Backends must use compatible balancing modes. For more information, see Supported balancing modes and target capacity settings and Restrictions and guidance for instance groups. Note: Currently, if you use the API to configure incompatible balancing modes, the configuration might be accepted even though it has no impact and is ignored. Specifically, Backend.maxUtilization is ignored when Backend.balancingMode is RATE. In the future, this incompatible combination will be rejected. |
max |
Optional parameter to define a target capacity for the
balancing mode. The valid range is
. For usage guidelines, see Utilization balancing mode. |
max |
Defines a maximum number of HTTP requests per second (RPS). For usage guidelines, see Rate balancing mode and Utilization balancing mode. Not available if the backend's
is
. |
max |
Defines a maximum target for requests per second (RPS). For usage guidelines, see Rate balancing mode and Utilization balancing mode. Not available if the backend's
is
. |
max |
Defines a maximum target for requests per second (RPS). For usage guidelines, see Rate balancing mode and Utilization balancing mode. Not available if the backend's
is
. |
max |
Defines a target maximum number of simultaneous connections. For usage guidelines, see Connection balancing mode and Utilization balancing mode. Not available if the backend's
is
. |
max |
Defines a target maximum number of simultaneous connections. For usage guidelines, see Connection balancing mode and Utilization balancing mode. Not available if the backend's
is
. |
max |
Defines a target maximum number of simultaneous connections. For usage guidelines, see Connection balancing mode and Utilization balancing mode. Not available if the backend's
is
. |
capacity |
A multiplier applied to the backend's target capacity of its balancing mode. The default value is
, which means the group serves up to 100% of its configured capacity (depending on
). A setting of
means the group is completely drained, offering 0% of its available capacity. The valid ranges are
and [0.1,1.0]. You cannot configure a setting larger than
and smaller than
. You cannot configure a setting of
when there is only one backend attached to the backend service. Not available with backends that don't support using a
. This includes backends such as global internet NEGs, regional serverless NEGs, and PSC NEGs. |
failover |
This field designates whether this is a failover backend. More than one failover backend can be configured for a given BackendService. |
preference |
This field indicates whether this backend should be fully utilized before sending traffic to backends with default preference. The possible values are:
|
BalancingMode
Enums | |
---|---|
UTILIZATION |
Balance based on the backend utilization. |
RATE |
Balance based on requests per second (RPS). |
CONNECTION |
Balance based on the number of simultaneous connections. |
Preference
The preference level of backends that is used to decide which backends should be used first.
Enums | |
---|---|
PREFERENCE_UNSPECIFIED |
If preference is unspecified, we set it to the DEFAULT value |
DEFAULT |
No preference. |
PREFERRED |
Traffic will be sent to this backend first. |
Protocol
The protocol this BackendService uses to communicate with backends.
Enums | |
---|---|
HTTP |
|
HTTPS |
|
HTTP2 |
HTTP/2 with SSL. |
TCP |
TCP proxying or TCP pass-through. |
SSL |
TCP proxying with SSL. |
UDP |
UDP. |
GRPC |
gRPC (available for Traffic Director). |
UNSPECIFIED |
If a Backend Service has UNSPECIFIED as its protocol, it can be used with any L3/L4 Forwarding Rules. |
FailoverPolicy
For load balancers that have configurable failover: Internal passthrough Network Load Balancers and external passthrough Network Load Balancers. On failover or failback, this field indicates whether connection draining will be honored. Google Cloud has a fixed connection draining timeout of 10 minutes. A setting of
true
terminates existing TCP connections to the active pool during failover and failback, immediately draining traffic. A setting of
false
allows existing TCP connections to persist, even on VMs no longer in the active pool, for up to the duration of the connection draining timeout (10 minutes).
JSON representation |
---|
{ "disableConnectionDrainOnFailover": boolean, "dropTrafficIfUnhealthy": boolean, "failoverRatio": number } |
Fields | |
---|---|
disable |
This can be set to
only if the
is
. The default is
. |
drop |
If set to
, connections to the load balancer are dropped when all primary and all backup backend VMs are unhealthy.If set to
, connections are distributed among all primary VMs when all primary and all backup backend VMs are unhealthy. For load balancers that have configurable failover: Internal passthrough Network Load Balancers and external passthrough Network Load Balancers. The default is
. |
failover |
The value of the field must be in the range
. If the value is 0, the load balancer performs a failover when the number of healthy primary VMs equals zero. For all other values, the load balancer performs a failover when the total number of healthy primary VMs is less than this ratio. For load balancers that have configurable failover: Internal TCP/UDP Load Balancing and external TCP/UDP Load Balancing. |
LoadBalancingScheme
Enums | |
---|---|
INVALID_LOAD_BALANCING_SCHEME |
|
INTERNAL |
Signifies that this will be used for internal passthrough Network Load Balancers. |
INTERNAL_MANAGED |
Signifies that this will be used for internal Application Load Balancers. |
INTERNAL_SELF_MANAGED |
Signifies that this will be used by Traffic Director. |
EXTERNAL |
Signifies that this will be used for classic Application Load Balancers, global external proxy Network Load Balancers, or external passthrough Network Load Balancers. |
EXTERNAL_MANAGED |
Signifies that this will be used for global external Application Load Balancers, regional external Application Load Balancers, or regional external proxy Network Load Balancers. |
ConnectionDraining
Message containing connection draining configuration.
JSON representation |
---|
{ "drainingTimeoutSec": integer } |
Fields | |
---|---|
draining |
Configures a duration timeout for existing requests on a removed backend instance. For supported load balancers and protocols, as described in Enabling connection draining. |
IAP
Identity-Aware Proxy
JSON representation |
---|
{ "enabled": boolean, "oauth2ClientId": string, "oauth2ClientSecret": string, "oauth2ClientSecretSha256": string } |
Fields | |
---|---|
enabled |
Whether the serving infrastructure will authenticate and authorize all incoming requests. |
oauth2 |
OAuth2 client ID to use for the authentication flow. |
oauth2 |
OAuth2 client secret to use for the authentication flow. For security reasons, this value cannot be retrieved via the API. Instead, the SHA-256 hash of the value is returned in the oauth2ClientSecretSha256 field. @InputOnly |
oauth2 |
[Output Only] SHA256 hash value for the field oauth2ClientSecret above. |
CdnPolicy
Message containing Cloud CDN configuration for a backend service.
JSON representation |
---|
{ "cacheKeyPolicy": { object ( |
Fields | |
---|---|
cache |
The CacheKeyPolicy for this CdnPolicy. |
signed |
[Output Only] Names of the keys for signing request URLs. |
signed |
Maximum number of seconds the response to a signed URL request will be considered fresh. After this time period, the response will be revalidated before being served. Defaults to 1hr (3600s). When serving responses to signed URL requests, Cloud CDN will internally behave as though all responses from this backend had a
header, regardless of any existing Cache-Control header. The actual headers served in responses will not be altered. |
request |
If true then Cloud CDN will combine multiple concurrent cache fill requests into a small number of requests to the origin. |
cache |
Specifies the cache setting for all responses from this backend. The possible values are:
Requires the origin to set valid caching headers to cache content. Responses without these headers will not be cached at Google's edge, and will require a full trip to the origin on every request, potentially impacting performance and increasing load on the origin server.
Cache all content, ignoring any "private", "no-store" or "no-cache" directives in Cache-Control response headers. Warning: this may result in Cloud CDN caching private, per-user (user identifiable) content.
Automatically cache static content, including common image formats, media (video and audio), and web assets (JavaScript and CSS). Requests and responses that are marked as uncacheable, as well as dynamic content (including HTML), will not be cached. If no value is provided for
, it defaults to
. |
default |
Specifies the default TTL for cached content served by this origin for responses that do not have an existing valid TTL (max-age or s-max-age). Setting a TTL of "0" means "always revalidate". The value of defaultTTL cannot be set to a value greater than that of maxTTL, but can be equal. When the cacheMode is set to
, the defaultTTL will overwrite the TTL set in all responses. The maximum allowed value is 31,622,400s (1 year), noting that infrequently accessed objects may be evicted from the cache before the defined TTL. |
max |
Specifies the maximum allowed TTL for cached content served by this origin. Cache directives that attempt to set a max-age or s-maxage higher than this, or an Expires header more than maxTTL seconds in the future will be capped at the value of maxTTL, as if it were the value of an s-maxage Cache-Control directive. Headers sent to the client will not be modified. Setting a TTL of "0" means "always revalidate". The maximum allowed value is 31,622,400s (1 year), noting that infrequently accessed objects may be evicted from the cache before the defined TTL. |
client |
Specifies a separate client (e.g. browser client) maximum TTL. This is used to clamp the max-age (or Expires) value sent to the client. With FORCE_CACHE_ALL, the lesser of clientTtl and defaultTtl is used for the response max-age directive, along with a "public" directive. For cacheable content in CACHE_ALL_STATIC mode, clientTtl clamps the max-age from the origin (if specified), or else sets the response max-age directive to the lesser of the clientTtl and defaultTtl, and also ensures a "public" cache-control directive is present. If a client TTL is not specified, a default value (1 hour) will be used. The maximum allowed value is 31,622,400s (1 year). |
negative |
Negative caching allows per-status code TTLs to be set, in order to apply fine-grained caching for common errors or redirects. This can reduce the load on your origin and improve end-user experience by reducing response latency. When the cache mode is set to CACHE_ALL_STATIC or USE_ORIGIN_HEADERS, negative caching applies to responses with the specified response code that lack any Cache-Control, Expires, or Pragma: no-cache directives. When the cache mode is set to FORCE_CACHE_ALL, negative caching applies to all responses with the specified response code, and override any caching headers. By default, Cloud CDN will apply the following default TTLs to these status codes: HTTP 300 (Multiple Choice), 301, 308 (Permanent Redirects): 10m HTTP 404 (Not Found), 410 (Gone), 451 (Unavailable For Legal Reasons): 120s HTTP 405 (Method Not Found), 421 (Misdirected Request), 501 (Not Implemented): 60s. These defaults can be overridden in negativeCachingPolicy. |
negative |
Sets a cache TTL for the specified HTTP status code. negativeCaching must be enabled to configure negativeCachingPolicy. Omitting the policy and leaving negativeCaching enabled will use Cloud CDN's default cache TTLs. Note that when specifying an explicit negativeCachingPolicy, you should take care to specify a cache TTL for all response codes that you wish to cache. Cloud CDN will not apply any default negative caching when a policy exists. |
bypass |
Bypass the cache when the specified request headers are matched - e.g. Pragma or Authorization headers. Up to 5 headers can be specified. The cache is bypassed for all cdnPolicy.cacheMode settings. |
serve |
Serve existing content from the cache (if available) when revalidating content with the origin, or when an error is encountered when refreshing the cache. This setting defines the default "max-stale" duration for any cached responses that do not specify a max-stale directive. Stale responses that exceed the TTL configured here will not be served. The default limit (max-stale) is 86400s (1 day), which will allow stale content to be served up to this limit beyond the max-age (or s-max-age) of a cached response. The maximum allowed value is 604800 (1 week). Set this to zero (0) to disable serve-while-stale. |
CacheKeyPolicy
Message containing what to include in the cache key for a request for Cloud CDN.
JSON representation |
---|
{ "includeProtocol": boolean, "includeHost": boolean, "includeQueryString": boolean, "queryStringWhitelist": [ string ], "queryStringBlacklist": [ string ], "includeHttpHeaders": [ string ], "includeNamedCookies": [ string ] } |
Fields | |
---|---|
include |
If true, http and https requests will be cached separately. |
include |
If true, requests to different hosts will be cached separately. |
include |
If true, include query string parameters in the cache key according to queryStringWhitelist and queryStringBlacklist. If neither is set, the entire query string will be included. If false, the query string will be excluded from the cache key entirely. |
query |
Names of query string parameters to include in cache keys. All other parameters will be excluded. Either specify queryStringWhitelist or queryStringBlacklist, not both. '&' and '=' will be percent encoded and not treated as delimiters. |
query |
Names of query string parameters to exclude in cache keys. All other parameters will be included. Either specify queryStringWhitelist or queryStringBlacklist, not both. '&' and '=' will be percent encoded and not treated as delimiters. |
include |
Allows HTTP request headers (by name) to be used in the cache key. |
include |
Allows HTTP cookies (by name) to be used in the cache key. The name=value pair will be used in the cache key Cloud CDN generates. |
CacheMode
Enums | |
---|---|
INVALID_CACHE_MODE |
|
USE_ORIGIN_HEADERS |
Requires the origin to set valid caching headers to cache content. Responses without these headers will not be cached at Google's edge, and will require a full trip to the origin on every request, potentially impacting performance and increasing load on the origin server. |
FORCE_CACHE_ALL |
Cache all content, ignoring any "private", "no-store" or "no-cache" directives in Cache-Control response headers. Warning: this may result in Cloud CDN caching private, per-user (user identifiable) content. |
CACHE_ALL_STATIC |
Automatically cache static content, including common image formats, media (video and audio), and web assets (JavaScript and CSS). Requests and responses that are marked as uncacheable, as well as dynamic content (including HTML), will not be cached. |
NegativeCachingPolicy
Specify CDN TTLs for response error codes.
JSON representation |
---|
{ "code": integer, "ttl": integer } |
Fields | |
---|---|
code |
The HTTP status code to define a TTL against. Only HTTP status codes 300, 301, 302, 307, 308, 404, 405, 410, 421, 451 and 501 are can be specified as values, and you cannot specify a status code more than once. |
ttl |
The TTL (in seconds) for which to cache responses with the corresponding status code. The maximum allowed value is 1800s (30 minutes), noting that infrequently accessed objects may be evicted from the cache before the defined TTL. |
BypassCacheOnRequestHeader
Bypass the cache when the specified request headers are present, e.g. Pragma or Authorization headers. Values are case insensitive. The presence of such a header overrides the cacheMode setting.
JSON representation |
---|
{ "headerName": string } |
Fields | |
---|---|
header |
The header field name to match on when bypassing cache. Values are case-insensitive. |
LogConfig
The available logging options for the load balancer traffic served by this backend service.
JSON representation |
---|
{
"enable": boolean,
"sampleRate": number,
"optionalMode": enum ( |
Fields | |
---|---|
enable |
Denotes whether to enable logging for the load balancer traffic served by this backend service. The default value is false. |
sample |
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. |
optional |
This field can only be specified if logging is enabled for this backend service. Configures whether all, none or a subset of optional fields should be added to the reported logs. One of [INCLUDE_ALL_OPTIONAL, EXCLUDE_ALL_OPTIONAL, CUSTOM]. Default is EXCLUDE_ALL_OPTIONAL. |
optional |
This field can only be specified if logging is enabled for this backend service and "logConfig.optionalMode" was set to CUSTOM. Contains a list of optional fields you want to include in the logs. For example: serverInstance, serverGkeDetails.cluster, serverGkeDetails.pod.podNamespace |
OptionalMode
Determines which optional fields should be added to the reported logs.
Enums | |
---|---|
EXCLUDE_ALL_OPTIONAL |
None optional fields. |
INCLUDE_ALL_OPTIONAL |
All optional fields. |
CUSTOM |
A subset of optional fields. |
SecuritySettings
The authentication and authorization settings for a BackendService.
JSON representation |
---|
{
"clientTlsPolicy": string,
"subjectAltNames": [
string
],
"awsV4Authentication": {
object ( |
Fields | |
---|---|
client |
Optional. A URL referring to a networksecurity.ClientTlsPolicy resource that describes how clients should authenticate with this service's backends.
only applies to a global
with the
set to
. If left blank, communications are not encrypted. |
subject |
Optional. A list of Subject Alternative Names (SANs) that the client verifies during a mutual TLS handshake with an server/endpoint for this
. When the server presents its X.509 certificate to the client, the client inspects the certificate's
field. If the field contains one of the specified values, the communication continues. Otherwise, it fails. This additional check enables the client to verify that the server is authorized to run the requested service. Note that the contents of the server certificate's
field are configured by the Public Key Infrastructure which provisions server identities. Only applies to a global
with
set to
. Only applies when
has an attached
with
(mTLS mode). |
aws |
The configuration needed to generate a signature for access to private storage buckets that support AWS's Signature Version 4 for authentication. Allowed only for INTERNET_IP_PORT and INTERNET_FQDN_PORT NEG backends. |
AWSV4Signature
Contains the configurations necessary to generate a signature for access to private storage buckets that support Signature Version 4 for authentication. The service name for generating the authentication header will always default to 's3'.
JSON representation |
---|
{ "accessKeyId": string, "accessKey": string, "accessKeyVersion": string, "originRegion": string } |
Fields | |
---|---|
access |
The identifier of an access key used for s3 bucket authentication. |
access |
The access key used for s3 bucket authentication. Required for updating or creating a backend that uses AWS v4 signature authentication, but will not be returned as part of the configuration when queried with a REST API GET request. @InputOnly |
access |
The optional version identifier for the access key. You can use this to keep track of different iterations of your access key. |
origin |
The name of the cloud region of your origin. This is a free-form field with the name of the region your cloud uses to host your origin. For example, "us-east-1" for AWS or "us-ashburn-1" for OCI. |
LocalityLoadBalancingPolicy
The load balancing policy used within a locality.
Enums | |
---|---|
INVALID_LB_POLICY |
|
ROUND_ROBIN |
This is a simple policy in which each healthy backend is selected in round robin order. This is the default. |
LEAST_REQUEST |
An
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 |
This algorithm implements consistent hashing to backends. Maglev can be 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, see https://ai.google/research/pubs/pub44824 |
WEIGHTED_MAGLEV |
Per-instance weighted Load Balancing via health check reported weights. If set, the Backend Service must configure a non legacy HTTP-based Health Check, and health check replies are expected to contain non-standard HTTP response header field X-Load-Balancing-Endpoint-Weight to specify the per-instance weights. If set, Load Balancing is weighted based on the per-instance weights reported in the last processed health check replies, as long as every instance either reported a valid weight or had UNAVAILABLE_WEIGHT. Otherwise, Load Balancing remains equal-weight. This option is only supported in Network Load Balancing. |
ConsistentHashLoadBalancerSettings
This message defines settings for a consistent hash style load balancer.
JSON representation |
---|
{
"httpCookie": {
object ( |
Fields | |
---|---|
http |
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
is set to
. Not supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true. |
http |
The hash based on the value of the specified header field. This field is applicable if the
is set to
. |
minimum |
The minimum number of virtual nodes to use for the hash ring. Defaults to 1024. 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. |
HttpCookie
The information about the HTTP Cookie on which the hash function is based for load balancing policies that use a consistent hash.
JSON representation |
---|
{
"name": string,
"path": string,
"ttl": {
object ( |
Fields | |
---|---|
name |
Name of the cookie. |
path |
Path to set for the cookie. |
ttl |
Lifetime of the cookie. |
CircuitBreakers
Settings controlling the volume of requests, connections and retries to this backend service.
JSON representation |
---|
{ "maxRequestsPerConnection": integer, "maxConnections": integer, "maxPendingRequests": integer, "maxRequests": integer, "maxRetries": integer } |
Fields | |
---|---|
max |
Maximum requests for a single connection to the backend service. 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. Not supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true. |
max |
The maximum number of connections to the backend service. If not specified, there is no limit. Not supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true. |
max |
The maximum number of pending requests allowed to the backend service. If not specified, there is no limit. Not supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true. |
max |
The maximum number of parallel requests that allowed to the backend service. If not specified, there is no limit. |
max |
The maximum number of parallel retries allowed to the backend cluster. If not specified, the default is 1. Not supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true. |
OutlierDetection
Settings controlling the eviction of unhealthy hosts from the load balancing pool for the backend service.
JSON representation |
---|
{ "consecutiveErrors": integer, "interval": { object ( |
Fields | |
---|---|
consecutive |
Number of consecutive errors before a backend endpoint is ejected from the load balancing pool. When the backend endpoint is accessed over HTTP, a 5xx return code qualifies as an error. Defaults to 5. |
interval |
Time interval between ejection analysis sweeps. This can result in both new ejections and backend endpoints being returned to service. The interval is equal to the number of seconds as defined in outlierDetection.interval.seconds plus the number of nanoseconds as defined in outlierDetection.interval.nanos. Defaults to 1 second. |
base |
The base time that a backend endpoint is ejected for. Defaults to 30000ms or 30s. After a backend endpoint is returned back to the load balancing pool, it can be ejected again in another ejection analysis. Thus, the total ejection time is equal to the base ejection time multiplied by the number of times the backend endpoint has been ejected. Defaults to 30000ms or 30s. |
max |
Maximum percentage of backend endpoints in the load balancing pool for the backend service that can be ejected if the ejection conditions are met. Defaults to 50%. |
enforcing |
The percentage chance that a backend endpoint will be 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 0. |
enforcing |
The percentage chance that a backend endpoint will be 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. Not supported when the backend service uses Serverless NEG. |
success |
The number of backend endpoints in the load balancing pool that must have enough request volume to detect success rate outliers. If the number of backend endpoints is fewer than this setting, outlier detection via success rate statistics is not performed for any backend endpoint in the load balancing pool. Defaults to 5. Not supported when the backend service uses Serverless NEG. |
success |
The minimum number of total requests that must be collected in one interval (as defined by the interval duration above) to include this backend endpoint 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 backend endpoint. Defaults to 100. Not supported when the backend service uses Serverless NEG. |
success |
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 * successRateStdevFactor). 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. Not supported when the backend service uses Serverless NEG. |
consecutive |
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 3. |
enforcing |
The percentage chance that a backend endpoint will be 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 100. |
Subsetting
Subsetting configuration for this BackendService. Currently this is applicable only for Internal TCP/UDP load balancing, Internal HTTP(S) load balancing and Traffic Director.
JSON representation |
---|
{
"policy": enum ( |
Fields | |
---|---|
policy |
|
Policy
The algorithm used for subsetting. The default value is 'NONE'.
Enums | |
---|---|
NONE |
No Subsetting. Clients may open connections and send traffic to all backends of this backend service. This can lead to performance issues if there is substantial imbalance in the count of clients and backends. |
CONSISTENT_HASH_SUBSETTING |
Subsetting based on consistent hashing. For Traffic Director, the number of backends per backend group (the subset size) is based on the For Internal HTTP(S) load balancing, the number of backends per backend group (the subset size) is dynamically adjusted in two cases: - As the number of proxy instances participating in Internal HTTP(S) load balancing increases, the subset size decreases. - When the total number of backends in a network exceeds the capacity of a single proxy instance, subset sizes are reduced automatically for each service that has backend subsetting enabled. |
ConnectionTrackingPolicy
Connection Tracking configuration for this BackendService.
JSON representation |
---|
{ "trackingMode": enum ( |
Fields | |
---|---|
tracking |
Specifies the key used for connection tracking. There are two options:
For more details, see Tracking Mode for Network Load Balancing and Tracking Mode for Internal TCP/UDP Load Balancing. |
connection |
Specifies connection persistence when backends are unhealthy. The default value is
. If set to
, the existing connections persist on unhealthy backends only for connection-oriented protocols (
and
) and only if the Tracking Mode is
(default tracking mode) or the Session Affinity is configured for 5-tuple. They do not persist for
. If set to
, after a backend becomes unhealthy, the existing connections on the unhealthy backend are never persisted on the unhealthy backend. They are always diverted to newly selected healthy backends (unless all backends are unhealthy). If set to
, existing connections always persist on unhealthy backends regardless of protocol and session affinity. It is generally not recommended to use this mode overriding the default. For more details, see Connection Persistence for Network Load Balancing and Connection Persistence for Internal TCP/UDP Load Balancing. |
idle |
Specifies how long to keep a Connection Tracking entry while there is no matching traffic (in seconds). For internal passthrough Network Load Balancers:
For external passthrough Network Load Balancers the default is 60 seconds. This option is not available publicly. |
enable |
Enable Strong Session Affinity for external passthrough Network Load Balancers. This option is not available publicly. |
TrackingMode
Enums | |
---|---|
INVALID_TRACKING_MODE |
|
PER_CONNECTION |
|
PER_SESSION |
ConnectionPersistenceOnUnhealthyBackends
Enums | |
---|---|
DEFAULT_FOR_PROTOCOL |
|
NEVER_PERSIST |
|
ALWAYS_PERSIST |
CompressionMode
Compress text responses using Brotli or gzip compression, based on the client's Accept-Encoding header.
Enums | |
---|---|
DISABLED |
Disables compression. Existing compressed responses cached by Cloud CDN will not be served to clients. |
AUTOMATIC |
Automatically uses the best compression based on the Accept-Encoding header sent by the client. |
LocalityLoadBalancingPolicyConfig
Container for either a built-in LB policy supported by gRPC or Envoy or a custom one implemented by the end user.
JSON representation |
---|
{ // Union field |
Fields | |
---|---|
Union field
|
|
policy |
|
custom |
|
Policy
The configuration for a built-in load balancing policy.
JSON representation |
---|
{
"name": enum ( |
Fields | |
---|---|
name |
The name of a locality load-balancing policy. Valid values include ROUND_ROBIN and, for Java clients, LEAST_REQUEST. For information about these values, see the description of localityLbPolicy. Do not specify the same policy more than once for a backend. If you do, the configuration is rejected. |
CustomPolicy
The configuration for a custom policy implemented by the user and deployed with the client.
JSON representation |
---|
{ "name": string, "data": string } |
Fields | |
---|---|
name |
Identifies the custom policy. The value should match the name of a custom implementation registered on the gRPC clients. It should follow protocol buffer message naming conventions and include the full path (for example, myorg.CustomLbPolicy). The maximum length is 256 characters. Do not specify the same custom policy more than once for a backend. If you do, the configuration is rejected. For an example of how to use this field, see Use a custom policy. |
data |
An optional, arbitrary JSON object with configuration data, understood by a locally installed custom policy implementation. |
IpAddressSelectionPolicy
Enums | |
---|---|
IP_ADDRESS_SELECTION_POLICY_UNSPECIFIED |
Unspecified IP address selection policy. |
IPV4_ONLY |
Only send IPv4 traffic to the backends of the Backend Service (Instance Group, Managed Instance Group, Network Endpoint Group) regardless of traffic from the client to the proxy. Only IPv4 health-checks are used to check the health of the backends. This is the default setting. |
PREFER_IPV6 |
Prioritize the connection to the endpoints IPv6 address over its IPv4 address (provided there is a healthy IPv6 address). |
IPV6_ONLY |
Only send IPv6 traffic to the backends of the Backend Service (Instance Group, Managed Instance Group, Network Endpoint Group) regardless of traffic from the client to the proxy. Only IPv6 health-checks are used to check the health of the backends. |
UsedBy
JSON representation |
---|
{ "reference": string } |
Fields | |
---|---|
reference |
[Output Only] Server-defined URL for resources referencing given BackendService like UrlMaps, TargetTcpProxies, TargetSslProxies and ForwardingRule. |
HttpCookie
The HTTP cookie used for stateful session affinity.
JSON representation |
---|
{
"name": string,
"path": string,
"ttl": {
object ( |
Fields | |
---|---|
name |
Name of the cookie. |
path |
Path to set for the cookie. |
ttl |
Lifetime of the cookie. |
Methods |
|
---|---|
|
The method compute.v1.BackendServicesService.AddSignedUrlKey is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.AggregatedList is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.Delete is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.DeleteSignedUrlKey is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.Get is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.GetHealth is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.GetPolicy is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.Insert is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.List is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.ListUsable is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.Patch is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.SetEdgeSecurityPolicy is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.SetPolicy is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.SetSecurityPolicy is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.TestPermissions is not available in this (s3nsapis.fr) universe. |
|
The method compute.v1.BackendServicesService.Update is not available in this (s3nsapis.fr) universe. |