mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-13 00:18:35 +00:00
gcloud: Wed Jan 31 10:36:17 UTC 2024
This commit is contained in:
parent
7a546ffea4
commit
fa6c1dc7ec
142 changed files with 1981 additions and 793 deletions
|
|
@ -218,9 +218,9 @@ FLAGS
|
|||
pd-standard.
|
||||
|
||||
device-name
|
||||
An optional name that indicates the disk name the guest operating
|
||||
system will see. If omitted, a device name of the form
|
||||
persistent-disk-N will be used.
|
||||
An optional name to display the disk name in the guest operating
|
||||
system. If omitted, a device name of the form persistent-disk-N is
|
||||
used.
|
||||
|
||||
provisioned-iops
|
||||
Indicates how many IOPS to provision for the disk. This sets the
|
||||
|
|
@ -318,36 +318,37 @@ FLAGS
|
|||
Specifies a textual description for the instance template.
|
||||
|
||||
--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]
|
||||
Attaches persistent disks to the instances. The disks specified must
|
||||
already exist.
|
||||
Attaches an existing persistent disk to the instances.
|
||||
|
||||
name
|
||||
The disk to attach to the instances. When creating more than one
|
||||
instance and using this property, the only valid mode for attaching
|
||||
the disk is read-only (see mode below).
|
||||
The disk to attach to the instances. If you create more than one
|
||||
instance, you can only attach a disk in read-only mode. By default,
|
||||
you attach a zonal persistent disk located in the same zone of the
|
||||
instance. If you want to attach a regional persistent disk, you
|
||||
must specify the disk using its URI; for example,
|
||||
projects/myproject/regions/us-central1/disks/my-regional-disk.
|
||||
|
||||
mode
|
||||
Specifies the mode of the disk. Supported options are ro for
|
||||
read-only and rw for read-write. If omitted, rw is used as a
|
||||
default. It is an error for mode to be rw when creating more than
|
||||
one instance because read-write disks can only be attached to a
|
||||
single instance.
|
||||
The mode of the disk. Supported options are ro for read-only mode
|
||||
and rw for read-write mode. If omitted, rw is used as a default
|
||||
value. If you use rw when creating more than one instance, you
|
||||
encounter errors.
|
||||
|
||||
boot
|
||||
If yes, indicates that this is a boot disk. The virtual machines
|
||||
will use the first partition of the disk for their root file
|
||||
systems. The default value for this is no.
|
||||
If set to yes, you attach a boot disk. The virtual machine then
|
||||
uses the first partition of the disk for the root file systems. The
|
||||
default value for this is no.
|
||||
|
||||
device-name
|
||||
An optional name that indicates the disk name the guest operating
|
||||
system will see. If omitted, a device name of the form
|
||||
persistent-disk-N will be used.
|
||||
An optional name to display the disk name in the guest operating
|
||||
system. If omitted, a device name of the form persistent-disk-N is
|
||||
used.
|
||||
|
||||
auto-delete
|
||||
If yes, this persistent disk will be automatically deleted when the
|
||||
instance is deleted. However, if the disk is later detached from
|
||||
the instance, this option won't apply. The default value for this
|
||||
is yes.
|
||||
If set to yes, the persistent disk is automatically deleted when
|
||||
the instance is deleted. However, if you detach the disk from the
|
||||
instance, deleting the instance doesn't delete the disk. The
|
||||
default value for this is yes.
|
||||
|
||||
--[no-]enable-nested-virtualization
|
||||
If set to true, enables nested virtualization for the instance. Use
|
||||
|
|
|
|||
|
|
@ -296,13 +296,13 @@ FLAGS
|
|||
pd-standard.
|
||||
|
||||
device-name
|
||||
An optional name that indicates the disk name the guest operating
|
||||
system will see. Must be the same as name if used with
|
||||
An optional name to display the disk name in the guest operating
|
||||
system. Must be the same as name if used with
|
||||
--container-mount-disk. If omitted, a device name of the form
|
||||
persistent-disk-N will be used. If omitted and used with
|
||||
persistent-disk-N is used. If omitted and used with
|
||||
--container-mount-disk (where the name of the container mount disk
|
||||
is the same as in this flag), a device name equal to disk name will
|
||||
be used.
|
||||
is the same as in this flag), a device name equal to disk name is
|
||||
used.
|
||||
|
||||
provisioned-iops
|
||||
Indicates how many IOPS to provision for the disk. This sets the
|
||||
|
|
@ -344,40 +344,41 @@ FLAGS
|
|||
Specifies a textual description for the instance template.
|
||||
|
||||
--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]
|
||||
Attaches persistent disks to the instances. The disks specified must
|
||||
already exist.
|
||||
Attaches an existing persistent disk to the instances.
|
||||
|
||||
name
|
||||
The disk to attach to the instances. When creating more than one
|
||||
instance and using this property, the only valid mode for attaching
|
||||
the disk is read-only (see mode below).
|
||||
The disk to attach to the instances. If you create more than one
|
||||
instance, you can only attach a disk in read-only mode. By default,
|
||||
you attach a zonal persistent disk located in the same zone of the
|
||||
instance. If you want to attach a regional persistent disk, you
|
||||
must specify the disk using its URI; for example,
|
||||
projects/myproject/regions/us-central1/disks/my-regional-disk.
|
||||
|
||||
mode
|
||||
Specifies the mode of the disk. Supported options are ro for
|
||||
read-only and rw for read-write. If omitted, rw is used as a
|
||||
default. It is an error for mode to be rw when creating more than
|
||||
one instance because read-write disks can only be attached to a
|
||||
single instance.
|
||||
The mode of the disk. Supported options are ro for read-only mode
|
||||
and rw for read-write mode. If omitted, rw is used as a default
|
||||
value. If you use rw when creating more than one instance, you
|
||||
encounter errors.
|
||||
|
||||
boot
|
||||
If yes, indicates that this is a boot disk. The virtual machines
|
||||
will use the first partition of the disk for their root file
|
||||
systems. The default value for this is no.
|
||||
If set to yes, you attach a boot disk. The virtual machine then
|
||||
uses the first partition of the disk for the root file systems. The
|
||||
default value for this is no.
|
||||
|
||||
device-name
|
||||
An optional name that indicates the disk name the guest operating
|
||||
system will see. Must be the same as name if used with
|
||||
An optional name to display the disk name in the guest operating
|
||||
system. Must be the same as name if used with
|
||||
--container-mount-disk. If omitted, a device name of the form
|
||||
persistent-disk-N will be used. If omitted and used with
|
||||
persistent-disk-N is used. If omitted and used with
|
||||
--container-mount-disk (where the name of the container mount disk
|
||||
is the same as in this flag), a device name equal to disk name will
|
||||
be used.
|
||||
is the same as in this flag), a device name equal to disk name is
|
||||
used.
|
||||
|
||||
auto-delete
|
||||
If yes, this persistent disk will be automatically deleted when the
|
||||
instance is deleted. However, if the disk is later detached from
|
||||
the instance, this option won't apply. The default value for this
|
||||
is yes.
|
||||
If set to yes, the persistent disk is automatically deleted when
|
||||
the instance is deleted. However, if you detach the disk from the
|
||||
instance, deleting the instance doesn't delete the disk. The
|
||||
default value for this is yes.
|
||||
|
||||
--external-ipv6-address=EXTERNAL_IPV6_ADDRESS
|
||||
Assigns the given external IPv6 address to the instance that is
|
||||
|
|
|
|||
|
|
@ -251,9 +251,9 @@ OPTIONAL FLAGS
|
|||
pd-standard.
|
||||
|
||||
device-name
|
||||
An optional name that indicates the disk name the guest operating
|
||||
system will see. If omitted, a device name of the form
|
||||
persistent-disk-N will be used.
|
||||
An optional name to display the disk name in the guest operating
|
||||
system. If omitted, a device name of the form persistent-disk-N is
|
||||
used.
|
||||
|
||||
provisioned-iops
|
||||
Indicates how many IOPS to provision for the disk. This sets the
|
||||
|
|
@ -384,9 +384,9 @@ OPTIONAL FLAGS
|
|||
systems. The default value for this is no.
|
||||
|
||||
device-name
|
||||
An optional name that indicates the disk name the guest operating
|
||||
system will see. If omitted, a device name of the form
|
||||
persistent-disk-N will be used.
|
||||
An optional name to display the disk name in the guest operating
|
||||
system. If omitted, a device name of the form persistent-disk-N is
|
||||
used.
|
||||
|
||||
scope
|
||||
Can be zonal or regional. If zonal, the disk is interpreted as a
|
||||
|
|
|
|||
|
|
@ -247,9 +247,9 @@ FLAGS
|
|||
pd-standard.
|
||||
|
||||
device-name
|
||||
An optional name that indicates the disk name the guest operating
|
||||
system will see. If omitted, a device name of the form
|
||||
persistent-disk-N will be used.
|
||||
An optional name to display the disk name in the guest operating
|
||||
system. If omitted, a device name of the form persistent-disk-N is
|
||||
used.
|
||||
|
||||
provisioned-iops
|
||||
Indicates how many IOPS to provision for the disk. This sets the
|
||||
|
|
@ -372,36 +372,37 @@ FLAGS
|
|||
Specifies a textual description of the instances.
|
||||
|
||||
--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE]
|
||||
Attaches persistent disks to the instances. The disks specified must
|
||||
already exist.
|
||||
Attaches an existing persistent disk to the instances.
|
||||
|
||||
name
|
||||
The disk to attach to the instances. When creating more than one
|
||||
instance and using this property, the only valid mode for attaching
|
||||
the disk is read-only (see mode below).
|
||||
The disk to attach to the instances. If you create more than one
|
||||
instance, you can only attach a disk in read-only mode. By default,
|
||||
you attach a zonal persistent disk located in the same zone of the
|
||||
instance. If you want to attach a regional persistent disk, you
|
||||
must specify the disk using its URI; for example,
|
||||
projects/myproject/regions/us-central1/disks/my-regional-disk.
|
||||
|
||||
mode
|
||||
Specifies the mode of the disk. Supported options are ro for
|
||||
read-only and rw for read-write. If omitted, rw is used as a
|
||||
default. It is an error for mode to be rw when creating more than
|
||||
one instance because read-write disks can only be attached to a
|
||||
single instance.
|
||||
The mode of the disk. Supported options are ro for read-only mode
|
||||
and rw for read-write mode. If omitted, rw is used as a default
|
||||
value. If you use rw when creating more than one instance, you
|
||||
encounter errors.
|
||||
|
||||
boot
|
||||
If yes, indicates that this is a boot disk. The virtual machines
|
||||
will use the first partition of the disk for their root file
|
||||
systems. The default value for this is no.
|
||||
If set to yes, you attach a boot disk. The virtual machine then
|
||||
uses the first partition of the disk for the root file systems. The
|
||||
default value for this is no.
|
||||
|
||||
device-name
|
||||
An optional name that indicates the disk name the guest operating
|
||||
system will see. If omitted, a device name of the form
|
||||
persistent-disk-N will be used.
|
||||
An optional name to display the disk name in the guest operating
|
||||
system. If omitted, a device name of the form persistent-disk-N is
|
||||
used.
|
||||
|
||||
auto-delete
|
||||
If yes, this persistent disk will be automatically deleted when the
|
||||
instance is deleted. However, if the disk is later detached from
|
||||
the instance, this option won't apply. The default value for this
|
||||
is yes.
|
||||
If set to yes, the persistent disk is automatically deleted when
|
||||
the instance is deleted. However, if you detach the disk from the
|
||||
instance, deleting the instance doesn't delete the disk. The
|
||||
default value for this is yes.
|
||||
|
||||
scope
|
||||
Can be zonal or regional. If zonal, the disk is interpreted as a
|
||||
|
|
|
|||
|
|
@ -319,13 +319,13 @@ FLAGS
|
|||
pd-standard.
|
||||
|
||||
device-name
|
||||
An optional name that indicates the disk name the guest operating
|
||||
system will see. Must be the same as name if used with
|
||||
An optional name to display the disk name in the guest operating
|
||||
system. Must be the same as name if used with
|
||||
--container-mount-disk. If omitted, a device name of the form
|
||||
persistent-disk-N will be used. If omitted and used with
|
||||
persistent-disk-N is used. If omitted and used with
|
||||
--container-mount-disk (where the name of the container mount disk
|
||||
is the same as in this flag), a device name equal to disk name will
|
||||
be used.
|
||||
is the same as in this flag), a device name equal to disk name is
|
||||
used.
|
||||
|
||||
provisioned-iops
|
||||
Indicates how many IOPS to provision for the disk. This sets the
|
||||
|
|
@ -367,40 +367,41 @@ FLAGS
|
|||
Specifies a textual description of the instances.
|
||||
|
||||
--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME],[force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE]
|
||||
Attaches persistent disks to the instances. The disks specified must
|
||||
already exist.
|
||||
Attaches an existing persistent disk to the instances.
|
||||
|
||||
name
|
||||
The disk to attach to the instances. When creating more than one
|
||||
instance and using this property, the only valid mode for attaching
|
||||
the disk is read-only (see mode below).
|
||||
The disk to attach to the instances. If you create more than one
|
||||
instance, you can only attach a disk in read-only mode. By default,
|
||||
you attach a zonal persistent disk located in the same zone of the
|
||||
instance. If you want to attach a regional persistent disk, you
|
||||
must specify the disk using its URI; for example,
|
||||
projects/myproject/regions/us-central1/disks/my-regional-disk.
|
||||
|
||||
mode
|
||||
Specifies the mode of the disk. Supported options are ro for
|
||||
read-only and rw for read-write. If omitted, rw is used as a
|
||||
default. It is an error for mode to be rw when creating more than
|
||||
one instance because read-write disks can only be attached to a
|
||||
single instance.
|
||||
The mode of the disk. Supported options are ro for read-only mode
|
||||
and rw for read-write mode. If omitted, rw is used as a default
|
||||
value. If you use rw when creating more than one instance, you
|
||||
encounter errors.
|
||||
|
||||
boot
|
||||
If yes, indicates that this is a boot disk. The virtual machines
|
||||
will use the first partition of the disk for their root file
|
||||
systems. The default value for this is no.
|
||||
If set to yes, you attach a boot disk. The virtual machine then
|
||||
uses the first partition of the disk for the root file systems. The
|
||||
default value for this is no.
|
||||
|
||||
device-name
|
||||
An optional name that indicates the disk name the guest operating
|
||||
system will see. Must be the same as name if used with
|
||||
An optional name to display the disk name in the guest operating
|
||||
system. Must be the same as name if used with
|
||||
--container-mount-disk. If omitted, a device name of the form
|
||||
persistent-disk-N will be used. If omitted and used with
|
||||
persistent-disk-N is used. If omitted and used with
|
||||
--container-mount-disk (where the name of the container mount disk
|
||||
is the same as in this flag), a device name equal to disk name will
|
||||
be used.
|
||||
is the same as in this flag), a device name equal to disk name is
|
||||
used.
|
||||
|
||||
auto-delete
|
||||
If yes, this persistent disk will be automatically deleted when the
|
||||
instance is deleted. However, if the disk is later detached from
|
||||
the instance, this option won't apply. The default value for this
|
||||
is yes.
|
||||
If set to yes, the persistent disk is automatically deleted when
|
||||
the instance is deleted. However, if you detach the disk from the
|
||||
instance, deleting the instance doesn't delete the disk. The
|
||||
default value for this is yes.
|
||||
|
||||
scope
|
||||
Can be zonal or regional. If zonal, the disk is interpreted as a
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ NAME
|
|||
custom subnet mode
|
||||
|
||||
SYNOPSIS
|
||||
gcloud compute networks subnets create NAME --network=NETWORK --range=RANGE
|
||||
gcloud compute networks subnets create NAME --network=NETWORK
|
||||
[--description=DESCRIPTION] [--enable-flow-logs]
|
||||
[--enable-private-ip-google-access]
|
||||
[--ipv6-access-type=IPV6_ACCESS_TYPE]
|
||||
|
|
@ -13,9 +13,11 @@ SYNOPSIS
|
|||
[--logging-metadata=LOGGING_METADATA]
|
||||
[--logging-metadata-fields=[METADATA_FIELD,...]]
|
||||
[--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE]
|
||||
[--purpose=PURPOSE] [--region=REGION] [--role=ROLE]
|
||||
[--secondary-range=PROPERTY=VALUE,[...]] [--stack-type=STACK_TYPE]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
[--purpose=PURPOSE] [--range=RANGE] [--region=REGION]
|
||||
[--reserved-internal-range=RESERVED_INTERNAL_RANGE] [--role=ROLE]
|
||||
[--secondary-range=PROPERTY=VALUE,[...]]
|
||||
[--secondary-range-with-reserved-internal-range=RANGE_NAME=INTERNAL_RANGE_URL,
|
||||
[...]] [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
gcloud compute networks subnets create define a subnetwork for a network in
|
||||
|
|
@ -36,9 +38,6 @@ REQUIRED FLAGS
|
|||
--network=NETWORK
|
||||
The network to which the subnetwork belongs.
|
||||
|
||||
--range=RANGE
|
||||
The IP space allocated to this subnetwork in CIDR format.
|
||||
|
||||
OPTIONAL FLAGS
|
||||
--description=DESCRIPTION
|
||||
An optional description of this subnetwork.
|
||||
|
|
@ -115,6 +114,9 @@ OPTIONAL FLAGS
|
|||
REGIONAL_MANAGED_PROXY
|
||||
Reserved for Regional Envoy-based Load Balancing.
|
||||
|
||||
--range=RANGE
|
||||
The IP space allocated to this subnetwork in CIDR format.
|
||||
|
||||
--region=REGION
|
||||
Region of the subnetwork to create. If not specified, you might be
|
||||
prompted to select a region (interactive mode only).
|
||||
|
|
@ -135,6 +137,18 @@ OPTIONAL FLAGS
|
|||
Alternatively, the region can be stored in the environment variable
|
||||
CLOUDSDK_COMPUTE_REGION.
|
||||
|
||||
--reserved-internal-range=RESERVED_INTERNAL_RANGE
|
||||
If set, the primary IP range of the subnetwork will be associated with
|
||||
the given internal range resource. If --range is set, the subnetwork
|
||||
will only use the given IP range, which must be contained by the IP
|
||||
range defined by the internal range resource. For example,
|
||||
--range=10.0.0.0/24 --reserved-internal-range
|
||||
//networkconnectivity.googleapis.com/projects/PROJECT/locations/global/internalRanges/RANGE
|
||||
If --range is not set, the subnetwork will use the entire IP range
|
||||
defined by the internal range resource. For example,
|
||||
--reserved-internal-range
|
||||
//networkconnectivity.googleapis.com/projects/PROJECT/locations/global/internalRanges/RANGE
|
||||
|
||||
--role=ROLE
|
||||
The role of subnetwork. This field is required when the purpose is set
|
||||
to GLOBAL_MANAGED_PROXY, REGIONAL_MANAGED_PROXY or
|
||||
|
|
@ -154,6 +168,14 @@ OPTIONAL FLAGS
|
|||
◆ RANGE_NAME - Name of the secondary range.
|
||||
◆ RANGE - IP range in CIDR format.
|
||||
|
||||
--secondary-range-with-reserved-internal-range=RANGE_NAME=INTERNAL_RANGE_URL,[...]
|
||||
Adds secondary IP ranges that are associated with internal range
|
||||
resources. For example, --secondary-range-with-reserved-internal-range
|
||||
range1=//networkconnectivity.googleapis.com/projects/PROJECT/locations/global/internalRanges/RANGE
|
||||
adds a secondary range with the reserved internal range resource.
|
||||
◆ RANGE_NAME - Name of the secondary range.
|
||||
◆ INTERNAL_RANGE_URL - URL of an internal range resource.
|
||||
|
||||
--stack-type=STACK_TYPE
|
||||
The stack type for this subnet. Determines if IPv6 is enabled on the
|
||||
subnet. If not specified IPV4_ONLY will be used. STACK_TYPE must be one
|
||||
|
|
|
|||
|
|
@ -4,7 +4,8 @@ NAME
|
|||
|
||||
SYNOPSIS
|
||||
gcloud compute networks subnets update NAME
|
||||
[--drain-timeout=DRAIN_TIMEOUT; default="0s"]
|
||||
[--add-secondary-ranges-with-reserved-internal-range=RANGE_NAME=INTERNAL_RANGE_URL,
|
||||
[...]] [--drain-timeout=DRAIN_TIMEOUT; default="0s"]
|
||||
[--ipv6-access-type=IPV6_ACCESS_TYPE]
|
||||
[--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL]
|
||||
[--logging-filter-expr=LOGGING_FILTER_EXPR]
|
||||
|
|
@ -35,6 +36,17 @@ POSITIONAL ARGUMENTS
|
|||
Name of the subnetwork to update.
|
||||
|
||||
FLAGS
|
||||
--add-secondary-ranges-with-reserved-internal-range=RANGE_NAME=INTERNAL_RANGE_URL,[...]
|
||||
Adds secondary IP ranges that are associated with internal range
|
||||
resources.
|
||||
|
||||
For example, --add-secondary-ranges-with-reserved-internal-range
|
||||
range1=//networkconnectivity.googleapis.com/projects/PROJECT/locations/global/internalRanges/RANGE
|
||||
adds a secondary range with the reserved internal range resource.
|
||||
|
||||
◆ RANGE_NAME - Name of the secondary range.
|
||||
◆ INTERNAL_RANGE_URL - URL of an internal range resource.
|
||||
|
||||
--drain-timeout=DRAIN_TIMEOUT; default="0s"
|
||||
The time period for draining traffic from Internal HTTP(S) Load
|
||||
Balancer proxies that are assigned addresses in the current ACTIVE
|
||||
|
|
|
|||
|
|
@ -72,8 +72,7 @@ REQUIRED FLAGS
|
|||
must be INTERNAL. You can use any --destination-range that doesn't
|
||||
exactly match the destination of a subnet route and isn't more
|
||||
specific (has a longer subnet mask) than the destination of a subnet
|
||||
route. Also, the forwarding rule's IP address can't be in the
|
||||
--destination-range. For more information, see
|
||||
route. For more information, see
|
||||
https://cloud.google.com/load-balancing/docs/internal/ilb-next-hop-overview#destination_range.
|
||||
|
||||
--next-hop-instance=NEXT_HOP_INSTANCE
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@ SYNOPSIS
|
|||
[--async] [--data-disk=[mode=MODE],[source=SOURCE]]
|
||||
[--description=DESCRIPTION] [--internal-ips] [--labels=[KEY=VALUE,...]]
|
||||
[--metadata=[KEY=VALUE,...]] [--metadata-from-file=[KEY=VALUE,...]]
|
||||
[--network=NETWORK; default="default"] [--preemptible] [--range=RANGE]
|
||||
[--reserved] [--scopes=[SCOPES,...]]
|
||||
[--service-account=SERVICE_ACCOUNT] [--shielded-secure-boot]
|
||||
[--subnetwork=SUBNETWORK] [--tags=[TAGS,...]]
|
||||
[--network=NETWORK; default="default"] [--preemptible]
|
||||
[--queue-count=QUEUE_COUNT] [--range=RANGE] [--reserved]
|
||||
[--scopes=[SCOPES,...]] [--service-account=SERVICE_ACCOUNT]
|
||||
[--shielded-secure-boot] [--subnetwork=SUBNETWORK] [--tags=[TAGS,...]]
|
||||
[--accelerator-type=ACCELERATOR_TYPE; default="v2-8"
|
||||
| --topology=TOPOLOGY --type=TYPE] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
|
|
@ -132,6 +132,13 @@ OPTIONAL FLAGS
|
|||
|
||||
Preemptible TPUs cannot be restarted.
|
||||
|
||||
--queue-count=QUEUE_COUNT
|
||||
Specifies the networking queue count for TPU VM instances. Both Rx and
|
||||
Tx queues will be set to this number. If it's not specified, a default
|
||||
queue count will be assigned. For Virtio-net, each interface will get
|
||||
min(floor(#vCPU / #vNIC), 32) queues. For gVNIC, each interface will
|
||||
get min(floor(#vCPU / #vNIC / 2), 16) queues.
|
||||
|
||||
--range=RANGE
|
||||
CIDR Range for the TPU.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue