NodePoolArgs

Whether to enable automatic renewal for nodes in the node pool takes effect only when instance_charge_type is set to PrePaid. Default value: true. Valid values:

The automatic renewal period of nodes in the node pool takes effect only when you select Prepaid and Automatic Renewal, and is a required value. When PeriodUnit = Month, the value range is {1, 2, 3, 6, 12}. Default value: 1.

Whether enable worker node to support cis security reinforcement, its valid value true or false. Default to false and apply to AliyunLinux series. Use security_hardening_os instead.

The id of kubernetes cluster.

Specifies whether to automatically create pay-as-you-go instances to meet the required number of ECS instances if preemptible instances cannot be created due to reasons such as cost or insufficient inventory. This parameter takes effect when you set multi_az_policy to COST_OPTIMIZED. Valid values: true: automatically creates pay-as-you-go instances to meet the required number of ECS instances if preemptible instances cannot be created. false: does not create pay-as-you-go instances to meet the required number of ECS instances if preemptible instances cannot be created.

Node CPU management policies. Default value: none. When the cluster version is 1.12.6 or later, the following two policies are supported:

Configure the data disk of the node in the node pool. See data_disks below.

The deployment set of node pool. Specify the deploymentSet to ensure that the nodes in the node pool can be distributed on different physical machines.

Number of expected nodes in the node pool.

Whether to force deletion.

After you select this check box, if data disks have been attached to the specified ECS instances and the file system of the last data disk is uninitialized, the system automatically formats the last data disk to ext4 and mounts the data disk to /var/lib/docker and /var/lib/kubelet. The original data on the disk will be cleared. Make sure that you back up data in advance. If no data disk is mounted on the ECS instance, no new data disk will be purchased. Default is false.

The custom image ID. The system-provided image is used by default.

The operating system image type and the platform parameter can be selected from the following values:

Whether to install cloud monitoring on the ECS node. After installation, you can view the monitoring information of the created ECS instance in the cloud monitoring console and recommend enable it. Default value: false. Valid values:

Node payment type. Valid values: PostPaid, PrePaid, default is PostPaid. If value is PrePaid, the arguments period, period_unit, auto_renew and auto_renew_period are required.

The instance list. Add existing nodes under the same cluster VPC to the node pool.

In the node instance specification list, you can select multiple instance specifications as alternatives. When each node is created, it will try to purchase from the first specification until it is created successfully. The final purchased instance specifications may vary with inventory changes.

The billing method for network usage. Valid values PayByBandwidth and PayByTraffic. Conflict with eip_internet_charge_type, EIP and public network IP can only choose one. .

The maximum bandwidth of the public IP address of the node. The unit is Mbps(Mega bit per second). The value range is:\[1,100\].

Add an existing instance to the node pool, whether to keep the original instance name. It is recommended to set to true.

The name of the key pair. When the node pool is a managed node pool, only key_name is supported.

An KMS encrypts password used to a cs kubernetes. You have to specify one of password key_name kms_encrypted_password fields.

An KMS encryption context used to decrypt kms_encrypted_password before creating or updating a cs kubernetes with kms_encrypted_password. See Encryption Context. It is valid when kms_encrypted_password is set.

Kubelet configuration parameters for worker nodes. See kubelet_configuration below. More information in Kubelet Configuration. See kubelet_configuration below.

A List of Kubernetes labels to assign to the nodes . Only labels that are applied with the ACK API are managed by this argument. Detailed below. More information in Labels. See labels below.

Whether the ECS instance is logged on as a ecs-user user. Valid value: true and false.

Managed node pool configuration. See management below.

The scaling policy for ECS instances in a multi-zone scaling group. Valid value: PRIORITY, COST_OPTIMIZED and BALANCE. PRIORITY: scales the capacity according to the virtual switches you define (VSwitchIds.N). When an ECS instance cannot be created in the zone where the higher-priority vSwitch is located, the next-priority vSwitch is automatically used to create an ECS instance. COST_OPTIMIZED: try to create by vCPU unit price from low to high. When the scaling configuration is configured with multiple instances of preemptible billing, preemptible instances are created first. You can continue to use the CompensateWithOnDemand parameter to specify whether to automatically try to create a preemptible instance by paying for it. It takes effect only when the scaling configuration has multi-instance specifications or preemptible instances. BALANCE: distributes ECS instances evenly among the multi-zone specified by the scaling group. If the zones become unbalanced due to insufficient inventory, you can use the API RebalanceInstances to balance resources.

. Field 'name' has been deprecated from provider version 1.219.0. New field 'node_pool_name' instead.

The worker node number of the node pool. From version 1.111.0, node_count is not required.

Each node name consists of a prefix, its private network IP, and a suffix, separated by commas. The input format is customized,,ip,.

The name of node pool.

The minimum number of pay-as-you-go instances that must be kept in the scaling group. Valid values: 0 to 1000. If the number of pay-as-you-go instances is less than the value of this parameter, Auto Scaling preferably creates pay-as-you-go instances.

The percentage of pay-as-you-go instances among the extra instances that exceed the number specified by on_demand_base_capacity. Valid values: 0 to 100.

The password of ssh login. You have to specify one of password and key_name fields. The password rule is 8 to 30 characters and contains at least three items (upper and lower case letters, numbers, and special symbols).

Node payment period. Its valid value is one of {1, 2, 3, 6, 12}.

Node payment period unit, valid value: Month. Default is Month.

Operating system release, using image_type instead.

Private node pool configuration. See private_pool_options below.

The list of RDS instances.

The ID of the resource group.

Rotary configuration. See rolling_policy below.

The runtime name of containers. If not set, the cluster runtime will be used as the node pool runtime. If you select another container runtime, see Comparison of Docker, containerd, and Sandboxed-Container.

The runtime version of containers. If not set, the cluster runtime will be used as the node pool runtime.

Automatic scaling configuration. See scaling_config below.

Scaling group mode, default value: release. Valid values:

The security group ID of the node pool. This field has been replaced by security_group_ids, please use the security_group_ids field instead.

Multiple security groups can be configured for a node pool. If both security_group_ids and security_group_id are configured, security_group_ids takes effect. This field cannot be modified.

Alibaba Cloud OS security reinforcement. Default value: false. Value:

Whether enable worker node to support soc security reinforcement, its valid value true or false. Default to false and apply to AliyunLinux series. See SOC Reinforcement.

The number of instance types that are available. Auto Scaling creates preemptible instances of multiple instance types that are available at the lowest cost. Valid values: 1 to 10.

Specifies whether to supplement preemptible instances when the number of preemptible instances drops below the specified minimum number. If you set the value to true, Auto Scaling attempts to create a new preemptible instance when the system notifies that an existing preemptible instance is about to be reclaimed. Valid values: true: enables the supplementation of preemptible instances. false: disables the supplementation of preemptible instances.

The current single preemptible instance type market price range configuration. See spot_price_limit below.

The preemptible instance type. Value:

Specifies whether to enable the burst feature for system disks. Valid values:true: enables the burst feature. false: disables the burst feature. This parameter is supported only when system_disk_category is set to cloud_auto.

The multi-disk categories of the system disk. When a high-priority disk type cannot be used, Auto Scaling automatically tries to create a system disk with the next priority disk category. Valid values: cloud: cloud disk. cloud_efficiency: a high-efficiency cloud disk. cloud_ssd:SSD cloud disk. cloud_essd: ESSD cloud disk.

The system disk category of worker node. Its valid value are cloud_ssd, cloud_efficiency, cloud_essd and cloud_auto. .

The encryption algorithm used by the system disk. Value range: aes-256.

Whether to encrypt the system disk. Value range: true: encryption. false: Do not encrypt.

The ID of the KMS key used by the system disk.

The system disk performance of the node takes effect only for the ESSD disk.

The predefined IOPS of a system disk. Valid values: 0 to min{50,000, 1,000 × Capacity - Baseline IOPS}. Baseline IOPS = min{1,800 + 50 × Capacity, 50,000}. This parameter is supported only when system_disk_category is set to cloud_auto.

The system disk category of worker node. Its valid value range 40~500 in GB. Default to 120.

The ID of the automatic snapshot policy used by the system disk.

Add tags only for ECS instances. The maximum length of the tag key is 128 characters. The tag key and value cannot start with aliyun or acs:, or contain https:// or http://".

A List of Kubernetes taints to assign to the nodes. Detailed below. More information in Taints and Toleration. See taints below.

The configuration about confidential computing for the cluster. See tee_config below.

Whether the node after expansion can be scheduled.

Synchronously update node labels and taints.

Node custom data.

The vswitches used by node pool workers.