BackendBucket is the Schema for the BackendBuckets API. Backend buckets allow you to use Google Cloud Storage buckets with HTTP(S) load balancing.
Type
CRD
Group
compute.gcp.upbound.io
Version
v1beta1
apiVersion: compute.gcp.upbound.io/v1beta1
kind: BackendBucket
BackendBucketSpec defines the desired state of BackendBucket
No description provided.
Reference to a Bucket in storage to populate bucketName.
Policies for referencing.
Selector for a Bucket in storage to populate bucketName.
Policies for selection.
Cloud CDN configuration for this Backend Bucket. Structure is documented below.
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. Structure is documented below.
The CacheKeyPolicy for this CdnPolicy. Structure is documented below.
Allows HTTP request headers (by name) to be used in the cache key.
Names of query string parameters to include in cache keys. Default parameters are always included. '&' and '=' will be percent encoded and not treated as delimiters.
Headers that the HTTP/S load balancer should add to proxied responses.
Reference to a SecurityPolicy in compute to populate edgeSecurityPolicy.
Policies for referencing.
Selector for a SecurityPolicy in compute to populate edgeSecurityPolicy.
Policies for selection.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. 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.
Reference to a Bucket in storage to populate bucketName.
Policies for referencing.
Selector for a Bucket in storage to populate bucketName.
Policies for selection.
Cloud CDN configuration for this Backend Bucket. Structure is documented below.
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. Structure is documented below.
The CacheKeyPolicy for this CdnPolicy. Structure is documented below.
Allows HTTP request headers (by name) to be used in the cache key.
Names of query string parameters to include in cache keys. Default parameters are always included. '&' and '=' will be percent encoded and not treated as delimiters.
Headers that the HTTP/S load balancer should add to proxied responses.
Reference to a SecurityPolicy in compute to populate edgeSecurityPolicy.
Policies for referencing.
Selector for a SecurityPolicy in compute to populate edgeSecurityPolicy.
Policies for selection.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. 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.
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.
BackendBucketStatus defines the observed state of BackendBucket.
No description provided.
Cloud CDN configuration for this Backend Bucket. Structure is documented below.
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. Structure is documented below.
The CacheKeyPolicy for this CdnPolicy. Structure is documented below.
Allows HTTP request headers (by name) to be used in the cache key.
Names of query string parameters to include in cache keys. Default parameters are always included. '&' and '=' will be percent encoded and not treated as delimiters.
Headers that the HTTP/S load balancer should add to proxied responses.
Conditions of the resource.
target-grpc-proxy
apiVersion: compute.gcp.upbound.io/v1beta1
kind: BackendBucket
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/targetgrpcproxy
labels:
testing.upbound.io/example-name: target-grpc-proxy
name: target-grpc-proxy
spec:
forProvider:
bucketNameSelector:
matchLabels:
testing.upbound.io/example-name: target-grpc-proxy
backend-bucket-${Rand.RFC1123Subdomain}
apiVersion: compute.gcp.upbound.io/v1beta1
kind: BackendBucket
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/backendbucket
labels:
testing.upbound.io/example-name: backend-bucket-signed-url-key
name: backend-bucket-${Rand.RFC1123Subdomain}
spec:
forProvider:
bucketNameSelector:
matchLabels:
testing.upbound.io/example-name: backend-bucket-signed-url-key
urlmap
apiVersion: compute.gcp.upbound.io/v1beta1
kind: BackendBucket
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/urlmap
labels:
testing.upbound.io/example-name: urlmap
name: urlmap
spec:
forProvider:
bucketNameSelector:
matchLabels:
testing.upbound.io/example-name: urlmap
enableCdn: true
target-https-proxy
apiVersion: compute.gcp.upbound.io/v1beta1
kind: BackendBucket
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/targethttpsproxy
labels:
testing.upbound.io/example-name: target-https-proxy
name: target-https-proxy
spec:
forProvider:
bucketNameSelector:
matchLabels:
testing.upbound.io/example-name: target-https-proxy
backend-bucket
apiVersion: compute.gcp.upbound.io/v1beta1
kind: BackendBucket
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/backendbucket
labels:
testing.upbound.io/example-name: backend-bucket
name: backend-bucket
spec:
forProvider:
bucketNameSelector:
matchLabels:
testing.upbound.io/example-name: backend-bucket
description: Contains beautiful images
enableCdn: true
target-http-proxy
apiVersion: compute.gcp.upbound.io/v1beta1
kind: BackendBucket
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/targethttpproxy
labels:
testing.upbound.io/example-name: target-http-proxy
name: target-http-proxy
spec:
forProvider:
bucketNameSelector:
matchLabels:
testing.upbound.io/example-name: target-http-proxy
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.