@alicloud/cs20151215 4.9.0 → 4.9.2

package/dist/client.d.ts

@@ -276,7 +276,7 @@ export default class Client extends OpenApi {
      */
     createClusterDiagnosis(clusterId: string, request: $_model.CreateClusterDiagnosisRequest): Promise<$_model.CreateClusterDiagnosisResponse>;
     /**
-     * 创建集群巡检配置
+     * Configures cluster inspection.
      *
      * @param request - CreateClusterInspectConfigRequest
      * @param headers - map
@@ -287,7 +287,7 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.CreateClusterInspectConfigResponse>;
     /**
-     * 创建集群巡检配置
+     * Configures cluster inspection.
      *
      * @param request - CreateClusterInspectConfigRequest
      * @returns CreateClusterInspectConfigResponse
@@ -458,7 +458,7 @@ export default class Client extends OpenApi {
      */
     deleteCluster(ClusterId: string, request: $_model.DeleteClusterRequest): Promise<$_model.DeleteClusterResponse>;
     /**
-     * 删除集群巡检配置
+     * Deletes cluster inspection configurations.
      *
      * @param headers - map
      * @param runtime - runtime options for this request RuntimeOptions
@@ -468,7 +468,7 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteClusterInspectConfigResponse>;
     /**
-     * 删除集群巡检配置
+     * Deletes cluster inspection configurations.
      * @returns DeleteClusterInspectConfigResponse
      */
     deleteClusterInspectConfig(clusterId: string): Promise<$_model.DeleteClusterInspectConfigResponse>;
@@ -491,12 +491,15 @@ export default class Client extends OpenApi {
      */
     deleteClusterNodepool(ClusterId: string, NodepoolId: string, request: $_model.DeleteClusterNodepoolRequest): Promise<$_model.DeleteClusterNodepoolResponse>;
     /**
-     * Removes nodes from a Container Service for Kubernetes (ACK) cluster. When you remove nodes, you can specify whether to release the Elastic Compute Service (ECS) instances and drain the nodes. When you remove nodes, pods on the nodes are migrated. This may adversely affect your businesses. We recommend that you back up data and perform this operation during off-peak hours.
+     * Removes nodes from a Container Service for Kubernetes (ACK) cluster when they are no longer required through the DeleteClusterNodes interface. When removing nodes, you can specify whether to release the Elastic Compute Service (ECS) instances and drain the nodes.
      *
      * @remarks
-     *   When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours.
-     * *   The operation may have unexpected risks. Back up the data before you perform this operation.
-     * *   When you remove a node, the system sets the status of the node to Unschedulable.
+     *   Use this API or the [ACK console](https://cs.console.aliyun.com) for node removal. Do not remove a node by running the `kubectl delete node` command.
+     * *   Never directly release or remove ECS instances through the ECS or Auto Scaling console/APIs. Renew subscription ECS instances before they expire. Violations may cause node termination and removal from the ACK console.
+     * *   If a node pool has the Expected Nodes parameter configured, the node pool automatically scales other ECS instances to maintain the expected number of nodes.
+     * *   When you remove a node, the pods on the node are migrated to other nodes. To prevent service interruptions, remove nodes during off-peak hours. Unexpected risks may arise during node removal. Back up the data in advance.
+     * *   ACK drains the node during node removal. Make sure that other nodes in the cluster have sufficient resources to host the evicted pods.
+     * *   To ensure the pods on the node you want to remove can be successfully scheduled to other nodes, check whether the node affinity rules and scheduling policies of the pods meet the requirements.
      *
      * @param request - DeleteClusterNodesRequest
      * @param headers - map
@@ -507,12 +510,15 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteClusterNodesResponse>;
     /**
-     * Removes nodes from a Container Service for Kubernetes (ACK) cluster. When you remove nodes, you can specify whether to release the Elastic Compute Service (ECS) instances and drain the nodes. When you remove nodes, pods on the nodes are migrated. This may adversely affect your businesses. We recommend that you back up data and perform this operation during off-peak hours.
+     * Removes nodes from a Container Service for Kubernetes (ACK) cluster when they are no longer required through the DeleteClusterNodes interface. When removing nodes, you can specify whether to release the Elastic Compute Service (ECS) instances and drain the nodes.
      *
      * @remarks
-     *   When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours.
-     * *   The operation may have unexpected risks. Back up the data before you perform this operation.
-     * *   When you remove a node, the system sets the status of the node to Unschedulable.
+     *   Use this API or the [ACK console](https://cs.console.aliyun.com) for node removal. Do not remove a node by running the `kubectl delete node` command.
+     * *   Never directly release or remove ECS instances through the ECS or Auto Scaling console/APIs. Renew subscription ECS instances before they expire. Violations may cause node termination and removal from the ACK console.
+     * *   If a node pool has the Expected Nodes parameter configured, the node pool automatically scales other ECS instances to maintain the expected number of nodes.
+     * *   When you remove a node, the pods on the node are migrated to other nodes. To prevent service interruptions, remove nodes during off-peak hours. Unexpected risks may arise during node removal. Back up the data in advance.
+     * *   ACK drains the node during node removal. Make sure that other nodes in the cluster have sufficient resources to host the evicted pods.
+     * *   To ensure the pods on the node you want to remove can be successfully scheduled to other nodes, check whether the node affinity rules and scheduling policies of the pods meet the requirements.
      *
      * @param request - DeleteClusterNodesRequest
      * @returns DeleteClusterNodesResponse
@@ -919,7 +925,8 @@ export default class Client extends OpenApi {
      * Kubeconfig files store identity and authentication information that is used by clients to access Container Service for Kubernetes (ACK) clusters. To use a kubectl client to manage an ACK cluster, you need to use the corresponding kubeconfig file to connect to the ACK cluster. We recommend that you keep kubeconfig files confidential and revoke kubeconfig files that are not in use. This helps prevent data leaks caused by the disclosure of kubeconfig files.
      *
      * @remarks
-     * >  The default validity period of a kubeconfig file is 3 years. 180 days before a kubeconfig file expires, you can renew it in the Container Service for Kubernetes (ACK) console or by calling API operations. After a kubeconfig file is renewed, the kubeconfig file is valid for 3 years. The previous kubeconfig file still remains valid until expiration. We recommend that you renew your kubeconfig file at the earliest opportunity.
+     *   The default validity period of a kubeconfig file is 3 years. 180 days before a kubeconfig file expires, you can renew it in the Container Service for Kubernetes (ACK) console or by calling API operations. After a kubeconfig file is renewed, the kubeconfig file is valid for 3 years. The previous kubeconfig file still remains valid until expiration. We recommend that you renew your kubeconfig file at the earliest opportunity.
+     * *   We recommend that you keep kubeconfig files confidential and revoke kubeconfig files that are not in use. This helps prevent data leaks caused by the disclosure of kubeconfig files.
      *
      * @param request - DescribeClusterUserKubeconfigRequest
      * @param headers - map
@@ -933,7 +940,8 @@ export default class Client extends OpenApi {
      * Kubeconfig files store identity and authentication information that is used by clients to access Container Service for Kubernetes (ACK) clusters. To use a kubectl client to manage an ACK cluster, you need to use the corresponding kubeconfig file to connect to the ACK cluster. We recommend that you keep kubeconfig files confidential and revoke kubeconfig files that are not in use. This helps prevent data leaks caused by the disclosure of kubeconfig files.
      *
      * @remarks
-     * >  The default validity period of a kubeconfig file is 3 years. 180 days before a kubeconfig file expires, you can renew it in the Container Service for Kubernetes (ACK) console or by calling API operations. After a kubeconfig file is renewed, the kubeconfig file is valid for 3 years. The previous kubeconfig file still remains valid until expiration. We recommend that you renew your kubeconfig file at the earliest opportunity.
+     *   The default validity period of a kubeconfig file is 3 years. 180 days before a kubeconfig file expires, you can renew it in the Container Service for Kubernetes (ACK) console or by calling API operations. After a kubeconfig file is renewed, the kubeconfig file is valid for 3 years. The previous kubeconfig file still remains valid until expiration. We recommend that you renew your kubeconfig file at the earliest opportunity.
+     * *   We recommend that you keep kubeconfig files confidential and revoke kubeconfig files that are not in use. This helps prevent data leaks caused by the disclosure of kubeconfig files.
      *
      * @param request - DescribeClusterUserKubeconfigRequest
      * @returns DescribeClusterUserKubeconfigResponse
@@ -1654,9 +1662,8 @@ export default class Client extends OpenApi {
      * Updates the role-based access control (RBAC) permissions of a Resource Access Management (RAM) user or RAM role. By default, you do not have the RBAC permissions on a Container Service for Kubernetes (ACK) cluster if you are not the cluster owner or you are not using an Alibaba Cloud account. You can call this operation to specify the resources that can be accessed, permission scope, and predefined roles. This helps you better manage the access control on resources in ACK clusters.
      *
      * @remarks
-     * *Precautions**:
-     * *   If you use a Resource Access Management (RAM) user to call the operation, make sure that the RAM user has the permissions to modify the permissions of other RAM users or RAM roles. Otherwise, the `StatusForbidden` or `ForbiddenGrantPermissions` error code is returned after you call the operation. For more information, see [Use a RAM user to grant RBAC permissions to other RAM users](https://help.aliyun.com/document_detail/119035.html).
-     * *   If you update full permissions, the existing permissions of the RAM user or RAM role on the cluster are overwritten. You must specify all the permissions that you want to grant to the RAM user or RAM role in the request parameters when you call the operation.
+     *   If you use a Resource Access Management (RAM) account to call this operation, make sure it has permissions to modify cluster authorization information for other RAM users or RAM roles. Otherwise, the `StatusForbidden` or `ForbiddenGrantPermissions` error code is returned. For more information, see [Use a RAM user to grant RBAC permissions to other RAM users](https://help.aliyun.com/document_detail/119035.html).
+     * *   This operation overwrites all existing cluster permissions for the target RAM user or RAM role. You must specify all the permissions you want to grant to the RAM user or RAM role in the request.
      *
      * @param request - GrantPermissionsRequest
      * @param headers - map
@@ -1670,16 +1677,15 @@ export default class Client extends OpenApi {
      * Updates the role-based access control (RBAC) permissions of a Resource Access Management (RAM) user or RAM role. By default, you do not have the RBAC permissions on a Container Service for Kubernetes (ACK) cluster if you are not the cluster owner or you are not using an Alibaba Cloud account. You can call this operation to specify the resources that can be accessed, permission scope, and predefined roles. This helps you better manage the access control on resources in ACK clusters.
      *
      * @remarks
-     * *Precautions**:
-     * *   If you use a Resource Access Management (RAM) user to call the operation, make sure that the RAM user has the permissions to modify the permissions of other RAM users or RAM roles. Otherwise, the `StatusForbidden` or `ForbiddenGrantPermissions` error code is returned after you call the operation. For more information, see [Use a RAM user to grant RBAC permissions to other RAM users](https://help.aliyun.com/document_detail/119035.html).
-     * *   If you update full permissions, the existing permissions of the RAM user or RAM role on the cluster are overwritten. You must specify all the permissions that you want to grant to the RAM user or RAM role in the request parameters when you call the operation.
+     *   If you use a Resource Access Management (RAM) account to call this operation, make sure it has permissions to modify cluster authorization information for other RAM users or RAM roles. Otherwise, the `StatusForbidden` or `ForbiddenGrantPermissions` error code is returned. For more information, see [Use a RAM user to grant RBAC permissions to other RAM users](https://help.aliyun.com/document_detail/119035.html).
+     * *   This operation overwrites all existing cluster permissions for the target RAM user or RAM role. You must specify all the permissions you want to grant to the RAM user or RAM role in the request.
      *
      * @param request - GrantPermissionsRequest
      * @returns GrantPermissionsResponse
      */
     grantPermissions(uid: string, request: $_model.GrantPermissionsRequest): Promise<$_model.GrantPermissionsResponse>;
     /**
-     * Installs a component by specifying the name and version of the component. To enhance Kubernetes capabilities, you can install a variety of components in Container Service for Kubernetes (ACK) clusters, such as fully-managed core components and application, logging and monitoring, network, storage, and security group components.
+     * 为了增强Kubernetes能力，ACK集群支持了多种组件，例如托管的核心组件，应用、日志和监控、网络、存储、安全组件等。您可以调用InstallClusterAddons接口，通过组件名称和版本安装组件。
      *
      * @param request - InstallClusterAddonsRequest
      * @param headers - map
@@ -1690,7 +1696,7 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.InstallClusterAddonsResponse>;
     /**
-     * Installs a component by specifying the name and version of the component. To enhance Kubernetes capabilities, you can install a variety of components in Container Service for Kubernetes (ACK) clusters, such as fully-managed core components and application, logging and monitoring, network, storage, and security group components.
+     * 为了增强Kubernetes能力，ACK集群支持了多种组件，例如托管的核心组件，应用、日志和监控、网络、存储、安全组件等。您可以调用InstallClusterAddons接口，通过组件名称和版本安装组件。
      *
      * @param request - InstallClusterAddonsRequest
      * @returns InstallClusterAddonsResponse
@@ -1748,7 +1754,7 @@ export default class Client extends OpenApi {
      */
     listClusterChecks(clusterId: string, request: $_model.ListClusterChecksRequest): Promise<$_model.ListClusterChecksResponse>;
     /**
-     * 获取巡检报告列表
+     * Obtains the details of the cluster inspection report.
      *
      * @param request - ListClusterInspectReportsRequest
      * @param headers - map
@@ -1759,7 +1765,7 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.ListClusterInspectReportsResponse>;
     /**
-     * 获取巡检报告列表
+     * Obtains the details of the cluster inspection report.
      *
      * @param request - ListClusterInspectReportsRequest
      * @returns ListClusterInspectReportsResponse
@@ -1852,7 +1858,7 @@ export default class Client extends OpenApi {
      */
     listUserKubeConfigStates(Uid: string, request: $_model.ListUserKubeConfigStatesRequest): Promise<$_model.ListUserKubeConfigStatesResponse>;
     /**
-     * Container Service for Kubernetes (ACK) Pro clusters are developed based on ACK Basic clusters. ACK Pro clusters provide all benefits of ACK managed clusters, such as fully-managed control planes and control plane high availability. In addition, ACK Pro clusters provide you with enhanced reliability, security, and schedulability. ACK Pro clusters are covered by the SLA that supports compensation clauses. ACK Pro clusters are suitable for large-scale businesses that require high stability and security in production environments. We recommend that you migrate from ACK Basic clusters to ACK Pro clusters.
+     * The Container Service for Kubernetes (ACK) managed Pro cluster type is developed based on the ACK managed Basic cluster type. It inherits all benefits of ACK managed clusters, such as fully-managed control planes and control plane high availability. It further enhances reliability, security, scheduling capabilities, and offers service level agreement (SLA)-backed guarantees, making it ideal for enterprise customers with large-scale production workloads requiring high stability and security. You can call the MigrateCluster operation to migrate an ACK managed Basic cluster to an ACK managed Pro cluster.
      *
      * @param request - MigrateClusterRequest
      * @param headers - map
@@ -1863,7 +1869,7 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.MigrateClusterResponse>;
     /**
-     * Container Service for Kubernetes (ACK) Pro clusters are developed based on ACK Basic clusters. ACK Pro clusters provide all benefits of ACK managed clusters, such as fully-managed control planes and control plane high availability. In addition, ACK Pro clusters provide you with enhanced reliability, security, and schedulability. ACK Pro clusters are covered by the SLA that supports compensation clauses. ACK Pro clusters are suitable for large-scale businesses that require high stability and security in production environments. We recommend that you migrate from ACK Basic clusters to ACK Pro clusters.
+     * The Container Service for Kubernetes (ACK) managed Pro cluster type is developed based on the ACK managed Basic cluster type. It inherits all benefits of ACK managed clusters, such as fully-managed control planes and control plane high availability. It further enhances reliability, security, scheduling capabilities, and offers service level agreement (SLA)-backed guarantees, making it ideal for enterprise customers with large-scale production workloads requiring high stability and security. You can call the MigrateCluster operation to migrate an ACK managed Basic cluster to an ACK managed Pro cluster.
      *
      * @param request - MigrateClusterRequest
      * @returns MigrateClusterResponse
@@ -2018,7 +2024,7 @@ export default class Client extends OpenApi {
      */
     modifyPolicyInstance(clusterId: string, policyName: string, request: $_model.ModifyPolicyInstanceRequest): Promise<$_model.ModifyPolicyInstanceResponse>;
     /**
-     * When you use Container Service for Kubernetes (ACK) for the first time, you must activate ACK by using an Alibaba Cloud account or RAM user with the required permissions and complete ACK authorization.
+     * When using Container Service for Kubernetes (ACK) for the first time, you must call the OpenAckService operation to activate the service.
      *
      * @remarks
      *   You can activate ACK by using Alibaba Cloud accounts.
@@ -2033,7 +2039,7 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.OpenAckServiceResponse>;
     /**
-     * When you use Container Service for Kubernetes (ACK) for the first time, you must activate ACK by using an Alibaba Cloud account or RAM user with the required permissions and complete ACK authorization.
+     * When using Container Service for Kubernetes (ACK) for the first time, you must call the OpenAckService operation to activate the service.
      *
      * @remarks
      *   You can activate ACK by using Alibaba Cloud accounts.
@@ -2269,7 +2275,7 @@ export default class Client extends OpenApi {
      */
     runClusterCheck(clusterId: string, request: $_model.RunClusterCheckRequest): Promise<$_model.RunClusterCheckResponse>;
     /**
-     * 发起集群巡检
+     * Triggers a cluster inspection and generates a report.
      *
      * @param request - RunClusterInspectRequest
      * @param headers - map
@@ -2280,7 +2286,7 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.RunClusterInspectResponse>;
     /**
-     * 发起集群巡检
+     * Triggers a cluster inspection and generates a report.
      *
      * @param request - RunClusterInspectRequest
      * @returns RunClusterInspectResponse
@@ -2497,7 +2503,7 @@ export default class Client extends OpenApi {
      */
     updateClusterAuditLogConfig(clusterid: string, request: $_model.UpdateClusterAuditLogConfigRequest): Promise<$_model.UpdateClusterAuditLogConfigResponse>;
     /**
-     * 更新集群巡检配置
+     * Modifies cluster inspection configurations.
      *
      * @param request - UpdateClusterInspectConfigRequest
      * @param headers - map
@@ -2508,7 +2514,7 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.UpdateClusterInspectConfigResponse>;
     /**
-     * 更新集群巡检配置
+     * Modifies cluster inspection configurations.
      *
      * @param request - UpdateClusterInspectConfigRequest
      * @returns UpdateClusterInspectConfigResponse
@@ -2639,7 +2645,7 @@ export default class Client extends OpenApi {
      */
     updateUserPermissions(uid: string, request: $_model.UpdateUserPermissionsRequest): Promise<$_model.UpdateUserPermissionsResponse>;
     /**
-     * You can call the UpgradeCluster operation to upgrade a cluster by cluster ID.
+     * Outdated Kubernetes versions may have security and stability issues. We recommend that you update the Kubernetes version of your cluster at the earliest opportunity to enjoy the new features of the new Kubernetes version. You can call the UpgradeCluster operation to manually upgrade a cluster.
      *
      * @remarks
      * After successfully calling the UpgradeCluster interface, this API returns the `task_id` of the upgrade task. You can manage this operation task by calling the following task APIs:
@@ -2657,7 +2663,7 @@ export default class Client extends OpenApi {
         [key: string]: string;
     }, runtime: $dara.RuntimeOptions): Promise<$_model.UpgradeClusterResponse>;
     /**
-     * You can call the UpgradeCluster operation to upgrade a cluster by cluster ID.
+     * Outdated Kubernetes versions may have security and stability issues. We recommend that you update the Kubernetes version of your cluster at the earliest opportunity to enjoy the new features of the new Kubernetes version. You can call the UpgradeCluster operation to manually upgrade a cluster.
      *
      * @remarks
      * After successfully calling the UpgradeCluster interface, this API returns the `task_id` of the upgrade task. You can manage this operation task by calling the following task APIs:

package/dist/client.js

@@ -672,6 +672,9 @@ class Client extends openapi_core_1.default {
         if (!$dara.isNull(request.apiAudiences)) {
             body["api_audiences"] = request.apiAudiences;
         }
+        if (!$dara.isNull(request.auditLogConfig)) {
+            body["audit_log_config"] = request.auditLogConfig;
+        }
         if (!$dara.isNull(request.autoRenew)) {
             body["auto_renew"] = request.autoRenew;
         }
@@ -1040,7 +1043,7 @@ class Client extends openapi_core_1.default {
         return await this.createClusterDiagnosisWithOptions(clusterId, request, headers, runtime);
     }
     /**
-     * 创建集群巡检配置
+     * Configures cluster inspection.
      *
      * @param request - CreateClusterInspectConfigRequest
      * @param headers - map
@@ -1077,7 +1080,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateClusterInspectConfigResponse({}));
     }
     /**
-     * 创建集群巡检配置
+     * Configures cluster inspection.
      *
      * @param request - CreateClusterInspectConfigRequest
      * @returns CreateClusterInspectConfigResponse
@@ -1545,7 +1548,7 @@ class Client extends openapi_core_1.default {
         return await this.deleteClusterWithOptions(ClusterId, request, headers, runtime);
     }
     /**
-     * 删除集群巡检配置
+     * Deletes cluster inspection configurations.
      *
      * @param headers - map
      * @param runtime - runtime options for this request RuntimeOptions
@@ -1569,7 +1572,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteClusterInspectConfigResponse({}));
     }
     /**
-     * 删除集群巡检配置
+     * Deletes cluster inspection configurations.
      * @returns DeleteClusterInspectConfigResponse
      */
     async deleteClusterInspectConfig(clusterId) {
@@ -1620,12 +1623,15 @@ class Client extends openapi_core_1.default {
         return await this.deleteClusterNodepoolWithOptions(ClusterId, NodepoolId, request, headers, runtime);
     }
     /**
-     * Removes nodes from a Container Service for Kubernetes (ACK) cluster. When you remove nodes, you can specify whether to release the Elastic Compute Service (ECS) instances and drain the nodes. When you remove nodes, pods on the nodes are migrated. This may adversely affect your businesses. We recommend that you back up data and perform this operation during off-peak hours.
+     * Removes nodes from a Container Service for Kubernetes (ACK) cluster when they are no longer required through the DeleteClusterNodes interface. When removing nodes, you can specify whether to release the Elastic Compute Service (ECS) instances and drain the nodes.
      *
      * @remarks
-     *   When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours.
-     * *   The operation may have unexpected risks. Back up the data before you perform this operation.
-     * *   When you remove a node, the system sets the status of the node to Unschedulable.
+     *   Use this API or the [ACK console](https://cs.console.aliyun.com) for node removal. Do not remove a node by running the `kubectl delete node` command.
+     * *   Never directly release or remove ECS instances through the ECS or Auto Scaling console/APIs. Renew subscription ECS instances before they expire. Violations may cause node termination and removal from the ACK console.
+     * *   If a node pool has the Expected Nodes parameter configured, the node pool automatically scales other ECS instances to maintain the expected number of nodes.
+     * *   When you remove a node, the pods on the node are migrated to other nodes. To prevent service interruptions, remove nodes during off-peak hours. Unexpected risks may arise during node removal. Back up the data in advance.
+     * *   ACK drains the node during node removal. Make sure that other nodes in the cluster have sufficient resources to host the evicted pods.
+     * *   To ensure the pods on the node you want to remove can be successfully scheduled to other nodes, check whether the node affinity rules and scheduling policies of the pods meet the requirements.
      *
      * @param request - DeleteClusterNodesRequest
      * @param headers - map
@@ -1662,12 +1668,15 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteClusterNodesResponse({}));
     }
     /**
-     * Removes nodes from a Container Service for Kubernetes (ACK) cluster. When you remove nodes, you can specify whether to release the Elastic Compute Service (ECS) instances and drain the nodes. When you remove nodes, pods on the nodes are migrated. This may adversely affect your businesses. We recommend that you back up data and perform this operation during off-peak hours.
+     * Removes nodes from a Container Service for Kubernetes (ACK) cluster when they are no longer required through the DeleteClusterNodes interface. When removing nodes, you can specify whether to release the Elastic Compute Service (ECS) instances and drain the nodes.
      *
      * @remarks
-     *   When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours.
-     * *   The operation may have unexpected risks. Back up the data before you perform this operation.
-     * *   When you remove a node, the system sets the status of the node to Unschedulable.
+     *   Use this API or the [ACK console](https://cs.console.aliyun.com) for node removal. Do not remove a node by running the `kubectl delete node` command.
+     * *   Never directly release or remove ECS instances through the ECS or Auto Scaling console/APIs. Renew subscription ECS instances before they expire. Violations may cause node termination and removal from the ACK console.
+     * *   If a node pool has the Expected Nodes parameter configured, the node pool automatically scales other ECS instances to maintain the expected number of nodes.
+     * *   When you remove a node, the pods on the node are migrated to other nodes. To prevent service interruptions, remove nodes during off-peak hours. Unexpected risks may arise during node removal. Back up the data in advance.
+     * *   ACK drains the node during node removal. Make sure that other nodes in the cluster have sufficient resources to host the evicted pods.
+     * *   To ensure the pods on the node you want to remove can be successfully scheduled to other nodes, check whether the node affinity rules and scheduling policies of the pods meet the requirements.
      *
      * @param request - DeleteClusterNodesRequest
      * @returns DeleteClusterNodesResponse
@@ -2646,7 +2655,8 @@ class Client extends openapi_core_1.default {
      * Kubeconfig files store identity and authentication information that is used by clients to access Container Service for Kubernetes (ACK) clusters. To use a kubectl client to manage an ACK cluster, you need to use the corresponding kubeconfig file to connect to the ACK cluster. We recommend that you keep kubeconfig files confidential and revoke kubeconfig files that are not in use. This helps prevent data leaks caused by the disclosure of kubeconfig files.
      *
      * @remarks
-     * >  The default validity period of a kubeconfig file is 3 years. 180 days before a kubeconfig file expires, you can renew it in the Container Service for Kubernetes (ACK) console or by calling API operations. After a kubeconfig file is renewed, the kubeconfig file is valid for 3 years. The previous kubeconfig file still remains valid until expiration. We recommend that you renew your kubeconfig file at the earliest opportunity.
+     *   The default validity period of a kubeconfig file is 3 years. 180 days before a kubeconfig file expires, you can renew it in the Container Service for Kubernetes (ACK) console or by calling API operations. After a kubeconfig file is renewed, the kubeconfig file is valid for 3 years. The previous kubeconfig file still remains valid until expiration. We recommend that you renew your kubeconfig file at the earliest opportunity.
+     * *   We recommend that you keep kubeconfig files confidential and revoke kubeconfig files that are not in use. This helps prevent data leaks caused by the disclosure of kubeconfig files.
      *
      * @param request - DescribeClusterUserKubeconfigRequest
      * @param headers - map
@@ -2683,7 +2693,8 @@ class Client extends openapi_core_1.default {
      * Kubeconfig files store identity and authentication information that is used by clients to access Container Service for Kubernetes (ACK) clusters. To use a kubectl client to manage an ACK cluster, you need to use the corresponding kubeconfig file to connect to the ACK cluster. We recommend that you keep kubeconfig files confidential and revoke kubeconfig files that are not in use. This helps prevent data leaks caused by the disclosure of kubeconfig files.
      *
      * @remarks
-     * >  The default validity period of a kubeconfig file is 3 years. 180 days before a kubeconfig file expires, you can renew it in the Container Service for Kubernetes (ACK) console or by calling API operations. After a kubeconfig file is renewed, the kubeconfig file is valid for 3 years. The previous kubeconfig file still remains valid until expiration. We recommend that you renew your kubeconfig file at the earliest opportunity.
+     *   The default validity period of a kubeconfig file is 3 years. 180 days before a kubeconfig file expires, you can renew it in the Container Service for Kubernetes (ACK) console or by calling API operations. After a kubeconfig file is renewed, the kubeconfig file is valid for 3 years. The previous kubeconfig file still remains valid until expiration. We recommend that you renew your kubeconfig file at the earliest opportunity.
+     * *   We recommend that you keep kubeconfig files confidential and revoke kubeconfig files that are not in use. This helps prevent data leaks caused by the disclosure of kubeconfig files.
      *
      * @param request - DescribeClusterUserKubeconfigRequest
      * @returns DescribeClusterUserKubeconfigResponse
@@ -4421,9 +4432,8 @@ class Client extends openapi_core_1.default {
      * Updates the role-based access control (RBAC) permissions of a Resource Access Management (RAM) user or RAM role. By default, you do not have the RBAC permissions on a Container Service for Kubernetes (ACK) cluster if you are not the cluster owner or you are not using an Alibaba Cloud account. You can call this operation to specify the resources that can be accessed, permission scope, and predefined roles. This helps you better manage the access control on resources in ACK clusters.
      *
      * @remarks
-     * *Precautions**:
-     * *   If you use a Resource Access Management (RAM) user to call the operation, make sure that the RAM user has the permissions to modify the permissions of other RAM users or RAM roles. Otherwise, the `StatusForbidden` or `ForbiddenGrantPermissions` error code is returned after you call the operation. For more information, see [Use a RAM user to grant RBAC permissions to other RAM users](https://help.aliyun.com/document_detail/119035.html).
-     * *   If you update full permissions, the existing permissions of the RAM user or RAM role on the cluster are overwritten. You must specify all the permissions that you want to grant to the RAM user or RAM role in the request parameters when you call the operation.
+     *   If you use a Resource Access Management (RAM) account to call this operation, make sure it has permissions to modify cluster authorization information for other RAM users or RAM roles. Otherwise, the `StatusForbidden` or `ForbiddenGrantPermissions` error code is returned. For more information, see [Use a RAM user to grant RBAC permissions to other RAM users](https://help.aliyun.com/document_detail/119035.html).
+     * *   This operation overwrites all existing cluster permissions for the target RAM user or RAM role. You must specify all the permissions you want to grant to the RAM user or RAM role in the request.
      *
      * @param request - GrantPermissionsRequest
      * @param headers - map
@@ -4453,9 +4463,8 @@ class Client extends openapi_core_1.default {
      * Updates the role-based access control (RBAC) permissions of a Resource Access Management (RAM) user or RAM role. By default, you do not have the RBAC permissions on a Container Service for Kubernetes (ACK) cluster if you are not the cluster owner or you are not using an Alibaba Cloud account. You can call this operation to specify the resources that can be accessed, permission scope, and predefined roles. This helps you better manage the access control on resources in ACK clusters.
      *
      * @remarks
-     * *Precautions**:
-     * *   If you use a Resource Access Management (RAM) user to call the operation, make sure that the RAM user has the permissions to modify the permissions of other RAM users or RAM roles. Otherwise, the `StatusForbidden` or `ForbiddenGrantPermissions` error code is returned after you call the operation. For more information, see [Use a RAM user to grant RBAC permissions to other RAM users](https://help.aliyun.com/document_detail/119035.html).
-     * *   If you update full permissions, the existing permissions of the RAM user or RAM role on the cluster are overwritten. You must specify all the permissions that you want to grant to the RAM user or RAM role in the request parameters when you call the operation.
+     *   If you use a Resource Access Management (RAM) account to call this operation, make sure it has permissions to modify cluster authorization information for other RAM users or RAM roles. Otherwise, the `StatusForbidden` or `ForbiddenGrantPermissions` error code is returned. For more information, see [Use a RAM user to grant RBAC permissions to other RAM users](https://help.aliyun.com/document_detail/119035.html).
+     * *   This operation overwrites all existing cluster permissions for the target RAM user or RAM role. You must specify all the permissions you want to grant to the RAM user or RAM role in the request.
      *
      * @param request - GrantPermissionsRequest
      * @returns GrantPermissionsResponse
@@ -4466,7 +4475,7 @@ class Client extends openapi_core_1.default {
         return await this.grantPermissionsWithOptions(uid, request, headers, runtime);
     }
     /**
-     * Installs a component by specifying the name and version of the component. To enhance Kubernetes capabilities, you can install a variety of components in Container Service for Kubernetes (ACK) clusters, such as fully-managed core components and application, logging and monitoring, network, storage, and security group components.
+     * 为了增强Kubernetes能力，ACK集群支持了多种组件，例如托管的核心组件，应用、日志和监控、网络、存储、安全组件等。您可以调用InstallClusterAddons接口，通过组件名称和版本安装组件。
      *
      * @param request - InstallClusterAddonsRequest
      * @param headers - map
@@ -4493,7 +4502,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.InstallClusterAddonsResponse({}));
     }
     /**
-     * Installs a component by specifying the name and version of the component. To enhance Kubernetes capabilities, you can install a variety of components in Container Service for Kubernetes (ACK) clusters, such as fully-managed core components and application, logging and monitoring, network, storage, and security group components.
+     * 为了增强Kubernetes能力，ACK集群支持了多种组件，例如托管的核心组件，应用、日志和监控、网络、存储、安全组件等。您可以调用InstallClusterAddons接口，通过组件名称和版本安装组件。
      *
      * @param request - InstallClusterAddonsRequest
      * @returns InstallClusterAddonsResponse
@@ -4639,7 +4648,7 @@ class Client extends openapi_core_1.default {
         return await this.listClusterChecksWithOptions(clusterId, request, headers, runtime);
     }
     /**
-     * 获取巡检报告列表
+     * Obtains the details of the cluster inspection report.
      *
      * @param request - ListClusterInspectReportsRequest
      * @param headers - map
@@ -4673,7 +4682,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.ListClusterInspectReportsResponse({}));
     }
     /**
-     * 获取巡检报告列表
+     * Obtains the details of the cluster inspection report.
      *
      * @param request - ListClusterInspectReportsRequest
      * @returns ListClusterInspectReportsResponse
@@ -4895,7 +4904,7 @@ class Client extends openapi_core_1.default {
         return await this.listUserKubeConfigStatesWithOptions(Uid, request, headers, runtime);
     }
     /**
-     * Container Service for Kubernetes (ACK) Pro clusters are developed based on ACK Basic clusters. ACK Pro clusters provide all benefits of ACK managed clusters, such as fully-managed control planes and control plane high availability. In addition, ACK Pro clusters provide you with enhanced reliability, security, and schedulability. ACK Pro clusters are covered by the SLA that supports compensation clauses. ACK Pro clusters are suitable for large-scale businesses that require high stability and security in production environments. We recommend that you migrate from ACK Basic clusters to ACK Pro clusters.
+     * The Container Service for Kubernetes (ACK) managed Pro cluster type is developed based on the ACK managed Basic cluster type. It inherits all benefits of ACK managed clusters, such as fully-managed control planes and control plane high availability. It further enhances reliability, security, scheduling capabilities, and offers service level agreement (SLA)-backed guarantees, making it ideal for enterprise customers with large-scale production workloads requiring high stability and security. You can call the MigrateCluster operation to migrate an ACK managed Basic cluster to an ACK managed Pro cluster.
      *
      * @param request - MigrateClusterRequest
      * @param headers - map
@@ -4929,7 +4938,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.MigrateClusterResponse({}));
     }
     /**
-     * Container Service for Kubernetes (ACK) Pro clusters are developed based on ACK Basic clusters. ACK Pro clusters provide all benefits of ACK managed clusters, such as fully-managed control planes and control plane high availability. In addition, ACK Pro clusters provide you with enhanced reliability, security, and schedulability. ACK Pro clusters are covered by the SLA that supports compensation clauses. ACK Pro clusters are suitable for large-scale businesses that require high stability and security in production environments. We recommend that you migrate from ACK Basic clusters to ACK Pro clusters.
+     * The Container Service for Kubernetes (ACK) managed Pro cluster type is developed based on the ACK managed Basic cluster type. It inherits all benefits of ACK managed clusters, such as fully-managed control planes and control plane high availability. It further enhances reliability, security, scheduling capabilities, and offers service level agreement (SLA)-backed guarantees, making it ideal for enterprise customers with large-scale production workloads requiring high stability and security. You can call the MigrateCluster operation to migrate an ACK managed Basic cluster to an ACK managed Pro cluster.
      *
      * @param request - MigrateClusterRequest
      * @returns MigrateClusterResponse
@@ -5344,7 +5353,7 @@ class Client extends openapi_core_1.default {
         return await this.modifyPolicyInstanceWithOptions(clusterId, policyName, request, headers, runtime);
     }
     /**
-     * When you use Container Service for Kubernetes (ACK) for the first time, you must activate ACK by using an Alibaba Cloud account or RAM user with the required permissions and complete ACK authorization.
+     * When using Container Service for Kubernetes (ACK) for the first time, you must call the OpenAckService operation to activate the service.
      *
      * @remarks
      *   You can activate ACK by using Alibaba Cloud accounts.
@@ -5379,7 +5388,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.OpenAckServiceResponse({}));
     }
     /**
-     * When you use Container Service for Kubernetes (ACK) for the first time, you must activate ACK by using an Alibaba Cloud account or RAM user with the required permissions and complete ACK authorization.
+     * When using Container Service for Kubernetes (ACK) for the first time, you must call the OpenAckService operation to activate the service.
      *
      * @remarks
      *   You can activate ACK by using Alibaba Cloud accounts.
@@ -5889,7 +5898,7 @@ class Client extends openapi_core_1.default {
         return await this.runClusterCheckWithOptions(clusterId, request, headers, runtime);
     }
     /**
-     * 发起集群巡检
+     * Triggers a cluster inspection and generates a report.
      *
      * @param request - RunClusterInspectRequest
      * @param headers - map
@@ -5920,7 +5929,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.RunClusterInspectResponse({}));
     }
     /**
-     * 发起集群巡检
+     * Triggers a cluster inspection and generates a report.
      *
      * @param request - RunClusterInspectRequest
      * @returns RunClusterInspectResponse
@@ -6543,7 +6552,7 @@ class Client extends openapi_core_1.default {
         return await this.updateClusterAuditLogConfigWithOptions(clusterid, request, headers, runtime);
     }
     /**
-     * 更新集群巡检配置
+     * Modifies cluster inspection configurations.
      *
      * @param request - UpdateClusterInspectConfigRequest
      * @param headers - map
@@ -6580,7 +6589,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.UpdateClusterInspectConfigResponse({}));
     }
     /**
-     * 更新集群巡检配置
+     * Modifies cluster inspection configurations.
      *
      * @param request - UpdateClusterInspectConfigRequest
      * @returns UpdateClusterInspectConfigResponse
@@ -6902,7 +6911,7 @@ class Client extends openapi_core_1.default {
         return await this.updateUserPermissionsWithOptions(uid, request, headers, runtime);
     }
     /**
-     * You can call the UpgradeCluster operation to upgrade a cluster by cluster ID.
+     * Outdated Kubernetes versions may have security and stability issues. We recommend that you update the Kubernetes version of your cluster at the earliest opportunity to enjoy the new features of the new Kubernetes version. You can call the UpgradeCluster operation to manually upgrade a cluster.
      *
      * @remarks
      * After successfully calling the UpgradeCluster interface, this API returns the `task_id` of the upgrade task. You can manage this operation task by calling the following task APIs:
@@ -6952,7 +6961,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.UpgradeClusterResponse({}));
     }
     /**
-     * You can call the UpgradeCluster operation to upgrade a cluster by cluster ID.
+     * Outdated Kubernetes versions may have security and stability issues. We recommend that you update the Kubernetes version of your cluster at the earliest opportunity to enjoy the new features of the new Kubernetes version. You can call the UpgradeCluster operation to manually upgrade a cluster.
      *
      * @remarks
      * After successfully calling the UpgradeCluster interface, this API returns the `task_id` of the upgrade task. You can manage this operation task by calling the following task APIs: