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 [--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,…]] [--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP] [--async] [--authorized-external-networks=[AUTHORIZED_NETWORK,…]] [--availability-type=AVAILABILITY_TYPE] [--[no-]outbound-public-ip] [--[no-]require-connectors] [--ssl-mode=SSL_MODE] [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
--allowed-psc-projects=[ALLOWED_PSC_PROJECTS,…]
Comma-separated list of allowed consumer projects to create endpoints for Private Service Connect (PSC) connectivity for the instance. Only instances in PSC-enabled clusters are allowed to set this field.(e.g., --allowed-psc-projects=project1,12345678,project2)
--assign-inbound-public-ip=ASSIGN_INBOUND_PUBLIC_IP
Specify to enable or disable public IP on an instance. ASSIGN_INBOUND_PUBLIC_IP must be one of:
  • NO_PUBLIC_IP
    • This disables public IP on the instance. Updating an instance to disable public IP will clear the list of authorized networks.
  • ASSIGN_IPV4
    • Assign an inbound public IPv4 address for the instance. Public IP is enabled.
--async
Return immediately, without waiting for the operation in progress to complete.
--authorized-external-networks=[AUTHORIZED_NETWORK,…]
Comma-separated list of authorized external networks to set on the instance. Authorized networks should use CIDR notation (e.g. 1.2.3.4/30). This flag is only allowed to be set for instances with public IP enabled.
--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.
--[no-]outbound-public-ip
Add outbound Public IP connectivity to an AlloyDB instance. Use --outbound-public-ip to enable and --no-outbound-public-ip to disable.
--[no-]require-connectors
Enable or disable enforcing connectors only (ex: AuthProxy) connections to the database. Use --require-connectors to enable and --no-require-connectors to disable.
--ssl-mode=SSL_MODE
Specify the SSL mode to use when the instance connects to the database. Default SSL mode will match what is set on the primary instance. SSL_MODE must be one of:
ALLOW_UNENCRYPTED_AND_ENCRYPTED
SSL connections are optional. CA verification is not enforced.
ENCRYPTED_ONLY
SSL connections are required. CA verification is not enforced.
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