Bucket is the Schema for the Buckets API. Creates a new bucket in Google Cloud Storage.
Type
CRD
Group
storage.gcp.upbound.io
Version
v1beta1
apiVersion: storage.gcp.upbound.io/v1beta1
kind: Bucket
BucketSpec defines the desired state of Bucket
No description provided.
The bucket's Autoclass configuration. Structure is documented below.
The bucket's Cross-Origin Resource Sharing (CORS) configuration. Multiple blocks of this type are permitted. Structure is documented below.
The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".
The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".
The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.
The bucket's custom location configuration, which specifies the individual regions that comprise a dual-region bucket. If the bucket is designated a single or multi-region, the parameters are empty. Structure is documented below.
The list of individual regions that comprise a dual-region bucket. See Cloud Storage bucket locations for a list of acceptable regions. Note: If any of the data_locations changes, it will recreate the bucket.
The bucket's encryption configuration. Structure is documented below.
The bucket's Lifecycle Rules configuration. Multiple blocks of this type are permitted. Structure is documented below.
The Lifecycle Rule's action configuration. A single block of this type is supported. Structure is documented below.
The Lifecycle Rule's condition configuration. A single block of this type is supported. Structure is documented below.
One or more matching name prefixes to satisfy this condition.
Storage Class of objects to satisfy this condition. Supported values include: STANDARD, MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, DURABLE_REDUCED_AVAILABILITY.
One or more matching name suffixes to satisfy this condition.
The bucket's Access & Storage Logs configuration. Structure is documented below.
Configuration of the bucket's data retention policy for how long objects in the bucket should be retained. Structure is documented below.
The bucket's Versioning configuration. Structure is documented below.
Configuration if the bucket acts as a website. 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 bucket's Autoclass configuration. Structure is documented below.
The bucket's Cross-Origin Resource Sharing (CORS) configuration. Multiple blocks of this type are permitted. Structure is documented below.
The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".
The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".
The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.
The bucket's custom location configuration, which specifies the individual regions that comprise a dual-region bucket. If the bucket is designated a single or multi-region, the parameters are empty. Structure is documented below.
The list of individual regions that comprise a dual-region bucket. See Cloud Storage bucket locations for a list of acceptable regions. Note: If any of the data_locations changes, it will recreate the bucket.
The bucket's encryption configuration. Structure is documented below.
The bucket's Lifecycle Rules configuration. Multiple blocks of this type are permitted. Structure is documented below.
The Lifecycle Rule's action configuration. A single block of this type is supported. Structure is documented below.
The Lifecycle Rule's condition configuration. A single block of this type is supported. Structure is documented below.
One or more matching name prefixes to satisfy this condition.
Storage Class of objects to satisfy this condition. Supported values include: STANDARD, MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, DURABLE_REDUCED_AVAILABILITY.
One or more matching name suffixes to satisfy this condition.
The bucket's Access & Storage Logs configuration. Structure is documented below.
Configuration of the bucket's data retention policy for how long objects in the bucket should be retained. Structure is documented below.
The bucket's Versioning configuration. Structure is documented below.
Configuration if the bucket acts as a website. 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.
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.
BucketStatus defines the observed state of Bucket.
No description provided.
The bucket's Autoclass configuration. Structure is documented below.
The bucket's Cross-Origin Resource Sharing (CORS) configuration. Multiple blocks of this type are permitted. Structure is documented below.
The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".
The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".
The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.
The bucket's custom location configuration, which specifies the individual regions that comprise a dual-region bucket. If the bucket is designated a single or multi-region, the parameters are empty. Structure is documented below.
The list of individual regions that comprise a dual-region bucket. See Cloud Storage bucket locations for a list of acceptable regions. Note: If any of the data_locations changes, it will recreate the bucket.
The bucket's encryption configuration. Structure is documented below.
The bucket's Lifecycle Rules configuration. Multiple blocks of this type are permitted. Structure is documented below.
The Lifecycle Rule's action configuration. A single block of this type is supported. Structure is documented below.
The Lifecycle Rule's condition configuration. A single block of this type is supported. Structure is documented below.
One or more matching name prefixes to satisfy this condition.
Storage Class of objects to satisfy this condition. Supported values include: STANDARD, MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, DURABLE_REDUCED_AVAILABILITY.
One or more matching name suffixes to satisfy this condition.
The bucket's Access & Storage Logs configuration. Structure is documented below.
Configuration of the bucket's data retention policy for how long objects in the bucket should be retained. Structure is documented below.
The bucket's Versioning configuration. Structure is documented below.
Configuration if the bucket acts as a website. Structure is documented below.
Conditions of the resource.
bucket-${Rand.RFC1123Subdomain}
apiVersion: storage.gcp.upbound.io/v1beta1
kind: Bucket
metadata:
annotations:
meta.upbound.io/example-id: storage/v1beta1/notification
labels:
testing.upbound.io/example-name: bucket
name: bucket-${Rand.RFC1123Subdomain}
spec:
forProvider:
location: US
bucket-${Rand.RFC1123Subdomain}
apiVersion: storage.gcp.upbound.io/v1beta1
kind: Bucket
metadata:
annotations:
meta.upbound.io/example-id: storage/v1beta1/objectaccesscontrol
labels:
testing.upbound.io/example-name: bucket
name: bucket-${Rand.RFC1123Subdomain}
spec:
forProvider:
cors:
- maxAgeSeconds: 3600
method:
- GET
- HEAD
- PUT
- POST
- DELETE
origin:
- http://image-store.com
responseHeader:
- "*"
forceDestroy: true
location: US
bucket-${Rand.RFC1123Subdomain}
apiVersion: storage.gcp.upbound.io/v1beta1
kind: Bucket
metadata:
annotations:
meta.upbound.io/example-id: storage/v1beta1/bucket
labels:
testing.upbound.io/example-name: bucket
name: bucket-${Rand.RFC1123Subdomain}
spec:
forProvider:
cors:
- maxAgeSeconds: 3600
method:
- GET
- HEAD
- PUT
- POST
- DELETE
origin:
- http://image-store.com
responseHeader:
- "*"
forceDestroy: true
location: US
uniformBucketLevelAccess: true
website:
- mainPageSuffix: index.html
notFoundPage: 404.html
bucket-iam-${Rand.RFC1123Subdomain}
apiVersion: storage.gcp.upbound.io/v1beta1
kind: Bucket
metadata:
annotations:
meta.upbound.io/example-id: storage/v1beta1/bucketiammember
labels:
testing.upbound.io/example-name: bucket-iam-member
name: bucket-iam-${Rand.RFC1123Subdomain}
spec:
forProvider:
location: US
default-object-access-control-${Rand.RFC1123Subdomain}
apiVersion: storage.gcp.upbound.io/v1beta1
kind: Bucket
metadata:
annotations:
meta.upbound.io/example-id: storage/v1beta1/defaultobjectaccesscontrol
labels:
testing.upbound.io/example-name: default-object-access-control
name: default-object-access-control-${Rand.RFC1123Subdomain}
spec:
forProvider:
location: US
default-object-acl-${Rand.RFC1123Subdomain}
apiVersion: storage.gcp.upbound.io/v1beta1
kind: Bucket
metadata:
annotations:
meta.upbound.io/example-id: storage/v1beta1/defaultobjectacl
labels:
testing.upbound.io/example-name: default-object-acl
name: default-object-acl-${Rand.RFC1123Subdomain}
spec:
forProvider:
location: US
bucket-object-${Rand.RFC1123Subdomain}
apiVersion: storage.gcp.upbound.io/v1beta1
kind: Bucket
metadata:
annotations:
meta.upbound.io/example-id: storage/v1beta1/bucketobject
labels:
testing.upbound.io/example-name: bucket-object
name: bucket-object-${Rand.RFC1123Subdomain}
spec:
forProvider:
location: US
storageClass: MULTI_REGIONAL
bucket-acl-${Rand.RFC1123Subdomain}
apiVersion: storage.gcp.upbound.io/v1beta1
kind: Bucket
metadata:
annotations:
meta.upbound.io/example-id: storage/v1beta1/bucketacl
labels:
testing.upbound.io/example-name: bucket-acl
name: bucket-acl-${Rand.RFC1123Subdomain}
spec:
forProvider:
location: US
bucket-${Rand.RFC1123Subdomain}
apiVersion: storage.gcp.upbound.io/v1beta1
kind: Bucket
metadata:
annotations:
meta.upbound.io/example-id: storage/v1beta1/objectacl
labels:
testing.upbound.io/example-name: bucket
name: bucket-${Rand.RFC1123Subdomain}
spec:
forProvider:
cors:
- maxAgeSeconds: 3600
method:
- GET
- HEAD
- PUT
- POST
- DELETE
origin:
- http://image-store.com
responseHeader:
- "*"
forceDestroy: true
location: US
uniformBucketLevelAccess: true
website:
- mainPageSuffix: index.html
notFoundPage: 404.html
bucket-access-control-${Rand.RFC1123Subdomain}
apiVersion: storage.gcp.upbound.io/v1beta1
kind: Bucket
metadata:
annotations:
meta.upbound.io/example-id: storage/v1beta1/bucketaccesscontrol
labels:
testing.upbound.io/example-name: bucket-access-control
name: bucket-access-control-${Rand.RFC1123Subdomain}
spec:
forProvider:
location: US
© 2024 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.