@alicloud/cs20151215 7.2.4 → 7.2.6

package/dist/client.js

@@ -41,6 +41,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 Object.defineProperty(exports, "__esModule", { value: true });
 // This file is auto-generated, don't edit it
 const $dara = __importStar(require("@darabonba/typescript"));
+const gateway_pop_1 = __importDefault(require("@alicloud/gateway-pop"));
 const openapi_core_1 = __importDefault(require("@alicloud/openapi-core"));
 const openapi_core_2 = require("@alicloud/openapi-core");
 const $_model = __importStar(require("./models/model"));
@@ -48,6 +49,9 @@ __exportStar(require("./models/model"), exports);
 class Client extends openapi_core_1.default {
     constructor(config) {
         super(config);
+        this._productId = "CS";
+        let gatewayClient = new gateway_pop_1.default();
+        this._spi = gatewayClient;
         this._endpointRule = "regional";
         this._endpointMap = {
             'ap-northeast-2-pop': "cs.aliyuncs.com",
@@ -178,7 +182,7 @@ class Client extends openapi_core_1.default {
         return await this.attachInstancesWithOptions(ClusterId, request, headers, runtime);
     }
     /**
-     * Adds existing ECS instances to a node pool as worker nodes in an ACK cluster, or re-adds removed worker nodes to a node pool.
+     * Adds existing ECS instances to an ACK cluster as worker nodes, or re-adds removed node instances to a node pool. You can invoke AttachInstancesToNodePool to add existing nodes to a node pool.
      *
      * @param request - AttachInstancesToNodePoolRequest
      * @param headers - map
@@ -218,7 +222,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.AttachInstancesToNodePoolResponse({}));
     }
     /**
-     * Adds existing ECS instances to a node pool as worker nodes in an ACK cluster, or re-adds removed worker nodes to a node pool.
+     * Adds existing ECS instances to an ACK cluster as worker nodes, or re-adds removed node instances to a node pool. You can invoke AttachInstancesToNodePool to add existing nodes to a node pool.
      *
      * @param request - AttachInstancesToNodePoolRequest
      * @returns AttachInstancesToNodePoolResponse
@@ -446,12 +450,12 @@ class Client extends openapi_core_1.default {
         return await this.checkServiceRoleWithOptions(request, headers, runtime);
     }
     /**
-     * Clears the issued KubeConfig credentials and Role-Based Access Control (RBAC) permissions of a specified user in a specified cluster. You can call this operation to clean up and revoke authorization for KubeConfig files that pose security risks.
+     * Clears the issued KubeConfig credentials and revokes the RBAC authorization of a specified user in a specified cluster. You can invoke CleanClusterUserPermissions to clean up and revoke authorization for KubeConfigs that pose a security risk.
      *
      * @remarks
-     * > 1. You must have the permissions to manage Container Service for Kubernetes (CS). The required policy is AliyunCSFullAccess.
-     * > 2. You cannot clear the permissions of an Alibaba Cloud account.
-     * > 3. You cannot clear the permissions of the user who performs this operation.
+     * > 1. You must have the permissions to manage Container Service for Kubernetes (CS) (AliyunCSFullAccess).
+     * > 2. This operation does not support clearing the permissions of an Alibaba Cloud account.
+     * > 3. This operation does not support clearing the permissions of the current user.
      *
      * @param request - CleanClusterUserPermissionsRequest
      * @param headers - map
@@ -482,12 +486,12 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CleanClusterUserPermissionsResponse({}));
     }
     /**
-     * Clears the issued KubeConfig credentials and Role-Based Access Control (RBAC) permissions of a specified user in a specified cluster. You can call this operation to clean up and revoke authorization for KubeConfig files that pose security risks.
+     * Clears the issued KubeConfig credentials and revokes the RBAC authorization of a specified user in a specified cluster. You can invoke CleanClusterUserPermissions to clean up and revoke authorization for KubeConfigs that pose a security risk.
      *
      * @remarks
-     * > 1. You must have the permissions to manage Container Service for Kubernetes (CS). The required policy is AliyunCSFullAccess.
-     * > 2. You cannot clear the permissions of an Alibaba Cloud account.
-     * > 3. You cannot clear the permissions of the user who performs this operation.
+     * > 1. You must have the permissions to manage Container Service for Kubernetes (CS) (AliyunCSFullAccess).
+     * > 2. This operation does not support clearing the permissions of an Alibaba Cloud account.
+     * > 3. This operation does not support clearing the permissions of the current user.
      *
      * @param request - CleanClusterUserPermissionsRequest
      * @returns CleanClusterUserPermissionsResponse
@@ -498,12 +502,12 @@ class Client extends openapi_core_1.default {
         return await this.cleanClusterUserPermissionsWithOptions(ClusterId, Uid, request, headers, runtime);
     }
     /**
-     * Cleans up and revokes the KubeConfig credentials and RBAC permissions issued to a specified user, such as resigned employees or users with frozen accounts.
+     * Clears the issued KubeConfig credentials and RBAC permissions of a specified user to revoke authorizations for risky users, such as resigned employees or users with frozen accounts.
      *
      * @remarks
-     * >- Requires the permissions to manage Container Service for Kubernetes (CS) (AliyunCSFullAccess).
-     * >- Clearing the permissions of Alibaba Cloud accounts is not supported.
-     * >- Clearing the permissions of the calling user is not supported.
+     * >- You must have the permissions to manage Container Service for Kubernetes (CS) (AliyunCSFullAccess).
+     * >- You cannot clear the permissions of an Alibaba Cloud account.
+     * >- You cannot clear your own permissions.
      *
      * @param tmpReq - CleanUserPermissionsRequest
      * @param headers - map
@@ -542,12 +546,12 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CleanUserPermissionsResponse({}));
     }
     /**
-     * Cleans up and revokes the KubeConfig credentials and RBAC permissions issued to a specified user, such as resigned employees or users with frozen accounts.
+     * Clears the issued KubeConfig credentials and RBAC permissions of a specified user to revoke authorizations for risky users, such as resigned employees or users with frozen accounts.
      *
      * @remarks
-     * >- Requires the permissions to manage Container Service for Kubernetes (CS) (AliyunCSFullAccess).
-     * >- Clearing the permissions of Alibaba Cloud accounts is not supported.
-     * >- Clearing the permissions of the calling user is not supported.
+     * >- You must have the permissions to manage Container Service for Kubernetes (CS) (AliyunCSFullAccess).
+     * >- You cannot clear the permissions of an Alibaba Cloud account.
+     * >- You cannot clear your own permissions.
      *
      * @param request - CleanUserPermissionsRequest
      * @returns CleanUserPermissionsResponse
@@ -702,16 +706,16 @@ class Client extends openapi_core_1.default {
         return await this.createAutoscalingConfigWithOptions(ClusterId, request, headers, runtime);
     }
     /**
-     * Creates an ACK cluster, including ACK managed clusters, ACK Serverless clusters, ACK Edge clusters, and registered clusters. When you create a cluster, you configure cluster information, cluster components, and ACK-related cloud resources.
+     * Creates an ACK cluster, including ACK managed clusters, ACK Serverless clusters, ACK Edge clusters, and registered clusters. When creating a cluster, you configure cluster information, cluster components, and ACK-related cloud resources.
      *
      * @remarks
      * ### Generate OpenAPI request parameters by using the console
-     * When you call the CreateCluster operation to create a cluster, if the API call fails due to incorrect combinations of request parameters, you can use the console to generate the required request parameter combinations. Perform the following steps:
-     * 1. Log on to the [Container Service for Kubernetes (ACK) console](https://csnew.console.aliyun.com) and choose **Clusters** in the left-side navigation pane.
-     * 1. On the **Clusters** page, click **Cluster Template**.
-     * 1. In the dialog box, select the cluster type that you want to create, click Create, and then configure the cluster information on the cluster configuration page.
-     * 1. After the configuration is complete, on the **Confirm Configuration** page, click **Equivalent Code** in the upper-right corner. The dialog box displays the parameter combinations required for creating the cluster. You can copy and use them.
-     * >Notice: Starting from July 04, 2026, some request parameters will no longer take effect. For details about the changes and replacement parameter descriptions, see [Notice on changes to OpenAPI request and response parameters for ACK cluster management and OpenAPI offline](https://help.aliyun.com/document_detail/2932733.html).</notice>
+     * When you call the CreateCluster API operation to create a cluster, if the API call fails due to an incorrect combination of request parameters, you can generate the required combination of request parameters for cluster creation by using the console. Proceed as follows:
+     * 1. Log on to the [Container Service console](https://csnew.console.aliyun.com). In the left-side navigation pane, click **Clusters**.
+     * 1. On the **Clusters** page, click **Cluster Templates**.
+     * 1. In the dialog box, select the type of cluster that you want to create, click Create, and then configure the cluster information on the cluster configuration page.
+     * 1. After the configuration is complete, on the **Confirm** page, click **Equivalent Code** in the upper-right corner. The dialog box displays the combination of parameters required for cluster creation. You can copy and use the parameters.
+     * >Notice: Starting July 4, 2026, some request parameters will no longer take effect. For details about the changes and replacement parameters, see [Announcement on changes to input and output parameters of ACK cluster management-related OpenAPIs and OpenAPI deprecation](https://help.aliyun.com/document_detail/2932733.html).</notice>
      *
      * @param request - CreateClusterRequest
      * @param headers - map
@@ -967,6 +971,9 @@ class Client extends openapi_core_1.default {
         if (!$dara.isNull(request.sshFlags)) {
             body["ssh_flags"] = request.sshFlags;
         }
+        if (!$dara.isNull(request.supportPolicy)) {
+            body["support_policy"] = request.supportPolicy;
+        }
         if (!$dara.isNull(request.tags)) {
             body["tags"] = request.tags;
         }
@@ -1051,16 +1058,16 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateClusterResponse({}));
     }
     /**
-     * Creates an ACK cluster, including ACK managed clusters, ACK Serverless clusters, ACK Edge clusters, and registered clusters. When you create a cluster, you configure cluster information, cluster components, and ACK-related cloud resources.
+     * Creates an ACK cluster, including ACK managed clusters, ACK Serverless clusters, ACK Edge clusters, and registered clusters. When creating a cluster, you configure cluster information, cluster components, and ACK-related cloud resources.
      *
      * @remarks
      * ### Generate OpenAPI request parameters by using the console
-     * When you call the CreateCluster operation to create a cluster, if the API call fails due to incorrect combinations of request parameters, you can use the console to generate the required request parameter combinations. Perform the following steps:
-     * 1. Log on to the [Container Service for Kubernetes (ACK) console](https://csnew.console.aliyun.com) and choose **Clusters** in the left-side navigation pane.
-     * 1. On the **Clusters** page, click **Cluster Template**.
-     * 1. In the dialog box, select the cluster type that you want to create, click Create, and then configure the cluster information on the cluster configuration page.
-     * 1. After the configuration is complete, on the **Confirm Configuration** page, click **Equivalent Code** in the upper-right corner. The dialog box displays the parameter combinations required for creating the cluster. You can copy and use them.
-     * >Notice: Starting from July 04, 2026, some request parameters will no longer take effect. For details about the changes and replacement parameter descriptions, see [Notice on changes to OpenAPI request and response parameters for ACK cluster management and OpenAPI offline](https://help.aliyun.com/document_detail/2932733.html).</notice>
+     * When you call the CreateCluster API operation to create a cluster, if the API call fails due to an incorrect combination of request parameters, you can generate the required combination of request parameters for cluster creation by using the console. Proceed as follows:
+     * 1. Log on to the [Container Service console](https://csnew.console.aliyun.com). In the left-side navigation pane, click **Clusters**.
+     * 1. On the **Clusters** page, click **Cluster Templates**.
+     * 1. In the dialog box, select the type of cluster that you want to create, click Create, and then configure the cluster information on the cluster configuration page.
+     * 1. After the configuration is complete, on the **Confirm** page, click **Equivalent Code** in the upper-right corner. The dialog box displays the combination of parameters required for cluster creation. You can copy and use the parameters.
+     * >Notice: Starting July 4, 2026, some request parameters will no longer take effect. For details about the changes and replacement parameters, see [Announcement on changes to input and output parameters of ACK cluster management-related OpenAPIs and OpenAPI deprecation](https://help.aliyun.com/document_detail/2932733.html).</notice>
      *
      * @param request - CreateClusterRequest
      * @returns CreateClusterResponse
@@ -1164,7 +1171,7 @@ class Client extends openapi_core_1.default {
         return await this.createClusterInspectConfigWithOptions(clusterId, request, headers, runtime);
     }
     /**
-     * Creates a node pool. A node pool is a logical collection of nodes with the same property, which allows unified management and O&M of nodes, such as node upgrades and elastic scaling. You can further use the automated O&M features of node pools, such as automatic repair of OS CVE vulnerabilities, automatic recovery of faulty nodes, and automatic upgrades of kubelet and containerd versions, to reduce O&M costs. You can invoke CreateClusterNodePool to create a node pool for a cluster.
+     * A node pool is a logical collection of nodes with the same properties, which allows unified management and O&M of nodes, such as node upgrades and elastic scaling. You can further use the automated O&M features of node pools, such as automatic repair of OS CVE vulnerabilities, automatic recovery of faulty nodes, and automatic upgrades of kubelet and containerd versions, to reduce O&M costs. You can call CreateClusterNodePool to create a node pool for a cluster.
      *
      * @param request - CreateClusterNodePoolRequest
      * @param headers - map
@@ -1240,7 +1247,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateClusterNodePoolResponse({}));
     }
     /**
-     * Creates a node pool. A node pool is a logical collection of nodes with the same property, which allows unified management and O&M of nodes, such as node upgrades and elastic scaling. You can further use the automated O&M features of node pools, such as automatic repair of OS CVE vulnerabilities, automatic recovery of faulty nodes, and automatic upgrades of kubelet and containerd versions, to reduce O&M costs. You can invoke CreateClusterNodePool to create a node pool for a cluster.
+     * A node pool is a logical collection of nodes with the same properties, which allows unified management and O&M of nodes, such as node upgrades and elastic scaling. You can further use the automated O&M features of node pools, such as automatic repair of OS CVE vulnerabilities, automatic recovery of faulty nodes, and automatic upgrades of kubelet and containerd versions, to reduce O&M costs. You can call CreateClusterNodePool to create a node pool for a cluster.
      *
      * @param request - CreateClusterNodePoolRequest
      * @returns CreateClusterNodePoolResponse
@@ -1707,7 +1714,7 @@ class Client extends openapi_core_1.default {
         return await this.deleteClusterInspectConfigWithOptions(clusterId, headers, runtime);
     }
     /**
-     * Deletes a node pool that is no longer in use. When a node pool is deleted, all pods on its nodes are deleted, which may trigger rescheduling. If rescheduling fails, your services may be affected. Ensure that the cluster has sufficient resources for rescheduling.
+     * Deletes a node pool that is no longer in use. When a node pool is deleted, all pods on its nodes are deleted, which may trigger descheduling. If the pods cannot be rescheduled, your services may be affected. Ensure that the cluster has sufficient resources for descheduling.
      *
      * @param request - DeleteClusterNodepoolRequest
      * @param headers - map
@@ -1738,7 +1745,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteClusterNodepoolResponse({}));
     }
     /**
-     * Deletes a node pool that is no longer in use. When a node pool is deleted, all pods on its nodes are deleted, which may trigger rescheduling. If rescheduling fails, your services may be affected. Ensure that the cluster has sufficient resources for rescheduling.
+     * Deletes a node pool that is no longer in use. When a node pool is deleted, all pods on its nodes are deleted, which may trigger descheduling. If the pods cannot be rescheduled, your services may be affected. Ensure that the cluster has sufficient resources for descheduling.
      *
      * @param request - DeleteClusterNodepoolRequest
      * @returns DeleteClusterNodepoolResponse
@@ -1749,14 +1756,14 @@ class Client extends openapi_core_1.default {
         return await this.deleteClusterNodepoolWithOptions(ClusterId, NodepoolId, request, headers, runtime);
     }
     /**
-     * Removes nodes from a cluster. When you remove nodes, you can specify whether to release the associated ECS instances and whether to automatically drain the nodes.
+     * Removes nodes from a cluster. When removing nodes, you can specify whether to release the associated ECS instances and whether to automatically drain the nodes.
      *
      * @remarks
-     * - When removing nodes, perform standard operations by calling this API operation or using the [Container Service console](https://cs.console.aliyun.com). Do not manually remove nodes by running the `kubectl delete node` command.
-     * - Do not manually release nodes or remove instances in the ECS or Auto Scaling (ESS) console or by calling related API operations, or passively release nodes when a subscription instance expires. In these cases, the nodes are directly shut down and automatically removed from the Container Service console.
-     * - If the expected number of nodes is configured for a node pool, the node pool automatically scales out other instances based on the corresponding configurations to maintain the expected number of nodes.
-     * - Removing nodes involves pod migration and may affect your services. Perform this operation during off-peak hours. Unexpected risks may occur during the operation. Back up your data in advance.
-     * - When you remove nodes, ACK executes drain operations. Make sure that other nodes in the cluster have sufficient resources to avoid application pod scheduling failures.
+     * - When removing nodes, perform standard operations by using this API operation or the [Container Service console](https://cs.console.aliyun.com). Do not manually remove nodes by running the `kubectl delete node` command.
+     * - Do not manually release nodes or remove instances in the ECS or Auto Scaling (ESS) console (or by calling related API operations), or passively release nodes when a subscription instance expires. In these cases, the nodes are directly stopped and automatically removed from the Container Service console.
+     * - If the expected number of nodes is configured for a node pool, the node pool automatically scales out other instances based on the configuration to maintain the expected number of nodes.
+     * - Removing nodes involves pod migration, which may affect your services. Perform this operation during off-peak hours. Unexpected risks may occur during the operation. Back up your data in advance.
+     * - When removing nodes, ACK executes a drain operation. Ensure that other nodes in the cluster have sufficient resources to avoid application pod scheduling failures.
      * - Check the node affinity rules and scheduling policies of the pods on the nodes to be removed to ensure that the pods can be scheduled to other nodes after the nodes are removed.
      *
      * @param request - DeleteClusterNodesRequest
@@ -1770,6 +1777,9 @@ class Client extends openapi_core_1.default {
         if (!$dara.isNull(request.drainNode)) {
             body["drain_node"] = request.drainNode;
         }
+        if (!$dara.isNull(request.drainTimeoutSeconds)) {
+            body["drain_timeout_seconds"] = request.drainTimeoutSeconds;
+        }
         if (!$dara.isNull(request.nodes)) {
             body["nodes"] = request.nodes;
         }
@@ -1794,14 +1804,14 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteClusterNodesResponse({}));
     }
     /**
-     * Removes nodes from a cluster. When you remove nodes, you can specify whether to release the associated ECS instances and whether to automatically drain the nodes.
+     * Removes nodes from a cluster. When removing nodes, you can specify whether to release the associated ECS instances and whether to automatically drain the nodes.
      *
      * @remarks
-     * - When removing nodes, perform standard operations by calling this API operation or using the [Container Service console](https://cs.console.aliyun.com). Do not manually remove nodes by running the `kubectl delete node` command.
-     * - Do not manually release nodes or remove instances in the ECS or Auto Scaling (ESS) console or by calling related API operations, or passively release nodes when a subscription instance expires. In these cases, the nodes are directly shut down and automatically removed from the Container Service console.
-     * - If the expected number of nodes is configured for a node pool, the node pool automatically scales out other instances based on the corresponding configurations to maintain the expected number of nodes.
-     * - Removing nodes involves pod migration and may affect your services. Perform this operation during off-peak hours. Unexpected risks may occur during the operation. Back up your data in advance.
-     * - When you remove nodes, ACK executes drain operations. Make sure that other nodes in the cluster have sufficient resources to avoid application pod scheduling failures.
+     * - When removing nodes, perform standard operations by using this API operation or the [Container Service console](https://cs.console.aliyun.com). Do not manually remove nodes by running the `kubectl delete node` command.
+     * - Do not manually release nodes or remove instances in the ECS or Auto Scaling (ESS) console (or by calling related API operations), or passively release nodes when a subscription instance expires. In these cases, the nodes are directly stopped and automatically removed from the Container Service console.
+     * - If the expected number of nodes is configured for a node pool, the node pool automatically scales out other instances based on the configuration to maintain the expected number of nodes.
+     * - Removing nodes involves pod migration, which may affect your services. Perform this operation during off-peak hours. Unexpected risks may occur during the operation. Back up your data in advance.
+     * - When removing nodes, ACK executes a drain operation. Ensure that other nodes in the cluster have sufficient resources to avoid application pod scheduling failures.
      * - Check the node affinity rules and scheduling policies of the pods on the nodes to be removed to ensure that the pods can be scheduled to other nodes after the nodes are removed.
      *
      * @param request - DeleteClusterNodesRequest
@@ -2437,7 +2447,7 @@ class Client extends openapi_core_1.default {
         return await this.describeClusterAddonsVersionWithOptions(ClusterId, headers, runtime);
     }
     /**
-     * Retrieves the script used to add existing ECS instances to an ACK cluster as worker nodes, or to re-add removed worker nodes to a node pool. ACK supports manually adding existing nodes to a node pool. You can invoke the DescribeClusterAttachScripts operation to obtain the script for adding existing nodes.
+     * Queries the script for adding existing nodes to a cluster node pool. Container Service for Kubernetes (ACK) supports manually adding existing nodes to a node pool if you need to add existing ECS instances to an ACK cluster as worker nodes or re-add node instances to a node pool after removing worker nodes. You can invoke the DescribeClusterAttachScripts operation to obtain the script for adding existing nodes.
      *
      * @param request - DescribeClusterAttachScriptsRequest
      * @param headers - map
@@ -2489,7 +2499,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeClusterAttachScriptsResponse({}));
     }
     /**
-     * Retrieves the script used to add existing ECS instances to an ACK cluster as worker nodes, or to re-add removed worker nodes to a node pool. ACK supports manually adding existing nodes to a node pool. You can invoke the DescribeClusterAttachScripts operation to obtain the script for adding existing nodes.
+     * Queries the script for adding existing nodes to a cluster node pool. Container Service for Kubernetes (ACK) supports manually adding existing nodes to a node pool if you need to add existing ECS instances to an ACK cluster as worker nodes or re-add node instances to a node pool after removing worker nodes. You can invoke the DescribeClusterAttachScripts operation to obtain the script for adding existing nodes.
      *
      * @param request - DescribeClusterAttachScriptsRequest
      * @returns DescribeClusterAttachScriptsResponse
@@ -2657,10 +2667,10 @@ class Client extends openapi_core_1.default {
      *
      * @remarks
      * - When you remove a node, perform standard operations by using this API operation or the [Container Service console](https://cs.console.aliyun.com). Do not manually remove nodes by running the `kubectl delete node` command.
-     * - Do not release nodes or remove instances in the ECS or Auto Scaling console, or by calling related API operations, or passively release nodes when a subscription instance expires. In these cases, the nodes are directly shut down and automatically removed from the Container Service console.
-     * - If the expected number of nodes is configured for a node pool, the node pool automatically scales out other instances based on the corresponding configurations to maintain the expected number of nodes.
-     * - Removing a node involves pod migration, which may affect your services. Perform this operation during off-peak hours. Unexpected risks may occur during the operation. Back up your data in advance.
-     * - When a node is removed, ACK drains the node. Make sure that other nodes in the cluster have sufficient resources to prevent application pods from failing to be scheduled.
+     * - Do not proactively release nodes or remove instances in the ECS or Auto Scaling (ESS) console or by calling related API operations, or passively release nodes when a subscription instance expires. In these cases, the nodes are directly shut down and automatically removed from the Container Service console.
+     * - If the expected number of nodes is configured for a node pool, the node pool automatically scales out other instances based on the configurations to maintain the expected number of nodes.
+     * - Removing a node involves pod migration and may affect your services. Perform this operation during off-peak hours. Unexpected risks may occur during the operation. Back up your data in advance.
+     * - When a node is removed, ACK performs a drain operation. Make sure that other nodes in the cluster have sufficient resources to prevent application pods from failing to be scheduled.
      * - Check the node affinity rules and scheduling policies of the pods on the node to be removed. Make sure that the pods can be scheduled to other nodes after the node is removed.
      *
      * @param request - DescribeClusterNodePoolsRequest
@@ -2696,10 +2706,10 @@ class Client extends openapi_core_1.default {
      *
      * @remarks
      * - When you remove a node, perform standard operations by using this API operation or the [Container Service console](https://cs.console.aliyun.com). Do not manually remove nodes by running the `kubectl delete node` command.
-     * - Do not release nodes or remove instances in the ECS or Auto Scaling console, or by calling related API operations, or passively release nodes when a subscription instance expires. In these cases, the nodes are directly shut down and automatically removed from the Container Service console.
-     * - If the expected number of nodes is configured for a node pool, the node pool automatically scales out other instances based on the corresponding configurations to maintain the expected number of nodes.
-     * - Removing a node involves pod migration, which may affect your services. Perform this operation during off-peak hours. Unexpected risks may occur during the operation. Back up your data in advance.
-     * - When a node is removed, ACK drains the node. Make sure that other nodes in the cluster have sufficient resources to prevent application pods from failing to be scheduled.
+     * - Do not proactively release nodes or remove instances in the ECS or Auto Scaling (ESS) console or by calling related API operations, or passively release nodes when a subscription instance expires. In these cases, the nodes are directly shut down and automatically removed from the Container Service console.
+     * - If the expected number of nodes is configured for a node pool, the node pool automatically scales out other instances based on the configurations to maintain the expected number of nodes.
+     * - Removing a node involves pod migration and may affect your services. Perform this operation during off-peak hours. Unexpected risks may occur during the operation. Back up your data in advance.
+     * - When a node is removed, ACK performs a drain operation. Make sure that other nodes in the cluster have sufficient resources to prevent application pods from failing to be scheduled.
      * - Check the node affinity rules and scheduling policies of the pods on the node to be removed. Make sure that the pods can be scheduled to other nodes after the node is removed.
      *
      * @param request - DescribeClusterNodePoolsRequest
@@ -3056,7 +3066,7 @@ class Client extends openapi_core_1.default {
         return await this.describeClustersWithOptions(request, headers, runtime);
     }
     /**
-     * Queries the list of all clusters in a specified region.
+     * Queries all clusters in a specified region.
      *
      * @param request - DescribeClustersForRegionRequest
      * @param headers - map
@@ -3105,7 +3115,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeClustersForRegionResponse({}));
     }
     /**
-     * Queries the list of all clusters in a specified region.
+     * Queries all clusters in a specified region.
      *
      * @param request - DescribeClustersForRegionRequest
      * @returns DescribeClustersForRegionResponse
@@ -3346,7 +3356,7 @@ class Client extends openapi_core_1.default {
         return await this.describeExternalAgentWithOptions(ClusterId, request, headers, runtime);
     }
     /**
-     * Queries the details of Kubernetes versions, including version information, release dates, expiration dates, compatible operating systems, and supported runtimes.
+     * Queries the details of Kubernetes versions, including version information, release dates, expiration dates, compatible operating systems, and runtimes.
      *
      * @param request - DescribeKubernetesVersionMetadataRequest
      * @param headers - map
@@ -3374,6 +3384,9 @@ class Client extends openapi_core_1.default {
         if (!$dara.isNull(request.region)) {
             query["Region"] = request.region;
         }
+        if (!$dara.isNull(request.supportPolicy)) {
+            query["SupportPolicy"] = request.supportPolicy;
+        }
         if (!$dara.isNull(request.runtime)) {
             query["runtime"] = request.runtime;
         }
@@ -3395,7 +3408,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeKubernetesVersionMetadataResponse({}));
     }
     /**
-     * Queries the details of Kubernetes versions, including version information, release dates, expiration dates, compatible operating systems, and supported runtimes.
+     * Queries the details of Kubernetes versions, including version information, release dates, expiration dates, compatible operating systems, and runtimes.
      *
      * @param request - DescribeKubernetesVersionMetadataRequest
      * @returns DescribeKubernetesVersionMetadataResponse
@@ -5245,10 +5258,10 @@ class Client extends openapi_core_1.default {
         return await this.listTagResourcesWithOptions(request, headers, runtime);
     }
     /**
-     * Queries the KubeConfig status list of all clusters for the current user.
+     * Queries the KubeConfig status list for all clusters of the current user.
      *
      * @remarks
-     * > To call this operation, you must have the permissions to manage Container Service (CS) (AliyunCSFullAccess).
+     * > To call this operation, you must have the AliyunCSFullAccess permission to manage Container Service for Kubernetes (CS).
      *
      * @param request - ListUserKubeConfigStatesRequest
      * @param headers - map
@@ -5282,10 +5295,10 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.ListUserKubeConfigStatesResponse({}));
     }
     /**
-     * Queries the KubeConfig status list of all clusters for the current user.
+     * Queries the KubeConfig status list for all clusters of the current user.
      *
      * @remarks
-     * > To call this operation, you must have the permissions to manage Container Service (CS) (AliyunCSFullAccess).
+     * > To call this operation, you must have the AliyunCSFullAccess permission to manage Container Service for Kubernetes (CS).
      *
      * @param request - ListUserKubeConfigStatesRequest
      * @returns ListUserKubeConfigStatesResponse
@@ -5398,10 +5411,10 @@ class Client extends openapi_core_1.default {
         return await this.modifyAutoRepairPolicyWithOptions(clusterId, policyId, request, headers, runtime);
     }
     /**
-     * Modifies the configuration of an ACK cluster.
+     * Modifies the configurations of an ACK cluster.
      *
      * @remarks
-     * <notice>Starting from July 4, 2026, the request parameters instance_deletion_protection, ingress_loadbalancer_id, and access_control_list will no longer take effect. For more information about the changes, see [Announcement on changes to OpenAPI request and response parameters and OpenAPI deprecation for ACK cluster management](https://help.aliyun.com/document_detail/2932733.html).</notice>
+     * <notice>Starting July 4, 2026, the request parameters instance_deletion_protection, ingress_loadbalancer_id, and access_control_list will no longer take effect. For more information about the changes, see [Announcement on changes to request and response parameters of ACK cluster management API operations and API operation deprecation](https://help.aliyun.com/document_detail/2932733.html).</notice>
      *
      * @param request - ModifyClusterRequest
      * @param headers - map
@@ -5465,6 +5478,9 @@ class Client extends openapi_core_1.default {
         if (!$dara.isNull(request.securityGroupId)) {
             body["security_group_id"] = request.securityGroupId;
         }
+        if (!$dara.isNull(request.supportPolicy)) {
+            body["support_policy"] = request.supportPolicy;
+        }
         if (!$dara.isNull(request.systemEventsLogging)) {
             body["system_events_logging"] = request.systemEventsLogging;
         }
@@ -5492,10 +5508,10 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyClusterResponse({}));
     }
     /**
-     * Modifies the configuration of an ACK cluster.
+     * Modifies the configurations of an ACK cluster.
      *
      * @remarks
-     * <notice>Starting from July 4, 2026, the request parameters instance_deletion_protection, ingress_loadbalancer_id, and access_control_list will no longer take effect. For more information about the changes, see [Announcement on changes to OpenAPI request and response parameters and OpenAPI deprecation for ACK cluster management](https://help.aliyun.com/document_detail/2932733.html).</notice>
+     * <notice>Starting July 4, 2026, the request parameters instance_deletion_protection, ingress_loadbalancer_id, and access_control_list will no longer take effect. For more information about the changes, see [Announcement on changes to request and response parameters of ACK cluster management API operations and API operation deprecation](https://help.aliyun.com/document_detail/2932733.html).</notice>
      *
      * @param request - ModifyClusterRequest
      * @returns ModifyClusterResponse
@@ -5560,10 +5576,10 @@ class Client extends openapi_core_1.default {
         return await this.modifyClusterAddonWithOptions(clusterId, componentId, request, headers, runtime);
     }
     /**
-     * Updates the configuration of a node pool based on the node pool ID by calling the ModifyClusterNodePool operation.
+     * Updates the configurations of a specified node pool.
      *
      * @remarks
-     * <notice>Starting July 4, 2026, the request parameters instance_deletion_protection, ingress_loadbalancer_id, and access_control_list will no longer take effect. For more information about the changes, see [Announcement on changes to input and output parameters of ACK cluster management OpenAPI operations and deprecation of OpenAPI operations](https://help.aliyun.com/document_detail/2932733.html).</notice>
+     * <notice>Starting July 4, 2026, the request parameters instance_deletion_protection, ingress_loadbalancer_id, and access_control_list will no longer take effect. For more information about the changes, see [Announcement on changes to request and response parameters and deprecation of OpenAPI operations related to ACK cluster management](https://help.aliyun.com/document_detail/2932733.html).</notice>
      *
      * @param request - ModifyClusterNodePoolRequest
      * @param headers - map
@@ -5618,10 +5634,10 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyClusterNodePoolResponse({}));
     }
     /**
-     * Updates the configuration of a node pool based on the node pool ID by calling the ModifyClusterNodePool operation.
+     * Updates the configurations of a specified node pool.
      *
      * @remarks
-     * <notice>Starting July 4, 2026, the request parameters instance_deletion_protection, ingress_loadbalancer_id, and access_control_list will no longer take effect. For more information about the changes, see [Announcement on changes to input and output parameters of ACK cluster management OpenAPI operations and deprecation of OpenAPI operations](https://help.aliyun.com/document_detail/2932733.html).</notice>
+     * <notice>Starting July 4, 2026, the request parameters instance_deletion_protection, ingress_loadbalancer_id, and access_control_list will no longer take effect. For more information about the changes, see [Announcement on changes to request and response parameters and deprecation of OpenAPI operations related to ACK cluster management](https://help.aliyun.com/document_detail/2932733.html).</notice>
      *
      * @param request - ModifyClusterNodePoolRequest
      * @returns ModifyClusterNodePoolResponse
@@ -5999,14 +6015,14 @@ class Client extends openapi_core_1.default {
         return await this.removeClusterNodesWithOptions(ClusterId, request, headers, runtime);
     }
     /**
-     * Removes nodes from a node pool in a cluster and adjusts the expected number of nodes when the nodes are no longer needed. When removing nodes, you can specify whether to release the associated ECS instances and whether to automatically drain the nodes. Node removal involves pod migration, which may affect your workloads. Perform this operation during off-peak hours and back up your data in advance.
+     * Removes nodes from a node pool in a cluster and adjusts the expected number of nodes when the nodes are no longer needed. When removing nodes, you can specify whether to release the associated Elastic Compute Service (ECS) instances and whether to automatically drain the nodes. Removing nodes involves pod migration, which may affect your services. Perform this operation during off-peak hours and back up your data in advance.
      *
      * @remarks
-     * - Node removal involves pod migration, which may affect your workloads. Perform this operation during off-peak hours.
+     * - Removing nodes involves pod migration, which may affect your services. Perform this operation during off-peak hours.
      * - Unexpected risks may occur during the operation. Back up your data in advance.
-     * - During the operation, the system sets the nodes to the unschedulable state.
+     * - During the operation, the system sets the current nodes to the unschedulable state.
      * - Only worker nodes are removed. Master nodes are not removed.
-     * - Even if you choose to release nodes (by setting release_node to true), subscription nodes are not released. You must release them manually in the [ECS console](https://ecs.console.aliyun.com/) after removing them from the node pool.
+     * - Even if you choose to release nodes (that is, set `release_node` to `true`), subscription nodes are not released. To release subscription nodes, you must remove them first and then release them in the [ECS console](https://ecs.console.aliyun.com/).
      *
      * @param tmpReq - RemoveNodePoolNodesRequest
      * @param headers - map
@@ -6030,6 +6046,9 @@ class Client extends openapi_core_1.default {
         if (!$dara.isNull(request.drainNode)) {
             query["drain_node"] = request.drainNode;
         }
+        if (!$dara.isNull(request.drainTimeoutSeconds)) {
+            query["drain_timeout_seconds"] = request.drainTimeoutSeconds;
+        }
         if (!$dara.isNull(request.instanceIdsShrink)) {
             query["instance_ids"] = request.instanceIdsShrink;
         }
@@ -6057,14 +6076,14 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.RemoveNodePoolNodesResponse({}));
     }
     /**
-     * Removes nodes from a node pool in a cluster and adjusts the expected number of nodes when the nodes are no longer needed. When removing nodes, you can specify whether to release the associated ECS instances and whether to automatically drain the nodes. Node removal involves pod migration, which may affect your workloads. Perform this operation during off-peak hours and back up your data in advance.
+     * Removes nodes from a node pool in a cluster and adjusts the expected number of nodes when the nodes are no longer needed. When removing nodes, you can specify whether to release the associated Elastic Compute Service (ECS) instances and whether to automatically drain the nodes. Removing nodes involves pod migration, which may affect your services. Perform this operation during off-peak hours and back up your data in advance.
      *
      * @remarks
-     * - Node removal involves pod migration, which may affect your workloads. Perform this operation during off-peak hours.
+     * - Removing nodes involves pod migration, which may affect your services. Perform this operation during off-peak hours.
      * - Unexpected risks may occur during the operation. Back up your data in advance.
-     * - During the operation, the system sets the nodes to the unschedulable state.
+     * - During the operation, the system sets the current nodes to the unschedulable state.
      * - Only worker nodes are removed. Master nodes are not removed.
-     * - Even if you choose to release nodes (by setting release_node to true), subscription nodes are not released. You must release them manually in the [ECS console](https://ecs.console.aliyun.com/) after removing them from the node pool.
+     * - Even if you choose to release nodes (that is, set `release_node` to `true`), subscription nodes are not released. To release subscription nodes, you must remove them first and then release them in the [ECS console](https://ecs.console.aliyun.com/).
      *
      * @param request - RemoveNodePoolNodesRequest
      * @returns RemoveNodePoolNodesResponse
@@ -6851,7 +6870,7 @@ class Client extends openapi_core_1.default {
         return await this.untagResourcesWithOptions(request, headers, runtime);
     }
     /**
-     * Enables or disables the audit log feature for a specified ACK cluster, or updates the audit log configurations to record requests to the Kubernetes API and the corresponding results for tracing cluster operation history and troubleshooting cluster faults.
+     * Updates the audit log configuration of a specified ACK cluster. You can call this operation to enable or disable the audit log feature, or update the audit log configuration to record requests to the Kubernetes API and their results for tracing cluster operation history and troubleshooting cluster faults.
      *
      * @remarks
      * Before you call this operation, make sure that you fully understand the billing methods and pricing of <props="china">[Simple Log Service](https://www.aliyun.com/price/product#/sls/detail/sls)<props="intl">[Simple Log Service](https://www.alibabacloud.com/product/log-service/pricing).
@@ -6888,7 +6907,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.UpdateClusterAuditLogConfigResponse({}));
     }
     /**
-     * Enables or disables the audit log feature for a specified ACK cluster, or updates the audit log configurations to record requests to the Kubernetes API and the corresponding results for tracing cluster operation history and troubleshooting cluster faults.
+     * Updates the audit log configuration of a specified ACK cluster. You can call this operation to enable or disable the audit log feature, or update the audit log configuration to record requests to the Kubernetes API and their results for tracing cluster operation history and troubleshooting cluster faults.
      *
      * @remarks
      * Before you call this operation, make sure that you fully understand the billing methods and pricing of <props="china">[Simple Log Service](https://www.aliyun.com/price/product#/sls/detail/sls)<props="intl">[Simple Log Service](https://www.alibabacloud.com/product/log-service/pricing).
@@ -7382,10 +7401,10 @@ class Client extends openapi_core_1.default {
         return await this.updateTemplateWithOptions(TemplateId, request, headers, runtime);
     }
     /**
-     * Updates the Role-Based Access Control (RBAC) access permissions of a Resource Access Management (RAM) user or RAM role in an ACK cluster. By default, RAM users, RAM roles, and users other than the cluster creator do not have any RBAC access permissions in the cluster. You can invoke the UpdateUserPermissions operation to update the RBAC access permissions of a RAM user or RAM role, including the accessible resources, the scope of the permissions, and the preset role types, to improve secure access control in cluster management.
+     * Updates the RBAC access permissions of a Resource Access Management (RAM) user or RAM role in an ACK cluster. By default, RAM users and RAM roles other than the cluster creator do not have any RBAC access permissions in the cluster. You can invoke the UpdateUserPermissions operation to update the RBAC access permissions of a RAM user or role, including the accessible resources, the scope of the permissions, and the preset role types, to improve secure access control in cluster management.
      *
      * @remarks
-     * You can update the cluster authorization information of a target Resource Access Management (RAM) user or RAM role by using a full update or an incremental update. A full update overwrites the existing cluster permissions of the target RAM user or RAM role. The request must include all permission configurations that you want to grant to the target RAM user or RAM role. An incremental update includes add and delete operations. It only modifies the permissions based on the cluster authorization information included in the request and does not affect other cluster permissions of the RAM user or RAM role.
+     * You can update the cluster authorization information of a target Resource Access Management (RAM) user or RAM role by using full update or incremental update. A full update overwrites the existing cluster permissions of the target RAM user or RAM role. The request must include all permission configurations that you want to grant to the target RAM user or RAM role. An incremental update includes add and delete operations. It only modifies the permissions based on the cluster authorization information included in the request and does not affect other cluster permissions of the RAM user or RAM role.
      *
      * @param request - UpdateUserPermissionsRequest
      * @param headers - map
@@ -7417,10 +7436,10 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.UpdateUserPermissionsResponse({}));
     }
     /**
-     * Updates the Role-Based Access Control (RBAC) access permissions of a Resource Access Management (RAM) user or RAM role in an ACK cluster. By default, RAM users, RAM roles, and users other than the cluster creator do not have any RBAC access permissions in the cluster. You can invoke the UpdateUserPermissions operation to update the RBAC access permissions of a RAM user or RAM role, including the accessible resources, the scope of the permissions, and the preset role types, to improve secure access control in cluster management.
+     * Updates the RBAC access permissions of a Resource Access Management (RAM) user or RAM role in an ACK cluster. By default, RAM users and RAM roles other than the cluster creator do not have any RBAC access permissions in the cluster. You can invoke the UpdateUserPermissions operation to update the RBAC access permissions of a RAM user or role, including the accessible resources, the scope of the permissions, and the preset role types, to improve secure access control in cluster management.
      *
      * @remarks
-     * You can update the cluster authorization information of a target Resource Access Management (RAM) user or RAM role by using a full update or an incremental update. A full update overwrites the existing cluster permissions of the target RAM user or RAM role. The request must include all permission configurations that you want to grant to the target RAM user or RAM role. An incremental update includes add and delete operations. It only modifies the permissions based on the cluster authorization information included in the request and does not affect other cluster permissions of the RAM user or RAM role.
+     * You can update the cluster authorization information of a target Resource Access Management (RAM) user or RAM role by using full update or incremental update. A full update overwrites the existing cluster permissions of the target RAM user or RAM role. The request must include all permission configurations that you want to grant to the target RAM user or RAM role. An incremental update includes add and delete operations. It only modifies the permissions based on the cluster authorization information included in the request and does not affect other cluster permissions of the RAM user or RAM role.
      *
      * @param request - UpdateUserPermissionsRequest
      * @returns UpdateUserPermissionsResponse