gcloud bigtable clusters create - create a bigtable cluster
gcloud bigtable clusters create (CLUSTER : --instance=INSTANCE) --zone=ZONE [--async] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [--num-nodes=NUM_NODES; default=3 | [--autoscaling-cpu-target=AUTOSCALING_CPU_TARGET --autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES : --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET]] [GCLOUD_WIDE_FLAG ...]
Create a bigtable cluster.
To add a cluster in zone us-east1-c to the instance with id my-instance-id, run:
$ gcloud bigtable clusters create my-cluster-id \ --instance=my-instance-id --zone=us-east1-c
To add a cluster with 10 nodes, run:
$ gcloud bigtable clusters create my-cluster-id \ --instance=my-instance-id --zone=us-east1-c --num-nodes=10
- Cluster resource - The cluster to describe. The arguments in this group can be
used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute:
- —
provide the argument cluster on the command line with a fully specified name;
- —
provide the argument --project on the command line;
- —
set the property core/project.
This must be specified.
- CLUSTER
ID of the cluster or fully qualified identifier for the cluster. To set the cluster attribute:
provide the argument cluster on the command line.
This positional argument must be specified if any of the other arguments in this group are specified.
- --instance=INSTANCE
Cloud Bigtable instance for the cluster. To set the instance attribute:
provide the argument cluster on the command line with a fully specified name;
provide the argument --instance on the command line.
- --zone=ZONE
ID of the zone where the cluster is located. Supported zones are listed at https://cloud.google.com/bigtable/docs/locations.
- --async
Return immediately, without waiting for the operation in progress to complete.
- Key resource - The Cloud KMS (Key Management Service) cryptokey that will be
used to protect the cluster. The arguments in this group can be used to specify the attributes of this resource.
- --kms-key=KMS_KEY
ID of the key or fully qualified identifier for the key. To set the kms-key attribute:
provide the argument --kms-key on the command line.
This flag argument must be specified if any of the other arguments in this group are specified.
- --kms-keyring=KMS_KEYRING
The KMS keyring id of the key. To set the kms-keyring attribute:
provide the argument --kms-key on the command line with a fully specified name;
provide the argument --kms-keyring on the command line.
- --kms-location=KMS_LOCATION
The Cloud location for the key. To set the kms-location attribute:
provide the argument --kms-key on the command line with a fully specified name;
provide the argument --kms-location on the command line.
- --kms-project=KMS_PROJECT
The Cloud project id for the key. To set the kms-project attribute:
provide the argument --kms-key on the command line with a fully specified name;
provide the argument --kms-project on the command line.
- At most one of these can be specified:
- Manual Scaling
- --num-nodes=NUM_NODES; default=3
Number of nodes to serve.
- Autoscaling
- --autoscaling-cpu-target=AUTOSCALING_CPU_TARGET
The target CPU utilization percentage for autoscaling. Accepted values are from 10 to 80.
This flag argument must be specified if any of the other arguments in this group are specified.
- --autoscaling-max-nodes=AUTOSCALING_MAX_NODES
The maximum number of nodes for autoscaling.
This flag argument must be specified if any of the other arguments in this group are specified.
- --autoscaling-min-nodes=AUTOSCALING_MIN_NODES
The minimum number of nodes for autoscaling.
This flag argument must be specified if any of the other arguments in this group are specified.
- --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET
The target storage utilization gibibytes per node for autoscaling. Accepted values are from 2560 to 5120 for SSD clusters and 8192 to 16384 for HDD clusters.
These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
These variants are also available:
$ gcloud alpha bigtable clusters create
$ gcloud beta bigtable clusters create