gcloud alpha bigtable instances create
Stay organized with collections
Save and categorize content based on your preferences.
- NAME
-
- gcloud alpha bigtable instances create - create a new Bigtable instance
- SYNOPSIS
-
-
gcloud alpha bigtable instances createINSTANCE--display-name=DISPLAY_NAME[--async] [--cluster=CLUSTER] [--cluster-config=[id=ID,zone=ZONE,[nodes=NODES],[node-scaling-factor=NODE_SCALING_FACTOR],[kms-key=KMS_KEY],[autoscaling-min-nodes=AUTOSCALING_MIN_NODES,autoscaling-max-nodes=AUTOSCALING_MAX_NODES,autoscaling-cpu-target=AUTOSCALING_CPU_TARGET,autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET],…]] [--cluster-num-nodes=CLUSTER_NUM_NODES] [--cluster-storage-type=CLUSTER_STORAGE_TYPE; default="ssd"] [--cluster-zone=CLUSTER_ZONE] [--edition=EDITION] [--instance-type=INSTANCE_TYPE; default="PRODUCTION"] [--tags=[KEY=VALUE,…]] [GCLOUD_WIDE_FLAG …]
-
- DESCRIPTION
-
(ALPHA)Create a new Bigtable instance. - EXAMPLES
-
To create an instance with id
my-instance-idwith a cluster located inus-east1-c, run:gcloudalphabigtableinstancescreatemy-instance-id--display-name="My Instance"--cluster-config=id=my-cluster-id,zone=us-east1-cTo create an instance with multiple clusters, run:
gcloudalphabigtableinstancescreatemy-instance-id--display-name="My Instance"--cluster-config=id=my-cluster-id-1,zone=us-east1-c--cluster-config=id=my-cluster-id-2,zone=us-west1-c,nodes=3To create an instance with
HDDstorage and10nodes, run:gcloudalphabigtableinstancescreatemy-hdd-instance--display-name="HDD Instance"--cluster-storage-type=HDD--cluster-config=id=my-cluster-id,zone=us-east1-c,nodes=10To create an instance with edition
ENTERPRISE_PLUS, run:gcloudalphabigtableinstancescreatemy-enterprise-plus-instance--display-name="Enterprise Plus Instance"--edition=ENTERPRISE_PLUS--cluster-config=id=my-cluster-id,zone=us-east1-c,nodes=1 - POSITIONAL ARGUMENTS
-
-
Instance resource - The instance to create. This represents a Cloud resource.
(NOTE) Some attributes are not given arguments in this group but can be set in
other ways.
To set the
projectattribute:-
provide the argument
instanceon the command line with a fully specified name; -
provide the argument
--projecton the command line; -
set the property
core/project.
This must be specified.
INSTANCE-
ID of the instance or fully qualified identifier for the instance.
To set the
instanceattribute:-
provide the argument
instanceon the command line.
-
provide the argument
-
provide the argument
-
Instance resource - The instance to create. This represents a Cloud resource.
(NOTE) Some attributes are not given arguments in this group but can be set in
other ways.
- REQUIRED FLAGS
-
--display-name=DISPLAY_NAME- Friendly name of the instance.
- OPTIONAL FLAGS
-
--async- Return immediately, without waiting for the operation in progress to complete.
--cluster=CLUSTER-
(DEPRECATED) ID of the cluster
The --cluster argument is deprecated; use --cluster-config instead.
--cluster-config=[id=ID,zone=ZONE,[nodes=NODES],[node-scaling-factor=NODE_SCALING_FACTOR],[kms-key=KMS_KEY],[autoscaling-min-nodes=AUTOSCALING_MIN_NODES,autoscaling-max-nodes=AUTOSCALING_MAX_NODES,autoscaling-cpu-target=AUTOSCALING_CPU_TARGET,autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET],…]-
Repeatable. Specify cluster config as a key-value dictionary.This is the recommended argument for specifying cluster configurations.
Keys can be:
*id*:Required.TheIDofthecluster.
*zone*:Required.IDofthezonewheretheclusterislocated.Supportedzonesarelistedathttps://cloud.google.com/bigtable/docs/locations.
*nodes*:Thenumberofnodesinthecluster.Default=1.
*node-scaling-factor*:Thenodescalingfactorforthecluster.Default=node-scaling-factor-1x.NODE_SCALING_FACTORmustbeoneof:node-scaling-factor-1x,node-scaling-factor-2x.
*kms-key*:TheCloudKMS(KeyManagementService)cryptokeythatwillbeusedtoprotectthecluster.
*autoscaling-min-nodes*:Theminimumnumberofnodesforautoscaling.*autoscaling-max-nodes*:Themaximumnumberofnodesforautoscaling.*autoscaling-cpu-target*:ThetargetCPUutilizationpercentageforautoscaling.Acceptedvaluesarefrom10to80.
*autoscaling-storage-target*:Thetargetstorageutilizationgibibytespernodeforautoscaling.Acceptedvaluesarefrom2560to5120forSSDclustersand8192to16384forHDDclusters.
If this argument is specified, the deprecated arguments for configuring a single cluster will be ignored, including
--cluster,--cluster-zone,--cluster-num-nodes.See
EXAMPLESsection. --cluster-num-nodes=CLUSTER_NUM_NODES-
(DEPRECATED) Number of nodes to serve.
The --cluster-num-nodes argument is deprecated; use --cluster-config instead.
--cluster-storage-type=CLUSTER_STORAGE_TYPE; default="ssd"-
Storage class for the cluster.
CLUSTER_STORAGE_TYPEmust be one of:hdd,ssd. --cluster-zone=CLUSTER_ZONE-
(DEPRECATED) ID of the zone where the cluster is located. Supported zones are
listed at https://cloud.google.com/bigtable/docs/locations.
The --cluster-zone argument is deprecated; use --cluster-config instead.
--edition=EDITION-
The edition of the instance.
EDITIONmust be one of:ENTERPRISE,ENTERPRISE_PLUS. --instance-type=INSTANCE_TYPE; default="PRODUCTION"-
(DEPRECATED) The type of instance to create.
The --instance-type argument is deprecated. DEVELOPMENT instances are no longer offered. All instances are of type PRODUCTION.
INSTANCE_TYPEmust be one of:DEVELOPMENT- Development instances are low-cost instances meant for development and testing only. They do not provide high availability and no service level agreement applies.
PRODUCTION- Production instances provide high availability and are suitable for applications in production. Production instances created with the --instance-type argument have 3 nodes if a value is not provided for --cluster-num-nodes.
-
List of tags KEY=VALUE pairs to bind. Each item must be specified in either ID
<tag_key_id>=<tag_value_id>or namespace format<tag-key-namespaced-name>=<tag-value-short-name>. Example:123/environment=production,123/costCenter=marketing
- GCLOUD WIDE FLAGS
-
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 helpfor details. - NOTES
-
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct project,
you might be trying to access an API with an invitation-only early access
allowlist. These variants are also available:
gcloudbigtableinstancescreategcloudbetabigtableinstancescreate