1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-20 04:58:26 +00:00

gcloud: Wed Oct 8 11:07:39 UTC 2025

This commit is contained in:
Automated 2025-10-08 11:07:39 +00:00
parent a0434a4d7a
commit 6f9bb9a0f0
137 changed files with 5133 additions and 291 deletions

View file

@ -14,14 +14,15 @@ SYNOPSIS
[--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER]
[--description=DESCRIPTION] [--failover]
[--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE]
[--traffic-duration=TRAFFIC_DURATION]
[--custom-metrics=[CUSTOM_METRICS,...]
| --custom-metrics-file=[CUSTOM_METRICS,...]]
[--global | --region=REGION]
[--max-connections=MAX_CONNECTIONS
| --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT
| --max-connections-per-instance=MAX_CONNECTIONS_PER_INSTANCE
| --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT
| --max-rate-per-instance=MAX_RATE_PER_INSTANCE]
| --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS
| --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT | --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT | --max-rate-per-instance=MAX_RATE_PER_INSTANCE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -188,6 +189,19 @@ OPTIONAL FLAGS
CUSTOM_METRICS
Spreads load based on custom defined and reported metrics.
IN_FLIGHT
Available if the backend service's load balancing scheme is
INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL_MANAGED.
Available if the backend service's protocol is one of HTTP, HTTPS,
or HTTP/2.
Spreads load based on how many in-flight requests the backend can
handle.
You must specify exactly one of these additional parameters:
--max-in-flight-requests, --max-in-flight-requests-per-instance, or
--max-in-flight-requests-per-endpoint, and --traffic-duration=LONG.
RATE
Available if the backend service's load balancing scheme is
INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL. Available if
@ -256,6 +270,20 @@ OPTIONAL FLAGS
Backends with this preference setting are used up to their capacity
limits first, while optimizing overall network latency.
--traffic-duration=TRAFFIC_DURATION
The expected traffic duration for this service. TRAFFIC_DURATION must
be one of:
LONG
Most of the requests are expected to take more than multiple
seconds to finish.
SHORT
Most requests are expected to finish with a sub-second latency.
TRAFFIC_DURATION_UNSPECIFIED
Default value. Defaults to SHORT.
At most one of these can be specified:
--custom-metrics=[CUSTOM_METRICS,...]
@ -372,6 +400,29 @@ OPTIONAL FLAGS
number of instances in the instance group, and then dividing by the
number of healthy instances.
--max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS
Maximum number of in-flight requests that the backend can handle.
This cannot be used when the endpoint type of an attached network
endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or
SERVERLESS.
--max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT
Only valid for network endpoint group backends. Defines the maximum
number of in-flight requests per endpoint.
This cannot be used when the endpoint type of an attached network
endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or
SERVERLESS.
--max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE
Only valid for instance group backends. Defines the maximum number of
in-flight requests per instance.
This cannot be used when the endpoint type of an attached network
endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or
SERVERLESS.
--max-rate=MAX_RATE
Maximum number of HTTP requests per second (RPS) that the backend can
handle. Valid for network endpoint group and instance group backends

View file

@ -12,14 +12,15 @@ SYNOPSIS
[--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER]
[--description=DESCRIPTION] [--failover]
[--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE]
[--traffic-duration=TRAFFIC_DURATION]
[--clear-custom-metrics | --custom-metrics=[CUSTOM_METRICS,...]
| --custom-metrics-file=[CUSTOM_METRICS,...]]
[--global | --region=REGION]
[--max-connections=MAX_CONNECTIONS
| --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT
| --max-connections-per-instance=MAX_CONNECTIONS_PER_INSTANCE
| --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT
| --max-rate-per-instance=MAX_RATE_PER_INSTANCE]
| --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS
| --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT | --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT | --max-rate-per-instance=MAX_RATE_PER_INSTANCE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -160,6 +161,19 @@ OPTIONAL FLAGS
CUSTOM_METRICS
Spreads load based on custom defined and reported metrics.
IN_FLIGHT
Available if the backend service's load balancing scheme is
INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL_MANAGED.
Available if the backend service's protocol is one of HTTP, HTTPS,
or HTTP/2.
Spreads load based on how many in-flight requests the backend can
handle.
You must specify exactly one of these additional parameters:
--max-in-flight-requests, --max-in-flight-requests-per-instance, or
--max-in-flight-requests-per-endpoint, and --traffic-duration=LONG.
RATE
Available if the backend service's load balancing scheme is
INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL. Available if
@ -225,6 +239,20 @@ OPTIONAL FLAGS
Backends with this preference setting are used up to their capacity
limits first, while optimizing overall network latency.
--traffic-duration=TRAFFIC_DURATION
The expected traffic duration for this service. TRAFFIC_DURATION must
be one of:
LONG
Most of the requests are expected to take more than multiple
seconds to finish.
SHORT
Most requests are expected to finish with a sub-second latency.
TRAFFIC_DURATION_UNSPECIFIED
Default value. Defaults to SHORT.
At most one of these can be specified:
--clear-custom-metrics
@ -336,6 +364,17 @@ OPTIONAL FLAGS
number of instances in the instance group, and then dividing by the
number of healthy instances.
--max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS
Maximum number of in-flight requests that the backend can handle.
--max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT
Only valid for network endpoint group backends. Defines the maximum
number of in-flight requests per endpoint.
--max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE
Only valid for instance group backends. Defines the maximum number of
in-flight requests per instance.
--max-rate=MAX_RATE
Maximum number of HTTP requests per second (RPS) that the backend can
handle. Valid for network endpoint group and instance group backends

View file

@ -0,0 +1,100 @@
NAME
gcloud beta compute health-sources create - create a health source
SYNOPSIS
gcloud beta compute health-sources create (HEALTH_SOURCE : --region=REGION)
--health-aggregation-policy=HEALTH_AGGREGATION_POLICY
--sources=[SOURCES,...] [--async] [--description=DESCRIPTION]
[--source-type=SOURCE_TYPE; default="backend-service"]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Create a health source.
EXAMPLES
The following command creates a new health source:
$ gcloud beta compute health-sources create <HEALTH_SOURCE_NAME> \
--region=<REGION> --source-type=BACKEND_SERVICE \
--sources=my-backend-service \
--health-aggregation-policy=my-health-aggregation-policy
POSITIONAL ARGUMENTS
Health source resource - The name of the health source you want to create.
The arguments in this group can be used to specify the attributes of this
resource. (NOTE) Some attributes are not given arguments in this group but
can be set in other ways.
To set the project attribute:
◆ provide the argument health_source on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
HEALTH_SOURCE
ID of the health source or fully qualified identifier for the health
source.
To set the health_source attribute:
▸ provide the argument health_source on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--region=REGION
The name of the Google Compute Engine region.
To set the region attribute:
▸ provide the argument health_source on the command line with a
fully specified name;
▸ provide the argument --region on the command line;
▸ set the property compute/region.
REQUIRED FLAGS
--health-aggregation-policy=HEALTH_AGGREGATION_POLICY
URL to the health aggregation policy resource. Must be set. Must be
regional and in the same region as the HealthSource. Can be mutated.
--sources=[SOURCES,...]
URLs to the source resources. Must be size 1. Must be a BackendService
if the sourceType is BACKEND_SERVICE. The BackendService must have load
balancing scheme INTERNAL or INTERNAL_MANAGED and must be regional and
in the same region as the HealthSource (cross-region deployment for
INTERNAL_MANAGED is not supported). The BackendService may use only
IGs, MIGs, or NEGs of type GCE_VM_IP or GCE_VM_IP_PORT. The
BackendService may not use haPolicy. Can be mutated.
OPTIONAL FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--description=DESCRIPTION
A textual description of the HealthSource.
--source-type=SOURCE_TYPE; default="backend-service"
Specifies the type of the HealthSource. The only allowed value is
BACKEND_SERVICE. Must be specified when the HealthSource is created,
and cannot be mutated. SOURCE_TYPE must be (only one value is
supported): backend-service.
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.
API REFERENCE
This command uses the compute/beta API. The full documentation for this API
can be found at: https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha compute health-sources create

View file

@ -0,0 +1,72 @@
NAME
gcloud beta compute health-sources delete - delete a health source
SYNOPSIS
gcloud beta compute health-sources delete (HEALTH_SOURCE : --region=REGION)
[--async] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Delete a health source.
EXAMPLES
To delete a single health source, run the following command:
$ gcloud beta compute health-sources delete <HEALTH_SOURCE_NAME> \
--region=<REGION>
POSITIONAL ARGUMENTS
Health source resource - Name of the health source you want to delete. The
arguments in this group can be used to specify the attributes of this
resource. (NOTE) Some attributes are not given arguments in this group but
can be set in other ways.
To set the project attribute:
◆ provide the argument health_source on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
HEALTH_SOURCE
ID of the health source or fully qualified identifier for the health
source.
To set the health_source attribute:
▸ provide the argument health_source on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--region=REGION
The name of the Google Compute Engine region.
To set the region attribute:
▸ provide the argument health_source on the command line with a
fully specified name;
▸ provide the argument --region on the command line;
▸ set the property compute/region.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
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.
API REFERENCE
This command uses the compute/beta API. The full documentation for this API
can be found at: https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha compute health-sources delete

View file

@ -0,0 +1,68 @@
NAME
gcloud beta compute health-sources describe - describe a health source
SYNOPSIS
gcloud beta compute health-sources describe
(HEALTH_SOURCE : --region=REGION) [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Describe a health source.
EXAMPLES
To retrieve a single health source and print its properties, run the
following command:
$ gcloud beta compute health-sources describe <HEALTH_SOURCE_NAME> \
--region=<REGION>
POSITIONAL ARGUMENTS
Health source resource - Name of the health source you want to inspect.
The arguments in this group can be used to specify the attributes of this
resource. (NOTE) Some attributes are not given arguments in this group but
can be set in other ways.
To set the project attribute:
◆ provide the argument health_source on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
HEALTH_SOURCE
ID of the health source or fully qualified identifier for the health
source.
To set the health_source attribute:
▸ provide the argument health_source on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--region=REGION
The name of the Google Compute Engine region.
To set the region attribute:
▸ provide the argument health_source on the command line with a
fully specified name;
▸ provide the argument --region on the command line;
▸ set the property compute/region.
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.
API REFERENCE
This command uses the compute/beta API. The full documentation for this API
can be found at: https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha compute health-sources describe

View file

@ -0,0 +1,38 @@
NAME
gcloud beta compute health-sources - manage health sources
SYNOPSIS
gcloud beta compute health-sources COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Manage health sources.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
create
(BETA) Create a health source.
delete
(BETA) Delete a health source.
describe
(BETA) Describe a health source.
list
(BETA) List health sources.
update
(BETA) Update a health source.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha compute health-sources

View file

@ -0,0 +1,77 @@
NAME
gcloud beta compute health-sources list - list health sources
SYNOPSIS
gcloud beta compute health-sources list [NAME ...]
[--regexp=REGEXP, -r REGEXP] [--regions=REGION,[REGION,...]]
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) List health sources.
POSITIONAL ARGUMENTS
[NAME ...]
(DEPRECATED) If provided, show details for the specified names and/or
URIs of resources.
Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )"
instead.
FLAGS
--regexp=REGEXP, -r REGEXP
(DEPRECATED) Regular expression to filter the names of the results on.
Any names that do not match the entire regular expression will be
filtered out.
Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead.
--regions=REGION,[REGION,...]
If provided, only resources from the given regions are queried.
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.
--uri
Print a list of resource URIs instead of the default output, and change
the command output to a list of URIs. If this flag is used with
--format, the formatting is applied on this URI list. To display URIs
alongside other keys instead, use the uri() transform.
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 beta and might change without notice. This
variant is also available:
$ gcloud alpha compute health-sources list

View file

@ -0,0 +1,96 @@
NAME
gcloud beta compute health-sources update - update a health source
SYNOPSIS
gcloud beta compute health-sources update (HEALTH_SOURCE : --region=REGION)
(--description=DESCRIPTION
--health-aggregation-policy=HEALTH_AGGREGATION_POLICY
--sources=[SOURCES,...]) [--async] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update a health source.
EXAMPLES
The following command updates a new health source named "my-health-source":
$ gcloud beta compute health-sources update <HEALTH_SOURCE_NAME> \
--region=<REGION> --source-type=BACKEND_SERVICE \
--sources=my-backend-service \
--health-aggregation-policy=my-health-aggregation-policy
POSITIONAL ARGUMENTS
Health source resource - The name of the health source you want to create.
The arguments in this group can be used to specify the attributes of this
resource. (NOTE) Some attributes are not given arguments in this group but
can be set in other ways.
To set the project attribute:
◆ provide the argument health_source on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
HEALTH_SOURCE
ID of the health source or fully qualified identifier for the health
source.
To set the health_source attribute:
▸ provide the argument health_source on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--region=REGION
The name of the Google Compute Engine region.
To set the region attribute:
▸ provide the argument health_source on the command line with a
fully specified name;
▸ provide the argument --region on the command line;
▸ set the property compute/region.
REQUIRED FLAGS
At least one of these must be specified:
--description=DESCRIPTION
A textual description of the health source.
--health-aggregation-policy=HEALTH_AGGREGATION_POLICY
URL to the health aggregation policy resource. Must be set. Must be
regional and in the same region as the HealthSource. Can be mutated.
--sources=[SOURCES,...]
URLs to the source resources. Must be size 1. Must be a
BackendService if the sourceType is BACKEND_SERVICE. The
BackendService must have load balancing scheme INTERNAL or
INTERNAL_MANAGED and must be regional and in the same region as the
HealthSource (cross-region deployment for INTERNAL_MANAGED is not
supported). The BackendService may use only IGs, MIGs, or NEGs of
type GCE_VM_IP or GCE_VM_IP_PORT. The BackendService may not use
haPolicy. Can be mutated.
OPTIONAL FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
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.
API REFERENCE
This command uses the compute/beta API. The full documentation for this API
can be found at: https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha compute health-sources update

View file

@ -74,6 +74,9 @@ GROUPS
health-checks
(BETA) Read and manipulate health checks for load balanced instances.
health-sources
(BETA) Manage health sources.
http-health-checks
(BETA) Read and manipulate HTTP health checks for load balanced
instances.

View file

@ -101,7 +101,11 @@ OPTIONAL FLAGS
CLOUDSDK_COMPUTE_REGION.
--resource-manager-tags=[KEY=VALUE,...]
A comma-separated list of Resource Manager tags to apply to the router.
Comma-separated list of Resource Manager tags to attach to the router.
Key-value pairs must be provided in the form
tagKeys/{TagKey_Numeric_ID}=tagValues/{TagValue_Numeric_ID}. See
Listing tag keys
(https://cloud.google.com/resource-manager/docs/tags/tags-creating-and-managing#listing_keys).
--set-advertisement-groups=[GROUP,...]
The list of pre-defined groups of IP ranges to dynamically advertise on

View file

@ -9,7 +9,10 @@ SYNOPSIS
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Create a new Cloud TPU.
(BETA) (DEPRECATED) This command is being deprecated. Please use gcloud
compute tpus tpu-vm create instead.
Create a new Cloud TPU.
EXAMPLES
The following command creates a TPU with ID my-tpu in the default user

View file

@ -6,7 +6,10 @@ SYNOPSIS
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Deletes a Cloud TPU.
(BETA) (DEPRECATED) This command is being deprecated. Please use gcloud
compute tpus tpu-vm delete instead.
Deletes a Cloud TPU.
EXAMPLES
The following command deletes a TPU with ID my-tpu in zone us-central1-b:

View file

@ -6,7 +6,10 @@ SYNOPSIS
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Describe a Cloud TPU.
(BETA) (DEPRECATED) This command is being deprecated. Please use gcloud
compute tpus tpu-vm describe instead.
Describe a Cloud TPU.
EXAMPLES
The following command describes a TPU with ID my-tpu in zone us-central1-b:

View file

@ -38,25 +38,25 @@ COMMANDS
COMMAND is one of the following:
create
(BETA) Create a new Cloud TPU.
(BETA) (DEPRECATED) Create a new Cloud TPU.
delete
(BETA) Deletes a Cloud TPU.
(BETA) (DEPRECATED) Deletes a Cloud TPU.
describe
(BETA) Describe a Cloud TPU.
(BETA) (DEPRECATED) Describe a Cloud TPU.
list
(BETA) List Cloud TPUs.
(BETA) (DEPRECATED) List Cloud TPUs.
reimage
(BETA) Reimages the OS on a Cloud TPU.
(BETA) (DEPRECATED) Reimages the OS on a Cloud TPU.
start
(BETA) Start a Cloud TPU.
(BETA) (DEPRECATED) Start a Cloud TPU.
stop
(BETA) Stop a Cloud TPU.
(BETA) (DEPRECATED) Stop a Cloud TPU.
NOTES
This command is currently in beta and might change without notice. These

View file

@ -7,7 +7,10 @@ SYNOPSIS
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) List Cloud TPUs
(BETA) (DEPRECATED) This command is being deprecated. Please use gcloud
compute tpus tpu-vm list instead.
List Cloud TPUs
EXAMPLES
The following command lists the status of TPUs in zone us-central1-b:

View file

@ -6,7 +6,10 @@ SYNOPSIS
[--async] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Reimages the OS on a Cloud TPU.
(BETA) (DEPRECATED) This command is being deprecated. Please use gcloud
compute tpus tpu-vm reimage instead.
Reimages the OS on a Cloud TPU.
EXAMPLES
The following command reimages a TPU with ID my-tpu in zone us-central1-b

View file

@ -6,7 +6,10 @@ SYNOPSIS
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Start a Cloud TPU.
(BETA) (DEPRECATED) This command is being deprecated. Please use gcloud
compute tpus tpu-vm start instead.
Start a Cloud TPU.
EXAMPLES
The following command starts a TPU with ID my-tpu in zone us-central1-b:

View file

@ -6,7 +6,10 @@ SYNOPSIS
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Stop a Cloud TPU.
(BETA) (DEPRECATED) This command is being deprecated. Please use gcloud
compute tpus tpu-vm stop instead.
Stop a Cloud TPU.
EXAMPLES
The following command stops a TPU with ID my-tpu in zone us-central1-b: