Cluster is the Schema for the Clusters API. A managed alloydb cluster.
Type
CRD
Group
alloydb.gcp.upbound.io
Version
v1beta1
apiVersion: alloydb.gcp.upbound.io/v1beta1
kind: Cluster
ClusterSpec defines the desired state of Cluster
No description provided.
The automated backup policy for this cluster. AutomatedBackupPolicy is disabled by default. Structure is documented below.
EncryptionConfig describes the encryption config of a cluster or a backup that is encrypted with a CMEK (customer-managed encryption key). Structure is documented below.
Quantity-based Backup retention policy to retain recent backups. Conflicts with 'time_based_retention', both can't be set together. Structure is documented below.
Time-based Backup retention policy. Conflicts with 'quantity_based_retention', both can't be set together. Structure is documented below.
Weekly schedule for the Backup. Structure is documented below.
The days of the week to perform a backup. At least one day of the week must be provided. Each value may be one of: MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY.
The continuous backup config for this cluster. If no policy is provided then the default policy will be used. The default policy takes one backup a day and retains backups for 14 days. Structure is documented below.
EncryptionConfig describes the encryption config of a cluster or a backup that is encrypted with a CMEK (customer-managed encryption key). Structure is documented below.
EncryptionConfig describes the encryption config of a cluster or a backup that is encrypted with a CMEK (customer-managed encryption key). Structure is documented below.
Initial user to setup during cluster creation. Structure is documented below.
Metadata related to network configuration. Structure is documented below.
Reference to a Network in compute to populate network.
Policies for referencing.
Selector for a Network in compute to populate network.
Policies for selection.
The source when restoring from a backup. Conflicts with 'restore_continuous_backup_source', both can't be set together. Structure is documented below.
Reference to a Backup in alloydb to populate backupName.
Policies for referencing.
Selector for a Backup in alloydb to populate backupName.
Policies for selection.
The source when restoring via point in time recovery (PITR). Conflicts with 'restore_backup_source', both can't be set together. Structure is documented below.
Reference to a Cluster in alloydb to populate cluster.
Policies for referencing.
Selector for a Cluster in alloydb to populate cluster.
Policies for selection.
Configuration of the secondary cluster for Cross Region Replication. This should be set if and only if the cluster is of type SECONDARY. Structure is documented below.
Reference to a Cluster in alloydb to populate primaryClusterName.
Policies for referencing.
Selector for a Cluster in alloydb to populate primaryClusterName.
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.
The automated backup policy for this cluster. AutomatedBackupPolicy is disabled by default. Structure is documented below.
EncryptionConfig describes the encryption config of a cluster or a backup that is encrypted with a CMEK (customer-managed encryption key). Structure is documented below.
Quantity-based Backup retention policy to retain recent backups. Conflicts with 'time_based_retention', both can't be set together. Structure is documented below.
Time-based Backup retention policy. Conflicts with 'quantity_based_retention', both can't be set together. Structure is documented below.
Weekly schedule for the Backup. Structure is documented below.
The days of the week to perform a backup. At least one day of the week must be provided. Each value may be one of: MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY.
The continuous backup config for this cluster. If no policy is provided then the default policy will be used. The default policy takes one backup a day and retains backups for 14 days. Structure is documented below.
EncryptionConfig describes the encryption config of a cluster or a backup that is encrypted with a CMEK (customer-managed encryption key). Structure is documented below.
EncryptionConfig describes the encryption config of a cluster or a backup that is encrypted with a CMEK (customer-managed encryption key). Structure is documented below.
Initial user to setup during cluster creation. Structure is documented below.
Metadata related to network configuration. Structure is documented below.
Reference to a Network in compute to populate network.
Policies for referencing.
Selector for a Network in compute to populate network.
Policies for selection.
The source when restoring from a backup. Conflicts with 'restore_continuous_backup_source', both can't be set together. Structure is documented below.
Reference to a Backup in alloydb to populate backupName.
Policies for referencing.
Selector for a Backup in alloydb to populate backupName.
Policies for selection.
The source when restoring via point in time recovery (PITR). Conflicts with 'restore_backup_source', both can't be set together. Structure is documented below.
Reference to a Cluster in alloydb to populate cluster.
Policies for referencing.
Selector for a Cluster in alloydb to populate cluster.
Policies for selection.
Configuration of the secondary cluster for Cross Region Replication. This should be set if and only if the cluster is of type SECONDARY. Structure is documented below.
Reference to a Cluster in alloydb to populate primaryClusterName.
Policies for referencing.
Selector for a Cluster in alloydb to populate primaryClusterName.
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.
ClusterStatus defines the observed state of Cluster.
No description provided.
The automated backup policy for this cluster. AutomatedBackupPolicy is disabled by default. Structure is documented below.
EncryptionConfig describes the encryption config of a cluster or a backup that is encrypted with a CMEK (customer-managed encryption key). Structure is documented below.
Quantity-based Backup retention policy to retain recent backups. Conflicts with 'time_based_retention', both can't be set together. Structure is documented below.
Time-based Backup retention policy. Conflicts with 'quantity_based_retention', both can't be set together. Structure is documented below.
Weekly schedule for the Backup. Structure is documented below.
The days of the week to perform a backup. At least one day of the week must be provided. Each value may be one of: MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY.
Cluster created from backup. Structure is documented below.
The continuous backup config for this cluster. If no policy is provided then the default policy will be used. The default policy takes one backup a day and retains backups for 14 days. Structure is documented below.
EncryptionConfig describes the encryption config of a cluster or a backup that is encrypted with a CMEK (customer-managed encryption key). Structure is documented below.
ContinuousBackupInfo describes the continuous backup properties of a cluster. Structure is documented below.
(Output) Output only. The encryption information for the WALs and backups required for ContinuousBackup. Structure is documented below.
(Output) Output only. Cloud KMS key versions that are being used to protect the database or the backup.
(Output) Days of the week on which a continuous backup is taken. Output only field. Ignored if passed into the request.
EncryptionConfig describes the encryption config of a cluster or a backup that is encrypted with a CMEK (customer-managed encryption key). Structure is documented below.
EncryptionInfo describes the encryption information of a cluster or a backup. Structure is documented below.
(Output) Output only. Cloud KMS key versions that are being used to protect the database or the backup.
Initial user to setup during cluster creation. Structure is documented below.
Cluster created via DMS migration. Structure is documented below.
Metadata related to network configuration. Structure is documented below.
The source when restoring from a backup. Conflicts with 'restore_continuous_backup_source', both can't be set together. Structure is documented below.
The source when restoring via point in time recovery (PITR). Conflicts with 'restore_backup_source', both can't be set together. Structure is documented below.
Configuration of the secondary cluster for Cross Region Replication. This should be set if and only if the cluster is of type SECONDARY. Structure is documented below.
Conditions of the resource.
alloydb-test
apiVersion: alloydb.gcp.upbound.io/v1beta1
kind: Cluster
metadata:
annotations:
meta.upbound.io/example-id: alloydb/v1beta1/instance
labels:
testing.upbound.io/example-name: alloydb-test
name: alloydb-test
spec:
forProvider:
initialUser:
- passwordSecretRef:
key: example-key
name: example-secret
namespace: upbound-system
location: us-central1
networkSelector:
matchLabels:
testing.upbound.io/example-name: google_compute_network
alloydb-test
apiVersion: alloydb.gcp.upbound.io/v1beta1
kind: Cluster
metadata:
annotations:
meta.upbound.io/example-id: alloydb/v1beta1/backup
labels:
testing.upbound.io/example-name: alloydb-test
name: alloydb-test
spec:
forProvider:
location: us-central1
networkSelector:
matchLabels:
testing.upbound.io/example-name: google_compute_network
alloydb-test
apiVersion: alloydb.gcp.upbound.io/v1beta1
kind: Cluster
metadata:
annotations:
meta.upbound.io/example-id: alloydb/v1beta1/cluster
labels:
testing.upbound.io/example-name: alloydb-test
name: alloydb-test
spec:
forProvider:
location: us-central1
networkSelector:
matchLabels:
testing.upbound.io/example-name: alloydb-test
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.