imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 23:08:48 +00:00
Code Activity

gcloud: Wed Dec 6 10:10:36 UTC 2023

Browse source
This commit is contained in:
Automated 2023-12-06 10:10:36 +00:00
parent d3074f94bb
commit f36750d203
469 changed files with 9617 additions and 1400 deletions
Download patch file Download diff file Expand all files Collapse all files

27
gcloud/container/aws/node-pools/create
View file

@ -10,7 +10,9 @@ SYNOPSIS
--max-pods-per-node=MAX_PODS_PER_NODE --node-version=NODE_VERSION
--subnet-id=SUBNET_ID (--max-nodes=MAX_NODES --min-nodes=MIN_NODES)
[--annotations=ANNOTATION,[ANNOTATION,...]] [--async]
[--enable-autorepair] [--node-labels=NODE_LABEL,[NODE_LABEL,...]]
[--enable-autorepair] [--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]
[--root-volume-kms-key-arn=ROOT_VOLUME_KMS_KEY_ARN]
@ -127,6 +129,29 @@ OPTIONAL FLAGS
Node autorepair is disabled by default.
--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 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 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.

29
gcloud/container/aws/node-pools/update
View file

@ -7,8 +7,9 @@ SYNOPSIS
(NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async]
[--config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN]
[--enable-autorepair] [--iam-instance-profile=IAM_INSTANCE_PROFILE]
[--instance-type=INSTANCE_TYPE] [--node-version=NODE_VERSION]
[--root-volume-iops=ROOT_VOLUME_IOPS]
[--instance-type=INSTANCE_TYPE] [--max-surge-update=MAX_SURGE_UPDATE]
[--max-unavailable-update=MAX_UNAVAILABLE_UPDATE]
[--node-version=NODE_VERSION] [--root-volume-iops=ROOT_VOLUME_IOPS]
[--root-volume-kms-key-arn=ROOT_VOLUME_KMS_KEY_ARN]
[--root-volume-size=ROOT_VOLUME_SIZE]
[--root-volume-throughput=ROOT_VOLUME_THROUGHPUT]
@ -96,6 +97,30 @@ FLAGS
--instance-type=INSTANCE_TYPE
AWS EC2 instance type for the node pool's nodes.
--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 container aws node-pools update --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 modify a node pool with 6 nodes such that, 3 nodes are updated in
parallel (1 + 2), but keep at least 4 nodes (6 - 2) available each time
this node pool is rolling updated, run:
$ gcloud container aws node-pools update --max-surge-update=1 \
--max-unavailable-update=2
--node-version=NODE_VERSION
Kubernetes version to use for the node pool.