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 Oct 25 11:42:23 UTC 2023

Browse source
This commit is contained in:
Automated 2023-10-25 11:42:23 +00:00
parent a15665661a
commit d34c41a2ce
305 changed files with 5549 additions and 699 deletions
Download patch file Download diff file Expand all files Collapse all files

14
gcloud/alpha/container/clusters/create
View file

@ -423,10 +423,10 @@ FLAGS
Size for node VM boot disks in GB. Defaults to 100GB.
--disk-type=DISK_TYPE
Type of the node VM boot disk. For version 1.24.0+, defaults to
pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE
must be one of: pd-standard, pd-ssd, pd-balanced, hyperdisk-balanced,
hyperdisk-extreme, hyperdisk-throughput.
Type of the node VM boot disk. For version 1.24 and later, defaults to
pd-balanced. For versions earlier than 1.24, defaults to pd-standard.
DISK_TYPE must be one of: pd-standard, pd-ssd, pd-balanced,
hyperdisk-balanced, hyperdisk-extreme, hyperdisk-throughput.
--enable-autorepair
Enable node autorepair feature for a cluster's default node pool(s).
@ -772,9 +772,9 @@ FLAGS
$ gcloud compute machine-types list
You can also specify custom machine types with the string
"custom-CPUS-RAM" where "CPUS" is the number of virtual CPUs and "RAM"
is the amount of RAM in MiB.
You can also specify custom machine types by providing a string with
the format "custom-CPUS-RAM" where "CPUS" is the number of virtual CPUs
and "RAM" is the amount of RAM in MiB.
For example, to create a node pool using custom machines with 2 vCPUs
and 12 GB of RAM:

5
gcloud/alpha/container/fleet/mesh/disable
View file

@ -12,6 +12,11 @@ EXAMPLES
$ gcloud alpha container fleet mesh disable
To delete the fleet-level default Membership configuration, run:
$ gcloud alpha container fleet mesh disable \
--fleet-default-member-config
FLAGS
--force
Disable this feature, even if it is currently in use. Force disablement

6
gcloud/alpha/container/fleet/mesh/enable
View file

@ -12,6 +12,12 @@ EXAMPLES
$ gcloud alpha container fleet mesh enable
To enable the Service Mesh Feature with a fleet-level default Membership
configuration, run:
$ gcloud alpha container fleet mesh enable \
--fleet-default-member-config=/path/to/service-mesh.yaml
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

85
gcloud/alpha/container/fleet/mesh/update
View file

@ -4,9 +4,9 @@ NAME
SYNOPSIS
gcloud alpha container fleet mesh update
(--control-plane=CONTROL_PLANE --management=MANAGEMENT)
[--membership=MEMBERSHIP
| [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]]
([(--control-plane=CONTROL_PLANE --management=MANAGEMENT)
: --membership=MEMBERSHIP
| [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]])
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -21,58 +21,59 @@ EXAMPLES
--control-plane=CONTROL_PLANE
REQUIRED FLAGS
At least one of these must be specified:
Exactly one of these must be specified:
--control-plane=CONTROL_PLANE
(DEPRECATED) The control plane management to update to.
At least one of these must be specified:
The --control-plane flag is now deprecated. Please use --management
instead. See
https://cloud.google.com/service-mesh/docs/managed/provision-managed-anthos-service-mesh.
CONTROL_PLANE must be one of: automatic, manual.
--control-plane=CONTROL_PLANE
(DEPRECATED) Control plane management to update to.
--management=MANAGEMENT
The management mode to update to. MANAGEMENT must be one of:
automatic, manual.
The --control-plane flag is now deprecated. Please use --management
instead. See
https://cloud.google.com/service-mesh/docs/managed/provision-managed-anthos-service-mesh.
CONTROL_PLANE must be one of: automatic, manual.
OPTIONAL FLAGS
At most one of these can be specified:
--management=MANAGEMENT
The management mode to update to. MANAGEMENT must be one of:
automatic, manual.
--membership=MEMBERSHIP
(DEPRECATED) Membership name to update.
At most one of these can be specified:
The --membership flag is now deprecated. Please use --memberships
instead.
--membership=MEMBERSHIP
(DEPRECATED) Membership name to update.
Membership resource - The group of arguments defining one or more
memberships. 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.
The --membership flag is now deprecated. Please use --memberships
instead.
To set the project attribute:
▸ provide the argument --memberships on the command line with a fully
specified name;
▸ provide the argument --project on the command line;
▸ set the property core/project.
Membership resource - The group of arguments defining one or more
memberships. 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.
--memberships=[MEMBERSHIPS,...]
IDs of the memberships or fully qualified identifiers for the
memberships.
To set the project attribute:
▫ provide the argument --memberships on the command line with a
fully specified name;
▫ provide the argument --project on the command line;
▫ set the property core/project.
To set the memberships attribute:
▫ provide the argument --memberships on the command line.
--memberships=[MEMBERSHIPS,...]
IDs of the memberships or fully qualified identifiers for the
memberships.
This flag argument must be specified if any of the other arguments
in this group are specified.
To set the memberships attribute:
◇ provide the argument --memberships on the command line.
--location=LOCATION
Location for the memberships.
This flag argument must be specified if any of the other
arguments in this group are specified.
To set the location attribute:
▫ provide the argument --memberships on the command line with a
fully specified name;
▫ provide the argument --location on the command line;
▫ set the property gkehub/location.
--location=LOCATION
Location for the memberships.
To set the location attribute:
◇ provide the argument --memberships on the command line with a
fully specified name;
◇ provide the argument --location on the command line;
◇ set the property gkehub/location.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

5
gcloud/alpha/container/hub/mesh/disable
View file

@ -12,6 +12,11 @@ EXAMPLES
$ gcloud alpha container hub mesh disable
To delete the fleet-level default Membership configuration, run:
$ gcloud alpha container hub mesh disable \
--fleet-default-member-config
FLAGS
--force
Disable this feature, even if it is currently in use. Force disablement

6
gcloud/alpha/container/hub/mesh/enable
View file

@ -12,6 +12,12 @@ EXAMPLES
$ gcloud alpha container hub mesh enable
To enable the Service Mesh Feature with a fleet-level default Membership
configuration, run:
$ gcloud alpha container hub mesh enable \
--fleet-default-member-config=/path/to/service-mesh.yaml
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

85
gcloud/alpha/container/hub/mesh/update
View file

@ -4,9 +4,9 @@ NAME
SYNOPSIS
gcloud alpha container hub mesh update
(--control-plane=CONTROL_PLANE --management=MANAGEMENT)
[--membership=MEMBERSHIP
| [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]]
([(--control-plane=CONTROL_PLANE --management=MANAGEMENT)
: --membership=MEMBERSHIP
| [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]])
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -21,58 +21,59 @@ EXAMPLES
--control-plane=CONTROL_PLANE
REQUIRED FLAGS
At least one of these must be specified:
Exactly one of these must be specified:
--control-plane=CONTROL_PLANE
(DEPRECATED) The control plane management to update to.
At least one of these must be specified:
The --control-plane flag is now deprecated. Please use --management
instead. See
https://cloud.google.com/service-mesh/docs/managed/provision-managed-anthos-service-mesh.
CONTROL_PLANE must be one of: automatic, manual.
--control-plane=CONTROL_PLANE
(DEPRECATED) Control plane management to update to.
--management=MANAGEMENT
The management mode to update to. MANAGEMENT must be one of:
automatic, manual.
The --control-plane flag is now deprecated. Please use --management
instead. See
https://cloud.google.com/service-mesh/docs/managed/provision-managed-anthos-service-mesh.
CONTROL_PLANE must be one of: automatic, manual.
OPTIONAL FLAGS
At most one of these can be specified:
--management=MANAGEMENT
The management mode to update to. MANAGEMENT must be one of:
automatic, manual.
--membership=MEMBERSHIP
(DEPRECATED) Membership name to update.
At most one of these can be specified:
The --membership flag is now deprecated. Please use --memberships
instead.
--membership=MEMBERSHIP
(DEPRECATED) Membership name to update.
Membership resource - The group of arguments defining one or more
memberships. 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.
The --membership flag is now deprecated. Please use --memberships
instead.
To set the project attribute:
▸ provide the argument --memberships on the command line with a fully
specified name;
▸ provide the argument --project on the command line;
▸ set the property core/project.
Membership resource - The group of arguments defining one or more
memberships. 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.
--memberships=[MEMBERSHIPS,...]
IDs of the memberships or fully qualified identifiers for the
memberships.
To set the project attribute:
▫ provide the argument --memberships on the command line with a
fully specified name;
▫ provide the argument --project on the command line;
▫ set the property core/project.
To set the memberships attribute:
▫ provide the argument --memberships on the command line.
--memberships=[MEMBERSHIPS,...]
IDs of the memberships or fully qualified identifiers for the
memberships.
This flag argument must be specified if any of the other arguments
in this group are specified.
To set the memberships attribute:
◇ provide the argument --memberships on the command line.
--location=LOCATION
Location for the memberships.
This flag argument must be specified if any of the other
arguments in this group are specified.
To set the location attribute:
▫ provide the argument --memberships on the command line with a
fully specified name;
▫ provide the argument --location on the command line;
▫ set the property gkehub/location.
--location=LOCATION
Location for the memberships.
To set the location attribute:
◇ provide the argument --memberships on the command line with a
fully specified name;
◇ provide the argument --location on the command line;
◇ set the property gkehub/location.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

14
gcloud/alpha/container/node-pools/create
View file

@ -192,10 +192,10 @@ FLAGS
Size for node VM boot disks in GB. Defaults to 100GB.
--disk-type=DISK_TYPE
Type of the node VM boot disk. For version 1.24.0+, defaults to
pd-balanced. Before version 1.24.0, defaults to pd-standard. DISK_TYPE
must be one of: pd-standard, pd-ssd, pd-balanced, hyperdisk-balanced,
hyperdisk-extreme, hyperdisk-throughput.
Type of the node VM boot disk. For version 1.24 and later, defaults to
pd-balanced. For versions earlier than 1.24, defaults to pd-standard.
DISK_TYPE must be one of: pd-standard, pd-ssd, pd-balanced,
hyperdisk-balanced, hyperdisk-extreme, hyperdisk-throughput.
--enable-autoprovisioning
Enables Cluster Autoscaler to treat the node pool as if it was
@ -313,9 +313,9 @@ FLAGS
$ gcloud compute machine-types list
You can also specify custom machine types with the string
"custom-CPUS-RAM" where "CPUS" is the number of virtual CPUs and "RAM"
is the amount of RAM in MiB.
You can also specify custom machine types by providing a string with
the format "custom-CPUS-RAM" where "CPUS" is the number of virtual CPUs
and "RAM" is the amount of RAM in MiB.
For example, to create a node pool using custom machines with 2 vCPUs
and 12 GB of RAM:

32
gcloud/alpha/container/node-pools/update
View file

@ -19,7 +19,8 @@ SYNOPSIS
--node-pool-soak-duration=NODE_POOL_SOAK_DURATION
--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,
batch-percent=BATCH_NODE_PERCENTAGE,
batch-soak-duration=BATCH_SOAK_DURATION,...]
batch-soak-duration=BATCH_SOAK_DURATION,...] | --disk-size=DISK_SIZE
--disk-type=DISK_TYPE --machine-type=MACHINE_TYPE
| --enable-autoprovisioning --enable-autoscaling
--location-policy=LOCATION_POLICY --max-nodes=MAX_NODES
--min-nodes=MIN_NODES
@ -354,6 +355,35 @@ REQUIRED FLAGS
--standard-rollout-policy=batch-percent=0.3,\
batch-soak-duration=60s
Node config
--disk-size=DISK_SIZE
Size for node VM boot disks in GB. Defaults to 100GB.
--disk-type=DISK_TYPE
Type of the node VM boot disk. For version 1.24 and later, defaults
to pd-balanced. For versions earlier than 1.24, defaults to
pd-standard. DISK_TYPE must be one of: pd-standard, pd-ssd,
pd-balanced, hyperdisk-balanced, hyperdisk-extreme,
hyperdisk-throughput.
--machine-type=MACHINE_TYPE
The type of machine to use for nodes. Defaults to e2-medium. The
list of predefined machine types is available using the following
command:
$ gcloud compute machine-types list
You can also specify custom machine types by providing a string
with the format "custom-CPUS-RAM" where "CPUS" is the number of
virtual CPUs and "RAM" is the amount of RAM in MiB.
For example, to create a node pool using custom machines with 2
vCPUs and 12 GB of RAM:
$ gcloud alpha container node-pools update high-mem-pool \
--machine-type=custom-2-12288
Cluster autoscaling
--enable-autoprovisioning

41
gcloud/alpha/container/vmware/clusters/create
View file

@ -29,7 +29,8 @@ SYNOPSIS
[ips=IPS],[netmask=NETMASK]) [--admin-users=ADMIN_USERS]
[--annotations=[KEY=VALUE,...]] [--async] [--description=DESCRIPTION]
[--disable-aag-config] [--disable-vsphere-csi] [--enable-auto-repair]
[--enable-vm-tracking] [--upgrade-control-plane=UPGRADE_CONTROL_PLANE]
[--enable-vm-tracking]
[--upgrade-policy=[control-plane-only=CONTROL-PLANE-ONLY]]
[--validate-only]
[--cpus=CPUS --enable-auto-resize --memory=MEMORY --replicas=REPLICAS]
[--disable-control-plane-v2 | --enable-control-plane-v2]
@ -336,21 +337,39 @@ OPTIONAL FLAGS
Upgrade policy for the cluster.
--upgrade-control-plane=UPGRADE_CONTROL_PLANE
If not specified, node pools are upgraded together with the control
plane.
--upgrade-policy=[control-plane-only=CONTROL-PLANE-ONLY]
If not specified, control-plane-only is set to False. In the next
upgrade operation, all worker node pools will be upgraded together
with the control plane.
Examples:
Example:
To upgrade control plane only and keep node pools version unchanged,
To upgrade the control plane only and keep worker node pools version unchanged, first specify the policy:
$ gcloud alpha container vmware clusters create \
--upgrade-control-plane=True
$ gcloud alpha container vmware clusters create CLUSTER \
--upgrade-policy control-plane-only=True
To upgrade both control plane and node pools,
Then to start the upgrade operation using the specified policy, run:
$ gcloud alpha container vmware clusters create \
--upgrade-control-plane=False
$ gcloud alpha container vmware clusters upgrade CLUSTER \
--version=VERSION
After upgrading only the cluster control plane, to upgrade an individual node pool, run:
$ gcloud alpha container vmware node-pools update NODE_POOL \
--version=VERSION
Example:
Alternatively, to upgrade both the control plane and all worker node pools, first specify the policy:
$ gcloud alpha container vmware clusters create CLUSTER \
--upgrade-policy control-plane-only=False
Then to start the upgrade operation using the specified policy, run:
$ gcloud alpha container vmware clusters upgrade CLUSTER \
--version=VERSION
--validate-only
If set, only validate the request, but do not actually perform the

42
gcloud/alpha/container/vmware/clusters/update
View file

@ -11,8 +11,8 @@ SYNOPSIS
[manual-assign=MANUAL-ASSIGN],[pool=POOL]]
[--static-ip-config-ip-blocks=[gateway=GATEWAY],
[ips=IPS],[netmask=NETMASK]]
[--upgrade-control-plane=UPGRADE_CONTROL_PLANE] [--validate-only]
[--version=VERSION]
[--upgrade-policy=[control-plane-only=CONTROL-PLANE-ONLY]]
[--validate-only] [--version=VERSION]
[--add-annotations=[KEY1=VALUE1,KEY2=VALUE2,...]
| --remove-annotations=[KEY1,KEY2,...]]
[--cpus=CPUS --memory=MEMORY --disable-auto-resize
@ -135,21 +135,39 @@ FLAGS
Upgrade policy for the cluster.
--upgrade-control-plane=UPGRADE_CONTROL_PLANE
If not specified, node pools are upgraded together with the control
plane.
--upgrade-policy=[control-plane-only=CONTROL-PLANE-ONLY]
If not specified, control-plane-only is set to False. In the next
upgrade operation, all worker node pools will be upgraded together
with the control plane.
Examples:
Example:
To upgrade control plane only and keep node pools version unchanged,
To upgrade the control plane only and keep worker node pools version unchanged, first specify the policy:
$ gcloud alpha container vmware clusters update \
--upgrade-control-plane=True
$ gcloud alpha container vmware clusters update CLUSTER \
--upgrade-policy control-plane-only=True
To upgrade both control plane and node pools,
Then to start the upgrade operation using the specified policy, run:
$ gcloud alpha container vmware clusters update \
--upgrade-control-plane=False
$ gcloud alpha container vmware clusters upgrade CLUSTER \
--version=VERSION
After upgrading only the cluster control plane, to upgrade an individual node pool, run:
$ gcloud alpha container vmware node-pools update NODE_POOL \
--version=VERSION
Example:
Alternatively, to upgrade both the control plane and all worker node pools, first specify the policy:
$ gcloud alpha container vmware clusters update CLUSTER \
--upgrade-policy control-plane-only=False
Then to start the upgrade operation using the specified policy, run:
$ gcloud alpha container vmware clusters upgrade CLUSTER \
--version=VERSION
--validate-only
If set, only validate the request, but do not actually perform the