mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 14:56:05 +00:00
gcloud: Wed Oct 11 10:37:28 UTC 2023
This commit is contained in:
parent
9641ff6585
commit
c30bb7b4ce
137 changed files with 3139 additions and 267 deletions
|
|
@ -1569,7 +1569,7 @@ FLAGS
|
|||
argument should be used in conjunction with
|
||||
--enable-autoprovisioning-blue-green-upgrade to take effect.
|
||||
|
||||
Batch sizes are specfied by one of, batch-node-count or
|
||||
Batch sizes are specified by one of, batch-node-count or
|
||||
batch-percent. The duration between batches is specified by
|
||||
batch-soak-duration.
|
||||
|
||||
|
|
@ -1823,9 +1823,11 @@ FLAGS
|
|||
--ephemeral-storage local-ssd-count=2
|
||||
|
||||
'local-ssd-count' specifies the number of local SSDs to use to back
|
||||
ephemeral storage. Local SDDs use NVMe interfaces and each is 375 GB
|
||||
in size. Setting 'local-ssd-count=0' disables using local SSDs as
|
||||
ephemeral storage.
|
||||
ephemeral storage. Local SDDs use NVMe interfaces. For first- and
|
||||
second-generation machine types, a nonzero count field is required
|
||||
for local ssd to be configured. For third-generation machine types,
|
||||
the count field is optional because the count is inferred from the
|
||||
machine type.
|
||||
|
||||
See https://cloud.google.com/compute/docs/disks/local-ssd for more
|
||||
information.
|
||||
|
|
@ -1840,8 +1842,11 @@ FLAGS
|
|||
--ephemeral-storage-local-ssd count=2
|
||||
|
||||
'count' specifies the number of local SSDs to use to back ephemeral
|
||||
storage. Local SDDs use NVMe interfaces and each is 375 GB in size.
|
||||
Setting 'count=0' disables using local SSDs as ephemeral storage.
|
||||
storage. Local SDDs use NVMe interfaces. For first- and
|
||||
second-generation machine types, a nonzero count field is required
|
||||
for local ssd to be configured. For third-generation machine types,
|
||||
the count field is optional because the count is inferred from the
|
||||
machine type.
|
||||
|
||||
See https://cloud.google.com/compute/docs/disks/local-ssd for more
|
||||
information.
|
||||
|
|
@ -1860,11 +1865,13 @@ FLAGS
|
|||
New nodes, including ones created by resize or recreate, will have
|
||||
these local SSDs.
|
||||
|
||||
Local SSDs have a fixed 375 GB capacity per device. The number of
|
||||
disks that can be attached to an instance is limited by the maximum
|
||||
number of disks available on a machine, which differs by compute
|
||||
zone. See https://cloud.google.com/compute/docs/disks/local-ssd for
|
||||
more information.
|
||||
For first- and second-generation machine types, a nonzero count field
|
||||
is required for local ssd to be configured. For third-generation
|
||||
machine types, the count field is optional because the count is
|
||||
inferred from the machine type.
|
||||
|
||||
See https://cloud.google.com/compute/docs/disks/local-ssd for more
|
||||
information.
|
||||
|
||||
--local-ssd-count=LOCAL_SSD_COUNT
|
||||
--local-ssd-count is the equivalent of using --local-ssd-volumes with
|
||||
|
|
|
|||
|
|
@ -255,10 +255,10 @@ FLAGS
|
|||
|
||||
Examples:
|
||||
|
||||
$ gcloud alpha container clusters create-auto --logging=SYSTEM
|
||||
$ gcloud alpha container clusters create-auto \
|
||||
--logging=SYSTEM,WORKLOAD
|
||||
$ gcloud alpha container clusters create-auto \
|
||||
--logging=SYSTEM,API_SERVER,WORKLOAD
|
||||
$ gcloud alpha container clusters create-auto --logging=NONE
|
||||
|
||||
--monitoring=[COMPONENT,...]
|
||||
Set the components that have monitoring enabled. Valid component values
|
||||
|
|
@ -273,7 +273,7 @@ FLAGS
|
|||
|
||||
$ gcloud alpha container clusters create-auto \
|
||||
--monitoring=SYSTEM,API_SERVER,POD
|
||||
$ gcloud alpha container clusters create-auto --monitoring=NONE
|
||||
$ gcloud alpha container clusters create-auto --monitoring=SYSTEM
|
||||
|
||||
--network=NETWORK
|
||||
The Compute Engine Network that the cluster will connect to. Google
|
||||
|
|
|
|||
|
|
@ -1122,7 +1122,7 @@ REQUIRED FLAGS
|
|||
argument should be used in conjunction with
|
||||
--enable-autoprovisioning-blue-green-upgrade to take effect.
|
||||
|
||||
Batch sizes are specfied by one of, batch-node-count or
|
||||
Batch sizes are specified by one of, batch-node-count or
|
||||
batch-percent. The duration between batches is specified by
|
||||
batch-soak-duration.
|
||||
|
||||
|
|
|
|||
|
|
@ -870,9 +870,11 @@ FLAGS
|
|||
--cluster=example cluster --ephemeral-storage local-ssd-count=2
|
||||
|
||||
'local-ssd-count' specifies the number of local SSDs to use to back
|
||||
ephemeral storage. Local SDDs use NVMe interfaces and each is 375 GB
|
||||
in size. Setting 'local-ssd-count=0' disables using local SSDs as
|
||||
ephemeral storage.
|
||||
ephemeral storage. Local SDDs use NVMe interfaces. For first- and
|
||||
second-generation machine types, a nonzero count field is required
|
||||
for local ssd to be configured. For third-generation machine types,
|
||||
the count field is optional because the count is inferred from the
|
||||
machine type.
|
||||
|
||||
See https://cloud.google.com/compute/docs/disks/local-ssd for more
|
||||
information.
|
||||
|
|
@ -887,8 +889,11 @@ FLAGS
|
|||
--cluster=example cluster --ephemeral-storage-local-ssd count=2
|
||||
|
||||
'count' specifies the number of local SSDs to use to back ephemeral
|
||||
storage. Local SDDs use NVMe interfaces and each is 375 GB in size.
|
||||
Setting 'count=0' disables using local SSDs as ephemeral storage.
|
||||
storage. Local SDDs use NVMe interfaces. For first- and
|
||||
second-generation machine types, a nonzero count field is required
|
||||
for local ssd to be configured. For third-generation machine types,
|
||||
the count field is optional because the count is inferred from the
|
||||
machine type.
|
||||
|
||||
See https://cloud.google.com/compute/docs/disks/local-ssd for more
|
||||
information.
|
||||
|
|
@ -907,11 +912,13 @@ FLAGS
|
|||
New nodes, including ones created by resize or recreate, will have
|
||||
these local SSDs.
|
||||
|
||||
Local SSDs have a fixed 375 GB capacity per device. The number of
|
||||
disks that can be attached to an instance is limited by the maximum
|
||||
number of disks available on a machine, which differs by compute
|
||||
zone. See https://cloud.google.com/compute/docs/disks/local-ssd for
|
||||
more information.
|
||||
For first- and second-generation machine types, a nonzero count field
|
||||
is required for local ssd to be configured. For third-generation
|
||||
machine types, the count field is optional because the count is
|
||||
inferred from the machine type.
|
||||
|
||||
See https://cloud.google.com/compute/docs/disks/local-ssd for more
|
||||
information.
|
||||
|
||||
--local-ssd-count=LOCAL_SSD_COUNT
|
||||
--local-ssd-count is the equivalent of using --local-ssd-volumes with
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue