pulumi-gcp-kotlin/com.pulumi.gcp.bigtable.kotlin.inputs/InstanceClusterArgs

InstanceClusterArgs

data class InstanceClusterArgs(val autoscalingConfig: Output<InstanceClusterAutoscalingConfigArgs>? = null, val clusterId: Output<String>, val kmsKeyName: Output<String>? = null, val numNodes: Output<Int>? = null, val storageType: Output<String>? = null, val zone: Output<String>? = null) : ConvertibleToJava<InstanceClusterArgs>

Constructors

Link copied to clipboard
constructor(autoscalingConfig: Output<InstanceClusterAutoscalingConfigArgs>? = null, clusterId: Output<String>, kmsKeyName: Output<String>? = null, numNodes: Output<Int>? = null, storageType: Output<String>? = null, zone: Output<String>? = null)

Properties

Link copied to clipboard
val autoscalingConfig: Output<InstanceClusterAutoscalingConfigArgs>? = null

Autoscaling config for the cluster, contains the following arguments:

Link copied to clipboard
val clusterId: Output<String>

The ID of the Cloud Bigtable cluster. Must be 6-30 characters and must only contain hyphens, lowercase letters and numbers.

Link copied to clipboard
val kmsKeyName: Output<String>? = null

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.

Link copied to clipboard
val numNodes: Output<Int>? = null

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.

Link copied to clipboard
val storageType: Output<String>? = null

The storage type to use. One of "SSD" or "HDD". Defaults to "SSD".

Link copied to clipboard
val zone: Output<String>? = null

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.

Functions

Link copied to clipboard
open override fun toJava(): InstanceClusterArgs