gcloud alpha alloydb instances create-secondary

NAME
gcloud alpha alloydb instances create-secondary - creates a new AlloyDB SECONDARY instance within a given cluster
SYNOPSIS
gcloud alpha alloydb instances create-secondary INSTANCE --cluster=CLUSTER --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE] [GCLOUD_WIDE_FLAG]
DESCRIPTION
(ALPHA) Creates a new AlloyDB SECONDARY instance within a given cluster.
EXAMPLES
To create a new secondary instance, run:
gcloud alpha alloydb instances create-secondary my-instance --cluster=my-cluster --region=us-central1
POSITIONAL ARGUMENTS
INSTANCE
AlloyDB instance ID
REQUIRED FLAGS
--cluster=CLUSTER
AlloyDB 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
--async
Return immediately, without waiting for the operation in progress to complete.
--availability-type=AVAILABILITY_TYPE
Specifies level of availability. AVAILABILITY_TYPE must be one of:
REGIONAL
Provide high availability instances. Recommended for production instances; instances automatically fail over to another zone within your selected region.
ZONAL
Provide zonal availability instances. Not recommended for production instances; instance does not automatically fail over to another zone.
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
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:
gcloud alloydb instances create-secondary
gcloud beta alloydb instances create-secondary