imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 14:56:05 +00:00
Code Activity

gcloud: Wed Jan 25 10:09:52 UTC 2023

Browse source
This commit is contained in:
Automated 2023-01-25 10:09:52 +00:00
parent 1248f773ec
commit 6dc17bdd4a
218 changed files with 6694 additions and 2033 deletions
Download patch file Download diff file Expand all files Collapse all files

134
gcloud/alpha/dataproc/clusters/create
View file

@ -5,7 +5,14 @@ SYNOPSIS
gcloud alpha dataproc clusters create (CLUSTER : --region=REGION)
--autoscaling-policy=AUTOSCALING_POLICY [--no-address] [--async]
[--bucket=BUCKET] [--dataproc-metastore=DATAPROC_METASTORE]
[--enable-component-gateway]
[--driver-pool-accelerator=[type=TYPE,[count=COUNT],...]]
[--driver-pool-boot-disk-size=DRIVER_POOL_BOOT_DISK_SIZE]
[--driver-pool-boot-disk-type=DRIVER_POOL_BOOT_DISK_TYPE]
[--driver-pool-id=DRIVER_POOL_ID]
[--driver-pool-local-ssd-interface=DRIVER_POOL_LOCAL_SSD_INTERFACE]
[--driver-pool-machine-type=DRIVER_POOL_MACHINE_TYPE]
[--driver-pool-min-cpu-platform=PLATFORM]
[--driver-pool-size=DRIVER_POOL_SIZE] [--enable-component-gateway]
[--initialization-action-timeout=TIMEOUT; default="10m"]
[--initialization-actions=CLOUD_STORAGE_URI,[...]]
[--labels=[KEY=VALUE,...]]
@ -16,6 +23,7 @@ SYNOPSIS
[--master-machine-type=MASTER_MACHINE_TYPE]
[--master-min-cpu-platform=PLATFORM] [--max-idle=MAX_IDLE]
[--node-group=NODE_GROUP]
[--num-driver-pool-local-ssds=NUM_DRIVER_POOL_LOCAL_SSDS]
[--num-master-local-ssds=NUM_MASTER_LOCAL_SSDS]
[--num-masters=NUM_MASTERS]
[--num-secondary-worker-local-ssds=NUM_SECONDARY_WORKER_LOCAL_SSDS]
@ -124,6 +132,55 @@ FLAGS
external metastore in the format:
"projects/{project-id}/locations/{region}/services/{service-name}".
--driver-pool-accelerator=[type=TYPE,[count=COUNT],...]
Attaches accelerators, such as GPUs, to the driver-pool instance(s).
type
The specific type of accelerator to attach to the instances, such
as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute
accelerator-types list to display available accelerator types.
count
The number of accelerators to attach to each instance. The default
value is 1.
--driver-pool-boot-disk-size=DRIVER_POOL_BOOT_DISK_SIZE
The size of the boot disk. The value must be a whole number followed by
a size unit of KB for kilobyte, MB for megabyte, GB for gigabyte, or TB
for terabyte. For example, 10GB will produce a 10 gigabyte disk. The
minimum size a boot disk can have is 10 GB. Disk size must be a
multiple of 1 GB.
--driver-pool-boot-disk-type=DRIVER_POOL_BOOT_DISK_TYPE
The type of the boot disk. The value must be pd-balanced, pd-ssd, or
pd-standard.
--driver-pool-id=DRIVER_POOL_ID
Custom identifier for the DRIVER Node Group being created. If not
provided, a random string is generated.
--driver-pool-local-ssd-interface=DRIVER_POOL_LOCAL_SSD_INTERFACE
Interface to use to attach local SSDs to cluster driver pool node(s).
--driver-pool-machine-type=DRIVER_POOL_MACHINE_TYPE
The type of machine to use for the cluster driver pool nodes. Defaults
to server-specified.
--driver-pool-min-cpu-platform=PLATFORM
When specified, the VM is scheduled on the host with a specified CPU
architecture or a more recent CPU platform that's available in that
zone. To list available CPU platforms in a zone, run:
$ gcloud compute zones describe ZONE
CPU platform selection may not be available in a zone. Zones that
support CPU platform selection provide an availableCpuPlatforms field,
which contains the list of available CPU platforms in the zone (see
Availability of CPU platforms for more information).
--driver-pool-size=DRIVER_POOL_SIZE
The size of the cluster driver pool.
--enable-component-gateway
Enable access to the web UIs of selected components on the cluster
through the component gateway.
@ -145,17 +202,16 @@ FLAGS
numbers.
--master-accelerator=[type=TYPE,[count=COUNT],...]
Attaches accelerators (e.g. GPUs) to the master instance(s).
Attaches accelerators, such as GPUs, to the master instance(s).
type
The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of
accelerator to attach to the instances. Use 'gcloud compute
accelerator-types list' to learn about all available accelerator
types.
The specific type of accelerator to attach to the instances, such
as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute
accelerator-types list to display available accelerator types.
count
The number of pieces of the accelerator to attach to each of the
instances. The default value is 1.
The number of accelerators to attach to each instance. The default
value is 1.
--master-boot-disk-size=MASTER_BOOT_DISK_SIZE
The size of the boot disk. The value must be a whole number followed by
@ -176,18 +232,16 @@ FLAGS
server-specified.
--master-min-cpu-platform=PLATFORM
When specified, the VM will be scheduled on host with specified CPU
architecture or a newer one. To list available CPU platforms in given
zone, run:
When specified, the VM is scheduled on the host with a specified CPU
architecture or a more recent CPU platform that's available in that
zone. To list available CPU platforms in a zone, run:
$ gcloud compute zones describe ZONE
CPU platform selection is available only in selected zones; zones that
allow CPU platform selection will have an availableCpuPlatforms field
that contains the list of available CPU platforms for that zone.
You can find more information online:
https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform
CPU platform selection may not be available in a zone. Zones that
support CPU platform selection provide an availableCpuPlatforms field,
which contains the list of available CPU platforms in the zone (see
Availability of CPU platforms for more information).
--max-idle=MAX_IDLE
The duration before cluster is auto-deleted after last job completes,
@ -199,6 +253,9 @@ FLAGS
a short name ("node-group-name") or in the format
"projects/{project-id}/zones/{zone}/nodeGroups/{node-group-name}".
--num-driver-pool-local-ssds=NUM_DRIVER_POOL_LOCAL_SSDS
The number of local SSDs to attach to each cluster driver pool node.
--num-master-local-ssds=NUM_MASTER_LOCAL_SSDS
The number of local SSDs to attach to the master in a cluster.
@ -264,17 +321,17 @@ FLAGS
for more information.
--secondary-worker-accelerator=[type=TYPE,[count=COUNT],...]
Attaches accelerators (e.g. GPUs) to the secondary-worker instance(s).
Attaches accelerators, such as GPUs, to the secondary-worker
instance(s).
type
The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of
accelerator to attach to the instances. Use 'gcloud compute
accelerator-types list' to learn about all available accelerator
types.
The specific type of accelerator to attach to the instances, such
as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute
accelerator-types list to display available accelerator types.
count
The number of pieces of the accelerator to attach to each of the
instances. The default value is 1.
The number of accelerators to attach to each instance. The default
value is 1.
--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE
The size of the boot disk. The value must be a whole number followed by
@ -312,17 +369,16 @@ FLAGS
cluster and jobs data, such as Spark and MapReduce history files.
--worker-accelerator=[type=TYPE,[count=COUNT],...]
Attaches accelerators (e.g. GPUs) to the worker instance(s).
Attaches accelerators, such as GPUs, to the worker instance(s).
type
The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of
accelerator to attach to the instances. Use 'gcloud compute
accelerator-types list' to learn about all available accelerator
types.
The specific type of accelerator to attach to the instances, such
as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute
accelerator-types list to display available accelerator types.
count
The number of pieces of the accelerator to attach to each of the
instances. The default value is 1.
The number of accelerators to attach to each instance. The default
value is 1.
--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE
The size of the boot disk. The value must be a whole number followed by
@ -342,18 +398,16 @@ FLAGS
The type of machine to use for workers. Defaults to server-specified.
--worker-min-cpu-platform=PLATFORM
When specified, the VM will be scheduled on host with specified CPU
architecture or a newer one. To list available CPU platforms in given
zone, run:
When specified, the VM is scheduled on the host with a specified CPU
architecture or a more recent CPU platform that's available in that
zone. To list available CPU platforms in a zone, run:
$ gcloud compute zones describe ZONE
CPU platform selection is available only in selected zones; zones that
allow CPU platform selection will have an availableCpuPlatforms field
that contains the list of available CPU platforms for that zone.
You can find more information online:
https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform
CPU platform selection may not be available in a zone. Zones that
support CPU platform selection provide an availableCpuPlatforms field,
which contains the list of available CPU platforms in the zone (see
Availability of CPU platforms for more information).
--zone=ZONE, -z ZONE
The compute zone (e.g. us-central1-a) for the cluster. If empty and

3
gcloud/alpha/dataproc/help
View file

@ -43,6 +43,9 @@ GROUPS
jobs
(ALPHA) Submit and manage Dataproc jobs.
node-groups
(ALPHA) Manage Dataproc node groups.
operations
(ALPHA) View and manage Dataproc operations.

71
gcloud/alpha/dataproc/node-groups/describe Normal file
View file

@ -0,0 +1,71 @@
NAME
gcloud alpha dataproc node-groups describe - describe the node group
SYNOPSIS
gcloud alpha dataproc node-groups describe
(NODE_GROUP : --cluster=CLUSTER --region=REGION) [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Describe the node group.
EXAMPLES
To describe a node group, run:
$ gcloud alpha dataproc node-groups describe my-node-group-id \
--region=us-central1 --cluster=my-cluster-name
POSITIONAL ARGUMENTS
Node group resource - ID of the node group to describe. The arguments in
this group can be used to specify the attributes of this resource. (NOTE)
Some attributes are not given arguments in this group but can be set in
other ways. To set the project attribute:
◆ provide the argument node_group on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
NODE_GROUP
ID of the node_group or fully qualified identifier for the
node_group. To set the node_group attribute:
▸ provide the argument node_group on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--cluster=CLUSTER
The Cluster name. To set the cluster attribute:
▸ provide the argument node_group on the command line with a fully
specified name;
▸ provide the argument --cluster on the command line.
--region=REGION
Dataproc region for the node_group. Each Dataproc region constitutes
an independent resource namespace constrained to deploying instances
into Compute Engine zones inside the region. Overrides the default
dataproc/region property value for this command invocation. To set
the region attribute:
▸ provide the argument node_group on the command line with a fully
specified name;
▸ provide the argument --region on the command line;
▸ set the property dataproc/region.
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
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct
project, you might be trying to access an API with an invitation-only early
access allowlist. These variants are also available:
$ gcloud dataproc node-groups describe
$ gcloud beta dataproc node-groups describe

45
gcloud/alpha/dataproc/node-groups/help Normal file
View file

@ -0,0 +1,45 @@
NAME
gcloud alpha dataproc node-groups - manage Dataproc node groups
SYNOPSIS
gcloud alpha dataproc node-groups COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Manage and modify Dataproc node groups created with a parent
cluster.
EXAMPLES
To describe a node group:
$ gcloud alpha dataproc node-groups describe NODE_GROUP_ID \
--cluster cluster_name --region region
To resize a node group:
$ gcloud alpha dataproc node-groups resize NODE_GROUP_ID \
--cluster cluster_name --region region --size new_size
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
describe
(ALPHA) Describe the node group.
resize
(ALPHA) Resize the number of nodes in the node group.
NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct
project, you might be trying to access an API with an invitation-only early
access allowlist. These variants are also available:
$ gcloud dataproc node-groups
$ gcloud beta dataproc node-groups

82
gcloud/alpha/dataproc/node-groups/resize Normal file
View file

@ -0,0 +1,82 @@
NAME
gcloud alpha dataproc node-groups resize - resize the number of nodes in
the node group
SYNOPSIS
gcloud alpha dataproc node-groups resize
(NODE_GROUP : --cluster=CLUSTER --region=REGION) --size=SIZE
[--graceful-decommission-timeout=GRACEFUL_DECOMMISSION_TIMEOUT]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Resize the number of nodes in the node group.
EXAMPLES
To resize a node group, run:
$ gcloud alpha dataproc node-groups resize my-node-group-id \
--region=us-central1 --cluster=my-cluster-name --size=5
POSITIONAL ARGUMENTS
Node group resource - ID of the node group to resize. The arguments in
this group can be used to specify the attributes of this resource. (NOTE)
Some attributes are not given arguments in this group but can be set in
other ways. To set the project attribute:
◆ provide the argument node_group on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
NODE_GROUP
ID of the node_group or fully qualified identifier for the
node_group. To set the node_group attribute:
▸ provide the argument node_group on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--cluster=CLUSTER
The Cluster name. To set the cluster attribute:
▸ provide the argument node_group on the command line with a fully
specified name;
▸ provide the argument --cluster on the command line.
--region=REGION
Dataproc region for the node_group. Each Dataproc region constitutes
an independent resource namespace constrained to deploying instances
into Compute Engine zones inside the region. Overrides the default
dataproc/region property value for this command invocation. To set
the region attribute:
▸ provide the argument node_group on the command line with a fully
specified name;
▸ provide the argument --region on the command line;
▸ set the property dataproc/region.
REQUIRED FLAGS
--size=SIZE
New size for a node group.
OPTIONAL FLAGS
--graceful-decommission-timeout=GRACEFUL_DECOMMISSION_TIMEOUT
Graceful decommission timeout for a node group scale-down resize.
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
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct
project, you might be trying to access an API with an invitation-only early
access allowlist. These variants are also available:
$ gcloud dataproc node-groups resize
$ gcloud beta dataproc node-groups resize

72
gcloud/alpha/dataproc/workflow-templates/set-managed-cluster
View file

@ -141,17 +141,16 @@ FLAGS
numbers.
--master-accelerator=[type=TYPE,[count=COUNT],...]
Attaches accelerators (e.g. GPUs) to the master instance(s).
Attaches accelerators, such as GPUs, to the master instance(s).
type
The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of
accelerator to attach to the instances. Use 'gcloud compute
accelerator-types list' to learn about all available accelerator
types.
The specific type of accelerator to attach to the instances, such
as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute
accelerator-types list to display available accelerator types.
count
The number of pieces of the accelerator to attach to each of the
instances. The default value is 1.
The number of accelerators to attach to each instance. The default
value is 1.
--master-boot-disk-size=MASTER_BOOT_DISK_SIZE
The size of the boot disk. The value must be a whole number followed by
@ -172,18 +171,16 @@ FLAGS
server-specified.
--master-min-cpu-platform=PLATFORM
When specified, the VM will be scheduled on host with specified CPU
architecture or a newer one. To list available CPU platforms in given
zone, run:
When specified, the VM is scheduled on the host with a specified CPU
architecture or a more recent CPU platform that's available in that
zone. To list available CPU platforms in a zone, run:
$ gcloud compute zones describe ZONE
CPU platform selection is available only in selected zones; zones that
allow CPU platform selection will have an availableCpuPlatforms field
that contains the list of available CPU platforms for that zone.
You can find more information online:
https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform
CPU platform selection may not be available in a zone. Zones that
support CPU platform selection provide an availableCpuPlatforms field,
which contains the list of available CPU platforms in the zone (see
Availability of CPU platforms for more information).
--node-group=NODE_GROUP
The name of the sole-tenant node group to create the cluster on. Can be
@ -255,17 +252,17 @@ FLAGS
for more information.
--secondary-worker-accelerator=[type=TYPE,[count=COUNT],...]
Attaches accelerators (e.g. GPUs) to the secondary-worker instance(s).
Attaches accelerators, such as GPUs, to the secondary-worker
instance(s).
type
The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of
accelerator to attach to the instances. Use 'gcloud compute
accelerator-types list' to learn about all available accelerator
types.
The specific type of accelerator to attach to the instances, such
as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute
accelerator-types list to display available accelerator types.
count
The number of pieces of the accelerator to attach to each of the
instances. The default value is 1.
The number of accelerators to attach to each instance. The default
value is 1.
--secondary-worker-boot-disk-size=SECONDARY_WORKER_BOOT_DISK_SIZE
The size of the boot disk. The value must be a whole number followed by
@ -303,17 +300,16 @@ FLAGS
cluster and jobs data, such as Spark and MapReduce history files.
--worker-accelerator=[type=TYPE,[count=COUNT],...]
Attaches accelerators (e.g. GPUs) to the worker instance(s).
Attaches accelerators, such as GPUs, to the worker instance(s).
type
The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of
accelerator to attach to the instances. Use 'gcloud compute
accelerator-types list' to learn about all available accelerator
types.
The specific type of accelerator to attach to the instances, such
as nvidia-tesla-k80 for NVIDIA Tesla K80. Use gcloud compute
accelerator-types list to display available accelerator types.
count
The number of pieces of the accelerator to attach to each of the
instances. The default value is 1.
The number of accelerators to attach to each instance. The default
value is 1.
--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE
The size of the boot disk. The value must be a whole number followed by
@ -333,18 +329,16 @@ FLAGS
The type of machine to use for workers. Defaults to server-specified.
--worker-min-cpu-platform=PLATFORM
When specified, the VM will be scheduled on host with specified CPU
architecture or a newer one. To list available CPU platforms in given
zone, run:
When specified, the VM is scheduled on the host with a specified CPU
architecture or a more recent CPU platform that's available in that
zone. To list available CPU platforms in a zone, run:
$ gcloud compute zones describe ZONE
CPU platform selection is available only in selected zones; zones that
allow CPU platform selection will have an availableCpuPlatforms field
that contains the list of available CPU platforms for that zone.
You can find more information online:
https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform
CPU platform selection may not be available in a zone. Zones that
support CPU platform selection provide an availableCpuPlatforms field,
which contains the list of available CPU platforms in the zone (see
Availability of CPU platforms for more information).
--zone=ZONE, -z ZONE
The compute zone (e.g. us-central1-a) for the cluster. If empty and