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

gcloud/alpha/container/aws/node-pools/create

@@ -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.
 

gcloud/alpha/container/aws/node-pools/update

@@ -7,6 +7,8 @@ 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] [--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]
@@ -92,6 +94,33 @@ FLAGS
      --iam-instance-profile=IAM_INSTANCE_PROFILE
         Name or ARN of the IAM instance profile associated with the node pool.
 
+     --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 alpha 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 alpha 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.
 

gcloud/alpha/container/binauthz/continuous-validation/enable

@@ -1,5 +1,5 @@
 NAME
-    gcloud alpha container binauthz continuous-validation enable - disable
+    gcloud alpha container binauthz continuous-validation enable - enable
         Binary Authorization Continuous Validation for the project
 
 SYNOPSIS

gcloud/alpha/container/binauthz/continuous-validation/help

@@ -26,7 +26,7 @@ COMMANDS
         project.
 
      enable
-        (ALPHA) Disable Binary Authorization Continuous Validation for the
+        (ALPHA) Enable Binary Authorization Continuous Validation for the
         project.
 
 NOTES