gcloud container aws node-pools create

NAME
gcloud container aws node-pools create - create a node pool in an Anthos cluster on AWS
SYNOPSIS
gcloud container aws node-pools create(NODE_POOL :--cluster=CLUSTER--location=LOCATION)--config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN--iam-instance-profile=IAM_INSTANCE_PROFILE--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][--kubelet-config-cpu-cfs-quota=KUBELET_CONFIG_CPU_CFS_QUOTA][--kubelet-config-cpu-cfs-quota-period=KUBELET_CONFIG_CPU_CFS_QUOTA_PERIOD][--kubelet-config-cpu-manager-policy=KUBELET_CONFIG_CPU_MANAGER_POLICY][--kubelet-config-pod-pids-limit=KUBELET_CONFIG_POD_PIDS_LIMIT][--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][--root-volume-size=ROOT_VOLUME_SIZE][--root-volume-throughput=ROOT_VOLUME_THROUGHPUT][--root-volume-type=ROOT_VOLUME_TYPE][--security-group-ids=[SECURITY_GROUP_ID,…]][--ssh-ec2-key-pair=SSH_EC2_KEY_PAIR][--tags=TAG,[TAG,…]][--validate-only][--autoscaling-metrics-granularity=AUTOSCALING_METRICS_GRANULARITY :--autoscaling-metrics=[AUTOSCALING_METRIC,…]][--instance-type=INSTANCE_TYPE    |--spot-instance-types=[INSTANCE_TYPE,…]][--proxy-secret-arn=PROXY_SECRET_ARN--proxy-secret-version-id=PROXY_SECRET_VERSION_ID][GCLOUD_WIDE_FLAG]
DESCRIPTION
(DEPRECATED) Create a node pool in an Anthos cluster on AWS.

This command is deprecated. Seehttps://cloud.google.com/kubernetes-engine/multi-cloud/docs/aws/deprecations/deprecation-announcementfor more details.

EXAMPLES
To create a node pool namedmy-node-pool ina cluster namedmy-cluster managed inlocationus-west1, run:
gcloudcontainerawsnode-poolscreatemy-node-pool--cluster=my-cluster--location=us-west1--iam-instance-profile=IAM_INSTANCE_PROFILE--node-version=NODE_VERSION--subnet-id=SUBNET_ID
POSITIONAL ARGUMENTS
Node pool resource - node pool to create. The arguments in this group can beused to specify the attributes of this resource. (NOTE) Some attributes are notgiven arguments in this group but can be set in other ways.

To set theproject attribute:

  • provide the argumentnode_pool on the command line with a fullyspecified name;
  • provide the argument--project on the command line;
  • set the propertycore/project.

This must be specified.

NODE_POOL
ID of the node_pool or fully qualified identifier for the node_pool.

To set thenode_pool attribute:

  • provide the argumentnode_pool on the command line.

This positional argument must be specified if any of the other arguments in thisgroup are specified.

--cluster=CLUSTER
cluster of the node_pool.

To set thecluster attribute:

  • provide the argumentnode_pool on the command line with a fullyspecified name;
  • provide the argument--cluster on the command line.
--location=LOCATION
Google Cloud location for the node_pool.

To set thelocation attribute:

  • provide the argumentnode_pool on the command line with a fullyspecified name;
  • provide the argument--location on the command line;
  • set the propertycontainer_aws/location.
REQUIRED FLAGS
--config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN
Amazon Resource Name (ARN) of the AWS KMS key to encrypt the user data.
--iam-instance-profile=IAM_INSTANCE_PROFILE
Name or ARN of the IAM instance profile associated with the node pool.
--max-pods-per-node=MAX_PODS_PER_NODE
Maximum number of pods per node.
--node-version=NODE_VERSION
Kubernetes version to use for the node pool.
--subnet-id=SUBNET_ID
Subnet ID of an existing VNET to use for the node pool.
Node pool autoscaling

This must be specified.

--max-nodes=MAX_NODES
Maximum number of nodes in the node pool.

This flag argument must be specified if any of the other arguments in this groupare specified.

--min-nodes=MIN_NODES
Minimum number of nodes in the node pool.

This flag argument must be specified if any of the other arguments in this groupare specified.

OPTIONAL FLAGS
--annotations=ANNOTATION,[ANNOTATION,…]
Annotations for the node pool.
--async
Return immediately, without waiting for the operation in progress to complete.
--enable-autorepair
Enable node autorepair feature for a node pool. Use --no-enable-autorepair todisable.
gcloudcontainerawsnode-poolscreate--enable-autorepair

Node autorepair is disabled by default.

--kubelet-config-cpu-cfs-quota=KUBELET_CONFIG_CPU_CFS_QUOTA
Enforce a Kubelet CPU CFS quota.
--kubelet-config-cpu-cfs-quota-period=KUBELET_CONFIG_CPU_CFS_QUOTA_PERIOD
Kubelet CPU CFS quota period, within the range "1ms" to "1s".
--kubelet-config-cpu-manager-policy=KUBELET_CONFIG_CPU_MANAGER_POLICY
Kubelet CPU manager policy.KUBELET_CONFIG_CPU_MANAGER_POLICY must be one of:none,static.
--kubelet-config-pod-pids-limit=KUBELET_CONFIG_POD_PIDS_LIMIT
Kubelet maximum number of PIDS in any pod, within the range 1024 to 4194304.
--max-surge-update=MAX_SURGE_UPDATE
Maximum number of extra (surge) nodes to be created beyond the current size ofthe 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:

gcloudcontainerawsnode-poolscreate--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 nodepool's update process. Use --max-surge-update as well, if needed, to control theoverall 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:

gcloudcontainerawsnode-poolscreate--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.
--node-taints=NODE_TAINT,[NODE_TAINT,…]
Taints assigned to nodes of the node pool. Node taint is of formatkey=value:effect. Effect must be one of: NoExecute, NoSchedule,PreferNoSchedule.
--root-volume-iops=ROOT_VOLUME_IOPS
Number of I/O operations per second (IOPS) to provision for the root volume.
--root-volume-kms-key-arn=ROOT_VOLUME_KMS_KEY_ARN
Amazon Resource Name (ARN) of the AWS KMS key to encrypt the root volume.
--root-volume-size=ROOT_VOLUME_SIZE
Size of the root volume. The value must be a whole number followed by a sizeunit ofGB for gigabyte, orTB for terabyte. If nosize unit is specified, GB is assumed.
--root-volume-throughput=ROOT_VOLUME_THROUGHPUT
Throughput to provision for the root volume, in MiB/s. Only valid if the volumetype is GP3. If volume type is GP3 and throughput is not provided, it defaultsto 125.
--root-volume-type=ROOT_VOLUME_TYPE
Type of the root volume.ROOT_VOLUME_TYPE must be oneof:gp2,gp3.
--security-group-ids=[SECURITY_GROUP_ID,…]
IDs of additional security groups to add to the node pool's nodes.
--ssh-ec2-key-pair=SSH_EC2_KEY_PAIR
Name of the EC2 key pair authorized to login to the node pool's nodes.
--tags=TAG,[TAG,…]
Applies the given tags (comma separated) on the node pool. Example:
gcloudcontainerawsnode-poolscreateEXAMPLE_NODE_POOL--tags=tag1=one,tag2=two
--validate-only
Validate the node pool to create, but don't actually perform it.
Node pool autoscaling metrics collection
--autoscaling-metrics-granularity=AUTOSCALING_METRICS_GRANULARITY
Frequency at which EC2 Auto Scaling sends aggregated data to AWS CloudWatch. Theonly valid value is "1Minute".

This flag argument must be specified if any of the other arguments in this groupare specified.

--autoscaling-metrics=[AUTOSCALING_METRIC,…]
Autoscaling metrics to enable. For a list of valid metrics, refer tohttps://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_EnableMetricsCollection.html.If granularity is specified but not any metrics, all metrics are enabled.
Node pool instance configuration

At most one of these can be specified:

--instance-type=INSTANCE_TYPE
AWS EC2 instance type for the node pool's nodes.
--spot-instance-types=[INSTANCE_TYPE,…]
List of AWS EC2 instance types for creating a spot node pool's nodes. Thespecified instance types must have the same CPU architecture, the same number ofCPUs and memory. You can use the Amazon EC2 Instance Selector tool(https://github.com/aws/amazon-ec2-instance-selector) to choose instance typeswith matching CPU and memory configurations.
Proxy config
--proxy-secret-arn=PROXY_SECRET_ARN
ARN of the AWS Secrets Manager secret that contains a proxy configuration.

This flag argument must be specified if any of the other arguments in this groupare specified.

--proxy-secret-version-id=PROXY_SECRET_VERSION_ID
Version ID string of the AWS Secrets Manager secret that contains a proxyconfiguration.

This flag argument must be specified if any of the other arguments in this groupare specified.

GCLOUD WIDE FLAGS
These flags are available to all commands:--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.

Run$gcloud help for details.

NOTES
This variant is also available:
gcloudalphacontainerawsnode-poolscreate

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-01-21 UTC.