mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-11 15:39:42 +00:00
95 lines
3.5 KiB
Text
95 lines
3.5 KiB
Text
NAME
|
|
gcloud alpha compute routers get-nat-mapping-info - display NAT Mapping
|
|
information in a router
|
|
|
|
SYNOPSIS
|
|
gcloud alpha compute routers get-nat-mapping-info NAME
|
|
[--nat-name=NAT_NAME] [--region=REGION] [--filter=EXPRESSION]
|
|
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
|
|
[GCLOUD_WIDE_FLAG ...]
|
|
|
|
DESCRIPTION
|
|
(ALPHA) $ gcloud alpha compute routers get-nat-mapping-info
|
|
|
|
shows a mapping of IP:port-ranges allocated to each VM's interface that is
|
|
configured to use NAT via the specified router.
|
|
|
|
EXAMPLES
|
|
To show NAT mappings from all NATs in router 'r1' in region 'us-central1',
|
|
run:
|
|
|
|
$ gcloud alpha compute routers get-nat-mapping-info r1 \
|
|
--region=us-central1
|
|
|
|
POSITIONAL ARGUMENTS
|
|
NAME
|
|
Name of the router to get NAT mapping info.
|
|
|
|
FLAGS
|
|
--nat-name=NAT_NAME
|
|
The NAT name to filter out NAT mapping information
|
|
|
|
--region=REGION
|
|
Region of the router to get NAT mapping info. If not specified, you
|
|
might be prompted to select a region (interactive mode only).
|
|
|
|
To avoid prompting when this flag is omitted, you can set the
|
|
compute/region property:
|
|
|
|
$ gcloud config set compute/region REGION
|
|
|
|
A list of regions can be fetched by running:
|
|
|
|
$ gcloud compute regions list
|
|
|
|
To unset the property, run:
|
|
|
|
$ gcloud config unset compute/region
|
|
|
|
Alternatively, the region can be stored in the environment variable
|
|
CLOUDSDK_COMPUTE_REGION.
|
|
|
|
LIST COMMAND FLAGS
|
|
--filter=EXPRESSION
|
|
Apply a Boolean filter EXPRESSION to each resource item to be listed.
|
|
If the expression evaluates True, then that item is listed. For more
|
|
details and examples of filter expressions, run $ gcloud topic filters.
|
|
This flag interacts with other flags that are applied in this order:
|
|
--flatten, --sort-by, --filter, --limit.
|
|
|
|
--limit=LIMIT
|
|
Maximum number of resources to list. The default is unlimited. This
|
|
flag interacts with other flags that are applied in this order:
|
|
--flatten, --sort-by, --filter, --limit.
|
|
|
|
--page-size=PAGE_SIZE
|
|
Some services group resource list output into pages. This flag
|
|
specifies the maximum number of resources per page. The default is
|
|
determined by the service if it supports paging, otherwise it is
|
|
unlimited (no paging). Paging may be applied before or after --filter
|
|
and --limit depending on the service.
|
|
|
|
--sort-by=[FIELD,...]
|
|
Comma-separated list of resource field key names to sort by. The
|
|
default order is ascending. Prefix a field with ``~'' for descending
|
|
order on that field. This flag interacts with other flags that are
|
|
applied in this order: --flatten, --sort-by, --filter, --limit.
|
|
|
|
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 compute routers get-nat-mapping-info
|
|
|
|
$ gcloud beta compute routers get-nat-mapping-info
|
|
|