Cluster is the Schema for the Clusters API. Provides a Redshift Cluster resource.
Type
CRD
Group
redshift.aws.upbound.io
Version
v1beta1
apiVersion: redshift.aws.upbound.io/v1beta1
kind: Cluster
ClusterSpec defines the desired state of Cluster
No description provided.
Reference to a Role in iam to populate defaultIamRoleArn.
Policies for referencing.
Selector for a Role in iam to populate defaultIamRoleArn.
Policies for selection.
References to Role in iam to populate iamRoles.
Policies for referencing.
Selector for a list of Role in iam to populate iamRoles.
Policies for selection.
A list of IAM Role ARNs to associate with the cluster. A Maximum of 10 can be associated to the cluster at any time.
Reference to a Key in kms to populate kmsKeyId.
Policies for referencing.
Selector for a Key in kms to populate kmsKeyId.
Policies for selection.
Logging, documented below.
The collection of exported log types. Log types include the connection log, user log and user activity log. Required when log_destination_type is cloudwatch. Valid log types are connectionlog, userlog, and useractivitylog.
Password for the master DB user. Conflicts with manage_master_password. One of master_password or manage_master_password is required unless snapshot_identifier is provided. Note that this may show up in logs, and it will be stored in the state file. Password must contain at least 8 characters and contain at least one uppercase letter, one lowercase letter, and one number.
Configuration of automatic copy of snapshots from one region to another. Documented below.
References to SecurityGroup in ec2 to populate vpcSecurityGroupIds.
Policies for referencing.
Selector for a list of SecurityGroup in ec2 to populate vpcSecurityGroupIds.
Policies for selection.
A list of Virtual Private Cloud (VPC) security groups to be associated with the cluster.
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 Role in iam to populate defaultIamRoleArn.
Policies for referencing.
Selector for a Role in iam to populate defaultIamRoleArn.
Policies for selection.
References to Role in iam to populate iamRoles.
Policies for referencing.
Selector for a list of Role in iam to populate iamRoles.
Policies for selection.
A list of IAM Role ARNs to associate with the cluster. A Maximum of 10 can be associated to the cluster at any time.
Reference to a Key in kms to populate kmsKeyId.
Policies for referencing.
Selector for a Key in kms to populate kmsKeyId.
Policies for selection.
Logging, documented below.
The collection of exported log types. Log types include the connection log, user log and user activity log. Required when log_destination_type is cloudwatch. Valid log types are connectionlog, userlog, and useractivitylog.
Configuration of automatic copy of snapshots from one region to another. Documented below.
References to SecurityGroup in ec2 to populate vpcSecurityGroupIds.
Policies for referencing.
Selector for a list of SecurityGroup in ec2 to populate vpcSecurityGroupIds.
Policies for selection.
A list of Virtual Private Cloud (VPC) security groups to be associated with the cluster.
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 nodes in the cluster. Cluster node blocks are documented below
A list of IAM Role ARNs to associate with the cluster. A Maximum of 10 can be associated to the cluster at any time.
Logging, documented below.
The collection of exported log types. Log types include the connection log, user log and user activity log. Required when log_destination_type is cloudwatch. Valid log types are connectionlog, userlog, and useractivitylog.
Configuration of automatic copy of snapshots from one region to another. Documented below.
A list of Virtual Private Cloud (VPC) security groups to be associated with the cluster.
Conditions of the resource.
example
apiVersion: redshift.aws.upbound.io/v1beta1
kind: Cluster
metadata:
annotations:
meta.upbound.io/example-id: redshift/v1beta1/cluster
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
clusterType: single-node
databaseName: mydb
masterPasswordSecretRef:
key: example-key
name: cluster-secret
namespace: upbound-system
masterUsername: exampleuser
nodeType: ra3.xlplus
region: us-west-1
skipFinalSnapshot: true
example
apiVersion: redshift.aws.upbound.io/v1beta1
kind: Cluster
metadata:
annotations:
meta.upbound.io/example-id: redshift/v1beta1/usagelimit
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
clusterType: single-node
databaseName: mydb
masterPasswordSecretRef:
key: example-key
name: cluster-secret
namespace: upbound-system
masterUsername: exampleuser
nodeType: ra3.xlplus
region: us-west-1
skipFinalSnapshot: true
example
apiVersion: redshift.aws.upbound.io/v1beta1
kind: Cluster
metadata:
annotations:
meta.upbound.io/example-id: redshift/v1beta1/scheduledaction
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
clusterType: single-node
databaseName: mydb
masterPasswordSecretRef:
key: example-key
name: cluster-secret
namespace: upbound-system
masterUsername: exampleuser
nodeType: ra3.xlplus
region: us-west-1
skipFinalSnapshot: true
default
apiVersion: redshift.aws.upbound.io/v1beta1
kind: Cluster
metadata:
annotations:
meta.upbound.io/example-id: redshift/v1beta1/snapshotscheduleassociation
labels:
testing.upbound.io/example-name: default
name: default
spec:
forProvider:
clusterType: single-node
databaseName: mydb
masterPasswordSecretRef:
key: example-key
name: cluster-secret
namespace: upbound-system
masterUsername: exampleuser
nodeType: ra3.xlplus
region: us-west-1
skipFinalSnapshot: true
example
apiVersion: redshift.aws.upbound.io/v1beta1
kind: Cluster
metadata:
annotations:
meta.upbound.io/example-id: redshift/v1beta1/eventsubscription
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
clusterType: single-node
databaseName: mydb
masterPasswordSecretRef:
key: example-key
name: cluster-secret
namespace: upbound-system
masterUsername: exampleuser
nodeType: ra3.xlplus
region: us-west-1
skipFinalSnapshot: true
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.