gcloud-help/gcloud/alloydb/instances/create-secondary

NAME
    gcloud alloydb instances create-secondary - creates a new AlloyDB SECONDARY
        instance within a given cluster

SYNOPSIS
    gcloud 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]
        [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]]
        [--[no-]outbound-public-ip]
        [--psc-auto-connections=[network=NETWORK],[project=PROJECT]]
        [--psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI]
        [--[no-]require-connectors] [--ssl-mode=SSL_MODE]
        [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    Creates a new AlloyDB SECONDARY instance within a given cluster.

EXAMPLES
    To create a new secondary instance, run:

        $ gcloud 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.

     --database-flags=FLAG=VALUE,[FLAG=VALUE,...]
        Comma-separated list of database flags to set on the instance. Use an
        equals sign to separate flag name and value. Flags without values, like
        skip_grant_tables, can be written out without a value after, e.g.,
        skip_grant_tables=. Use on/off for booleans. View the Instance Resource
        API for allowed flags. (e.g., --database-flags
        max_allowed_packet=55555,skip_grant_tables=,log_output=1)

     --[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.

     --psc-auto-connections=[network=NETWORK],[project=PROJECT]
        Comma-separated list of consumer project and consumer network pairs to
        create endpoints for Private Service Connect (PSC) connectivity for the
        instance. Only instances in PSC-enabled clusters are allowed to set
        this field. Both project and network must be specified. (e.g.,
        --psc-auto-connections=project=project1,network=projects/vpc-host-project1/global/networks/network1
        --psc-auto-connections=project=project2,network=projects/vpc-host-project2/global/networks/network2).
        Sets psc_auto_connections value.

         network
            Required, Sets network value.

         project
            Required, Sets project value.

        Shorthand Example:

            --psc-auto-connections=network=string,project=string

        JSON Example:

            --psc-auto-connections='{"network": "string", "project": "string"}'

        File Example:

            --psc-auto-connections=path_to_file.(yaml|json)

     --psc-network-attachment-uri=PSC_NETWORK_ATTACHMENT_URI
        Full URI of the network attachment that is configured to support
        outbound connectivity from an AlloyDB instance which uses Private
        Service Connect (PSC). For example, this would be of the
        form:psc-network-attachment-uri=projects/test-project/regions/us-central1/networkAttachments/my-na

     --[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
    These variants are also available:

        $ gcloud alpha alloydb instances create-secondary

        $ gcloud beta alloydb instances create-secondary