RegionDisk is the Schema for the RegionDisks API. Persistent disks are durable storage devices that function similarly to the physical disks in a desktop or a server.
Type
CRD
Group
compute.gcp.upbound.io
Version
v1beta1
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RegionDisk
RegionDiskSpec defines the desired state of RegionDisk
No description provided.
Encrypts the disk using a customer-supplied encryption key. After you encrypt a disk with a customer-supplied key, you must provide the same key if you use the disk later (e.g. to create a disk snapshot or an image, or to attach the disk to a virtual machine). Customer-supplied encryption keys do not protect access to metadata of the disk. If you do not provide an encryption key when creating the disk, then the disk will be encrypted using an automatically generated key and you do not need to provide a key to use the disk later. Structure is documented below.
URLs of the zones where the disk should be replicated to.
Reference to a Snapshot in compute to populate snapshot.
Policies for referencing.
Selector for a Snapshot in compute to populate snapshot.
Policies for selection.
The customer-supplied encryption key of the source snapshot. Required if the source snapshot is protected by a customer-supplied encryption key. 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.
Encrypts the disk using a customer-supplied encryption key. After you encrypt a disk with a customer-supplied key, you must provide the same key if you use the disk later (e.g. to create a disk snapshot or an image, or to attach the disk to a virtual machine). Customer-supplied encryption keys do not protect access to metadata of the disk. If you do not provide an encryption key when creating the disk, then the disk will be encrypted using an automatically generated key and you do not need to provide a key to use the disk later. Structure is documented below.
URLs of the zones where the disk should be replicated to.
The customer-supplied encryption key of the source snapshot. Required if the source snapshot is protected by a customer-supplied encryption key. 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.
RegionDiskStatus defines the observed state of RegionDisk.
No description provided.
Encrypts the disk using a customer-supplied encryption key. After you encrypt a disk with a customer-supplied key, you must provide the same key if you use the disk later (e.g. to create a disk snapshot or an image, or to attach the disk to a virtual machine). Customer-supplied encryption keys do not protect access to metadata of the disk. If you do not provide an encryption key when creating the disk, then the disk will be encrypted using an automatically generated key and you do not need to provide a key to use the disk later. Structure is documented below.
URLs of the zones where the disk should be replicated to.
Links to the users of the disk (attached instances) in form: project/zones/zone/instances/instance
Conditions of the resource.
region-disk
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RegionDisk
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/regiondisk
labels:
testing.upbound.io/example-name: region-disk
name: region-disk
spec:
forProvider:
physicalBlockSizeBytes: 4096
region: us-central1
replicaZones:
- us-central1-a
- us-central1-f
type: pd-ssd
region-disk-policy-attachment
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RegionDisk
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/regiondiskresourcepolicyattachment
labels:
testing.upbound.io/example-name: region-disk-policy-attachment
name: region-disk-policy-attachment
spec:
forProvider:
region: us-central1
replicaZones:
- us-central1-a
- us-central1-f
size: 50
type: pd-ssd
region-disk-member
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RegionDisk
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/regiondisk
labels:
testing.upbound.io/example-name: region-disk-member
name: region-disk-member
spec:
forProvider:
physicalBlockSizeBytes: 4096
region: us-central1
replicaZones:
- us-central1-a
- us-central1-f
type: pd-ssd