@alicloud/cs20151215 7.2.0 → 7.2.1

package/src/models/Addon.ts

@@ -13,10 +13,10 @@ export class Addon extends $dara.Model {
   config?: string;
   /**
    * @remarks
-   * Specifies whether to disable automatic installation. When you create a cluster, some additional log components are automatically installed in addition to the required components. You can disable the automatic installations of a component and install the component later by calling the component API or in the corresponding console. Valid values:
+   * 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:
    * 
-   * *   `true`: disables the automatic installation of a component.
-   * *   `false`: allows the automatic installation of a component.
+   * - `true`: Disables default installation.
+   * - `false`: Allows default installation.
    * 
    * @example
    * false
@@ -24,7 +24,7 @@ export class Addon extends $dara.Model {
   disabled?: boolean;
   /**
    * @remarks
-   * The component name.
+   * The name of the component.
    * 
    * @example
    * nginx-ingress-controller

package/src/models/AttachInstancesRequest.ts

@@ -7,7 +7,7 @@ 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 of version 1.12.6 or later:
+   * The CPU management policy of the node. The following policies are supported for clusters running version 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.
@@ -33,9 +33,9 @@ export class AttachInstancesRequest extends $dara.Model {
    * 
    * 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 (the default data directories for the Docker container runtime and the kubelet component, respectively).
-   * - 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, existing data on the data cloud disk is 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. 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.
    * 
    * @example
    * false
@@ -64,7 +64,7 @@ export class AttachInstancesRequest extends $dara.Model {
   instances?: string[];
   /**
    * @remarks
-   * Specifies whether the node to be added is an edge node, that is, an Edge Node Service (ENS) node. Valid values:
+   * Specifies whether the node to be added is an edge node, which is an Edge Node Service (ENS) node. Valid values:
    * 
    * - `true`: The node to be added is an edge node.
    * 
@@ -94,7 +94,8 @@ export class AttachInstancesRequest extends $dara.Model {
   keepInstanceName?: boolean;
   /**
    * @remarks
-   * The name of the key pair for the instances to be added. Specify either key_pair or password. You can also leave both parameters empty.
+   * 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.
    * 
    * @example
@@ -111,14 +112,14 @@ export class AttachInstancesRequest extends $dara.Model {
   nodepoolId?: string;
   /**
    * @remarks
-   * The SSH logon password for the instances to be added. Specify either key_pair or password. You can also leave both parameters empty.
+   * 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 password must meet the following requirements:
    * - The password must be 8 to 30 characters in length.
-   * - The password must contain uppercase letters, lowercase letters, digits, and special characters at the same time.
+   * - The password must contain at least uppercase letters, lowercase letters, digits, and special characters.
    * - The password cannot contain backslashes (\\) or double quotation marks (").
    * 
-   * The password is encrypted during transmission for security purposes.
+   * For security purposes, the password is encrypted during transmission.
    * 
    * @example
    * Hello1234
@@ -134,27 +135,27 @@ export class AttachInstancesRequest extends $dara.Model {
    * The container runtime.
    * > After you specify `nodepool_id`, this parameter is not supported.
    * 
-   * name: The name of the container runtime. ACK supports the following three container runtimes:
+   * 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 of version 1.24 or earlier.
-   * - docker: Supported by clusters of version 1.22 or earlier.
+   * - 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.
    * 
    * Default value: containerd.
    * 
-   * containerd: The container runtime version. Default value: the latest version.
+   * containerd: the container runtime version. Default value: the latest version.
    * 
-   * For more information about changes to the sandboxed container runtime, see [Release notes for the sandboxed container runtime](https://help.aliyun.com/document_detail/160312.html).
+   * For more information about 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 set up to 20 labels.
+   * - 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.
    * - Label values can be empty and can be up to 128 characters in length.
-   * - Label keys and values cannot start with `aliyun`, `acs:`, `https://`, or `http://`.
+   * - Label keys and label 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.
@@ -162,7 +163,7 @@ export class AttachInstancesRequest extends $dara.Model {
   tags?: Tag[];
   /**
    * @remarks
-   * The instance user data of the node. For more information, see [Generate instance user data](https://help.aliyun.com/document_detail/49121.html).
+   * The node user data. 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.
    * 

package/src/models/AttachInstancesToNodePoolRequest.ts

@@ -16,9 +16,9 @@ export class AttachInstancesToNodePoolRequest extends $dara.Model {
    * 
    * 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 as EXT4 to store /var/lib/docker and /var/lib/kubelet.
-   * - If the ECS instance has no 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, 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 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.
    * 
    * @example
    * false

package/src/models/CheckControlPlaneLogEnableResponseBody.ts

@@ -20,7 +20,7 @@ export class CheckControlPlaneLogEnableResponseBody extends $dara.Model {
   components?: string[];
   /**
    * @remarks
-   * The name of the Simple Log Service (SLS) project that stores the control plane component logs.
+   * The name of the SLS project that stores the control plane component logs.
    * 
    * Default value: k8s-log-$Cluster ID.
    * 

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 service role has been granted.
+   * Indicates whether the role has been authorized.
    * 
    * @example
    * true
@@ -13,7 +13,7 @@ export class CheckServiceRoleResponseBodyRoles extends $dara.Model {
   granted?: boolean;
   /**
    * @remarks
-   * The prompt message returned when the service role is not granted.
+   * The message returned when the role is not authorized.
    * 
    * @example
    * The role does not exist: AliyunCSManagedAutoScalerRole

package/src/models/CleanClusterUserPermissionsRequest.ts

@@ -6,6 +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.
    * - true: Force deletes the KubeConfig without checking cluster access records.
    * 

package/src/models/CreateAutoRepairPolicyRequest.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class CreateAutoRepairPolicyRequestRulesIncidents extends $dara.Model {
   /**
    * @remarks
-   * The name of the fault.
+   * The name of the incident.
    * 
    * @example
    * Node.FaultNeedReboot.HOST
@@ -13,7 +13,7 @@ export class CreateAutoRepairPolicyRequestRulesIncidents extends $dara.Model {
   name?: string;
   /**
    * @remarks
-   * The type of the fault.
+   * The type of the incident.
    * 
    * @example
    * system
@@ -125,7 +125,7 @@ export class CreateAutoRepairPolicyRequestRulesRepairProcedureInterventionInquir
 export class CreateAutoRepairPolicyRequestRulesRepairProcedureIntervention extends $dara.Model {
   /**
    * @remarks
-   * The label configuration for authorization confirmation. When you add the following label to the node, you authorize ACK to execute the action in this stage. After completing the action in this stage, ACK automatically removes the authorization inquiry and authorization confirmation labels for this stage. If you do not add the following label to authorize the action promptly, ACK does not execute the action in this stage or subsequent actions, and the node may remain in a damaged state.
+   * 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.
    */
   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 label to your node and waits for you to authorize the execution of the action in 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 action for this stage.
    */
   inquiringLabel?: CreateAutoRepairPolicyRequestRulesRepairProcedureInterventionInquiringLabel;
   /**
@@ -185,12 +185,12 @@ export class CreateAutoRepairPolicyRequestRulesRepairProcedureIntervention exten
 export class CreateAutoRepairPolicyRequestRulesRepairProcedure extends $dara.Model {
   /**
    * @remarks
-   * The configuration parameters of the repair procedure.
+   * The configuration parameters for the repair procedure.
    */
   config?: { [key: string]: any };
   /**
    * @remarks
-   * The configuration for manual intervention in the procedure.
+   * The manual intervention process.
    */
   intervention?: CreateAutoRepairPolicyRequestRulesRepairProcedureIntervention;
   /**
@@ -235,7 +235,7 @@ export class CreateAutoRepairPolicyRequestRulesRepairProcedure extends $dara.Mod
 export class CreateAutoRepairPolicyRequestRules extends $dara.Model {
   /**
    * @remarks
-   * The list of identified faults.
+   * The list of identified incidents.
    */
   incidents?: CreateAutoRepairPolicyRequestRulesIncidents[];
   /**
@@ -283,7 +283,7 @@ export class CreateAutoRepairPolicyRequest extends $dara.Model {
   name?: string;
   /**
    * @remarks
-   * The resource subtype that the self-healing rule can be bound to.
+   * The resource subtype to which the self-healing rule can be bound.
    * 
    * @example
    * ess
@@ -291,7 +291,7 @@ export class CreateAutoRepairPolicyRequest extends $dara.Model {
   resourceSubType?: string;
   /**
    * @remarks
-   * The resource type that the self-healing rule can be bound to.
+   * The resource type to which the self-healing rule can be bound.
    * 
    * @example
    * nodepool

package/src/models/CreateAutoRepairPolicyResponseBody.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class CreateAutoRepairPolicyResponseBody extends $dara.Model {
   /**
    * @remarks
-   * The self-healing rule ID.
+   * The ID of the self-healing rule.
    * 
    * @example
    * r-xxxxxxx

package/src/models/CreateAutoscalingConfigRequest.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class CreateAutoscalingConfigRequest extends $dara.Model {
   /**
    * @remarks
-   * The scale-down trigger delay. The time interval between detecting a scale-down need (reaching the scale-down threshold) and actually performing the scale-down operation (reducing the number of Pods).
+   * The scale-in trigger delay, which is the time interval between when a scale-in need is detected (the scale-in threshold is reached) and when the scale-in operation (reducing the number of Pods) is actually performed.
    * 
    * Valid values: [1,60]. Unit: minutes.
    * 
@@ -17,9 +17,9 @@ export class CreateAutoscalingConfigRequest extends $dara.Model {
   coolDownDuration?: string;
   /**
    * @remarks
-   * Specifies whether cluster-autoscaler evicts DaemonSet Pods on nodes during scale-down. Valid values:
-   * - `true`: DaemonSet Pods are evicted.
-   * - `false`: DaemonSet Pods are not evicted.
+   * Specifies whether cluster-autoscaler evicts DaemonSet Pods on a node during scale-in. Valid values:
+   * - `true`: Eviction is performed.
+   * - `false`: Eviction is not performed.
    * 
    * @example
    * false
@@ -29,8 +29,8 @@ export class CreateAutoscalingConfigRequest extends $dara.Model {
    * @remarks
    * The node pool scale-out order policy. Valid values:
    * - `least-waste`: The default policy. If multiple node pools are available for scale-out, the node pool with the least resource waste is selected.
-   * - `random`: The random policy. If multiple node pools are available for scale-out, a random node pool is selected.
-   * - `priority`: The priority policy. If multiple node pools are available for scale-out, the node pool with the highest priority is selected based on the custom scaling group order you defined. Node pool priorities are defined by the `priorities` parameter.
+   * - `random`: The random policy. If multiple node pools are available for scale-out, a node pool is randomly selected.
+   * - `priority`: The priority policy. If multiple node pools are available for scale-out, the node pool with the highest priority based on your custom scaling group order is selected. Node pool priorities are defined by the `priorities` parameter.
    * 
    * @example
    * least-waste
@@ -38,9 +38,9 @@ export class CreateAutoscalingConfigRequest extends $dara.Model {
   expander?: string;
   /**
    * @remarks
-   * The GPU scale-down threshold. The ratio of requested resources to total resources on a node.
+   * The GPU scale-in threshold, which is the ratio of requested resources to total resources on a node.
    * 
-   * A GPU node can be scaled down only when this ratio falls below the configured threshold, meaning the CPU, memory, and GPU utilization of the node are all below the GPU scale-down threshold.
+   * A GPU node can be scaled in only when this ratio falls below the configured threshold, meaning the CPU, memory, and GPU resource utilization of the node are all below the GPU scale-in threshold.
    * 
    * Valid values: [0.1~1].
    * 
@@ -52,7 +52,7 @@ export class CreateAutoscalingConfigRequest extends $dara.Model {
   gpuUtilizationThreshold?: string;
   /**
    * @remarks
-   * The timeout period that cluster-autoscaler waits for Pod termination during node draining in scale-down scenarios.
+   * The timeout period for cluster-autoscaler to wait for Pod termination during node draining in a scale-in scenario.
    * 
    * Unit: seconds.
    * 
@@ -64,7 +64,7 @@ export class CreateAutoscalingConfigRequest extends $dara.Model {
   maxGracefulTerminationSec?: number;
   /**
    * @remarks
-   * The minimum number of Pods allowed in each ReplicaSet before a node can be scaled down.
+   * The minimum number of Pods allowed in each ReplicaSet before a node can be scaled in.
    * 
    * Default value: 0.
    * 
@@ -74,17 +74,17 @@ export class CreateAutoscalingConfigRequest extends $dara.Model {
   minReplicaCount?: number;
   /**
    * @remarks
-   * The priority configuration for automatic scaling. After you create a node pool with auto scaling enabled, you can choose whether to configure a priority policy and priority settings by using [Enable node auto scaling](https://help.aliyun.com/document_detail/119099.html) to assign priorities to the scaling groups of specified auto scaling node pools.
+   * The priority configuration for auto scaling. After you create a node pool with elastic scaling enabled, you can configure priority policies and priority settings for the scaling groups of specified auto scaling node pools by using [Enable node auto scaling](https://help.aliyun.com/document_detail/119099.html).
    * 
    * Valid values: [1, 100]. The value must be a positive integer. A larger value indicates a higher priority.
    */
   priorities?: { [key: string]: string[] };
   /**
    * @remarks
-   * Specifies whether to delete the corresponding Kubernetes Node object after a node is successfully scaled down in swift mode. For more information about swift mode, see [Scaling modes](https://help.aliyun.com/document_detail/119099.html). Default value: false. Valid values:
+   * Specifies whether to delete the corresponding Kubernetes Node object after a node in rapid mode is successfully scaled in. For more information about rapid mode, see [Scaling modes](https://help.aliyun.com/document_detail/119099.html). Default value: false. Valid values:
    * 
-   * - `true`: The Kubernetes Node object is deleted after the node is stopped in swift mode. Setting this parameter to true is not recommended because it may cause Kubernetes object data inconsistency.
-   * - `false`: The Kubernetes Node object is retained after the node is stopped in swift mode.
+   * - `true`: The Kubernetes Node object is deleted after the node in rapid mode is stopped. Setting this parameter to true is not recommended because it may cause data inconsistency in Kubernetes objects.
+   * - `false`: The Kubernetes Node object is retained after the node in rapid mode is stopped.
    * 
    * @example
    * false
@@ -92,9 +92,9 @@ export class CreateAutoscalingConfigRequest extends $dara.Model {
   recycleNodeDeletionEnabled?: boolean;
   /**
    * @remarks
-   * Specifies whether to allow node scale-down. Valid values:
-   * - `true`: Scale-down is allowed.
-   * - `false`: Scale-down is not allowed.
+   * Specifies whether to allow node scale-in. Valid values:
+   * - `true`: Scale-in is allowed.
+   * - `false`: Scale-in is prohibited.
    * 
    * @example
    * true
@@ -113,11 +113,11 @@ export class CreateAutoscalingConfigRequest extends $dara.Model {
   scaleUpFromZero?: boolean;
   /**
    * @remarks
-   * The type of the auto scaling component. For clusters of version 1.24 and later, the default value is goatscaler. For earlier versions, the default value is cluster-autoscaler. Valid values:
+   * The elastic component type. For clusters running version 1.24 or later, the default value is goatscaler. For earlier versions, the default value is cluster-autoscaler. Valid values:
    * 
-   * - `goatscaler`: instant scaling.
+   * - `goatscaler`: Instant scaling.
    * 
-   * - `cluster-autoscaler`: automatic scaling.
+   * - `cluster-autoscaler`: Auto scaling.
    * 
    * @example
    * goatscaler
@@ -125,9 +125,9 @@ export class CreateAutoscalingConfigRequest extends $dara.Model {
   scalerType?: string;
   /**
    * @remarks
-   * The scaling sensitivity, which adjusts the interval at which the system evaluates scaling decisions.
+   * The scaling sensitivity, which adjusts the interval for the system to evaluate scaling decisions.
    * 
-   * Valid values: 15, 30, 60, 120, 180, and 300. Unit: seconds.
+   * Valid values: 15, 30, 60, 120, 180, 300. Unit: seconds.
    * 
    * Default value: 60.
    * 
@@ -137,9 +137,9 @@ export class CreateAutoscalingConfigRequest extends $dara.Model {
   scanInterval?: string;
   /**
    * @remarks
-   * Specifies whether cluster-autoscaler skips scaling down nodes that run Pods with local storage (such as EmptyDir or HostPath). Valid values:
-   * - `true`: Nodes are not scaled down.
-   * - `false`: Nodes are scaled down.
+   * Specifies whether cluster-autoscaler skips scale-in for nodes that run Pods with local storage (such as EmptyDir or HostPath). Valid values:
+   * - `true`: Scale-in is skipped.
+   * - `false`: Scale-in is performed.
    * 
    * @example
    * false
@@ -147,9 +147,9 @@ export class CreateAutoscalingConfigRequest extends $dara.Model {
   skipNodesWithLocalStorage?: boolean;
   /**
    * @remarks
-   * Specifies whether cluster-autoscaler skips scaling down nodes that run Pods in the kube-system namespace. This feature does not apply to DaemonSet Pods or Mirror Pods. Valid values:
-   * - `true`: Nodes are not scaled down.
-   * - `false`: Nodes are scaled down.
+   * Specifies whether cluster-autoscaler skips scale-in for nodes that run Pods in the kube-system namespace. This feature does not apply to DaemonSet Pods or Mirror Pods. Valid values:
+   * - `true`: Scale-in is skipped.
+   * - `false`: Scale-in is performed.
    * 
    * @example
    * true
@@ -157,7 +157,7 @@ export class CreateAutoscalingConfigRequest extends $dara.Model {
   skipNodesWithSystemPods?: boolean;
   /**
    * @remarks
-   * The cool-down period. The time interval after the most recent scale-out during which the auto scaling component does not perform scale-down operations. Nodes added during scale-out can only be evaluated for scale-down after the cool-down period expires.
+   * The cool-down period. The time interval after the most recent scale-out event during which the elastic component does not perform scale-in operations. A node that is scaled out can be considered for scale-in only after the cool-down period elapses.
    * 
    * Valid values: [1,60]. Unit: minutes.
    * 
@@ -169,9 +169,9 @@ export class CreateAutoscalingConfigRequest extends $dara.Model {
   unneededDuration?: string;
   /**
    * @remarks
-   * The scale-down threshold. The ratio of requested resources to total resources on a node.
+   * The scale-in threshold, which is the ratio of requested resources to total resources on a node.
    * 
-   * A node can be scaled down only when this ratio falls below the configured threshold, meaning both the CPU and memory resources utilization of the node are below the scale-down threshold.
+   * A node can be scaled in only when this ratio falls below the configured threshold, meaning both the CPU and memory resources utilization of the node are below the scale-in threshold.
    * 
    * Valid values: [0.1~1].
    * 

package/src/models/CreateClusterDiagnosisRequest.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class CreateClusterDiagnosisRequest extends $dara.Model {
   /**
    * @remarks
-   * The parameters that specify the diagnosis target. The following examples show the parameters for different diagnosis types:
+   * The parameters used to specify the diagnosis target. The following examples show the parameters for different diagnosis types:
    * 
    * node:
    * ```
@@ -29,13 +29,13 @@ export class CreateClusterDiagnosisRequest extends $dara.Model {
    * 
    * memory
    * ```
-   * {"node":"ap-southeast-1.172.16.9.240"}
+   * {"node":"cn-hangzhou.172.16.9.240"}
    * ```
    * 
    * service
    * ```
    * {"namespace": "kube-system", "name": "nginx-ingress-lb"}
-   * ```.
+   * ```
    * 
    * @example
    * {"namespace": "kube-system", "name": "csi-plugin-2cg9f"}

package/src/models/CreateClusterInspectConfigRequest.ts

@@ -20,7 +20,7 @@ export class CreateClusterInspectConfigRequest extends $dara.Model {
   enabled?: boolean;
   /**
    * @remarks
-   * The inspection cycle defined using RFC 5545 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. You must specify BYHOUR and BYMINUTE. Only FREQ=DAILY is supported. COUNT and UNTIL are not supported.
    * 
    * This parameter is required.
    *