imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-08 10:35:03 +00:00
Code Activity

gcloud: Fri Mar 24 11:31:22 UTC 2023

Browse source
This commit is contained in:
Automated 2023-03-24 11:31:22 +00:00
parent a4bd29dd06
commit 4ccfc7a5e3
142 changed files with 4081 additions and 397 deletions
Download patch file Download diff file Expand all files Collapse all files

3
gcloud/compute/disks/create
View file

@ -73,7 +73,8 @@ FLAGS
their boot disks. See the descriptions of supported features at:
https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features.
GUEST_OS_FEATURE must be one of: GVNIC, MULTI_IP_SUBNET, SEV_CAPABLE,
SEV_SNP_CAPABLE, UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, WINDOWS.
SEV_LIVE_MIGRATABLE, SEV_SNP_CAPABLE, UEFI_COMPATIBLE,
VIRTIO_SCSI_MULTIQUEUE, WINDOWS.
--labels=[KEY=VALUE,...]
List of label KEY=VALUE pairs to add.

3
gcloud/compute/images/create
View file

@ -144,7 +144,8 @@ OPTIONAL FLAGS
their boot disks. See the descriptions of supported features at:
https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features.
GUEST_OS_FEATURE must be one of: GVNIC, MULTI_IP_SUBNET, SEV_CAPABLE,
SEV_SNP_CAPABLE, UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, WINDOWS.
SEV_LIVE_MIGRATABLE, SEV_SNP_CAPABLE, UEFI_COMPATIBLE,
VIRTIO_SCSI_MULTIQUEUE, WINDOWS.
--key-exchange-key-file=[KEK_VALUE,...]
Comma-separated list of file paths that point to X.509 certificates in

82
gcloud/compute/images/import
View file

@ -3,8 +3,13 @@ NAME
SYNOPSIS
gcloud compute images import IMAGE_NAME
(--source-file=SOURCE_FILE | --source-image=SOURCE_IMAGE)
[--no-address] [--async]
(--aws-access-key-id=AWS_ACCESS_KEY_ID --aws-region=AWS_REGION
--aws-secret-access-key=AWS_SECRET_ACCESS_KEY
--aws-session-token=AWS_SESSION_TOKEN
(--aws-source-ami-file-path=AWS_SOURCE_AMI_FILE_PATH
| --aws-ami-export-location=AWS_AMI_EXPORT_LOCATION
--aws-ami-id=AWS_AMI_ID) | --source-file=SOURCE_FILE
| --source-image=SOURCE_IMAGE) [--no-address] [--async]
[--compute-service-account=COMPUTE_SERVICE_ACCOUNT]
[--description=DESCRIPTION] [--family=FAMILY] [--no-guest-environment]
[--guest-os-features=[GUEST_OS_FEATURE,...]]
@ -54,14 +59,73 @@ POSITIONAL ARGUMENTS
REQUIRED FLAGS
Exactly one of these must be specified:
--source-file=SOURCE_FILE
A local file, or the Cloud Storage URI of the virtual disk file to
import. For example: gs://my-bucket/my-image.vmdk or
./my-local-image.vmdk. For more information about Cloud Storage URIs,
see https://cloud.google.com/storage/docs/request-endpoints#json-api.
Image import from AWS.
--source-image=SOURCE_IMAGE
An existing Compute Engine image from which to import.
--aws-access-key-id=AWS_ACCESS_KEY_ID
Access key ID for a temporary AWS credential. This ID must be
generated using the AWS Security Token Service.
This flag argument must be specified if any of the other arguments
in this group are specified.
--aws-region=AWS_REGION
AWS region of the image that you want to import.
This flag argument must be specified if any of the other arguments
in this group are specified.
--aws-secret-access-key=AWS_SECRET_ACCESS_KEY
Secret access key for a temporary AWS credential. This key must be
generated using the AWS Security Token Service.
This flag argument must be specified if any of the other arguments
in this group are specified.
--aws-session-token=AWS_SESSION_TOKEN
Session token for a temporary AWS credential. This session token
must be generated using the AWS Security Token Service.
This flag argument must be specified if any of the other arguments
in this group are specified.
Specify whether to import from an AMI or disk image.
Exactly one of these must be specified:
If importing a disk image, specify the following:
--aws-source-ami-file-path=AWS_SOURCE_AMI_FILE_PATH
S3 resource path of the exported image file that you want to
import.
If importing an AMI, specify the following two flags:
--aws-ami-export-location=AWS_AMI_EXPORT_LOCATION
An AWS S3 bucket location where the converted image file can be
temporarily exported to before the import to Cloud Storage.
This flag argument must be specified if any of the other
arguments in this group are specified.
--aws-ami-id=AWS_AMI_ID
AWS AMI ID of the image to import.
This flag argument must be specified if any of the other
arguments in this group are specified.
Image import from local file, Cloud Storage or Compute Engine image.
At most one of these can be specified:
--source-file=SOURCE_FILE
A local file, or the Cloud Storage URI of the virtual disk file to
import. For example: gs://my-bucket/my-image.vmdk or
./my-local-image.vmdk. For more information about Cloud Storage
URIs, see
https://cloud.google.com/storage/docs/request-endpoints#json-api.
--source-image=SOURCE_IMAGE
An existing Compute Engine image from which to import.
OPTIONAL FLAGS
--no-address

13
gcloud/compute/instance-templates/create
View file

@ -21,8 +21,9 @@ SYNOPSIS
[--internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH]
[--ipv6-network-tier=IPV6_NETWORK_TIER]
[--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]]
[--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]]
[--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY]
[--local-ssd=[device-name=DEVICE-NAME],
[interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE]
[--maintenance-policy=MAINTENANCE_POLICY]
[--metadata=KEY=VALUE,[KEY=VALUE,...]]
[--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]]
[--min-cpu-platform=PLATFORM] [--min-node-cpu=MIN_NODE_CPU]
@ -404,7 +405,7 @@ FLAGS
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]
--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE],[size=SIZE]
Attaches a local SSD to the instances.
device-name
@ -418,6 +419,12 @@ FLAGS
supported by more guest operating systems. NVME might provide
higher performance.
size
Optional. The only valid value is 375GB. Specify the --local-ssd
flag multiple times if you need multiple 375GB local SSD
partitions. You can specify a maximum of 24 local SSDs for a
maximum of 9TB attached to an instance.
--machine-type=MACHINE_TYPE
Specifies the machine type used for the instances. To get a list of
available machine types, run 'gcloud compute machine-types list'. If

11
gcloud/compute/instances/bulk/create
View file

@ -19,7 +19,8 @@ SYNOPSIS
[--erase-windows-vss-signature]
[--instance-termination-action=INSTANCE_TERMINATION_ACTION]
[--labels=[KEY=VALUE,...]]
[--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]]
[--local-ssd=[device-name=DEVICE-NAME],
[interface=INTERFACE],[size=SIZE]]
[--location-policy=[ZONE=POLICY,...]] [--machine-type=MACHINE_TYPE]
[--metadata=KEY=VALUE,[KEY=VALUE,...]]
[--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]]
@ -413,7 +414,7 @@ OPTIONAL FLAGS
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]
--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE],[size=SIZE]
Attaches a local SSD to the instances.
device-name
@ -427,6 +428,12 @@ OPTIONAL FLAGS
supported by more guest operating systems. NVME might provide
higher performance.
size
Optional. The only valid value is 375GB. Specify the --local-ssd
flag multiple times if you need multiple 375GB local SSD
partitions. You can specify a maximum of 24 local SSDs for a
maximum of 9TB attached to an instance.
--location-policy=[ZONE=POLICY,...]
Policy for which zones to include or exclude during bulk instance
creation within a region. Policy is defined as a list of key-value

13
gcloud/compute/instances/create
View file

@ -25,8 +25,9 @@ SYNOPSIS
[--ipv6-network-tier=IPV6_NETWORK_TIER]
[--ipv6-public-ptr-domain=IPV6_PUBLIC_PTR_DOMAIN]
[--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]]
[--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]]
[--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY]
[--local-ssd=[device-name=DEVICE-NAME],
[interface=INTERFACE],[size=SIZE]] [--machine-type=MACHINE_TYPE]
[--maintenance-policy=MAINTENANCE_POLICY]
[--metadata=KEY=VALUE,[KEY=VALUE,...]]
[--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]]
[--min-cpu-platform=PLATFORM] [--min-node-cpu=MIN_NODE_CPU]
@ -477,7 +478,7 @@ FLAGS
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]
--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE],[size=SIZE]
Attaches a local SSD to the instances.
device-name
@ -491,6 +492,12 @@ FLAGS
supported by more guest operating systems. NVME might provide
higher performance.
size
Optional. The only valid value is 375GB. Specify the --local-ssd
flag multiple times if you need multiple 375GB local SSD
partitions. You can specify a maximum of 24 local SSDs for a
maximum of 9TB attached to an instance.
--machine-type=MACHINE_TYPE
Specifies the machine type used for the instances. To get a list of
available machine types, run 'gcloud compute machine-types list'. If

3
gcloud/compute/sole-tenancy/node-groups/help
View file

@ -43,6 +43,9 @@ COMMANDS
set-iam-policy
Set the IAM policy for a Compute Engine node group.
simulate-maintenance-event
Simulate maintenance of a Compute Engine node group.
update
Update a Compute Engine node group.

67
gcloud/compute/sole-tenancy/node-groups/simulate-maintenance-event Normal file
View file

@ -0,0 +1,67 @@
NAME
gcloud compute sole-tenancy node-groups simulate-maintenance-event -
simulate maintenance of a Compute Engine node group
SYNOPSIS
gcloud compute sole-tenancy node-groups simulate-maintenance-event NAME
[--async] [--nodes=[NODE,...]] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Simulate maintenance of a Compute Engine node group.
EXAMPLES
To simulate maintenance of a node group, run:
$ gcloud compute sole-tenancy node-groups \
simulate-maintenance-event my-node-group --nodes=example-nodes
POSITIONAL ARGUMENTS
NAME
Name of the node group to operate on.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--nodes=[NODE,...]
The names of the nodes to simulate maintenance event.
--zone=ZONE
Zone of the node group to operate on. If not specified and the
compute/zone property isn't set, you might be prompted to select a zone
(interactive mode only).
To avoid prompting when this flag is omitted, you can set the
compute/zone property:
$ gcloud config set compute/zone ZONE
A list of zones can be fetched by running:
$ gcloud compute zones list
To unset the property, run:
$ gcloud config unset compute/zone
Alternatively, the zone can be stored in the environment variable
CLOUDSDK_COMPUTE_ZONE.
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
These variants are also available:
$ gcloud alpha compute sole-tenancy node-groups \
simulate-maintenance-event
$ gcloud beta compute sole-tenancy node-groups \
simulate-maintenance-event