RegionBackendService is the Schema for the RegionBackendServices API. A Region Backend Service defines a regionally-scoped group of virtual machines that will serve traffic for load balancing.
Type
CRD
Group
compute.gcp.upbound.io
Version
v1beta1
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RegionBackendService
RegionBackendServiceSpec defines the desired state of RegionBackendService
No description provided.
The set of backends that serve this RegionBackendService. Structure is documented below.
Reference to a RegionInstanceGroupManager to populate group.
Policies for referencing.
Selector for a RegionInstanceGroupManager to populate group.
Policies for selection.
Cloud CDN configuration for this BackendService. Structure is documented below.
The CacheKeyPolicy for this CdnPolicy. Structure is documented below.
Names of cookies to include in cache keys.
Names of query string parameters to exclude in cache keys. All other parameters will be included. Either specify query_string_whitelist or query_string_blacklist, not both. '&' and '=' will be percent encoded and not treated as delimiters.
Names of query string parameters to include in cache keys. All other parameters will be excluded. Either specify query_string_whitelist or query_string_blacklist, not both. '&' and '=' will be percent encoded and not treated as delimiters.
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. Structure is documented below.
Settings controlling the volume of connections to a backend service. This field is applicable only when the load_balancing_scheme is set to INTERNAL_MANAGED and the protocol is set to HTTP, HTTPS, or HTTP2. Structure is documented below.
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 -
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.
Policy for failovers. Structure is documented below.
The set of URLs to HealthCheck resources for health checking this RegionBackendService. Currently at most one health check can be specified. A health check must be specified unless the backend service uses an internet or serverless NEG as a backend.
References to RegionHealthCheck to populate healthChecks.
Policies for referencing.
Selector for a list of RegionHealthCheck to populate healthChecks.
Policies for selection.
Settings for enabling Cloud Identity Aware Proxy Structure is documented below.
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.
Settings controlling eviction of unhealthy hosts from the load balancing pool. This field is applicable only when the load_balancing_scheme is set to INTERNAL_MANAGED and the protocol is set to HTTP, HTTPS, or HTTP2. Structure is documented below.
THIS IS AN ALPHA FIELD. Do not use it in production. It is not honored unless the relevant Crossplane feature flag is enabled, and may be changed or removed without notice. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
The set of backends that serve this RegionBackendService. Structure is documented below.
Cloud CDN configuration for this BackendService. Structure is documented below.
The CacheKeyPolicy for this CdnPolicy. Structure is documented below.
Names of cookies to include in cache keys.
Names of query string parameters to exclude in cache keys. All other parameters will be included. Either specify query_string_whitelist or query_string_blacklist, not both. '&' and '=' will be percent encoded and not treated as delimiters.
Names of query string parameters to include in cache keys. All other parameters will be excluded. Either specify query_string_whitelist or query_string_blacklist, not both. '&' and '=' will be percent encoded and not treated as delimiters.
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. Structure is documented below.
Settings controlling the volume of connections to a backend service. This field is applicable only when the load_balancing_scheme is set to INTERNAL_MANAGED and the protocol is set to HTTP, HTTPS, or HTTP2. Structure is documented below.
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 -
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.
Policy for failovers. Structure is documented below.
Settings for enabling Cloud Identity Aware Proxy Structure is documented below.
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.
Settings controlling eviction of unhealthy hosts from the load balancing pool. This field is applicable only when the load_balancing_scheme is set to INTERNAL_MANAGED and the protocol is set to HTTP, HTTPS, or HTTP2. Structure is documented below.
THIS IS AN ALPHA FIELD. Do not use it in production. It is not honored unless the relevant Crossplane feature flag is enabled, and may be changed or removed without notice. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
RegionBackendServiceStatus defines the observed state of RegionBackendService.
No description provided.
The set of backends that serve this RegionBackendService. Structure is documented below.
Cloud CDN configuration for this BackendService. Structure is documented below.
The CacheKeyPolicy for this CdnPolicy. Structure is documented below.
Names of cookies to include in cache keys.
Names of query string parameters to exclude in cache keys. All other parameters will be included. Either specify query_string_whitelist or query_string_blacklist, not both. '&' and '=' will be percent encoded and not treated as delimiters.
Names of query string parameters to include in cache keys. All other parameters will be excluded. Either specify query_string_whitelist or query_string_blacklist, not both. '&' and '=' will be percent encoded and not treated as delimiters.
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. Structure is documented below.
Settings controlling the volume of connections to a backend service. This field is applicable only when the load_balancing_scheme is set to INTERNAL_MANAGED and the protocol is set to HTTP, HTTPS, or HTTP2. Structure is documented below.
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 -
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.
Policy for failovers. Structure is documented below.
The set of URLs to HealthCheck resources for health checking this RegionBackendService. Currently at most one health check can be specified. A health check must be specified unless the backend service uses an internet or serverless NEG as a backend.
Settings for enabling Cloud Identity Aware Proxy Structure is documented below.
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.
Settings controlling eviction of unhealthy hosts from the load balancing pool. This field is applicable only when the load_balancing_scheme is set to INTERNAL_MANAGED and the protocol is set to HTTP, HTTPS, or HTTP2. Structure is documented below.
Conditions of the resource.
region-target-https-proxy
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RegionBackendService
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/regiontargethttpproxy
labels:
testing.upbound.io/example-name: region-target-https-proxy
name: region-target-https-proxy
spec:
forProvider:
healthChecksRefs:
- name: region-target-https-proxy
loadBalancingScheme: INTERNAL_MANAGED
protocol: HTTP
region: us-central1
timeoutSec: 10
packet-mirroring
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RegionBackendService
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/packetmirroring
labels:
testing.upbound.io/example-name: packet-mirroring
name: packet-mirroring
spec:
forProvider:
healthChecksRefs:
- name: packet-mirroring
region: us-central1
region-backend-service
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RegionBackendService
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/regionbackendservice
labels:
testing.upbound.io/example-name: region-backend-service
name: region-backend-service
spec:
forProvider:
connectionDrainingTimeoutSec: 10
healthChecksRefs:
- name: region-backend-service
region: us-central1
sessionAffinity: CLIENT_IP
region-url-map-home
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RegionBackendService
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/regionurlmap
labels:
testing.upbound.io/example-name: region-url-map-home
name: region-url-map-home
spec:
forProvider:
healthChecksRefs:
- name: region-url-map
loadBalancingScheme: INTERNAL_MANAGED
protocol: HTTP
region: us-central1
region-target-http-proxy
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RegionBackendService
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/regiontargethttpproxy
labels:
testing.upbound.io/example-name: region-target-http-proxy
name: region-target-http-proxy
spec:
forProvider:
healthChecksRefs:
- name: region-target-http-proxy
loadBalancingScheme: INTERNAL_MANAGED
protocol: HTTP
region: us-central1
service-attachment
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RegionBackendService
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/serviceattachment
upjet.upbound.io/manual-intervention: Must be authorized to administer the domain gcp.example.com
labels:
testing.upbound.io/example-name: service-attachment
name: service-attachment
spec:
forProvider:
healthChecksSelector:
matchLabels:
testing.upbound.io/example-name: service-attachment
region: us-central1
region-url-map-login
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RegionBackendService
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/regionurlmap
labels:
testing.upbound.io/example-name: region-url-map-login
name: region-url-map-login
spec:
forProvider:
healthChecksRefs:
- name: region-url-map
loadBalancingScheme: INTERNAL_MANAGED
protocol: HTTP
region: us-central1
forwarding-rule
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RegionBackendService
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/forwardingrule
labels:
testing.upbound.io/example-name: forwarding-rule
name: forwarding-rule
spec:
forProvider:
backend:
- balancingMode: UTILIZATION
capacityScaler: 1
groupRef:
name: forwarding-rule
healthChecksSelector:
matchLabels:
testing.upbound.io/example-name: forwarding-rule
loadBalancingScheme: INTERNAL_MANAGED
protocol: HTTP
region: us-central1
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.