1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-12 07:58:28 +00:00
gcloud-help/gcloud/alloydb/clusters/create-secondary
2023-08-23 10:30:46 +00:00

103 lines
3.7 KiB
Text

NAME
gcloud alloydb clusters create-secondary - create a new AlloyDB SECONDARY
cluster within a given project
SYNOPSIS
gcloud alloydb clusters create-secondary CLUSTER
--primary-cluster=PRIMARY_CLUSTER --region=REGION
[--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async]
[--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
--kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Create a new AlloyDB SECONDARY cluster within a given project.
EXAMPLES
To create a new cluster, run:
$ gcloud alloydb clusters create-secondary my-cluster \
--region=us-central1 \
--primary-cluster=projects/12345/locations/us-central1/\
clusters/cluster1
POSITIONAL ARGUMENTS
CLUSTER
AlloyDB cluster ID
REQUIRED FLAGS
--primary-cluster=PRIMARY_CLUSTER
AlloyDB primary cluster ID
--region=REGION
Regional location (e.g. asia-east1, us-east1). See the full list of
regions at https://cloud.google.com/sql/docs/instance-locations.
OPTIONAL FLAGS
--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME
Name of the allocated IP range for the private IP AlloyDB cluster, for
example: "google-managed-services-default". If set, the instance IPs
for this cluster will be created in the allocated range. The range name
must comply with RFC 1035. Specifically, the name must be 1-63
characters long and match the regular expression
[a-z]([-a-z0-9][a-z0-9])?.
--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 'AlloyDB Service Agent' service
account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'.
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 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 Google 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 Google Cloud project 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;
▸ set the property core/project.
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 help for details.
NOTES
These variants are also available:
$ gcloud alpha alloydb clusters create-secondary
$ gcloud beta alloydb clusters create-secondary