@alicloud/cs20151215 7.2.3 → 7.2.5

package/dist/client.d.ts

@@ -322,7 +322,7 @@ export default class Client extends OpenApi {
      */
     createClusterInspectConfig(clusterId: string, request: $_model.CreateClusterInspectConfigRequest): Promise<$_model.CreateClusterInspectConfigResponse>;
     /**
-     * Creates a node pool for a cluster. A node pool is a logical collection of nodes that share the same attributes. It allows unified management and O&M of nodes, such as node upgrades and elastic scaling. You can use the automated O&M capabilities of node pools to reduce O&M costs. These capabilities include automatic repair of OS CVE vulnerabilities, automatic recovery of faulty nodes, and automatic upgrades of kubelet and containerd versions.
+     * 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
@@ -333,7 +333,7 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.CreateClusterNodePoolResponse>;
     /**
-     * Creates a node pool for a cluster. A node pool is a logical collection of nodes that share the same attributes. It allows unified management and O&M of nodes, such as node upgrades and elastic scaling. You can use the automated O&M capabilities of node pools to reduce O&M costs. These capabilities include automatic repair of OS CVE vulnerabilities, automatic recovery of faulty nodes, and automatic upgrades of kubelet and containerd versions.
+     * 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
@@ -528,7 +528,7 @@ export default class Client extends OpenApi {
      */
     deleteClusterInspectConfig(clusterId: string): Promise<$_model.DeleteClusterInspectConfigResponse>;
     /**
-     * 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
@@ -539,7 +539,7 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_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
@@ -930,10 +930,10 @@ export default class Client extends OpenApi {
      *
      * @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
@@ -949,10 +949,10 @@ export default class Client extends OpenApi {
      *
      * @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
@@ -1014,11 +1014,11 @@ export default class Client extends OpenApi {
      */
     describeClusterTasks(clusterId: string, request: $_model.DescribeClusterTasksRequest): Promise<$_model.DescribeClusterTasksResponse>;
     /**
-     * Retrieves the kubeconfig file of a cluster.
+     * Retrieves the kubeconfig of a cluster.
      *
      * @remarks
-     * - The default validity period of the certificate issued for a kubeconfig file is three years. Within 180 days before expiration, you can obtain a refreshed kubeconfig file with rotated credentials through the Container Service for Kubernetes console or by calling the API operation to retrieve the cluster kubeconfig. The new kubeconfig certificate remains valid for three years. The old kubeconfig credentials remain valid until the certificate expires. Obtain the rotated credentials promptly based on the kubeconfig expiration time displayed in the console or returned by the API operation.
-     * - Properly manage the kubeconfig credentials used for cluster management, and revoke them promptly when they are no longer needed. This prevents security risks such as data leaks caused by kubeconfig exposure.
+     * - The default validity period of a certificate issued for a kubeconfig file is three years. Within 180 days before expiration, you can obtain a refreshed kubeconfig file with rotated certificates through the Container Service for Kubernetes console or by calling the API operation to retrieve the cluster kubeconfig. The new kubeconfig certificate remains valid for three years. The old kubeconfig credentials remain valid until the certificate expires. Obtain the rotated credentials promptly based on the kubeconfig expiration time displayed in the console or returned by the API operation.
+     * - Properly manage the kubeconfig credentials for cluster management and revoke them promptly when they are no longer needed to prevent security risks such as data leaks caused by kubeconfig exposure.
      *
      * @param request - DescribeClusterUserKubeconfigRequest
      * @param headers - map
@@ -1029,11 +1029,11 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeClusterUserKubeconfigResponse>;
     /**
-     * Retrieves the kubeconfig file of a cluster.
+     * Retrieves the kubeconfig of a cluster.
      *
      * @remarks
-     * - The default validity period of the certificate issued for a kubeconfig file is three years. Within 180 days before expiration, you can obtain a refreshed kubeconfig file with rotated credentials through the Container Service for Kubernetes console or by calling the API operation to retrieve the cluster kubeconfig. The new kubeconfig certificate remains valid for three years. The old kubeconfig credentials remain valid until the certificate expires. Obtain the rotated credentials promptly based on the kubeconfig expiration time displayed in the console or returned by the API operation.
-     * - Properly manage the kubeconfig credentials used for cluster management, and revoke them promptly when they are no longer needed. This prevents security risks such as data leaks caused by kubeconfig exposure.
+     * - The default validity period of a certificate issued for a kubeconfig file is three years. Within 180 days before expiration, you can obtain a refreshed kubeconfig file with rotated certificates through the Container Service for Kubernetes console or by calling the API operation to retrieve the cluster kubeconfig. The new kubeconfig certificate remains valid for three years. The old kubeconfig credentials remain valid until the certificate expires. Obtain the rotated credentials promptly based on the kubeconfig expiration time displayed in the console or returned by the API operation.
+     * - Properly manage the kubeconfig credentials for cluster management and revoke them promptly when they are no longer needed to prevent security risks such as data leaks caused by kubeconfig exposure.
      *
      * @param request - DescribeClusterUserKubeconfigRequest
      * @returns DescribeClusterUserKubeconfigResponse
@@ -1265,7 +1265,7 @@ export default class Client extends OpenApi {
      */
     describePolicyDetails(policyName: string): Promise<$_model.DescribePolicyDetailsResponse>;
     /**
-     * Queries the details of policy governance in a specified ACK cluster. Container security policies for ACK clusters provide a comprehensive built-in rule library that includes Compliance, Infra, K8s-general, and PSP to ensure the secure operation of containers in production environments. This operation retrieves details such as the counts of enabled policies at different severity levels, policy governance audit logs, and interception and alerting statistics.
+     * Queries the details of policy governance for a specified ACK cluster. Container security policies for ACK clusters provide a comprehensive set of built-in rule libraries, including Compliance, Infra, K8s-general, and PSP, to ensure the secure operation of containers in production environments. You can use this operation to retrieve information such as the counts of enabled policies at different severity levels, policy governance audit logs, and interception and alerting statistics.
      *
      * @param headers - map
      * @param runtime - runtime options for this request RuntimeOptions
@@ -1275,7 +1275,7 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.DescribePolicyGovernanceInClusterResponse>;
     /**
-     * Queries the details of policy governance in a specified ACK cluster. Container security policies for ACK clusters provide a comprehensive built-in rule library that includes Compliance, Infra, K8s-general, and PSP to ensure the secure operation of containers in production environments. This operation retrieves details such as the counts of enabled policies at different severity levels, policy governance audit logs, and interception and alerting statistics.
+     * Queries the details of policy governance for a specified ACK cluster. Container security policies for ACK clusters provide a comprehensive set of built-in rule libraries, including Compliance, Infra, K8s-general, and PSP, to ensure the secure operation of containers in production environments. You can use this operation to retrieve information such as the counts of enabled policies at different severity levels, policy governance audit logs, and interception and alerting statistics.
      * @returns DescribePolicyGovernanceInClusterResponse
      */
     describePolicyGovernanceInCluster(clusterId: string): Promise<$_model.DescribePolicyGovernanceInClusterResponse>;
@@ -1758,10 +1758,10 @@ export default class Client extends OpenApi {
      */
     listAddons(request: $_model.ListAddonsRequest): Promise<$_model.ListAddonsResponse>;
     /**
-     * Retrieves the list of self-healing rules.
+     * Retrieves a list of self-healing rules.
      *
      * @remarks
-     * >Notice: This API is not yet available. Stay tuned.</notice>
+     * >Notice: This API is not yet available. Stay tuned.
      *
      * @param headers - map
      * @param runtime - runtime options for this request RuntimeOptions
@@ -1771,10 +1771,10 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.ListAutoRepairPoliciesResponse>;
     /**
-     * Retrieves the list of self-healing rules.
+     * Retrieves a list of self-healing rules.
      *
      * @remarks
-     * >Notice: This API is not yet available. Stay tuned.</notice>
+     * >Notice: This API is not yet available. Stay tuned.
      * @returns ListAutoRepairPoliciesResponse
      */
     listAutoRepairPolicies(clusterId: string): Promise<$_model.ListAutoRepairPoliciesResponse>;
@@ -2105,10 +2105,10 @@ export default class Client extends OpenApi {
      */
     modifyClusterAddon(clusterId: string, componentId: string, request: $_model.ModifyClusterAddonRequest): Promise<$_model.ModifyClusterAddonResponse>;
     /**
-     * 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
@@ -2119,10 +2119,10 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_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
@@ -2296,14 +2296,14 @@ export default class Client extends OpenApi {
      */
     removeClusterNodes(ClusterId: string, request: $_model.RemoveClusterNodesRequest): Promise<$_model.RemoveClusterNodesResponse>;
     /**
-     * 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 ECS instances and whether to automatically drain the nodes. Removing nodes involves pod migration and 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 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.
      * - During the operation, the system sets the 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 (by setting `release_node` to `true`), subscription nodes are not released. To release subscription nodes, you must first [change their billing method to pay-as-you-go](https://www.alibabacloud.com/help/en/ecs/change-the-billing-method-of-an-instance-from-subscription-to-pay-as-you-go-1) and then release them in the [ECS console](https://ecs.console.aliyun.com/).
      *
      * @param tmpReq - RemoveNodePoolNodesRequest
      * @param headers - map
@@ -2314,14 +2314,14 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_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 ECS instances and whether to automatically drain the nodes. Removing nodes involves pod migration and 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 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.
      * - During the operation, the system sets the 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 (by setting `release_node` to `true`), subscription nodes are not released. To release subscription nodes, you must first [change their billing method to pay-as-you-go](https://www.alibabacloud.com/help/en/ecs/change-the-billing-method-of-an-instance-from-subscription-to-pay-as-you-go-1) and then release them in the [ECS console](https://ecs.console.aliyun.com/).
      *
      * @param request - RemoveNodePoolNodesRequest
      * @returns RemoveNodePoolNodesResponse

package/dist/client.js

@@ -967,6 +967,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;
         }
@@ -1164,7 +1167,7 @@ class Client extends openapi_core_1.default {
         return await this.createClusterInspectConfigWithOptions(clusterId, request, headers, runtime);
     }
     /**
-     * Creates a node pool for a cluster. A node pool is a logical collection of nodes that share the same attributes. It allows unified management and O&M of nodes, such as node upgrades and elastic scaling. You can use the automated O&M capabilities of node pools to reduce O&M costs. These capabilities include automatic repair of OS CVE vulnerabilities, automatic recovery of faulty nodes, and automatic upgrades of kubelet and containerd versions.
+     * 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 +1243,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateClusterNodePoolResponse({}));
     }
     /**
-     * Creates a node pool for a cluster. A node pool is a logical collection of nodes that share the same attributes. It allows unified management and O&M of nodes, such as node upgrades and elastic scaling. You can use the automated O&M capabilities of node pools to reduce O&M costs. These capabilities include automatic repair of OS CVE vulnerabilities, automatic recovery of faulty nodes, and automatic upgrades of kubelet and containerd versions.
+     * 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 +1710,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 +1741,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
@@ -2657,10 +2660,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 +2699,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
@@ -2867,11 +2870,11 @@ class Client extends openapi_core_1.default {
         return await this.describeClusterTasksWithOptions(clusterId, request, headers, runtime);
     }
     /**
-     * Retrieves the kubeconfig file of a cluster.
+     * Retrieves the kubeconfig of a cluster.
      *
      * @remarks
-     * - The default validity period of the certificate issued for a kubeconfig file is three years. Within 180 days before expiration, you can obtain a refreshed kubeconfig file with rotated credentials through the Container Service for Kubernetes console or by calling the API operation to retrieve the cluster kubeconfig. The new kubeconfig certificate remains valid for three years. The old kubeconfig credentials remain valid until the certificate expires. Obtain the rotated credentials promptly based on the kubeconfig expiration time displayed in the console or returned by the API operation.
-     * - Properly manage the kubeconfig credentials used for cluster management, and revoke them promptly when they are no longer needed. This prevents security risks such as data leaks caused by kubeconfig exposure.
+     * - The default validity period of a certificate issued for a kubeconfig file is three years. Within 180 days before expiration, you can obtain a refreshed kubeconfig file with rotated certificates through the Container Service for Kubernetes console or by calling the API operation to retrieve the cluster kubeconfig. The new kubeconfig certificate remains valid for three years. The old kubeconfig credentials remain valid until the certificate expires. Obtain the rotated credentials promptly based on the kubeconfig expiration time displayed in the console or returned by the API operation.
+     * - Properly manage the kubeconfig credentials for cluster management and revoke them promptly when they are no longer needed to prevent security risks such as data leaks caused by kubeconfig exposure.
      *
      * @param request - DescribeClusterUserKubeconfigRequest
      * @param headers - map
@@ -2905,11 +2908,11 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeClusterUserKubeconfigResponse({}));
     }
     /**
-     * Retrieves the kubeconfig file of a cluster.
+     * Retrieves the kubeconfig of a cluster.
      *
      * @remarks
-     * - The default validity period of the certificate issued for a kubeconfig file is three years. Within 180 days before expiration, you can obtain a refreshed kubeconfig file with rotated credentials through the Container Service for Kubernetes console or by calling the API operation to retrieve the cluster kubeconfig. The new kubeconfig certificate remains valid for three years. The old kubeconfig credentials remain valid until the certificate expires. Obtain the rotated credentials promptly based on the kubeconfig expiration time displayed in the console or returned by the API operation.
-     * - Properly manage the kubeconfig credentials used for cluster management, and revoke them promptly when they are no longer needed. This prevents security risks such as data leaks caused by kubeconfig exposure.
+     * - The default validity period of a certificate issued for a kubeconfig file is three years. Within 180 days before expiration, you can obtain a refreshed kubeconfig file with rotated certificates through the Container Service for Kubernetes console or by calling the API operation to retrieve the cluster kubeconfig. The new kubeconfig certificate remains valid for three years. The old kubeconfig credentials remain valid until the certificate expires. Obtain the rotated credentials promptly based on the kubeconfig expiration time displayed in the console or returned by the API operation.
+     * - Properly manage the kubeconfig credentials for cluster management and revoke them promptly when they are no longer needed to prevent security risks such as data leaks caused by kubeconfig exposure.
      *
      * @param request - DescribeClusterUserKubeconfigRequest
      * @returns DescribeClusterUserKubeconfigResponse
@@ -3374,6 +3377,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;
         }
@@ -3514,7 +3520,7 @@ class Client extends openapi_core_1.default {
         return await this.describePolicyDetailsWithOptions(policyName, headers, runtime);
     }
     /**
-     * Queries the details of policy governance in a specified ACK cluster. Container security policies for ACK clusters provide a comprehensive built-in rule library that includes Compliance, Infra, K8s-general, and PSP to ensure the secure operation of containers in production environments. This operation retrieves details such as the counts of enabled policies at different severity levels, policy governance audit logs, and interception and alerting statistics.
+     * Queries the details of policy governance for a specified ACK cluster. Container security policies for ACK clusters provide a comprehensive set of built-in rule libraries, including Compliance, Infra, K8s-general, and PSP, to ensure the secure operation of containers in production environments. You can use this operation to retrieve information such as the counts of enabled policies at different severity levels, policy governance audit logs, and interception and alerting statistics.
      *
      * @param headers - map
      * @param runtime - runtime options for this request RuntimeOptions
@@ -3538,7 +3544,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribePolicyGovernanceInClusterResponse({}));
     }
     /**
-     * Queries the details of policy governance in a specified ACK cluster. Container security policies for ACK clusters provide a comprehensive built-in rule library that includes Compliance, Infra, K8s-general, and PSP to ensure the secure operation of containers in production environments. This operation retrieves details such as the counts of enabled policies at different severity levels, policy governance audit logs, and interception and alerting statistics.
+     * Queries the details of policy governance for a specified ACK cluster. Container security policies for ACK clusters provide a comprehensive set of built-in rule libraries, including Compliance, Infra, K8s-general, and PSP, to ensure the secure operation of containers in production environments. You can use this operation to retrieve information such as the counts of enabled policies at different severity levels, policy governance audit logs, and interception and alerting statistics.
      * @returns DescribePolicyGovernanceInClusterResponse
      */
     async describePolicyGovernanceInCluster(clusterId) {
@@ -4670,10 +4676,10 @@ class Client extends openapi_core_1.default {
         return await this.listAddonsWithOptions(request, headers, runtime);
     }
     /**
-     * Retrieves the list of self-healing rules.
+     * Retrieves a list of self-healing rules.
      *
      * @remarks
-     * >Notice: This API is not yet available. Stay tuned.</notice>
+     * >Notice: This API is not yet available. Stay tuned.
      *
      * @param headers - map
      * @param runtime - runtime options for this request RuntimeOptions
@@ -4697,10 +4703,10 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.ListAutoRepairPoliciesResponse({}));
     }
     /**
-     * Retrieves the list of self-healing rules.
+     * Retrieves a list of self-healing rules.
      *
      * @remarks
-     * >Notice: This API is not yet available. Stay tuned.</notice>
+     * >Notice: This API is not yet available. Stay tuned.
      * @returns ListAutoRepairPoliciesResponse
      */
     async listAutoRepairPolicies(clusterId) {
@@ -5465,6 +5471,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;
         }
@@ -5560,10 +5569,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 +5627,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 +6008,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 ECS instances and whether to automatically drain the nodes. Removing nodes involves pod migration and 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 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.
      * - During the operation, the system sets the 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 (by setting `release_node` to `true`), subscription nodes are not released. To release subscription nodes, you must first [change their billing method to pay-as-you-go](https://www.alibabacloud.com/help/en/ecs/change-the-billing-method-of-an-instance-from-subscription-to-pay-as-you-go-1) and then release them in the [ECS console](https://ecs.console.aliyun.com/).
      *
      * @param tmpReq - RemoveNodePoolNodesRequest
      * @param headers - map
@@ -6057,14 +6066,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 ECS instances and whether to automatically drain the nodes. Removing nodes involves pod migration and 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 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.
      * - During the operation, the system sets the 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 (by setting `release_node` to `true`), subscription nodes are not released. To release subscription nodes, you must first [change their billing method to pay-as-you-go](https://www.alibabacloud.com/help/en/ecs/change-the-billing-method-of-an-instance-from-subscription-to-pay-as-you-go-1) and then release them in the [ECS console](https://ecs.console.aliyun.com/).
      *
      * @param request - RemoveNodePoolNodesRequest
      * @returns RemoveNodePoolNodesResponse