mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-21 06:27:15 +00:00
gcloud: Wed Sep 17 11:04:06 UTC 2025
This commit is contained in:
parent
78d417f901
commit
79c9fb4d92
193 changed files with 12122 additions and 1486 deletions
|
|
@ -754,6 +754,9 @@ FLAGS
|
|||
affects the price, availability, and how long your VM instances can
|
||||
run. PROVISIONING_MODEL must be one of:
|
||||
|
||||
FLEX_START
|
||||
The VM instance is provisioned using the Flex Start provisioning
|
||||
model and has a limited runtime.
|
||||
RESERVATION_BOUND
|
||||
The VM instances run for the entire duration of their associated
|
||||
reservation. You can only specify this provisioning model if you
|
||||
|
|
|
|||
|
|
@ -47,6 +47,7 @@ SYNOPSIS
|
|||
[--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE]
|
||||
[--private-network-ip=PRIVATE_NETWORK_IP]
|
||||
[--provisioning-model=PROVISIONING_MODEL]
|
||||
[--request-valid-for-duration=REQUEST_VALID_FOR_DURATION]
|
||||
[--no-require-csek-key-create]
|
||||
[--resource-manager-tags=[KEY=VALUE,...]]
|
||||
[--resource-policies=[RESOURCE_POLICY,...]] [--no-restart-on-failure]
|
||||
|
|
@ -855,6 +856,9 @@ FLAGS
|
|||
affects the price, availability, and how long your VM instances can
|
||||
run. PROVISIONING_MODEL must be one of:
|
||||
|
||||
FLEX_START
|
||||
The VM instance is provisioned using the Flex Start provisioning
|
||||
model and has a limited runtime.
|
||||
RESERVATION_BOUND
|
||||
The VM instances run for the entire duration of their associated
|
||||
reservation. You can only specify this provisioning model if you
|
||||
|
|
@ -868,6 +872,17 @@ FLAGS
|
|||
The default option. The STANDARD provisioning model gives you full
|
||||
control over your VM instances' runtime.
|
||||
|
||||
--request-valid-for-duration=REQUEST_VALID_FOR_DURATION
|
||||
When you create an instance by using the FLEX_START provisioning model,
|
||||
you can specify the duration to wait for available resources. If the
|
||||
instance creation request is still pending after this duration, then
|
||||
the request fails. You specify a duration by using numbers followed by
|
||||
h, m, and s for hours, minutes, and seconds, respectively. For example,
|
||||
specify 30m for a duration of 30 minutes, or 1h2m3s for 1 hour, 2
|
||||
minutes, and 3 seconds. Longer durations give you higher chances that
|
||||
your instance creation request succeeds when resources are in high
|
||||
demand.
|
||||
|
||||
--require-csek-key-create
|
||||
Refuse to create resources not protected by a user managed key in the
|
||||
key file when --csek-key-file is given. This behavior is enabled by
|
||||
|
|
|
|||
|
|
@ -49,6 +49,7 @@ SYNOPSIS
|
|||
[--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE]
|
||||
[--private-network-ip=PRIVATE_NETWORK_IP]
|
||||
[--provisioning-model=PROVISIONING_MODEL]
|
||||
[--request-valid-for-duration=REQUEST_VALID_FOR_DURATION]
|
||||
[--resource-policies=[RESOURCE_POLICY,...]] [--no-restart-on-failure]
|
||||
[--shielded-integrity-monitoring] [--shielded-secure-boot]
|
||||
[--shielded-vtpm] [--source-instance-template=SOURCE_INSTANCE_TEMPLATE]
|
||||
|
|
@ -760,6 +761,9 @@ FLAGS
|
|||
affects the price, availability, and how long your VM instances can
|
||||
run. PROVISIONING_MODEL must be one of:
|
||||
|
||||
FLEX_START
|
||||
The VM instance is provisioned using the Flex Start provisioning
|
||||
model and has a limited runtime.
|
||||
RESERVATION_BOUND
|
||||
The VM instances run for the entire duration of their associated
|
||||
reservation. You can only specify this provisioning model if you
|
||||
|
|
@ -773,6 +777,17 @@ FLAGS
|
|||
The default option. The STANDARD provisioning model gives you full
|
||||
control over your VM instances' runtime.
|
||||
|
||||
--request-valid-for-duration=REQUEST_VALID_FOR_DURATION
|
||||
When you create an instance by using the FLEX_START provisioning model,
|
||||
you can specify the duration to wait for available resources. If the
|
||||
instance creation request is still pending after this duration, then
|
||||
the request fails. You specify a duration by using numbers followed by
|
||||
h, m, and s for hours, minutes, and seconds, respectively. For example,
|
||||
specify 30m for a duration of 30 minutes, or 1h2m3s for 1 hour, 2
|
||||
minutes, and 3 seconds. Longer durations give you higher chances that
|
||||
your instance creation request succeeds when resources are in high
|
||||
demand.
|
||||
|
||||
--resource-policies=[RESOURCE_POLICY,...]
|
||||
A list of resource policy names to be added to the instance. The
|
||||
policies must exist in the same region as the instance.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,8 @@ SYNOPSIS
|
|||
[--admin-enabled] [--customer-name=CUSTOMER_NAME]
|
||||
[--description=DESCRIPTION] [--noc-contact-email=NOC_CONTACT_EMAIL]
|
||||
[--remote-location=REMOTE_LOCATION]
|
||||
[--requested-features=[FEATURES,...]] [GCLOUD_WIDE_FLAG ...]
|
||||
[--requested-features=[FEATURES,...]] [--subzone=SUBZONE]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
gcloud compute interconnects create is used to create interconnects. An
|
||||
|
|
@ -114,6 +115,15 @@ OPTIONAL FLAGS
|
|||
only be provided during interconnect INSERT and cannot be changed
|
||||
using interconnect PATCH.
|
||||
|
||||
--subzone=SUBZONE
|
||||
Subzone in the LOCATION specified by the --location flag. SUBZONE must
|
||||
be one of:
|
||||
|
||||
a
|
||||
Subzone a.
|
||||
b
|
||||
Subzone b.
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
--billing-project, --configuration, --flags-file, --flatten, --format,
|
||||
|
|
|
|||
|
|
@ -7,9 +7,10 @@ SYNOPSIS
|
|||
(--accelerator-type=ACCELERATOR_TYPE | --topology=TOPOLOGY --type=TYPE)
|
||||
(--node-id=NODE_ID
|
||||
| [--node-count=NODE_COUNT : --node-prefix=NODE_PREFIX]) [--async]
|
||||
[--data-disk=[mode=MODE],[source=SOURCE]] [--description=DESCRIPTION]
|
||||
[--guaranteed] [--internal-ips] [--labels=[KEY=VALUE,...]]
|
||||
[--metadata=[KEY=VALUE,...]] [--metadata-from-file=[KEY=VALUE,...]]
|
||||
[--boot-disk=[KEY=VALUE,...]] [--data-disk=[mode=MODE],[source=SOURCE]]
|
||||
[--description=DESCRIPTION] [--guaranteed] [--internal-ips]
|
||||
[--labels=[KEY=VALUE,...]] [--metadata=[KEY=VALUE,...]]
|
||||
[--metadata-from-file=[KEY=VALUE,...]]
|
||||
[--network=NETWORK; default="default"] [--range=RANGE] [--reserved]
|
||||
[--scopes=[SCOPES,...]] [--service-account=SERVICE_ACCOUNT]
|
||||
[--shielded-secure-boot] [--spot] [--subnetwork=SUBNETWORK]
|
||||
|
|
@ -138,6 +139,19 @@ OPTIONAL FLAGS
|
|||
Return immediately, without waiting for the operation in progress to
|
||||
complete.
|
||||
|
||||
--boot-disk=[KEY=VALUE,...]
|
||||
Specifies the boot disk configuration.
|
||||
|
||||
$ gcloud compute tpus queued-resources create \
|
||||
--boot-disk kms-key=<full_kms_key_name_here>
|
||||
|
||||
The following keys are allowed:
|
||||
|
||||
kms-key
|
||||
Specifies the fully qualified Cloud KMS cryptokey name which will
|
||||
be used to protect the disk. KMS cryptokey name format:
|
||||
projects/<kms-project>/locations/<kms-location>/keyRings/<kms-keyring>/cryptoKeys/<key-name>
|
||||
|
||||
--data-disk=[mode=MODE],[source=SOURCE]
|
||||
Additional data disks for the TPU VM.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,8 +3,9 @@ NAME
|
|||
|
||||
SYNOPSIS
|
||||
gcloud compute tpus tpu-vm create (TPU : --zone=ZONE) --version=VERSION
|
||||
[--async] [--data-disk=[mode=MODE],[source=SOURCE]]
|
||||
[--description=DESCRIPTION] [--internal-ips] [--labels=[KEY=VALUE,...]]
|
||||
[--async] [--boot-disk=[KEY=VALUE,...]]
|
||||
[--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]
|
||||
[--queue-count=QUEUE_COUNT] [--range=RANGE] [--reserved]
|
||||
|
|
@ -82,6 +83,19 @@ OPTIONAL FLAGS
|
|||
Return immediately, without waiting for the operation in progress to
|
||||
complete.
|
||||
|
||||
--boot-disk=[KEY=VALUE,...]
|
||||
Specifies the boot disk configuration.
|
||||
|
||||
$ gcloud compute tpus tpu-vm create \
|
||||
--boot-disk kms-key=<full_kms_key_name_here>
|
||||
|
||||
The following keys are allowed:
|
||||
|
||||
kms-key
|
||||
Specifies the fully qualified Cloud KMS cryptokey name which will
|
||||
be used to protect the disk. KMS cryptokey name format:
|
||||
projects/<kms-project>/locations/<kms-location>/keyRings/<kms-keyring>/cryptoKeys/<key-name>
|
||||
|
||||
--data-disk=[mode=MODE],[source=SOURCE]
|
||||
Additional data disks for the TPU VM.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue