@alicloud/cs20151215 7.2.1 → 7.2.3

package/src/models/Addon.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class Addon extends $dara.Model {
   /**
    * @remarks
-   * The configuration of the component.
+   * The component configuration.
    * 
    * @example
    * {\\"IngressSlbNetworkType\\":\\"internet\\"}
@@ -13,8 +13,7 @@ export class Addon extends $dara.Model {
   config?: string;
   /**
    * @remarks
-   * Specifies whether to disable default installation. When a cluster is created, required components and additional components such as log components are installed by default. You can disable this default behavior and install these components later by calling the component installation API or by using the console. Valid values:
-   * 
+   * Specifies whether to disable default installation. When a cluster is created, in addition to required components, additional components such as log components are installed by default. You can disable this default behavior and install these components later by calling the component installation API or through the console. Valid values:
    * - `true`: Disables default installation.
    * - `false`: Allows default installation.
    * 
@@ -24,7 +23,7 @@ export class Addon extends $dara.Model {
   disabled?: boolean;
   /**
    * @remarks
-   * The name of the component.
+   * The component name.
    * 
    * @example
    * nginx-ingress-controller
@@ -32,7 +31,7 @@ export class Addon extends $dara.Model {
   name?: string;
   /**
    * @remarks
-   * The version of the component.
+   * The component version.
    * 
    * @example
    * v1.9.3-aliyun.1

package/src/models/AttachInstancesRequest.ts

@@ -7,14 +7,14 @@ import { Tag } from "./Tag";
 export class AttachInstancesRequest extends $dara.Model {
   /**
    * @remarks
-   * The CPU management policy of the node. The following policies are supported for clusters running version 1.12.6 or later:
+   * The CPU management policy for the node. The following two policies are supported when the cluster version is 1.12.6 or later:
    * 
-   * - `static`: Allows pods with certain resource characteristics on the node to be granted enhanced CPU affinity and exclusivity.
-   * - `none`: Uses the existing default CPU affinity scheme.
+   * - `static`: allows you to enhance CPU affinity and exclusivity for pods with specific resource characteristics on the node.
+   * - `none`: uses the existing default CPU affinity policy.
    * 
    * Default value: `none`.
    * 
-   * > After you specify `nodepool_id`, this parameter is not supported.
+   * > This parameter is not supported if nodepool_id is specified.
    * 
    * @example
    * none
@@ -24,18 +24,16 @@ export class AttachInstancesRequest extends $dara.Model {
    * @remarks
    * Specifies whether to store container data and images on a data cloud disk. Valid values:
    * 
-   * - `true`: Stores container data and images on a data cloud disk.
-   * 
-   * - `false`: Does not store container data and images on a data cloud disk.
+   * - `true`: stores container data and images on a data cloud disk.
+   * - `false`: does not store container data and images on a data cloud disk.
    * 
    * Default value: `false`.
    * 
-   * 
    * Data cloud disk mounting rules:
    * 
-   * - If the ECS instance has data cloud disks attached and the file system of the last data cloud disk is not initialized, the system automatically formats the data cloud disk to EXT4. The data cloud disk is then used to store the content of /var/lib/docker and /var/lib/kubelet, which are the default data directories for the Docker container runtime and the kubelet component, respectively.
-   * - If the ECS instance does not have data cloud disks attached, no new data cloud disk is mounted.
-   * > If you choose to store data on a data cloud disk and the ECS instance already has data cloud disks attached, the existing data on the data cloud disk will be lost. Back up your data in advance.
+   * - If the ECS instance has data cloud disks attached and the file system of the last data cloud disk is not initialized, the system automatically formats the data cloud disk to EXT4 to store the /var/lib/docker and /var/lib/kubelet directories, which are the default data directories for the Docker container runtime and kubelet component.
+   * - If the ECS instance does not have data cloud disks attached, no new data cloud disk is attached.
+   * > If you choose to store data on a data cloud disk and the ECS instance already has data cloud disks attached, the existing data on the data cloud disks will be lost. Back up your data first.
    * 
    * @example
    * false
@@ -46,10 +44,9 @@ export class AttachInstancesRequest extends $dara.Model {
    * The custom image ID.
    * 
    * - If you specify a custom image ID, the system cloud disk image of the instance is replaced with the custom image.
-   * 
    * - If you do not specify this parameter, the default system image is used.
    * 
-   * > After you specify `nodepool_id`, this parameter is not supported.
+   * > This parameter is not supported if nodepool_id is specified.
    * 
    * @example
    * aliyun_2_1903_x64_20G_alibase_20200529.vhd
@@ -64,15 +61,14 @@ export class AttachInstancesRequest extends $dara.Model {
   instances?: string[];
   /**
    * @remarks
-   * Specifies whether the node to be added is an edge node, which is an Edge Node Service (ENS) node. Valid values:
+   * Specifies whether the node to be added is an edge node, namely an ENS node. Valid values:
    * 
    * - `true`: The node to be added is an edge node.
-   * 
    * - `false`: The node to be added is not an edge node.
    * 
    * Default value: `false`.
    * 
-   * > If the node is an edge node, set this parameter to `true` to identify the node type as an ENS node.
+   * > If the node is an edge node, you must set this parameter to `true` to identify the node type as an ENS node.
    * 
    * @example
    * false
@@ -82,9 +78,8 @@ export class AttachInstancesRequest extends $dara.Model {
    * @remarks
    * Specifies whether to retain the original instance name. Valid values:
    * 
-   * - `true`: Retains the instance name.
-   * 
-   * - `false`: Does not retain the instance name.
+   * - `true`: retains the instance name.
+   * - `false`: does not retain the instance name.
    * 
    * Default value: `false`.
    * 
@@ -94,9 +89,8 @@ export class AttachInstancesRequest extends $dara.Model {
   keepInstanceName?: boolean;
   /**
    * @remarks
-   * The name of the key pair for the instances to be added.
-   * You need to specify only one of key_pair and password, or you can leave both parameters empty.
-   * > After you specify `nodepool_id`, this parameter is not supported.
+   * The name of the key pair for the instances to be added. You can specify either the key_pair or password parameter, or leave both empty.
+   * > This parameter is not supported if nodepool_id is specified.
    * 
    * @example
    * security-key
@@ -112,11 +106,11 @@ export class AttachInstancesRequest extends $dara.Model {
   nodepoolId?: string;
   /**
    * @remarks
-   * The SSH logon password for the instances to be added. You need to specify only one of key_pair and password, or you can leave both parameters empty.
+   * The SSH logon password for the instances to be added. You can specify either the key_pair or password parameter, or leave both empty.
    * 
    * The password must meet the following requirements:
    * - The password must be 8 to 30 characters in length.
-   * - The password must contain at least uppercase letters, lowercase letters, digits, and special characters.
+   * - The password must contain uppercase letters, lowercase letters, digits, and special characters.
    * - The password cannot contain backslashes (\\) or double quotation marks (").
    * 
    * For security purposes, the password is encrypted during transmission.
@@ -133,39 +127,39 @@ export class AttachInstancesRequest extends $dara.Model {
   /**
    * @remarks
    * The container runtime.
-   * > After you specify `nodepool_id`, this parameter is not supported.
+   * > This parameter is not supported if nodepool_id is specified.
    * 
    * name: the name of the container runtime. ACK supports the following three container runtimes:
    * 
-   * - containerd: Recommended. Supported by all cluster versions.
-   * - Sandboxed-Container.runv: Sandboxed container that provides higher isolation. Supported by clusters running version 1.24 or earlier.
-   * - docker: Supported by clusters running version 1.22 or earlier.
+   * - containerd: recommended. Supported by all cluster versions.
+   * - Sandboxed-Container.runv: sandboxed container. Provides higher isolation. Supported by clusters runtime version 1.24 and earlier.
+   * - docker: supported by clusters runtime version 1.22 and earlier.
    * 
    * Default value: containerd.
    * 
-   * containerd: the container runtime version. Default value: the latest version.
+   * containerd: the version of the container runtime. The default value is the latest version.
    * 
-   * For more information about changes to the sandboxed container runtime, see [Sandboxed container runtime release notes](https://help.aliyun.com/document_detail/160312.html).
+   * For more information about the changes to the sandboxed container runtime, see [Sandboxed container runtime release notes](https://help.aliyun.com/document_detail/160312.html).
    */
   runtime?: Runtime;
   /**
    * @remarks
    * The node labels. Label definition rules:
    * 
-   * - Labels are case-sensitive key-value pairs. You can configure up to 20 labels.
-   * - Label keys cannot be duplicate and can be up to 64 characters in length.
+   * - A label is a case-sensitive key-value pair. You can configure up to 20 labels.
+   * - Label keys must be unique and can be up to 64 characters in length.
    * - Label values can be empty and can be up to 128 characters in length.
-   * - Label keys and label values cannot start with `aliyun`, `acs:`, `https://`, or `http://`.
+   * - Label keys and values cannot start with `aliyun`, `acs:`, `https://`, or `http://`.
    * 
    * For more information, see [Labels and Selectors](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set).
-   * > After you specify `nodepool_id`, this parameter is not supported.
+   * > This parameter is not supported if nodepool_id is specified.
    */
   tags?: Tag[];
   /**
    * @remarks
-   * The node user data. For more information, see [Generate instance user data](https://help.aliyun.com/document_detail/49121.html).
+   * The custom data for the node. For more information, see [Generate instance user data](https://help.aliyun.com/document_detail/49121.html).
    * 
-   * > After you specify `nodepool_id`, this parameter is not supported.
+   * > This parameter is not supported if nodepool_id is specified.
    * 
    * @example
    * IyEvdXNyL2Jpbi9iYXNoCmVjaG8gIkhlbGxvIEFDSyEi

package/src/models/AttachInstancesToNodePoolRequest.ts

@@ -5,20 +5,20 @@ import * as $dara from '@darabonba/typescript';
 export class AttachInstancesToNodePoolRequest extends $dara.Model {
   /**
    * @remarks
-   * Specifies whether to store container data and images on a data cloud disk. Valid values:
+   * Specifies whether to store container data and images on data cloud disks. Valid values:
    * 
-   * - `true`: Stores container data and images on a data cloud disk.
+   * - `true`: Stores container data and images on data cloud disks.
    * 
-   * - `false`: Does not store container data and images on a data cloud disk.
+   * - `false`: Does not store container data and images on data cloud disks.
    * 
    * Default value: `false`.
    * 
    * 
    * Data cloud disk mounting rules:
    * 
-   * - If the ECS instance has data cloud disks mounted and the file system of the last data cloud disk is not initialized, the system automatically formats the data cloud disk to EXT4 to store the content of /var/lib/docker and /var/lib/kubelet.
-   * - If the ECS instance has no data cloud disks mounted, no new data cloud disk is mounted.
-   * >If you choose to store data on a data cloud disk and the ECS instance already has data cloud disks mounted, the existing data on the data cloud disk is lost. Back up your data in advance.
+   * - If the ECS instance has data cloud disks mounted and the file system of the last data cloud disk is not initialized, the system automatically formats the data cloud disk to EXT4 to store the /var/lib/docker and /var/lib/kubelet directories.
+   * - If the ECS instance does not have data cloud disks mounted, no new data cloud disks are mounted.
+   * > If you choose to store data on data cloud disks and the ECS instance already has data cloud disks mounted, the existing data on the data cloud disks will be lost. Back up your data in advance.
    * 
    * @example
    * false
@@ -45,7 +45,7 @@ export class AttachInstancesToNodePoolRequest extends $dara.Model {
   keepInstanceName?: boolean;
   /**
    * @remarks
-   * The SSH logon password of the instances to be added.
+   * The SSH logon password for the instances to be added.
    * 
    * @example
    * ******

package/src/models/CheckControlPlaneLogEnableResponseBody.ts

@@ -13,16 +13,16 @@ export class CheckControlPlaneLogEnableResponseBody extends $dara.Model {
   aliuid?: string;
   /**
    * @remarks
-   * The list of components for which control plane logging is enabled.
+   * The list of components for which control plane logging is currently enabled.
    * 
    * This parameter is required.
    */
   components?: string[];
   /**
    * @remarks
-   * The name of the SLS project that stores the control plane component logs.
+   * The name of the SLS project where control plane component logs are stored.
    * 
-   * Default value: k8s-log-$Cluster ID.
+   * Default value: k8s-log-$ClusterId.
    * 
    * @example
    * k8s-log-c5b5e80b0b64a4bf6939d2d8fbbc5****
@@ -30,7 +30,7 @@ export class CheckControlPlaneLogEnableResponseBody extends $dara.Model {
   logProject?: string;
   /**
    * @remarks
-   * The data retention period of logs in the SLS Logstore. Unit: days.
+   * The retention period of logs in the SLS Logstore. Unit: days.
    * 
    * @example
    * 30

package/src/models/CheckServiceRoleRequest.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class CheckServiceRoleRequestRoles extends $dara.Model {
   /**
    * @remarks
-   * Container service role name. For information about container service roles and permission scopes included in ACK, see [ACK service roles](https://help.aliyun.com/document_detail/86483.html).
+   * The name of the service role. For more information about the service roles and permission scopes in Container Service for Kubernetes (ACK), see [Service roles for ACK](https://help.aliyun.com/document_detail/86483.html).
    * 
    * This parameter is required.
    * 

package/src/models/CheckServiceRoleResponseBody.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class CheckServiceRoleResponseBodyRoles extends $dara.Model {
   /**
    * @remarks
-   * Indicates whether the role has been authorized.
+   * Indicates whether the service role is authorized.
    * 
    * @example
    * true
@@ -13,7 +13,7 @@ export class CheckServiceRoleResponseBodyRoles extends $dara.Model {
   granted?: boolean;
   /**
    * @remarks
-   * The message returned when the role is not authorized.
+   * The prompt message when the service role is not authorized.
    * 
    * @example
    * The role does not exist: AliyunCSManagedAutoScalerRole
@@ -21,7 +21,7 @@ export class CheckServiceRoleResponseBodyRoles extends $dara.Model {
   message?: string;
   /**
    * @remarks
-   * The service role name.
+   * The name of the service role.
    * 
    * @example
    * AliyunCSManagedAutoScalerRole
@@ -55,7 +55,7 @@ export class CheckServiceRoleResponseBodyRoles extends $dara.Model {
 export class CheckServiceRoleResponseBody extends $dara.Model {
   /**
    * @remarks
-   * The service role check results.
+   * The check results of the service roles.
    */
   roles?: CheckServiceRoleResponseBodyRoles[];
   static names(): { [key: string]: string } {

package/src/models/CleanClusterUserPermissionsRequest.ts

@@ -6,8 +6,7 @@ export class CleanClusterUserPermissionsRequest extends $dara.Model {
   /**
    * @remarks
    * Specifies whether to force delete the specified KubeConfig. Valid values:
-   * 
-   * - false (default): Before deleting the KubeConfig, the system checks whether cluster access records exist within the last seven days. If access records exist or cannot be retrieved, the deletion is not allowed.
+   * - false (default): Before deleting the KubeConfig, the system checks whether there are cluster access records within the last seven days. If such records exist or cannot be found, the deletion is not allowed.
    * - true: Force deletes the KubeConfig without checking cluster access records.
    * 
    * @example

package/src/models/CleanUserPermissionsRequest.ts

@@ -5,13 +5,13 @@ import * as $dara from '@darabonba/typescript';
 export class CleanUserPermissionsRequest extends $dara.Model {
   /**
    * @remarks
-   * The list of cluster IDs. If this list is specified, only the KubeConfig credentials and RBAC permissions of the current user in the specified clusters are cleaned up.
+   * The list of cluster IDs. If you specify this list, only the KubeConfig credentials and RBAC permissions of the specified user in the listed clusters are cleared.
    */
   clusterIds?: string[];
   /**
    * @remarks
    * Specifies whether to force delete the specified KubeConfig. Valid values:
-   * - false (default): Before deleting the KubeConfig, the system checks whether cluster access records exist within the last seven days. If access records exist or cannot be retrieved, the deletion is not allowed.
+   * - false (default): Checks whether there are cluster access records within the last seven days before deleting the KubeConfig. If such records exist or cannot be found, the deletion is not allowed.
    * - true: Force deletes the KubeConfig without checking cluster access records.
    * 
    * @example

package/src/models/CleanUserPermissionsShrinkRequest.ts

@@ -5,13 +5,13 @@ import * as $dara from '@darabonba/typescript';
 export class CleanUserPermissionsShrinkRequest extends $dara.Model {
   /**
    * @remarks
-   * The list of cluster IDs. If this list is specified, only the KubeConfig credentials and RBAC permissions of the current user in the specified clusters are cleaned up.
+   * The list of cluster IDs. If you specify this list, only the KubeConfig credentials and RBAC permissions of the specified user in the listed clusters are cleared.
    */
   clusterIdsShrink?: string;
   /**
    * @remarks
    * Specifies whether to force delete the specified KubeConfig. Valid values:
-   * - false (default): Before deleting the KubeConfig, the system checks whether cluster access records exist within the last seven days. If access records exist or cannot be retrieved, the deletion is not allowed.
+   * - false (default): Checks whether there are cluster access records within the last seven days before deleting the KubeConfig. If such records exist or cannot be found, the deletion is not allowed.
    * - true: Force deletes the KubeConfig without checking cluster access records.
    * 
    * @example

package/src/models/CreateAutoRepairPolicyRequest.ts

@@ -125,7 +125,7 @@ export class CreateAutoRepairPolicyRequestRulesRepairProcedureInterventionInquir
 export class CreateAutoRepairPolicyRequestRulesRepairProcedureIntervention extends $dara.Model {
   /**
    * @remarks
-   * The label configuration for authorization confirmation. Adding the following labels to the node indicates that you authorize ACK to execute the action for this stage. After completing the action for this stage, ACK automatically removes the authorization inquiry and authorization confirmation labels corresponding to this stage. If you do not add the following labels in time to grant authorization, ACK will not execute the action for this stage and subsequent actions, and the node may remain in an impaired state.
+   * The label configuration for authorization confirmation. Adding the following labels to the node indicates that you authorize ACK to execute the operations in this stage. After completing the operations in this stage, ACK automatically removes the authorization inquiry and confirmation labels corresponding to this stage. If you do not add the following labels in time to grant authorization, ACK will not execute the actions in this stage and subsequent stages, and the node may remain in a damaged state.
    */
   approvedLabel?: CreateAutoRepairPolicyRequestRulesRepairProcedureInterventionApprovedLabel;
   /**
@@ -138,7 +138,7 @@ export class CreateAutoRepairPolicyRequestRulesRepairProcedureIntervention exten
   enable?: boolean;
   /**
    * @remarks
-   * The label configuration for authorization inquiry. When this stage is reached, ACK adds the following labels to your node and waits for your authorization to execute the action for this stage.
+   * The label configuration for authorization inquiry. When this stage is reached, ACK adds the following labels to your node and waits for your authorization to execute the actions in this stage.
    */
   inquiringLabel?: CreateAutoRepairPolicyRequestRulesRepairProcedureInterventionInquiringLabel;
   /**
@@ -190,7 +190,7 @@ export class CreateAutoRepairPolicyRequestRulesRepairProcedure extends $dara.Mod
   config?: { [key: string]: any };
   /**
    * @remarks
-   * The manual intervention process.
+   * The configuration for the manual intervention procedure.
    */
   intervention?: CreateAutoRepairPolicyRequestRulesRepairProcedureIntervention;
   /**
@@ -283,7 +283,7 @@ export class CreateAutoRepairPolicyRequest extends $dara.Model {
   name?: string;
   /**
    * @remarks
-   * The resource subtype to which the self-healing rule can be bound.
+   * The resource subtype that can be associated with the self-healing rule.
    * 
    * @example
    * ess
@@ -291,7 +291,7 @@ export class CreateAutoRepairPolicyRequest extends $dara.Model {
   resourceSubType?: string;
   /**
    * @remarks
-   * The resource type to which the self-healing rule can be bound.
+   * The resource type that can be associated with the self-healing rule.
    * 
    * @example
    * nodepool
@@ -299,7 +299,7 @@ export class CreateAutoRepairPolicyRequest extends $dara.Model {
   resourceType?: string;
   /**
    * @remarks
-   * The list of self-healing sub-rules.
+   * The list of self-healing subrules.
    * 
    * @example
    * ["np-xxx"]

package/src/models/CreateClusterDiagnosisRequest.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class CreateClusterDiagnosisRequest extends $dara.Model {
   /**
    * @remarks
-   * The parameters used to specify the diagnosis target. The following examples show the parameters for different diagnosis types:
+   * The parameters used to specify the diagnosis target. Examples of parameters for different diagnosis types:
    * 
    * node:
    * ```

package/src/models/CreateClusterInspectConfigRequest.ts

@@ -20,7 +20,7 @@ export class CreateClusterInspectConfigRequest extends $dara.Model {
   enabled?: boolean;
   /**
    * @remarks
-   * The inspection cycle defined by using the RFC5545 Recurrence Rule syntax. You must specify BYHOUR and BYMINUTE. Only FREQ=DAILY is supported. COUNT and UNTIL are not supported.
+   * The inspection cycle defined by using the RFC5545 Recurrence Rule syntax. BYHOUR and BYMINUTE must be specified. Only FREQ=DAILY is supported. COUNT or UNTIL is not supported.
    * 
    * This parameter is required.
    *