Creates a new InstanceCluster.
autoscalingConfigAutoscaling config for the cluster, contains the following arguments:
clusterId The ID of the Cloud Bigtable cluster. Must be 6-30 characters and must only contain hyphens, lowercase letters and numbers.
kmsKeyName Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the cloudkms.cryptoKeyEncrypterDecrypter role on the CMEK key. 2) Only regional keys can be used and the region of the CMEK key must match the region of the cluster.
nodeScalingFactor The node scaling factor for this cluster. One of "NodeScalingFactor1X" or "NodeScalingFactor2X". Defaults to "NodeScalingFactor1X". If "NodeScalingFactor2X" is specified, then numNodes, minNodes, and maxNodes would need to be specified in increments of 2. This value cannot be updated after the cluster is created.
numNodes The number of nodes in the cluster.
state describes the current state of the cluster.
storageType The storage type to use. One of "SSD" or
zone The zone to create the Cloud Bigtable cluster in. If it not
Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the cloudkms.cryptoKeyEncrypterDecrypter role on the CMEK key. 2) Only regional keys can be used and the region of the CMEK key must match the region of the cluster.
The node scaling factor for this cluster. One of "NodeScalingFactor1X" or "NodeScalingFactor2X". Defaults to "NodeScalingFactor1X". If "NodeScalingFactor2X" is specified, then numNodes, minNodes, and maxNodes would need to be specified in increments of 2. This value cannot be updated after the cluster is created.
The number of nodes in the cluster.
If no value is set, Cloud Bigtable automatically allocates nodes based on your data footprint and optimized for 50% storage utilization.
The zone to create the Cloud Bigtable cluster in. If it not
specified, the provider zone is used. Each cluster must have a different zone in the same region. Zones that support
Bigtable instances are noted on the Cloud Bigtable locations page.