mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-14 17:05:28 +00:00
gcloud: Thu Sep 4 11:11:30 UTC 2025
This commit is contained in:
Automated
parent
c0b004f719
commit
be3f81b90a
355 changed files with 10181 additions and 607 deletions
|
|
@ -24,7 +24,13 @@ SYNOPSIS
|
|||
| --storage-pools=STORAGE_POOL,[...]
|
||||
| --system-config-from-file=PATH_TO_FILE | --tags=[TAG,...]
|
||||
| --windows-os-version=WINDOWS_OS_VERSION
|
||||
| --workload-metadata=WORKLOAD_METADATA
|
||||
| --workload-metadata=WORKLOAD_METADATA | --enable-blue-green-upgrade
|
||||
--enable-surge-upgrade --max-surge-upgrade=MAX_SURGE_UPGRADE
|
||||
--max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE
|
||||
--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,...]
|
||||
| --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS
|
||||
--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT
|
||||
--disk-size=DISK_SIZE
|
||||
|
|
@ -33,14 +39,7 @@ SYNOPSIS
|
|||
--location-policy=LOCATION_POLICY --max-nodes=MAX_NODES
|
||||
--min-nodes=MIN_NODES
|
||||
--total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES
|
||||
| --enable-autorepair --enable-autoupgrade
|
||||
| --enable-blue-green-upgrade --enable-surge-upgrade
|
||||
--max-surge-upgrade=MAX_SURGE_UPGRADE
|
||||
--max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE
|
||||
--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,...]) [--async]
|
||||
| --enable-autorepair --enable-autoupgrade) [--async]
|
||||
[--cluster=CLUSTER]
|
||||
[--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
|
@ -666,6 +665,70 @@ REQUIRED FLAGS
|
|||
This feature can only be enabled if Workload Identity is enabled
|
||||
at the cluster level.
|
||||
|
||||
Upgrade settings
|
||||
|
||||
--enable-blue-green-upgrade
|
||||
Changes node pool upgrade strategy to blue-green upgrade.
|
||||
|
||||
--enable-surge-upgrade
|
||||
Changes node pool upgrade strategy to surge upgrade.
|
||||
|
||||
--max-surge-upgrade=MAX_SURGE_UPGRADE
|
||||
Number of extra (surge) nodes to be created on each upgrade of the
|
||||
node pool.
|
||||
|
||||
Specifies the number of extra (surge) nodes to be created during
|
||||
this node pool's upgrades. For example, running the following
|
||||
command will result in creating an extra node each time the node
|
||||
pool is upgraded:
|
||||
|
||||
$ gcloud container node-pools update node-pool-1 \
|
||||
--cluster=example-cluster --max-surge-upgrade=1 \
|
||||
--max-unavailable-upgrade=0
|
||||
|
||||
Must be used in conjunction with '--max-unavailable-upgrade'.
|
||||
|
||||
--max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE
|
||||
Number of nodes that can be unavailable at the same time on each
|
||||
upgrade of the node pool.
|
||||
|
||||
Specifies the number of nodes that can be unavailable at the same
|
||||
time during this node pool's upgrades. For example, assume the node
|
||||
pool has 5 nodes, running the following command will result in
|
||||
having 3 nodes being upgraded in parallel (1 + 2), but keeping
|
||||
always at least 3 (5 - 2) available each time the node pool is
|
||||
upgraded:
|
||||
|
||||
$ gcloud container node-pools update node-pool-1 \
|
||||
--cluster=example-cluster --max-surge-upgrade=1 \
|
||||
--max-unavailable-upgrade=2
|
||||
|
||||
Must be used in conjunction with '--max-surge-upgrade'.
|
||||
|
||||
--node-pool-soak-duration=NODE_POOL_SOAK_DURATION
|
||||
Time in seconds to be spent waiting during blue-green upgrade
|
||||
before deleting the blue pool and completing the upgrade.
|
||||
|
||||
$ gcloud container node-pools update node-pool-1 \
|
||||
--cluster=example-cluster --node-pool-soak-duration=600s
|
||||
|
||||
--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,batch-percent=BATCH_NODE_PERCENTAGE,batch-soak-duration=BATCH_SOAK_DURATION,...]
|
||||
Standard rollout policy options for blue-green upgrade.
|
||||
|
||||
Batch sizes are specified by one of, batch-node-count or
|
||||
batch-percent. The duration between batches is specified by
|
||||
batch-soak-duration.
|
||||
|
||||
$ gcloud container node-pools update node-pool-1 \
|
||||
--cluster=example-cluster \
|
||||
--standard-rollout-policy=batch-node-count=3,\
|
||||
batch-soak-duration=60s
|
||||
|
||||
$ gcloud container node-pools update node-pool-1 \
|
||||
--cluster=example-cluster \
|
||||
--standard-rollout-policy=batch-percent=0.3,\
|
||||
batch-soak-duration=60s
|
||||
|
||||
Node config
|
||||
|
||||
--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS
|
||||
|
|
@ -781,70 +844,6 @@ REQUIRED FLAGS
|
|||
https://cloud.google.com/kubernetes-engine/docs/node-auto-upgrades
|
||||
for more info.
|
||||
|
||||
Upgrade settings
|
||||
|
||||
--enable-blue-green-upgrade
|
||||
Changes node pool upgrade strategy to blue-green upgrade.
|
||||
|
||||
--enable-surge-upgrade
|
||||
Changes node pool upgrade strategy to surge upgrade.
|
||||
|
||||
--max-surge-upgrade=MAX_SURGE_UPGRADE
|
||||
Number of extra (surge) nodes to be created on each upgrade of the
|
||||
node pool.
|
||||
|
||||
Specifies the number of extra (surge) nodes to be created during
|
||||
this node pool's upgrades. For example, running the following
|
||||
command will result in creating an extra node each time the node
|
||||
pool is upgraded:
|
||||
|
||||
$ gcloud container node-pools update node-pool-1 \
|
||||
--cluster=example-cluster --max-surge-upgrade=1 \
|
||||
--max-unavailable-upgrade=0
|
||||
|
||||
Must be used in conjunction with '--max-unavailable-upgrade'.
|
||||
|
||||
--max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE
|
||||
Number of nodes that can be unavailable at the same time on each
|
||||
upgrade of the node pool.
|
||||
|
||||
Specifies the number of nodes that can be unavailable at the same
|
||||
time during this node pool's upgrades. For example, assume the node
|
||||
pool has 5 nodes, running the following command will result in
|
||||
having 3 nodes being upgraded in parallel (1 + 2), but keeping
|
||||
always at least 3 (5 - 2) available each time the node pool is
|
||||
upgraded:
|
||||
|
||||
$ gcloud container node-pools update node-pool-1 \
|
||||
--cluster=example-cluster --max-surge-upgrade=1 \
|
||||
--max-unavailable-upgrade=2
|
||||
|
||||
Must be used in conjunction with '--max-surge-upgrade'.
|
||||
|
||||
--node-pool-soak-duration=NODE_POOL_SOAK_DURATION
|
||||
Time in seconds to be spent waiting during blue-green upgrade
|
||||
before deleting the blue pool and completing the upgrade.
|
||||
|
||||
$ gcloud container node-pools update node-pool-1 \
|
||||
--cluster=example-cluster --node-pool-soak-duration=600s
|
||||
|
||||
--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,batch-percent=BATCH_NODE_PERCENTAGE,batch-soak-duration=BATCH_SOAK_DURATION,...]
|
||||
Standard rollout policy options for blue-green upgrade.
|
||||
|
||||
Batch sizes are specified by one of, batch-node-count or
|
||||
batch-percent. The duration between batches is specified by
|
||||
batch-soak-duration.
|
||||
|
||||
$ gcloud container node-pools update node-pool-1 \
|
||||
--cluster=example-cluster \
|
||||
--standard-rollout-policy=batch-node-count=3,\
|
||||
batch-soak-duration=60s
|
||||
|
||||
$ gcloud container node-pools update node-pool-1 \
|
||||
--cluster=example-cluster \
|
||||
--standard-rollout-policy=batch-percent=0.3,\
|
||||
batch-soak-duration=60s
|
||||
|
||||
OPTIONAL FLAGS
|
||||
--async
|
||||
Return immediately, without waiting for the operation in progress to
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue