gcloud alpha compute public-advertised-prefixes create - creates a Compute Engine public advertised prefix
gcloud alpha compute public-advertised-prefixes create NAME --dns-verification-ip=DNS_VERIFICATION_IP --range=RANGE [--description=DESCRIPTION] [--pdp-scope=PDP_SCOPE] [GCLOUD_WIDE_FLAG ...]
To create a public advertised prefix:
$ gcloud alpha compute public-advertised-prefixes create \ my-public-advertised-prefix --range=120.120.10.0/24 \ --dns-verification-ip=120.120.10.15
To create a v2 public advertised prefix:
$ gcloud alpha compute public-advertised-prefixes create \ my-v2-public-advertised-prefix --range=120.120.10.0/24 \ --dns-verification-ip=120.120.10.15 --pdp-scope=REGIONAL
- NAME
Name of the public advertised prefix to operate on.
- --dns-verification-ip=DNS_VERIFICATION_IP
IPv4 address to use for verification. It must be within the IPv4 range specified in --range.
- --range=RANGE
IPv4 range allocated to this public advertised prefix, in CIDR format.
- --description=DESCRIPTION
Description of this public advertised prefix.
- --pdp-scope=PDP_SCOPE
Specifies how child public delegated prefix will be scoped. PDP_SCOPE must be one of: GLOBAL, REGIONAL.
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.
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 compute public-advertised-prefixes create
$ gcloud beta compute public-advertised-prefixes create