mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 14:56:05 +00:00
gcloud: Wed Sep 11 09:52:17 UTC 2024
This commit is contained in:
parent
78a4d78e9e
commit
a3842bba95
197 changed files with 6656 additions and 691 deletions
|
|
@ -53,7 +53,7 @@ SYNOPSIS
|
|||
[--source-instance-zone=SOURCE_INSTANCE_ZONE] [--stack-type=STACK_TYPE]
|
||||
[--subnet=SUBNET] [--tags=TAG,[TAG,...]]
|
||||
[--termination-time=TERMINATION_TIME]
|
||||
[--threads-per-core=THREADS_PER_CORE]
|
||||
[--threads-per-core=THREADS_PER_CORE] [--turbo-mode=TURBO_MODE]
|
||||
[--visible-core-count=VISIBLE_CORE_COUNT]
|
||||
[--address=ADDRESS | --no-address]
|
||||
[--boot-disk-kms-key=BOOT_DISK_KMS_KEY
|
||||
|
|
@ -957,6 +957,14 @@ FLAGS
|
|||
For more information about configuring SMT, see:
|
||||
https://cloud.google.com/compute/docs/instances/configuring-simultaneous-multithreading.
|
||||
|
||||
--turbo-mode=TURBO_MODE
|
||||
Turbo mode to use for the instance. Supported modes include:
|
||||
◆ ALL_CORE_MAX
|
||||
|
||||
To achieve all-core-turbo frequency for more consistent CPU
|
||||
performance, set the field to ALL_CORE_MAX. The field is unset by
|
||||
default, which results in maximum performance single-core boosting.
|
||||
|
||||
--visible-core-count=VISIBLE_CORE_COUNT
|
||||
The number of physical cores to expose to the instance's guest
|
||||
operating system. The number of virtual CPUs visible to the instance's
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ SYNOPSIS
|
|||
[--stack-type=STACK_TYPE] [--subnet=SUBNET] [--tags=TAG,[TAG,...]]
|
||||
[--target-distribution-shape=SHAPE]
|
||||
[--termination-time=TERMINATION_TIME]
|
||||
[--threads-per-core=THREADS_PER_CORE]
|
||||
[--threads-per-core=THREADS_PER_CORE] [--turbo-mode=TURBO_MODE]
|
||||
[--visible-core-count=VISIBLE_CORE_COUNT]
|
||||
[--boot-disk-kms-key=BOOT_DISK_KMS_KEY
|
||||
: --boot-disk-kms-keyring=BOOT_DISK_KMS_KEYRING
|
||||
|
|
@ -840,6 +840,14 @@ OPTIONAL FLAGS
|
|||
For more information about configuring SMT, see:
|
||||
https://cloud.google.com/compute/docs/instances/configuring-simultaneous-multithreading.
|
||||
|
||||
--turbo-mode=TURBO_MODE
|
||||
Turbo mode to use for the instance. Supported modes include:
|
||||
◆ ALL_CORE_MAX
|
||||
|
||||
To achieve all-core-turbo frequency for more consistent CPU
|
||||
performance, set the field to ALL_CORE_MAX. The field is unset by
|
||||
default, which results in maximum performance single-core boosting.
|
||||
|
||||
--visible-core-count=VISIBLE_CORE_COUNT
|
||||
The number of physical cores to expose to the instance's guest
|
||||
operating system. The number of virtual CPUs visible to the instance's
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ SYNOPSIS
|
|||
[--source-machine-image-csek-key-file=FILE] [--stack-type=STACK_TYPE]
|
||||
[--subnet=SUBNET] [--tags=TAG,[TAG,...]]
|
||||
[--termination-time=TERMINATION_TIME]
|
||||
[--threads-per-core=THREADS_PER_CORE]
|
||||
[--threads-per-core=THREADS_PER_CORE] [--turbo-mode=TURBO_MODE]
|
||||
[--visible-core-count=VISIBLE_CORE_COUNT] [--zone=ZONE]
|
||||
[--address=ADDRESS | --no-address]
|
||||
[--boot-disk-kms-key=BOOT_DISK_KMS_KEY
|
||||
|
|
@ -1023,6 +1023,14 @@ FLAGS
|
|||
For more information about configuring SMT, see:
|
||||
https://cloud.google.com/compute/docs/instances/configuring-simultaneous-multithreading.
|
||||
|
||||
--turbo-mode=TURBO_MODE
|
||||
Turbo mode to use for the instance. Supported modes include:
|
||||
◆ ALL_CORE_MAX
|
||||
|
||||
To achieve all-core-turbo frequency for more consistent CPU
|
||||
performance, set the field to ALL_CORE_MAX. The field is unset by
|
||||
default, which results in maximum performance single-core boosting.
|
||||
|
||||
--visible-core-count=VISIBLE_CORE_COUNT
|
||||
The number of physical cores to expose to the instance's guest
|
||||
operating system. The number of virtual CPUs visible to the instance's
|
||||
|
|
|
|||
|
|
@ -123,12 +123,12 @@ FLAGS
|
|||
serverless, gce-vm-ip, private-service-connect, gce-vm-ip-portmap.
|
||||
|
||||
--producer-port=PRODUCER_PORT
|
||||
The psc producer port to use when consumer PSC NEG connects to a
|
||||
producer.
|
||||
|
||||
If this flag isn't specified for a PSC NEG with endpoint type
|
||||
private-service-connect, then PSC NEG will be connected to a first port
|
||||
in the available pcs producer port range.
|
||||
The producer port to use when a consumer PSC NEG connects to a
|
||||
producer's internal network load balancer. If this flag isn't specified
|
||||
for a NEG with endpoint type private-service-connect, the PSC NEG will
|
||||
connect to port 443 or the first available port in the PSC producer
|
||||
port range, or to port 1 if the PSC producer's forwarding rule ports
|
||||
flag is set to all-ports.
|
||||
|
||||
This flag is not supported for NEGs with endpoint type other than
|
||||
private-service-connect.
|
||||
|
|
|
|||
|
|
@ -9,9 +9,8 @@ SYNOPSIS
|
|||
|
||||
DESCRIPTION
|
||||
(BETA) gcloud beta compute security-policies import imports a security
|
||||
policy to update an existing policy. The command does not support updating
|
||||
rules for the policy. To create a new policy from a file please use the
|
||||
create command instead.
|
||||
policy to update an existing policy. To create a new policy from a file
|
||||
please use the create command instead.
|
||||
|
||||
EXAMPLES
|
||||
To import a security policy from a YAML file run this:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue