imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-15 17:35:31 +00:00
Code Activity

gcloud: Wed Sep 13 10:32:10 UTC 2023

Browse source
This commit is contained in:
Automated 2023-09-13 10:32:10 +00:00
parent 6c8d2eb024
commit 39a8a4f491
111 changed files with 1798 additions and 302 deletions
Download patch file Download diff file Expand all files Collapse all files

25
gcloud/alpha/container/aws/node-pools/create
View file

@ -12,6 +12,8 @@ SYNOPSIS
[--annotations=ANNOTATION,[ANNOTATION,...]] [--async]
[--enable-autorepair] [--image-type=IMAGE_TYPE]
[--instance-placement=INSTANCE_PLACEMENT]
[--max-surge-update=MAX_SURGE_UPDATE]
[--max-unavailable-update=MAX_UNAVAILABLE_UPDATE]
[--node-labels=NODE_LABEL,[NODE_LABEL,...]]
[--node-taints=NODE_TAINT,[NODE_TAINT,...]]
[--root-volume-iops=ROOT_VOLUME_IOPS]
@ -141,6 +143,29 @@ OPTIONAL FLAGS
Type of the tenancy. INSTANCE_PLACEMENT must be one of: dedicated,
default, host.
--max-surge-update=MAX_SURGE_UPDATE
Maximum number of extra (surge) nodes to be created beyond the current
size of the node pool during its update process. Use
--max-unavailable-update as well, if needed, to control the overall
surge settings.
To create an extra node each time the node pool is rolling updated,
run:
$ gcloud alpha container aws node-pools create \
--max-surge-update=1 --max-unavailable-update=0
--max-unavailable-update=MAX_UNAVAILABLE_UPDATE
Maximum number of nodes that can be simultaneously unavailable during
this node pool's update process. Use --max-surge-update as well, if
needed, to control the overall surge settings.
To update 3 nodes in parallel (1 + 2), but keep at least 4 nodes (6 -
2) available each time the node pool is rolling updated, run:
$ gcloud alpha container aws node-pools create --min-nodes=6 \
--max-surge-update=1 --max-unavailable-update=2
--node-labels=NODE_LABEL,[NODE_LABEL,...]
Labels assigned to the node pool's nodes.