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

gcloud: Wed Oct 25 11:42:23 UTC 2023

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

View file

@ -29,7 +29,9 @@ 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] [--validate-only]
[--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]
[--enable-advanced-networking --enable-dataplane-v2]
@ -333,6 +335,40 @@ OPTIONAL FLAGS
--enable-vm-tracking
If set, enable VM tracking.
Upgrade policy for the cluster.
--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.
Example:
To upgrade the control plane only and keep worker node pools version unchanged, first specify the policy:
$ gcloud container vmware clusters create CLUSTER \
--upgrade-policy control-plane-only=True
Then to start the upgrade operation using the specified policy, run:
$ gcloud container vmware clusters upgrade CLUSTER --version=VERSION
After upgrading only the cluster control plane, to upgrade an individual node pool, run:
$ gcloud 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 container vmware clusters create CLUSTER \
--upgrade-policy control-plane-only=False
Then to start the upgrade operation using the specified policy, run:
$ gcloud container vmware clusters upgrade CLUSTER --version=VERSION
--validate-only
If set, only validate the request, but do not actually perform the
operation.

View file

@ -9,7 +9,9 @@ SYNOPSIS
[avoid-buggy-ips=AVOID-BUGGY-IPS],
[manual-assign=MANUAL-ASSIGN],[pool=POOL]]
[--static-ip-config-ip-blocks=[gateway=GATEWAY],
[ips=IPS],[netmask=NETMASK]] [--validate-only] [--version=VERSION]
[ips=IPS],[netmask=NETMASK]]
[--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
@ -130,6 +132,40 @@ FLAGS
Use quote around the flag value to escape semicolon in the
terminal.
Upgrade policy for the cluster.
--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.
Example:
To upgrade the control plane only and keep worker node pools version unchanged, first specify the policy:
$ gcloud container vmware clusters update CLUSTER \
--upgrade-policy control-plane-only=True
Then to start the upgrade operation using the specified policy, run:
$ gcloud container vmware clusters upgrade CLUSTER --version=VERSION
After upgrading only the cluster control plane, to upgrade an individual node pool, run:
$ gcloud 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 container vmware clusters update CLUSTER \
--upgrade-policy control-plane-only=False
Then to start the upgrade operation using the specified policy, run:
$ gcloud container vmware clusters upgrade CLUSTER --version=VERSION
--validate-only
If set, only validate the request, but do not actually perform the
operation.