@alicloud/cs20151215 6.6.4 → 6.6.5

package/dist/models/CreateClusterRequest.d.ts

@@ -7,7 +7,29 @@ import { Tag } from "./Tag";
 import { Taint } from "./Taint";
 import { InstanceMetadataOptions } from "./InstanceMetadataOptions";
 export declare class CreateClusterRequestAuditLogConfig extends $dara.Model {
+    /**
+     * @remarks
+     * Whether to enable cluster audit logging.
+     *
+     * - true: Enable.
+     *
+     * - false: Disable.
+     *
+     * @example
+     * true
+     */
     enabled?: boolean;
+    /**
+     * @remarks
+     * The [SLS Project](https://help.aliyun.com/document_detail/48873.html) containing the [Logstore](https://help.aliyun.com/document_detail/48873.html) for cluster audit logs.
+     *
+     * - Default value: `k8s-log-{clusterid}`.
+     *
+     * - When audit logging is enabled, a Logstore for audit logs is created in the specified SLS Project.
+     *
+     * @example
+     * k8s-log-c2345xxxxxxxxxxxx
+     */
     slsProjectName?: string;
     static names(): {
         [key: string]: string;
@@ -21,6 +43,17 @@ export declare class CreateClusterRequestAuditLogConfig extends $dara.Model {
     });
 }
 export declare class CreateClusterRequestAutoMode extends $dara.Model {
+    /**
+     * @remarks
+     * Whether to enable Intelligent Managed Mode.
+     *
+     * - true: Enable.
+     *
+     * - false: Disable.
+     *
+     * @example
+     * true
+     */
     enable?: boolean;
     static names(): {
         [key: string]: string;
@@ -36,7 +69,13 @@ export declare class CreateClusterRequestAutoMode extends $dara.Model {
 export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model {
     /**
      * @remarks
-     * Specifies whether to enable auto-renewal for the node.
+     * Whether to enable auto-renewal for control plane nodes. Valid only when charge_type is `PrePaid`.
+     *
+     * - true: Enable auto-renewal.
+     *
+     * - false: Disable auto-renewal.
+     *
+     * Default value: true.
      *
      * @example
      * true
@@ -44,7 +83,11 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     autoRenew?: boolean;
     /**
      * @remarks
-     * The auto-renewal duration for the node.
+     * Auto-renewal duration for control plane nodes in months.
+     *
+     * Valid values: {1, 2, 3, 6, 12}.
+     *
+     * Default value: 1.
      *
      * @example
      * 1
@@ -52,23 +95,41 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     autoRenewPeriod?: number;
     /**
      * @remarks
-     * The billing method of the node.
+     * Control plane node billing type.
+     *
+     * - `PrePaid`: Subscription.
+     *
+     * - `PostPaid`: Pay-as-you-go.
+     *
+     * Default value: `PostPaid`.
      *
      * @example
-     * PrePaid
+     * PostPaid
      */
     chargeType?: string;
     /**
      * @remarks
-     * Specifies whether to install CloudMonitor on the node.
+     * Whether to install Cloud Monitor on nodes.
+     *
+     * - true: Install the CloudMonitor agent.
+     *
+     * - false: Do not install the CloudMonitor agent.
+     *
+     * Default value: false.
      *
      * @example
-     * true
+     * false
      */
     cloudMonitorFlags?: boolean;
     /**
      * @remarks
-     * The CPU management policy of the node.
+     * Node CPU management policy.
+     *
+     * - static: Enhances CPU affinity and exclusivity for pods with specific resource characteristics on the node.
+     *
+     * - none: Uses the default CPU affinity scheme.
+     *
+     * Default value: none.
      *
      * @example
      * none
@@ -76,7 +137,7 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     cpuPolicy?: string;
     /**
      * @remarks
-     * The ID of the deployment set.
+     * Deployment set ID.
      *
      * @example
      * ds-bp10b35imuam5amw****
@@ -84,7 +145,7 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     deploymentsetId?: string;
     /**
      * @remarks
-     * The image ID.
+     * Image ID.
      *
      * @example
      * aliyun_3_x64_20G_alibase_20240819.vhd
@@ -92,21 +153,25 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     imageId?: string;
     /**
      * @remarks
-     * The type of the OS image.
+     * Operating system image type.
      *
      * @example
      * AliyunLinux3
      */
     imageType?: string;
+    /**
+     * @remarks
+     * ECS instance metadata access configuration.
+     */
     instanceMetadataOptions?: InstanceMetadataOptions;
     /**
      * @remarks
-     * The instance types of the nodes.
+     * Node instance types.
      */
     instanceTypes?: string[];
     /**
      * @remarks
-     * The name of the key pair. You must set this parameter or login_password.
+     * Key pair name. Choose either this parameter or login_password.
      *
      * @example
      * ack
@@ -114,15 +179,15 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     keyPair?: string;
     /**
      * @remarks
-     * The SSH logon password. The password must be 8 to 30 characters in length and contain a minimum of three of the following character types: uppercase letters, lowercase letters, digits, and special characters. You must set this parameter or key_pair.
+     * SSH login password. Password rules: 8–30 characters, containing at least three of the following: uppercase letters, lowercase letters, digits, and special characters. Choose either this parameter or key_pair.
      *
      * @example
-     * ack@Test
+     * ********
      */
     loginPassword?: string;
     /**
      * @remarks
-     * The node port range.
+     * **[Deprecated]** Node service port range.
      *
      * @example
      * 30000-32767
@@ -130,7 +195,11 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     nodePortRange?: string;
     /**
      * @remarks
-     * The subscription duration of the node.
+     * Subscription duration for control plane nodes in months. Required and valid only when charge_type is `PrePaid`.
+     *
+     * Valid values: {1, 2, 3, 6, 12, 24, 36, 48, 60}.
+     *
+     * Default value: 1.
      *
      * @example
      * 1
@@ -138,7 +207,9 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     period?: number;
     /**
      * @remarks
-     * The unit of the subscription duration of the node.
+     * Billing cycle unit for control plane nodes. Required and valid only when charge_type is `PrePaid`.
+     *
+     * Valid value: `Month`. Only monthly billing is supported.
      *
      * @example
      * Month
@@ -146,7 +217,9 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     periodUnit?: string;
     /**
      * @remarks
-     * The container runtime.
+     * **[Deprecated]** Control plane node runtime name. Valid value:
+     *
+     * containerd: Containerd runtime, supported for all cluster versions.
      *
      * @example
      * containerd
@@ -154,15 +227,23 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     runtime?: string;
     /**
      * @remarks
-     * Specifies whether to enable Alibaba Cloud Linux Security Hardening.
+     * Whether to enable Alibaba Cloud OS security hardening.
+     *
+     * - true: Enable Alibaba Cloud OS security hardening.
+     *
+     * - false: Disable Alibaba Cloud OS security hardening.
+     *
+     * Default value: false.
      *
      * @example
-     * true
+     * false
      */
     securityHardeningOs?: boolean;
     /**
      * @remarks
-     * The number of control plane nodes.
+     * Number of control plane nodes.
+     *
+     * Valid values: `3` or `5`.
      *
      * @example
      * 3
@@ -170,15 +251,27 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     size?: number;
     /**
      * @remarks
-     * Specifies whether to enable MLPS security hardening.
+     * Whether to enable MLPS 2.0 security hardening.
+     *
+     * - true: Enable MLPS 2.0 security hardening.
+     *
+     * - false: Disable MLPS 2.0 security hardening.
+     *
+     * Default value: false.
      *
      * @example
-     * true
+     * false
      */
     socEnabled?: boolean;
     /**
      * @remarks
-     * Specifies whether to enable the burst feature for the system disk.
+     * Whether to enable performance burst for node system disks.
+     *
+     * - true: Enable.
+     *
+     * - false: Disable.
+     *
+     * This parameter is supported only when `system_disk_category` is `cloud_auto`.
      *
      * @example
      * true
@@ -186,15 +279,29 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     systemDiskBurstingEnabled?: boolean;
     /**
      * @remarks
-     * The system disk category for the node.
+     * Node system disk type.
+     *
+     * - `cloud_efficiency`: Ultra disk.
+     *
+     * - `cloud_ssd`: Standard SSD.
+     *
+     * - `cloud_essd`: ESSD.
+     *
+     * - `cloud_auto`: ESSD AutoPL.
+     *
+     * - `cloud_essd_entry`: ESSD Entry.
+     *
+     * Default value: `cloud_ssd`. The default may vary by zone.
      *
      * @example
-     * cloud_essd
+     * cloud_ssd
      */
     systemDiskCategory?: string;
     /**
      * @remarks
-     * The PL of the system disk that you want to use for the node. This parameter takes effect only for ESSDs.
+     * Node system disk performance level. Applies only to ESSD disks.
+     *
+     * Disk performance levels depend on disk size. For more information, see [ESSD](https://help.aliyun.com/document_detail/122389.html).
      *
      * @example
      * PL1
@@ -202,7 +309,11 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     systemDiskPerformanceLevel?: string;
     /**
      * @remarks
-     * The preset read/write IOPS of the system disk.
+     * Provisioned read/write IOPS for node system disks.
+     *
+     * Valid range: 0 to min{50,000, 1000 × capacity - baseline performance}. Baseline performance = min{1,800 + 50 × capacity, 50,000}.
+     *
+     * This parameter is supported only when `system_disk_category` is `cloud_auto`.
      *
      * @example
      * 1000
@@ -210,7 +321,11 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     systemDiskProvisionedIops?: number;
     /**
      * @remarks
-     * The system disk size of the node. The value must be at least 40 GB.
+     * Node system disk size in GiB.
+     *
+     * Valid range: [40,500].
+     *
+     * Default value: `120`.
      *
      * @example
      * 120
@@ -218,7 +333,7 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     systemDiskSize?: number;
     /**
      * @remarks
-     * The automatic snapshot policy of the node.
+     * Automatic snapshot backup policy for node system disks.
      *
      * @example
      * sp-2zej1nogjvovnz4z****
@@ -236,6 +351,10 @@ export declare class CreateClusterRequestControlPlaneConfig extends $dara.Model
     });
 }
 export declare class CreateClusterRequestControlPlaneEndpointsConfigInternalDnsConfig extends $dara.Model {
+    /**
+     * @remarks
+     * VPCs where the internal domain name resolution takes effect.
+     */
     bindVpcs?: string[];
     static names(): {
         [key: string]: string;
@@ -249,6 +368,10 @@ export declare class CreateClusterRequestControlPlaneEndpointsConfigInternalDnsC
     });
 }
 export declare class CreateClusterRequestControlPlaneEndpointsConfig extends $dara.Model {
+    /**
+     * @remarks
+     * Internal domain name configuration for the cluster, applicable to ACK managed clusters. Internal domain names allow node-side system components such as kubelet and kube-proxy to access the API Server. Without internal domain name access, node-side components access the API Server through the CLB IP address.
+     */
     internalDnsConfig?: CreateClusterRequestControlPlaneEndpointsConfigInternalDnsConfig;
     static names(): {
         [key: string]: string;
@@ -264,19 +387,25 @@ export declare class CreateClusterRequestControlPlaneEndpointsConfig extends $da
 export declare class CreateClusterRequestOperationPolicyClusterAutoUpgrade extends $dara.Model {
     /**
      * @remarks
-     * The automatic update frequency. Valid values:
+     * Cluster automatic upgrade frequency. Valid values:
+     *
+     * - patch: Automatically upgrade to the latest patch version within the current minor version. New Kubernetes versions do not include breaking changes.
+     *
+     * - stable: Automatically upgrade to the latest patch version of the second-newest minor version. New Kubernetes versions may include API and feature changes but have undergone extensive stability validation.
      *
-     * *   patch
-     * *   stable
-     * *   rapid
+     * - rapid: Automatically upgrade to the latest patch version of the newest minor version to quickly access new Kubernetes community features.
      *
      * @example
-     * patch
+     * stable
      */
     channel?: string;
     /**
      * @remarks
-     * Specifies whether to enable auto cluster update.
+     * Whether to enable cluster automatic upgrade.
+     *
+     * - true: Enable.
+     *
+     * - false: Disable.
      *
      * @example
      * true
@@ -296,7 +425,7 @@ export declare class CreateClusterRequestOperationPolicyClusterAutoUpgrade exten
 export declare class CreateClusterRequestOperationPolicy extends $dara.Model {
     /**
      * @remarks
-     * The configurations of auto cluster upgrade.
+     * Cluster automatic upgrade.
      */
     clusterAutoUpgrade?: CreateClusterRequestOperationPolicyClusterAutoUpgrade;
     static names(): {
@@ -311,6 +440,17 @@ export declare class CreateClusterRequestOperationPolicy extends $dara.Model {
     });
 }
 export declare class CreateClusterRequestRrsaConfig extends $dara.Model {
+    /**
+     * @remarks
+     * Whether to enable RRSA.
+     *
+     * - true: Enable.
+     *
+     * - false: Disable.
+     *
+     * @example
+     * true
+     */
     enabled?: boolean;
     static names(): {
         [key: string]: string;
@@ -326,7 +466,7 @@ export declare class CreateClusterRequestRrsaConfig extends $dara.Model {
 export declare class CreateClusterRequestWorkerDataDisks extends $dara.Model {
     /**
      * @remarks
-     * The data disk category.
+     * Data disk type.
      *
      * This parameter is required.
      *
@@ -336,10 +476,11 @@ export declare class CreateClusterRequestWorkerDataDisks extends $dara.Model {
     category?: string;
     /**
      * @remarks
-     * Specifies whether to encrypt the data disk. Valid values:
+     * Whether to encrypt the data disk. Valid values:
+     *
+     * - `true`: Encrypt the data disk.
      *
-     * *   `true`: encrypts the data disk.
-     * *   `false`: does not encrypt the data disk.
+     * - `false`: Do not encrypt the data disk.
      *
      * Default value: `false`.
      *
@@ -349,7 +490,7 @@ export declare class CreateClusterRequestWorkerDataDisks extends $dara.Model {
     encrypted?: string;
     /**
      * @remarks
-     * The PL of the data disk. This parameter takes effect only for ESSDs. You can specify a higher PL if you increase the size of a data disk. For more information, see [Enterprise SSDs](https://help.aliyun.com/document_detail/122389.html).
+     * Data disk performance level. Applies only to [ESSD](https://help.aliyun.com/document_detail/122389.html).
      *
      * @example
      * PL1
@@ -357,7 +498,7 @@ export declare class CreateClusterRequestWorkerDataDisks extends $dara.Model {
     performanceLevel?: string;
     /**
      * @remarks
-     * The data disk size. Valid values: 40 to 32767. Unit: GiB.
+     * Data disk size in GiB. Valid range: 40–32767.
      *
      * This parameter is required.
      *
@@ -379,65 +520,77 @@ export declare class CreateClusterRequestWorkerDataDisks extends $dara.Model {
 export declare class CreateClusterRequest extends $dara.Model {
     /**
      * @remarks
-     * The network access control list (ACL) rule of the SLB instance associated with the API server if the cluster is a registered cluster.
+     * **[Deprecated]** Access control list for the registered cluster API Server SLB.
      *
      * @deprecated
      */
     accessControlList?: string[];
     /**
      * @remarks
-     * The components that you want to install in the cluster. When you create a cluster, you can configure the `addons` parameter to specify the components that you want to install.
+     * List of cluster components. Specify components to install during cluster creation using the `addons` parameter.
+     *
+     * **Network components**: Required. Choose between Flannel and Terway:
      *
-     * **Network plug-in**: required. The Flannel and Terway plug-ins are supported. Select one of the plug-ins for the cluster.
+     * - Flannel network: [{"name":"flannel","config":""}].
      *
-     * *   If you want to use the Terway component, specify the network plug-in in the [{"name":"flannel","config":""}] format.
-     * *   If you want to use the Terway component, specify the value network plug-in in the [{"name": "terway-eniip","Config": ""}] format.
+     * - Terway network: [{"name": "terway-eniip","config": ""}].
      *
-     * **Volume plug-in**: optional. Only the `Container Storage Interface (CSI)` plug-in is supported.
+     * **Storage components**: Optional. Only `csi` is supported:
      *
-     * Specify the `CSI` plug-in in the following format: [{"name":"csi-plugin","config": ""},{"name": "csi-provisioner","config": ""}].
+     * `csi`: [{"name":"csi-plugin","config": ""},{"name": "csi-provisioner","config": ""}].
      *
-     * **Simple Log Service component**: optional. We recommend that you enable Simple Log Service. If Simple Log Service is disabled, you cannot use the cluster auditing feature.
+     * **Logging components**: Optional. We recommend enabling this. Without SLS, you cannot use cluster audit features.
      *
-     * *   Specify an existing `Simple Log Service project` in the following format: [{"name": "logtail-ds","config": "{"IngressDashboardEnabled":"true","sls_project_name":"your_sls_project_name"}"}].
-     * *   To create a `Simple Log Service project`, specify the component in the following format: [{"name": "logtail-ds","config": "{"IngressDashboardEnabled":"true"}"}].
+     * - Use an existing `SLS Project`: [{"name": "loongcollector","config": "{"IngressDashboardEnabled":"true","sls_project_name":"your_sls_project_name"}"}].
      *
-     * **Ingress controller**: optional. By default, the `nginx-ingress-controller` component is installed in ACK dedicated clusters.
+     * - Create a new `SLS Project`: [{"name": "loongcollector","config": "{"IngressDashboardEnabled":"true"}"}].
      *
-     * *   To install nginx-ingress-controller and enable Internet access, specify the Ingress controller in the following format: [{"name":"nginx-ingress-controller","config":"{"IngressSlbNetworkType":"internet"}"}].
-     * *   To disable the automatic installation of nginx-ingress-controller, specify the Ingress controller in the following format: [{"name": "nginx-ingress-controller","config": "","disabled": true}].
+     * **Ingress components**: Optional. ACK dedicated clusters install the `nginx-ingress-controller` by default.
      *
-     * **Event center**: optional. By default, the event center feature is enabled.
+     * - Install Ingress with public network access: [{"name":"nginx-ingress-controller","config":"{"IngressSlbNetworkType":"internet"}"}].
      *
-     * You can use ACK event centers to store and query events and configure alerts. You can use the Logstores that are associated with ACK event centers free of charge within 90 days. For more information, see [Create and use an event center](https://help.aliyun.com/document_detail/150476.html).
+     * - Disable default Ingress installation: [{"name": "nginx-ingress-controller","config": "","disabled": true}].
      *
-     * To enable the event center feature, specify the event center component in the following format: [{"name":"ack-node-problem-detector","config":"{"sls_project_name":"your_sls_project_name"}"}].
+     * **Event Hub**: Optional. Enabled by default.
+     *
+     * Event Hub provides storage, querying, and alerting for Kubernetes events. The associated Logstore is free for 90 days. For more information about the free policy, see [Create and use Kubernetes Event Hub](https://help.aliyun.com/document_detail/150476.html).
+     *
+     * Example to enable Event Hub: [{"name":"ack-node-problem-detector","config":"{"sls_project_name":"your_sls_project_name"}"}].
      */
     addons?: Addon[];
     /**
      * @remarks
-     * Service accounts provide identities for pods when pods communicate with the `API server` of the cluster. The `api-audiences` parameter validates `tokens` and is used by the `API server` to check whether the `tokens` of requests are valid. Separate multiple values with commas (,).``
+     * ServiceAccount is the access credential used by pods to communicate with the cluster API Server. The `api-audiences` specifies valid `token` identities for authenticating requests on the `apiserver` side. You can configure multiple `audience` values separated by commas (,).
      *
-     * For more information about `service accounts`, see [Enable service account token volume projection](https://help.aliyun.com/document_detail/160384.html).
+     * For more information about `ServiceAccount`, see [Deploy service account token volume projection](https://help.aliyun.com/document_detail/160384.html).
      *
      * @example
      * kubernetes.default.svc
      */
     apiAudiences?: string;
+    /**
+     * @remarks
+     * Cluster audit log configuration.
+     */
     auditLogConfig?: CreateClusterRequestAuditLogConfig;
+    /**
+     * @remarks
+     * [Intelligent Managed Mode](https://help.aliyun.com/document_detail/2938898.html) configuration.
+     */
     autoMode?: CreateClusterRequestAutoMode;
     /**
      * @remarks
-     * [**Deprecated**]
+     * **[Deprecated]**
+     *
+     * Whether to enable auto-renewal. Valid only when `charge_type` is `PrePaid`. Valid values:
      *
-     * Specifies whether to enable auto-renewal. This parameter takes effect only when `charge_type` is set to `PrePaid`. Valid values:
+     * - `true`: Enable auto-renewal.
      *
-     * *   `true`: enables auto-renewal.
-     * *   `false`: disables auto-renewal.
+     * - `false`: Disable auto-renewal.
      *
      * Default value: `false`.
      *
-     * This parameter was changed on October 15, 2024. For more information, see [Announcement on changes to the parameter behavior of the CreateCluster operation](https://help.aliyun.com/document_detail/2849194.html).
+     * This parameter changed on October 15, 2024. For more information, see [Announcement on Changes to CreateCluster API Parameters](https://help.aliyun.com/document_detail/2849194.html).
      *
      * @example
      * true
@@ -447,13 +600,13 @@ export declare class CreateClusterRequest extends $dara.Model {
     autoRenew?: boolean;
     /**
      * @remarks
-     * [**Deprecated**]
+     * **[Deprecated]**
      *
-     * The auto-renewal duration. This parameter takes effect only if charge_type is set to PrePaid and auto_renew is set to true. If you set `period_unit` to Month, the valid values of auto_renew_period are 1, 2, 3, 6, and 12.
+     * Auto-renewal period in months. Valid only when prepaid and auto-renewal are enabled. When `PeriodUnit=Month`, valid values are {1, 2, 3, 6, 12}.
      *
      * Default value: 1.
      *
-     * This parameter was changed on October 15, 2024. For more information, see [Announcement on changes to the parameter behavior of the CreateCluster operation](https://help.aliyun.com/document_detail/2849194.html).
+     * This parameter changed on October 15, 2024. For more information, see [Announcement on Changes to CreateCluster API Parameters](https://help.aliyun.com/document_detail/2849194.html).
      *
      * @example
      * 1
@@ -463,30 +616,32 @@ export declare class CreateClusterRequest extends $dara.Model {
     autoRenewPeriod?: number;
     /**
      * @remarks
-     * [**Deprecated**]
+     * **[Deprecated]**
+     *
+     * Billing type for the CLB instance used by the API Server. Default value: PostPaid. Valid values:
      *
-     * The billing method of the CLB instance that is used by the API server. Default value: PostPaid. Valid values:
+     * - PostPaid: Pay-as-you-go.
      *
-     * *   PostPaid: pay-as-you-go.
-     * *   PrePaid: subscription. This billing method is not supported by newly created CLB instances. Existing CLB instances are not affected.
+     * - PrePaid: Subscription. New CLB instances no longer support subscription billing, but existing instances are unaffected.
      *
-     * >
+     * >Notice:
      *
-     * *   This parameter was changed on October 15, 2024. For more information, see [Announcement on changes to the parameter behavior of the CreateCluster operation](https://help.aliyun.com/document_detail/2849194.html).
+     * - This parameter changed on October 15, 2024. For more information, see [Announcement on Changes to CreateCluster API Parameters](https://help.aliyun.com/document_detail/2849194.html).
      *
-     * *   Starting from December 1, 2024, newly created CLB instances no longer support the subscription billing method, and an instance fee will be charged for newly created CLB instances
+     * - Starting December 1, 2024, new CLB instances will no longer support subscription billing and will incur an instance fee.
      *
-     * For more information, see [CLB billing adjustments](https://help.aliyun.com/document_detail/2839797.html).
+     * <props="china">For details, see [[Product Announcement\\] Discontinuation of Subscription Billing for API Server CLB in New Clusters](~~2851191~~) and [Adjustment of Classic Load Balancer Billing Items](https://help.aliyun.com/document_detail/2839797.html).
+     * <props="intl">For details, see [Adjustment of Classic Load Balancer Billing Items](https://help.aliyun.com/document_detail/2839797.html).
      *
      * @example
-     * 1
+     * PostPaid
      *
      * @deprecated
      */
     chargeType?: string;
     /**
      * @remarks
-     * [Deprecated] When you configure the control plane, use the `security_hardening_os` parameter in the `control_plane_config` section instead. When you configure a node pool, use the `security_hardening_os` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For control plane configuration, use the `security_hardening_os` parameter under `control_plane_config`. For node pool configuration, use the `security_hardening_os` parameter under `scaling_group` in `nodepool`.
      *
      * @example
      * false
@@ -496,26 +651,27 @@ export declare class CreateClusterRequest extends $dara.Model {
     cisEnabled?: boolean;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `cloud_monitor_flags` parameter in the `control_plane_config` section instead. When you configure a node pool, use the `cms_enabled` parameter of the `kubernetes_config` field in the nodepool section instead.
+     * **[Deprecated]** For control plane node configuration, use the cloud_monitor_flags parameter under `control_plane_config`. For node pool configuration, use the `cms_enabled` parameter under `kubernetes_config` in `nodepool`.
+     *
+     * Whether to install the CloudMonitor agent on the cluster. Valid values:
      *
-     * Specifies whether to install the CloudMonitor agent. Valid values:
+     * - `true`: Install the CloudMonitor agent.
      *
-     * *   `true`: installs the CloudMonitor agent.
-     * *   `false`: does not install the CloudMonitor agent.
+     * - `false`: Do not install the CloudMonitor agent.
      *
      * Default value: `false`.
      *
      * @example
-     * true
+     * false
      *
      * @deprecated
      */
     cloudMonitorFlags?: boolean;
     /**
      * @remarks
-     * The domain name of the cluster.
+     * Cluster local domain name.
      *
-     * The domain name can contain one or more parts that are separated by periods (.). Each part cannot exceed 63 characters in length, and can contain lowercase letters, digits, and hyphens (-). Each part must start and end with a lowercase letter or digit.
+     * Naming rules: The domain name consists of one or more parts separated by dots (.). Each part can be up to 63 characters long and can contain lowercase letters, digits, and hyphens (-). Each part must start and end with a lowercase letter or digit.
      *
      * @example
      * cluster.local
@@ -523,10 +679,21 @@ export declare class CreateClusterRequest extends $dara.Model {
     clusterDomain?: string;
     /**
      * @remarks
-     * If you set `cluster_type` to `ManagedKubernetes` and specify `profile`, you can further specify the edition of the cluster. Valid values:
+     * When you set `cluster_type` to `ManagedKubernetes` and configure `profile`, you can further specify the cluster specification. Valid values:
+     *
+     * - `ack.standard`: Basic Edition (default when this parameter is empty)
+     *
+     * - `ack.pro.small`: Pro Edition
+     *
+     * - `ack.pro.xlarge`: Pro XL
+     *
+     * - `ack.pro.2xlarge`: Pro 2XL
+     *
+     * - `ack.pro.4xlarge`: Pro 4XL (requires whitelist approval from customer service)
      *
-     * *   `ack.pro.small`: Pro Edition.
-     * *   `ack.standard`: Basic Edition. If you leave the parameter empty, an ACK Basic cluster is created.
+     * Pro XL, Pro 2XL, and Pro 4XL are three tiers provided by <props="china">[ACK Pro Provisioned Control Plane](https://help.aliyun.com/ack/ack-managed-and-ack-dedicated/user-guide/ack-pro-provisioned-control-plane)<props="intl">[ACK Pro Provisioned Control Plane](https://www.alibabacloud.com/help/ack/ack-managed-and-ack-dedicated/user-guide/ack-pro-provisioned-control-plane). These tiers pre-allocate and dedicate control plane resources to ensure consistently high API concurrency and pod scheduling performance. They are suitable for AI training and inference, ultra-large-scale clusters, and mission-critical workloads.
+     *
+     * For cluster management fees for Pro Edition and provisioned control plane clusters, see <props="china">[Cluster management fees](https://help.aliyun.com/ack/ack-managed-and-ack-dedicated/product-overview/cluster-management-fee)<props="intl">[Cluster management fees](https://www.alibabacloud.com/help/ack/ack-managed-and-ack-dedicated/product-overview/cluster-management-fee).
      *
      * @example
      * ack.pro.small
@@ -534,9 +701,11 @@ export declare class CreateClusterRequest extends $dara.Model {
     clusterSpec?: string;
     /**
      * @remarks
-     * *   `Kubernetes`: ACK dedicated cluster.
-     * *   `ManagedKubernetes`: ACK managed cluster. ACK managed clusters include ACK Basic clusters, ACK Pro clusters, ACK Serverless clusters (Basic Edition and Pro Edition), ACK Edge clusters (Basic Edition and Pro Edition), and ACK Lingjun clusters (Pro Edition).
-     * *   `ExternalKubernetes`: registered cluster.
+     * - `Kubernetes`: ACK dedicated cluster.
+     *
+     * - `ManagedKubernetes`: ACK managed clusters, including ACK managed clusters (Pro Edition, Basic Edition), ACK serverless clusters (Pro Edition, Basic Edition), ACK Edge clusters (Pro Edition, Basic Edition), and ACK LINGJUN clusters (Pro Edition).
+     *
+     * - `ExternalKubernetes`: registered cluster.
      *
      * @example
      * Kubernetes
@@ -544,11 +713,11 @@ export declare class CreateClusterRequest extends $dara.Model {
     clusterType?: string;
     /**
      * @remarks
-     * The pod CIDR block. You can specify 10.0.0.0/8, 172.16-31.0.0/12-16, 192.168.0.0/16, or their subnets as the pod CIDR block. The pod CIDR block cannot overlap with the CIDR block of the VPC in which the cluster is deployed and the CIDR blocks of existing clusters in the VPC. You cannot modify the pod CIDR block after you create the cluster.
+     * Pod network CIDR block. It must be a valid private CIDR block: 10.0.0.0/8, 172.16.0.0/12 to 172.31.0.0/16, or 192.168.0.0/16. It cannot overlap with the VPC or existing Kubernetes cluster CIDR blocks in the VPC. This cannot be modified after cluster creation.
      *
-     * For more information about how to plan the network of an ACK cluster, see [Plan the network of an ACK cluster](https://help.aliyun.com/document_detail/86500.html).
+     * For cluster network planning, see [Network planning for ACK managed clusters](https://help.aliyun.com/document_detail/86500.html).
      *
-     * >  This parameter is required if the cluster uses the Flannel plug-in.
+     * > This field is required for Flannel clusters.
      *
      * @example
      * 172.20.0.0/16
@@ -556,20 +725,24 @@ export declare class CreateClusterRequest extends $dara.Model {
     containerCidr?: string;
     /**
      * @remarks
-     * The control plane configurations of an ACK dedicated cluster.
+     * Control plane configuration for ACK dedicated clusters.
      */
     controlPlaneConfig?: CreateClusterRequestControlPlaneConfig;
+    /**
+     * @remarks
+     * Cluster connection configuration.
+     */
     controlPlaneEndpointsConfig?: CreateClusterRequestControlPlaneEndpointsConfig;
     /**
      * @remarks
-     * The control plane components for which you want to enable log collection.
+     * List of component names specifying which control plane component logs to collect.
      *
-     * By default, the logs of kube-apiserver, kube-controller-manager, and kube-scheduler are collected.
+     * By default, logs are collected for kube-apiserver, kube-controller-manager, kube-scheduler, and cloud-controller-manager.
      */
     controlplaneLogComponents?: string[];
     /**
      * @remarks
-     * The Simple Log Service project that is used to store the logs of control plane components. You can use an existing project or create one. If you choose to create a Simple Log Service project, the created project is named in the `k8s-log-{ClusterID}` format.
+     * SLS Project for control plane component logs. You can use an existing Project for log storage or let the system automatically create one. If auto-created, the Project name will be `k8s-log-{ClusterID}`.
      *
      * @example
      * k8s-log-xxx
@@ -577,7 +750,7 @@ export declare class CreateClusterRequest extends $dara.Model {
     controlplaneLogProject?: string;
     /**
      * @remarks
-     * The retention period of control plane logs in days.
+     * Number of days to retain control plane component logs.
      *
      * @example
      * 30
@@ -585,12 +758,13 @@ export declare class CreateClusterRequest extends $dara.Model {
     controlplaneLogTtl?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `cpu_policy` parameter in the `control_plane_config` section instead. When you configure a node pool, use the `cpu_policy` parameter of the `kubernetes_config` field in the `nodepool` section instead.
+     * **[Deprecated]** For control plane configuration, use the `cpu_policy` parameter under `control_plane_config`. For node pool configuration, use the `cpu_policy` parameter under `kubernetes_config` in `nodepool`.
      *
-     * The CPU management policy of the node. The following policies are supported if the Kubernetes version of the cluster is 1.12.6 or later:
+     * Node CPU management policy. Supported for cluster versions 1.12.6 and later:
      *
-     * *   `static`: allows pods with specific resource characteristics on the node to be granted enhanced CPU affinity and exclusivity.
-     * *   `none`: specifies that the default CPU affinity is used.
+     * - `static`: Enhances CPU affinity and exclusivity for pods with specific resource characteristics on the node.
+     *
+     * - `none`: Uses the default CPU affinity scheme.
      *
      * Default value: `none`.
      *
@@ -602,7 +776,9 @@ export declare class CreateClusterRequest extends $dara.Model {
     cpuPolicy?: string;
     /**
      * @remarks
-     * The custom subject alternative names (SANs) for the API server certificate to accept requests from specified IP addresses or domain names. Separate multiple IP addresses and domain names with commas (,).
+     * **[Deprecated]** Use the `extra_sans` parameter instead.
+     *
+     * Custom certificate SAN. Separate multiple IP addresses or domain names with commas (,).
      *
      * @example
      * cs.aliyun.com
@@ -612,10 +788,11 @@ export declare class CreateClusterRequest extends $dara.Model {
     customSan?: string;
     /**
      * @remarks
-     * Specifies whether to enable cluster deletion protection. If you enable this option, the cluster cannot be deleted in the console or by calling API operations. Valid values:
+     * Cluster deletion protection prevents accidental cluster deletion through the console or API. Valid values:
+     *
+     * - `true`: Enable deletion protection. You cannot delete the cluster through the console or API.
      *
-     * *   `true`: enables cluster deletion protection.
-     * *   `false`: disables cluster deletion protection.
+     * - `false`: Disable deletion protection. You can delete the cluster through the console or API.
      *
      * Default value: `false`.
      *
@@ -625,12 +802,13 @@ export declare class CreateClusterRequest extends $dara.Model {
     deletionProtection?: boolean;
     /**
      * @remarks
-     * [**Deprecated**] By default, the system does not perform a rollback when the cluster fails to be created. You must manually delete the cluster that fails to be created.
+     * **[Deprecated]** By default, clusters are not rolled back on creation failure. You must manually clean up failed clusters.
      *
-     * Specifies whether to perform a rollback when the cluster fails to be created. Valid values:
+     * Whether to roll back on cluster creation failure. Valid values:
      *
-     * *   `true`: performs a rollback when the cluster fails to be created.
-     * *   `false`: does not perform a rollback when the cluster fails to be created.
+     * - `true`: Roll back on failure.
+     *
+     * - `false`: Do not roll back on failure.
      *
      * Default value: `true`.
      *
@@ -642,19 +820,25 @@ export declare class CreateClusterRequest extends $dara.Model {
     disableRollback?: boolean;
     /**
      * @remarks
-     * Specifies whether to enable the RAM Roles for Service Accounts (RRSA) feature.
+     * **[Deprecated]** Use the `rrsa_config` parameter instead.
+     *
+     * Whether to enable RRSA.
+     *
+     * - true: Enable.
+     *
+     * - false: Disable.
      *
      * @example
-     * true
+     * false
      *
      * @deprecated
      */
     enableRrsa?: boolean;
     /**
      * @remarks
-     * The ID of the Key Management Service (KMS) key that is used to encrypt the system disk. For more information, see [What is KMS?](https://help.aliyun.com/document_detail/28935.html)
+     * KMS key ID used to encrypt data disks. For more information, see [Key Management Service](https://help.aliyun.com/document_detail/28935.html).
      *
-     * >  The key can be used only in ACK Pro clusters.
+     * > This feature is available only for professional managed clusters (ACK Pro clusters).
      *
      * @example
      * 0fe64791-55eb-4fc7-84c5-c6c7cdca****
@@ -662,10 +846,11 @@ export declare class CreateClusterRequest extends $dara.Model {
     encryptionProviderKey?: string;
     /**
      * @remarks
-     * Specifies whether to enable Internet access for the cluster. You can use an elastic IP address (EIP) to expose the API server. This way, you can access the cluster over the Internet. Valid values:
+     * Whether to enable public network access. Expose the API Server through an EIP to allow public network access to the cluster.
      *
-     * *   `true`: enables Internet access for the cluster.
-     * *   `false`: disables Internet access for the cluster. If you set the value to false, the API server cannot be accessed over the Internet.
+     * - `true`: Enable public network access.
+     *
+     * - `false`: Disable public network access. If disabled, you cannot access the cluster API Server from external networks.
      *
      * Default value: `false`.
      *
@@ -673,22 +858,28 @@ export declare class CreateClusterRequest extends $dara.Model {
      * true
      */
     endpointPublicAccess?: boolean;
+    /**
+     * @remarks
+     * Custom API Server certificate SAN (Subject Alternative Name).
+     */
     extraSans?: string[];
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, you cannot add existing nodes to the cluster. If you want to add existing nodes, you must first create a node pool and then call the [AttachInstancesToNodePool](https://help.aliyun.com/document_detail/2667920.html) operation.
+     * **[Deprecated]** Adding existing nodes during cluster creation is not supported. To add existing nodes to a cluster, first create a node pool and then call the [AttachInstancesToNodePool](https://help.aliyun.com/document_detail/2667920.html) API.
+     *
+     * When using existing instances to create a cluster, whether to mount data disks. Valid values:
      *
-     * Specifies whether to mount a data disk to a node that is created based on an existing ECS instance. Valid values:
+     * - `true`: Store containers and images on the data disk. Existing data on the data disk will be lost. Back up your data.
      *
-     * *   `true`: stores the data of containers and images on a data disk. The existing data stored in the data disk is lost. Back up the existing data first.
-     * *   `false`: does not store the data of containers and images on a data disk.
+     * - `false`: Do not store containers and images on the data disk.
      *
      * Default value: `false`.
      *
-     * How data disks are mounted:
+     * Data disk mounting rules:
+     *
+     * - If the ECS instance has a mounted data disk and the file system of the last data disk is uninitialized, the system automatically formats it as ext4 to store /var/lib/docker and /var/lib/kubelet.
      *
-     * *   If an ECS instance has data disks mounted and the file system of the last data disk is not initialized, the system automatically formats the data disk to ext4. Then, the system mounts the data disk to /var/lib/docker and /var/lib/kubelet.
-     * *   If no data disk is mounted to the ECS instance, the system does not purchase a new data disk.
+     * - If the ECS instance has no mounted data disks, no new data disks are mounted.
      *
      * @example
      * false
@@ -698,9 +889,9 @@ export declare class CreateClusterRequest extends $dara.Model {
     formatDisk?: boolean;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `image_id` parameter in the `control_plane_config` section instead. When you configure a node pool, use the `image_id` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For control plane configuration, use the `image_id` parameter under `control_plane_config`. For node pool configuration, use the `image_id` parameter under `scaling_group` in `nodepool`.
      *
-     * The custom image for nodes. By default, the image provided by ACK is used. You can select a custom image to replace the default image. For more information, see [Use a custom image to create an ACK cluster](https://help.aliyun.com/document_detail/146647.html).
+     * Custom node image. By default, the system image is used. When you select a custom image, it replaces the default system image. See [Custom images](https://help.aliyun.com/document_detail/146647.html).
      *
      * @example
      * m-bp16z7xko3vvv8gt****
@@ -710,19 +901,27 @@ export declare class CreateClusterRequest extends $dara.Model {
     imageId?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `image_type` parameter in the `control_plane_config` section instead. When you configure a node pool, use the `image_type` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For control plane configuration, use the `image_type` parameter under `control_plane_config`. For node pool configuration, use the `image_type` parameter under `scaling_group` in `nodepool`.
+     *
+     * Operating system distribution type. We recommend using this parameter to specify the node operating system. Valid values:
+     *
+     * - CentOS
+     *
+     * - AliyunLinux
      *
-     * The type of OS distribution that you want to use. To specify the node OS, we recommend that you use this parameter. Valid values:
+     * - AliyunLinux Qboot
      *
-     * *   CentOS
-     * *   AliyunLinux
-     * *   AliyunLinux Qboot
-     * *   AliyunLinuxUEFI
-     * *   AliyunLinux3
-     * *   Windows
-     * *   WindowsCore
-     * *   AliyunLinux3Arm64
-     * *   ContainerOS
+     * - AliyunLinuxUEFI
+     *
+     * - AliyunLinux3
+     *
+     * - Windows
+     *
+     * - WindowsCore
+     *
+     * - AliyunLinux3Arm64
+     *
+     * - ContainerOS
      *
      * Default value: `CentOS`.
      *
@@ -734,32 +933,34 @@ export declare class CreateClusterRequest extends $dara.Model {
     imageType?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, you cannot add existing nodes to the cluster. If you want to add existing nodes, you must first create a node pool and then call the [AttachInstancesToNodePool](https://help.aliyun.com/document_detail/2667920.html) operation.
+     * **[Deprecated]** Adding existing nodes during cluster creation is not supported. To add existing nodes to a cluster, first create a node pool and then call the [AttachInstancesToNodePool](https://help.aliyun.com/document_detail/2667920.html) API.
      *
-     * The existing ECS instances that are specified as worker nodes for the cluster.
+     * When using existing nodes to create a cluster, specify the ECS instance list. These instances are added as worker nodes to the cluster.
      *
-     * >  This parameter is required if you create worker nodes on existing ECS instances.
+     * > This field is required when using existing instances to create a cluster.
      *
      * @deprecated
      */
     instances?: string[];
     /**
      * @remarks
-     * The IP stack of the cluster.
+     * Cluster IP stack.
      *
      * @example
-     * Optional value: ipv4 (Single stack) or ipv6 (Dual Stack)
-     * Default value: IPV4
+     * 可选值：
+     * ipv4（单栈）
+     * dual（双栈），默认值为ipv4。
      */
     ipStack?: string;
     /**
      * @remarks
-     * Specifies whether to create an advanced security group. This parameter takes effect only if `security_group_id` is left empty.
+     * Automatically create an advanced security group. This takes effect when `security_group_id` is empty.
+     *
+     * > With basic security groups, the total number of nodes and Terway pods in a cluster cannot exceed 2,000. We recommend using advanced security groups for Terway network clusters.
      *
-     * >  To use a basic security group, make sure that the sum of the number of nodes in the cluster and the number of pods that use Terway does not exceed 2,000. Therefore, we recommend that you specify an advanced security group for a cluster that uses Terway.
+     * - `true`: Create and use an advanced security group.
      *
-     * *   `true`: creates an advanced security group.
-     * *   `false`: does not create an advanced security group.
+     * - `false`: Use a basic security group.
      *
      * Default value: `true`.
      *
@@ -769,12 +970,13 @@ export declare class CreateClusterRequest extends $dara.Model {
     isEnterpriseSecurityGroup?: boolean;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, you cannot add existing nodes to the cluster. If you want to add existing nodes, you must first create a node pool and then call the [AttachInstancesToNodePool](https://help.aliyun.com/document_detail/2667920.html) operation.
+     * **[Deprecated]** Adding existing nodes during cluster creation is not supported. To add existing nodes to a cluster, first create a node pool and then call the [AttachInstancesToNodePool](https://help.aliyun.com/document_detail/2667920.html) API.
      *
-     * Specifies whether to retain the names of existing ECS instances that are used in the cluster. Valid values:
+     * When using existing instances to create a cluster, whether to keep the instance names.
      *
-     * *   `true`: retains the names.
-     * *   `false`: does not retain the names. The system assigns new names.
+     * - `true`: Keep.
+     *
+     * - `false`: Replace with system-generated names.
      *
      * Default value: `true`.
      *
@@ -786,31 +988,33 @@ export declare class CreateClusterRequest extends $dara.Model {
     keepInstanceName?: boolean;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `key_pair` parameter in the `control_plane_config` section instead. When you configure a node pool, use the `key_pair` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For control plane configuration, use the `key_pair` parameter under `control_plane_config`. For node pool configuration, use the `key_pair` parameter under `scaling_group` in `nodepool`.
      *
-     * The name of the key pair. You must configure this parameter or `login_password`.
+     * Key pair name. Choose either this parameter or `login_password`.
      *
      * @example
-     * secrity-key
+     * security-key
      *
      * @deprecated
      */
     keyPair?: string;
     /**
      * @remarks
-     * The Kubernetes version of the cluster. The Kubernetes versions supported by ACK are the same as the Kubernetes versions supported by open source Kubernetes. We recommend that you specify the latest Kubernetes version. If you do not specify this parameter, the latest Kubernetes version is used.
+     * Cluster version, aligned with the Kubernetes community baseline version. We recommend selecting the latest version. If not specified, the latest version is used by default.
+     *
+     * You can create clusters using any of the three most recent versions. Use the [DescribeKubernetesVersionMetadata](https://help.aliyun.com/document_detail/2667899.html) API to query supported cluster versions.
      *
-     * You can create ACK clusters of the latest three Kubernetes versions in the ACK console. If you want to create clusters that run earlier Kubernetes versions, use the ACK API. For more information about the Kubernetes versions supported by ACK, see [Support for Kubernetes versions](https://help.aliyun.com/document_detail/185269.html).
+     * For more information about Kubernetes versions supported by ACK, see [Overview of Kubernetes version releases](https://help.aliyun.com/document_detail/185269.html).
      *
      * @example
-     * 1.16.9-aliyun.1
+     * 1.32.1-aliyun.1
      */
     kubernetesVersion?: string;
     /**
      * @remarks
-     * Specifies the ID of the CLB instance for accessing the API server. If this parameter is specified, the system does not automatically create a CLB instance for the API server.
+     * Specify the CLB instance ID for API Server access. If specified, no new API Server CLB is automatically created.
      *
-     * >  Make sure that the CLB instance does not have other dependencies, such as listeners and backend servers. You cannot specify shared-resource or Internet-facing CLB instances.
+     * > Ensure the CLB instance has no dependencies (such as listeners or backend servers). Shared and public CLB instances are not supported.
      *
      * @example
      * lb-wz9t256gqa3vbouk****
@@ -818,16 +1022,21 @@ export declare class CreateClusterRequest extends $dara.Model {
     loadBalancerId?: string;
     /**
      * @remarks
-     * [**Deprecated**] The pay-as-you-go billing method is used by Classic Load Balancer (CLB) instances. This parameter does not take effect.
+     * **[Deprecated]** CLB is billed based on usage. This parameter has no effect.
+     *
+     * Load Balancer specification. Valid values:
+     *
+     * - slb.s1.small
+     *
+     * - slb.s2.small
+     *
+     * - slb.s2.medium
+     *
+     * - slb.s3.small
      *
-     * The specification of the Server Load Balancer (SLB) instance. Valid values:
+     * - slb.s3.medium
      *
-     * *   slb.s1.small
-     * *   slb.s2.small
-     * *   slb.s2.medium
-     * *   slb.s3.small
-     * *   slb.s3.medium
-     * *   slb.s3.large
+     * - slb.s3.large
      *
      * Default value: `slb.s2.small`.
      *
@@ -839,7 +1048,7 @@ export declare class CreateClusterRequest extends $dara.Model {
     loadBalancerSpec?: string;
     /**
      * @remarks
-     * Enables Simple Log Service for the cluster. This parameter takes effect only for ACK Serverless clusters. Set the value to `SLS`.
+     * **[Deprecated]** Enables SLS for the cluster. Applies only to ACK Serverless clusters and must be set to `SLS`.
      *
      * @example
      * SLS
@@ -849,29 +1058,30 @@ export declare class CreateClusterRequest extends $dara.Model {
     loggingType?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `login_password` parameter in the `control_plane_config` section instead. When you configure a node pool, use the `login_password` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For control plane configuration, use the `login_password` parameter under `control_plane_config`. For node pool configuration, use the `login_password` parameter under `scaling_group` in `nodepool`.
      *
-     * The password for SSH logon. You must set this parameter or `key_pair`. The password must be 8 to 30 characters in length, and must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters.
+     * SSH login password. Choose either this parameter or `key_pair`. Password rules: 8–30 characters, containing at least three of the following: uppercase letters, lowercase letters, digits, and special characters.
      *
      * @example
-     * Hello@1234
+     * null
      *
      * @deprecated
      */
     loginPassword?: string;
     /**
      * @remarks
-     * The configurations of the cluster maintenance window.
+     * Cluster maintenance window.
      */
     maintenanceWindow?: MaintenanceWindow;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `auto-renew` parameter in the `control_plane_config` section instead.
+     * **[Deprecated]** For control plane configuration, use the `auto_renew` parameter under `control_plane_config`.
      *
-     * Specifies whether to enable auto-renewal for master nodes. This parameter takes effect only when `master_instance_charge_type` is set to `PrePaid`. Valid values:
+     * Whether to enable auto-renewal for master nodes. Valid only when `master_instance_charge_type` is `PrePaid`. Valid values:
      *
-     * *   `true`: enables auto-renewal.
-     * *   `false`: disables auto-renewal.
+     * - `true`: Enable auto-renewal.
+     *
+     * - `false`: Disable auto-renewal.
      *
      * Default value: `true`.
      *
@@ -883,11 +1093,11 @@ export declare class CreateClusterRequest extends $dara.Model {
     masterAutoRenew?: boolean;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `auto-renew_period` parameter in the `control_plane_config` section instead.
+     * **[Deprecated]** For control plane configuration, use the `auto_renew_period` parameter under `control_plane_config`.
      *
-     * The auto-renewal duration. This parameter takes effect and is required only when the subscription billing method is selected for master nodes.
+     * Auto-renewal period for master nodes in months. Required and valid only when subscription billing is selected.
      *
-     * Valid values: 1, 2, 3, 6, and 12.
+     * Valid values: {1, 2, 3, 6, 12}.
      *
      * Default value: 1.
      *
@@ -899,9 +1109,9 @@ export declare class CreateClusterRequest extends $dara.Model {
     masterAutoRenewPeriod?: number;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `size` parameter in the `control_plane_config` section instead.
+     * **[Deprecated]** For control plane configuration, use the `size` parameter under `control_plane_config`.
      *
-     * The number of master nodes. Valid values: `3` and `5`.
+     * Number of master nodes. Valid values: `3` or `5`.
      *
      * Default value: `3`.
      *
@@ -913,12 +1123,13 @@ export declare class CreateClusterRequest extends $dara.Model {
     masterCount?: number;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `instance_charge_type` parameter in the `control_plane_config` section instead.
+     * **[Deprecated]** For control plane configuration, use the `instance_charge_type` parameter under `control_plane_config`.
+     *
+     * Master node billing type. Valid values:
      *
-     * The billing method of master nodes. Valid values:
+     * - `PrePaid`: Subscription.
      *
-     * *   `PrePaid`: subscription.
-     * *   `PostPaid`: pay-as-you-go.
+     * - `PostPaid`: Pay-as-you-go.
      *
      * Default value: `PostPaid`.
      *
@@ -930,20 +1141,20 @@ export declare class CreateClusterRequest extends $dara.Model {
     masterInstanceChargeType?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `instance_types` parameter in the `control_plane_config` section instead.
+     * **[Deprecated]** For control plane configuration, use the `instance_types` parameter under `control_plane_config`.
      *
-     * The instance types of master nodes. For more information, see [Overview of instance families](https://help.aliyun.com/document_detail/25378.html).
+     * Master node instance types. For more information, see [Instance families](https://help.aliyun.com/document_detail/25378.html).
      *
      * @deprecated
      */
     masterInstanceTypes?: string[];
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `unit` parameter in the `control_plane_config` section instead.
+     * **[Deprecated]** For control plane configuration, use the `unit` parameter under `control_plane_config`.
      *
-     * The subscription duration of master nodes. This parameter takes effect and is required only when `master_instance_charge_type` is set to `PrePaid`.
+     * Subscription duration for master nodes in months. Required and valid only when `master_instance_charge_type` is `PrePaid`.
      *
-     * Valid values: 1, 2, 3, 6, 12, 24, 36, 48, and 60.
+     * Valid values: {1, 2, 3, 6, 12, 24, 36, 48, 60}.
      *
      * Default value: 1.
      *
@@ -955,11 +1166,11 @@ export declare class CreateClusterRequest extends $dara.Model {
     masterPeriod?: number;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `period_unit` parameter in the `control_plane_config` section instead.
+     * **[Deprecated]** For control plane configuration, use the `period_unit` parameter under `control_plane_config`.
      *
-     * The billing cycle of the master nodes in the cluster. This parameter is required if master_instance_charge_type is set to `PrePaid`.
+     * Master node billing cycle. Required when master_instance_charge_type is `PrePaid`.
      *
-     * Valid value: `Month`, which indicates that master nodes are billed only on a monthly basis.
+     * Valid value: `Month`. Only monthly billing is supported.
      *
      * @example
      * Month
@@ -969,15 +1180,17 @@ export declare class CreateClusterRequest extends $dara.Model {
     masterPeriodUnit?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `system_disk_category` parameter in the `control_plane_config` section instead.
+     * **[Deprecated]** For control plane configuration, use the `system_disk_category` parameter under `control_plane_config`.
+     *
+     * Master node system disk type. Valid values:
      *
-     * The system disk category of master nodes. Valid values:
+     * - `cloud_efficiency`: Ultra disk.
      *
-     * *   `cloud_efficiency`: ultra disk.
-     * *   `cloud_ssd`: standard SSD.
-     * *   `cloud_essd`: Enterprise SSD (ESSD).
+     * - `cloud_ssd`: Standard SSD.
      *
-     * Default value: `cloud_ssd`. The default value may vary in different zones.
+     * - `cloud_essd`: ESSD.
+     *
+     * Default value: `cloud_ssd`. The default may vary by zone.
      *
      * @example
      * cloud_ssd
@@ -987,9 +1200,9 @@ export declare class CreateClusterRequest extends $dara.Model {
     masterSystemDiskCategory?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `system_disk_performance_level` parameter in the `control_plane_config` section instead.
+     * **[Deprecated]** For control plane configuration, use the `system_disk_performance_level` parameter under `control_plane_config`.
      *
-     * The performance level (PL) of the system disk that you want to use for master nodes. This parameter takes effect only for ESSDs. For more information about the relationship between disk PLs and disk sizes, see [ESSDs](https://help.aliyun.com/document_detail/122389.html).
+     * Performance level for master node system disks. Applies only to ESSD disks. Disk performance levels depend on disk size. For more information, see [ESSD](https://help.aliyun.com/document_detail/122389.html).
      *
      * @example
      * PL1
@@ -999,9 +1212,9 @@ export declare class CreateClusterRequest extends $dara.Model {
     masterSystemDiskPerformanceLevel?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `system_disk_disk` parameter in the `control_plane_config` section instead.
+     * **[Deprecated]** For control plane configuration, use the `system_disk_size` parameter under `control_plane_config`.
      *
-     * The system disk size of master nodes. Valid values: 40 to 500. Unit: GiB.
+     * Valid range: [40,500].
      *
      * Default value: `120`.
      *
@@ -1013,9 +1226,9 @@ export declare class CreateClusterRequest extends $dara.Model {
     masterSystemDiskSize?: number;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `system_disk_snapshot_policy_id` parameter in the `control_plane_config` section instead.
+     * **[Deprecated]** For control plane configuration, use the `system_disk_snapshot_policy_id` parameter under `control_plane_config`.
      *
-     * The ID of the automatic snapshot policy that is used by the system disk specified for master nodes.
+     * Automatic snapshot policy ID for master node system disks.
      *
      * @example
      * sp-2zej1nogjvovnz4z****
@@ -1025,20 +1238,18 @@ export declare class CreateClusterRequest extends $dara.Model {
     masterSystemDiskSnapshotPolicyId?: string;
     /**
      * @remarks
-     * [**Deprecated**] Use the `vswitch_ids` parameter instead.
+     * **[Deprecated]** Use the `vswitch_ids` parameter instead.
      *
-     * The IDs of the vSwitches that are specified for master nodes. You can specify up to three vSwitches. We recommend that you specify three vSwitches in different zones to ensure high availability.
+     * List of master node vSwitch IDs. The number of vSwitches must be in the range [1,3]. For high availability, we recommend selecting three vSwitches in different zones.
      *
-     * The number of vSwitches must be the same as the value of the `master_count` parameter and also the same as the number of vSwitches specified in the `master_vswitch_ids` parameter.
+     * The number of specified instance types must match `master_count` and correspond one-to-one with elements in `master_vswitch_ids`.
      *
      * @deprecated
      */
     masterVswitchIds?: string[];
     /**
      * @remarks
-     * The cluster name.
-     *
-     * The name must be 1 to 63 characters in length, and can contain digits, letters, and hyphens (-). The name cannot start with a hyphen (-).
+     * Custom cluster name. It can contain digits, letters, Chinese characters, or hyphens (-). The name must be 1 to 63 characters long and cannot start with a hyphen (-).
      *
      * This parameter is required.
      *
@@ -1048,7 +1259,7 @@ export declare class CreateClusterRequest extends $dara.Model {
     name?: string;
     /**
      * @remarks
-     * [Deprecated] Use the `snat_entry` parameter instead.
+     * **[Deprecated]** Use the `snat_entry` parameter instead.
      *
      * @example
      * true
@@ -1058,7 +1269,7 @@ export declare class CreateClusterRequest extends $dara.Model {
     natGateway?: boolean;
     /**
      * @remarks
-     * The maximum number of IP addresses that can be assigned to each node. This number is determined by the subnet mask of the specified CIDR block. This parameter takes effect only if the cluster uses the Flannel plug-in.
+     * Number of node IP addresses, determined by the specified CIDR mask. This applies only to Flannel network clusters.
      *
      * Default value: `26`.
      *
@@ -1068,26 +1279,17 @@ export declare class CreateClusterRequest extends $dara.Model {
     nodeCidrMask?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `node_name_mode` parameter of the `kubernetes_config` field in the `nodepool` section instead.
-     *
-     * The custom node name.
-     *
-     * A custom node name consists of a prefix, a node IP address, and a suffix.
-     *
-     * *   The prefix and suffix can contain multiple parts that are separated by periods (.). Each part can contain lowercase letters, digits, and hyphens (-), and must start and end with a lowercase letter or digit.
-     * *   The IP substring length specifies the number of digits to be truncated from the end of the node IP address. The IP substring length ranges from 5 to 12.
-     *
-     * For example, if the node IP address is 192.168.0.55, the prefix is aliyun.com, the IP substring length is 5, and the suffix is test, the node name will aliyun.com00055test.
+     * **[Deprecated]** Use the `node_name_mode` parameter under `kubernetes_config` in `nodepool` instead.
      *
      * @example
-     * aliyun.com00055test
+     * null
      *
      * @deprecated
      */
     nodeNameMode?: string;
     /**
      * @remarks
-     * The node port range. Valid values: 30000 to 65535.
+     * Node service port range: [30000,65535].
      *
      * Default value: `30000-32767`.
      *
@@ -1099,14 +1301,14 @@ export declare class CreateClusterRequest extends $dara.Model {
     nodePortRange?: string;
     /**
      * @remarks
-     * The list of node pools.
+     * List of node pools.
      */
     nodepools?: Nodepool[];
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `desired_size` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `desired_size` parameter under `scaling_group` in `nodepool`.
      *
-     * The number of worker nodes. Valid values: 0 to 100.
+     * Number of worker nodes. Range: [0,100].
      *
      * @example
      * 3
@@ -1116,17 +1318,18 @@ export declare class CreateClusterRequest extends $dara.Model {
     numOfNodes?: number;
     /**
      * @remarks
-     * The automatic O\\&M policy of the cluster.
+     * Cluster automated operations policy.
      */
     operationPolicy?: CreateClusterRequestOperationPolicy;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `image_type` parameter in the `control_plane_config` section instead. When you configure a node pool, use the `image_type` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For control plane node configuration, use the `image_type` parameter under `control_plane_config`. For node pool configuration, use the `image_type` parameter under `scaling_group` in `nodepool`.
      *
-     * The type of OS. Valid values:
+     * Operating system platform type. Valid values:
      *
-     * *   Windows
-     * *   Linux
+     * - Windows
+     *
+     * - Linux
      *
      * Default value: `Linux`.
      *
@@ -1138,31 +1341,31 @@ export declare class CreateClusterRequest extends $dara.Model {
     osType?: string;
     /**
      * @remarks
-     * [**Deprecated**]
+     * **[Deprecated]**
      *
-     * The subscription duration. This parameter takes effect and is required only when you set charge_type to PrePaid.
+     * Subscription duration in months. Required and valid only when charge_type is PrePaid.
      *
-     * Valid values: 1, 2, 3, 6, 12, 24, 36, 48, and 60.
+     * Valid values: {1, 2, 3, 6, 12, 24, 36, 48, 60}.
      *
      * Default value: 1.
      *
-     * This parameter was changed on October 15, 2024. For more information, see [Announcement on changes to the parameter behavior of the CreateCluster operation](https://help.aliyun.com/document_detail/2849194.html).
+     * This parameter changed on October 15, 2024. For more information, see [Announcement on Changes to CreateCluster API Parameters](https://help.aliyun.com/document_detail/2849194.html).
      *
      * @example
-     * FY2023
+     * 1
      *
      * @deprecated
      */
     period?: number;
     /**
      * @remarks
-     * [**Deprecated**]
+     * **[Deprecated]**
      *
-     * The billing cycle. This parameter is required if charge_type is set to PrePaid.
+     * Billing cycle. Required when the billing type is PrePaid.
      *
-     * Valid value: Month, which indicates that resources are billed only on a monthly basis.
+     * Valid value: Month. Only monthly billing is supported.
      *
-     * This parameter was changed on October 15, 2024. For more information, see [Announcement on changes to the parameter behavior of the CreateCluster operation](https://help.aliyun.com/document_detail/2849194.html).
+     * This parameter changed on October 15, 2024. For more information, see [Announcement on Changes to CreateCluster API Parameters](https://help.aliyun.com/document_detail/2849194.html).
      *
      * @example
      * Month
@@ -1172,16 +1375,21 @@ export declare class CreateClusterRequest extends $dara.Model {
     periodUnit?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `platform` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `platform` parameter under `scaling_group` in `nodepool`.
+     *
+     * Operating system distribution. Valid values:
      *
-     * The OS distribution that is used. Valid values:
+     * - CentOS
      *
-     * *   CentOS
-     * *   AliyunLinux
-     * *   QbootAliyunLinux
-     * *   Qboot
-     * *   Windows
-     * *   WindowsCore
+     * - AliyunLinux
+     *
+     * - QbootAliyunLinux
+     *
+     * - Qboot
+     *
+     * - Windows
+     *
+     * - WindowsCore
      *
      * Default value: `CentOS`.
      *
@@ -1193,21 +1401,24 @@ export declare class CreateClusterRequest extends $dara.Model {
     platform?: string;
     /**
      * @remarks
-     * If you select Terway as the network plug-in, you must allocate vSwitches to pods. For each vSwitch that allocates IP addresses to worker nodes, you must select a vSwitch in the same zone to allocate IP addresses to pods.
+     * **[Deprecated]** When using the Terway network plugin, specify virtual switches to assign IP addresses to pods. Each pod virtual switch corresponds to a worker node virtual switch, and both must be in the same zone.
      *
-     * >  We recommend that you select pod vSwitches whose subnet masks do not exceed 19 bits in length. The maximum subnet mask length of a pod vSwitch is 25 bits. If you select a pod vSwitch whose subnet mask exceeds 25 bits in length, the IP addresses that can be allocated to pods may be insufficient.
+     * > We recommend that the pod virtual switch CIDR mask not exceed /19 and must not exceed /25. Otherwise, the number of assignable pod IP addresses becomes very limited, affecting normal cluster operation.
      *
      * @deprecated
      */
     podVswitchIds?: string[];
     /**
      * @remarks
-     * If you set `cluster_type` to `ManagedKubernetes`, an ACK managed cluster is created. In this case, you can further specify the cluster edition. Valid values:
+     * When you set `cluster_type` to `ManagedKubernetes` (ACK managed cluster), you can further specify the cluster subtype.
+     *
+     * - `Default`: ACK managed cluster, including ACK clusters (Pro Edition, Basic Edition).
+     *
+     * - `Edge`: ACK Edge cluster, including ACK Edge clusters (Pro Edition, Basic Edition).
      *
-     * *   `Default`: ACK managed cluster. ACK managed clusters include ACK Basic clusters and ACK Pro clusters.
-     * *   `Edge`: ACK Edge cluster. ACK Edge clusters include ACK Edge Basic clusters and ACK Edge Pro clusters.
-     * *   `Serverless`: ACK Serverless cluster. ACK Serverless clusters include ACK Serverless Basic clusters and ACK Serverless Pro clusters.
-     * *   `Lingjun`: ACK Lingjun Pro cluster.
+     * - `Serverless`: ACK serverless cluster, including ACK serverless clusters (Pro Edition, Basic Edition).
+     *
+     * - `Lingjun`: ACK LINGJUN cluster, available only in Pro Edition.
      *
      * @example
      * Default
@@ -1215,10 +1426,14 @@ export declare class CreateClusterRequest extends $dara.Model {
     profile?: string;
     /**
      * @remarks
-     * The kube-proxy mode. Valid values:
+     * kube-proxy proxy mode
+     *
+     * - `iptables`: A mature and stable kube-proxy mode. Kubernetes Service discovery and load balancing use iptables rules. Performance is moderate and scales poorly with large numbers of Services. Suitable for clusters with few Services.
+     *
+     * - `ipvs`: A high-performance kube-proxy mode. Kubernetes Service discovery and load balancing use the Linux IPVS module. Suitable for clusters with many Services requiring high-performance load balancing.
      *
-     * *   `iptables`: a mature and stable mode that uses iptables rules to conduct service discovery and load balancing. The performance of this mode is limited by the size of the cluster. This mode is suitable for clusters that run a small number of Services.
-     * *   `ipvs`: a mode that provides high performance and uses IP Virtual Server (IPVS) to conduct service discovery and load balancing. This mode is suitable for clusters that run a large number of Services. We recommend that you use this mode in scenarios that require high-performance load balancing.
+     * - `nftables`: A next-generation kube-proxy mode based on Linux nftables for Service discovery and load balancing. It is the modern replacement for iptables. Compared to iptables, nftables offers better network performance, faster rule updates, and superior scalability for large numbers of Services.<br>
+     *   Supported only for clusters running Kubernetes version 1.35 or later. The Kubernetes community deprecated IPVS starting in version 1.35. We recommend using nftables for new clusters to ensure long-term community support.<br>
      *
      * Default value: `ipvs`.
      *
@@ -1228,16 +1443,16 @@ export declare class CreateClusterRequest extends $dara.Model {
     proxyMode?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `rds_instances` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `rds_instances` parameter under `scaling_group` in `nodepool`.
      *
-     * The ApsaraDB RDS instances. The pod CIDR block and node CIDR block are added to the whitelists of the ApsaraDB RDS instances. We recommend that you add the pod CIDR block and node CIDR block to the whitelists of the ApsaraDB RDS instances in the ApsaraDB RDS console. If the RDS instances are not in the Running state, new nodes cannot be added to the cluster.
+     * List of RDS instances to add to the whitelist. We recommend adding the pod and node CIDR blocks of your container cluster to the RDS whitelist. Setting RDS instances might fail if they are not in the Running state.
      *
      * @deprecated
      */
     rdsInstances?: string[];
     /**
      * @remarks
-     * The ID of the region in which the cluster is deployed. For more information about the regions supported by ACK, see [Regions supported by ACK](https://help.aliyun.com/document_detail/216938.html).
+     * The region ID where the cluster is deployed. For more information, see [Regions supported by Container Service for Kubernetes](https://help.aliyun.com/document_detail/216938.html).
      *
      * This parameter is required.
      *
@@ -1247,25 +1462,31 @@ export declare class CreateClusterRequest extends $dara.Model {
     regionId?: string;
     /**
      * @remarks
-     * The ID of the resource group to which the cluster belongs. You can use resource groups to isolate clusters.
+     * The resource group ID to which the cluster belongs, used to isolate different resources.
      *
      * @example
      * rg-acfm3mkrure****
      */
     resourceGroupId?: string;
+    /**
+     * @remarks
+     * RRSA feature configuration.
+     */
     rrsaConfig?: CreateClusterRequestRrsaConfig;
     /**
      * @remarks
-     * The container runtime. The default container runtime is Docker. containerd and Sandboxed-Container are also supported.
+     * Container runtime for the cluster. Supports containerd, sandboxed containers, and Docker.
      *
-     * For more information about how to select a proper container runtime, see [Comparison among Docker, containerd, and Sandboxed-Container](https://help.aliyun.com/document_detail/160313.html).
+     * > Kubernetes 1.24 no longer supports Docker as a built-in container runtime.
+     *
+     * For more information, see [Comparison of Docker, containerd, and sandboxed container runtimes](https://help.aliyun.com/document_detail/160313.html).
      *
      * @deprecated
      */
     runtime?: Runtime;
     /**
      * @remarks
-     * The ID of an existing security group. You must specify this parameter or `is_enterprise_security_group`. Cluster nodes are automatically added to the security group.
+     * Specify an existing security group ID when creating a cluster. Choose either this parameter or `is_enterprise_security_group`. Cluster nodes are automatically added to this security group.
      *
      * @example
      * sg-bp1bdue0qc1g7k****
@@ -1273,12 +1494,13 @@ export declare class CreateClusterRequest extends $dara.Model {
     securityGroupId?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `security_hardening_os` parameter in the `control_plane_config` section instead. When you configure a node pool, use the `security_hardening_os` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For control plane configuration, use the `security_hardening_os` parameter under `control_plane_config`. For node pool configuration, use the `security_hardening_os` parameter under `scaling_group` in `nodepool`.
+     *
+     * Alibaba Cloud OS security hardening. Valid values:
      *
-     * Specifies whether to enable Alibaba Cloud Linux Security Hardening. Valid values:
+     * - `true`: Enable Alibaba Cloud OS security hardening.
      *
-     * *   `true`: enables Alibaba Cloud Linux Security Hardening.
-     * *   `false`: disables Alibaba Cloud Linux Security Hardening.
+     * - `false`: Disable Alibaba Cloud OS security hardening.
      *
      * Default value: `false`.
      *
@@ -1290,9 +1512,9 @@ export declare class CreateClusterRequest extends $dara.Model {
     securityHardeningOs?: boolean;
     /**
      * @remarks
-     * Service accounts provide identities for pods when pods communicate with the `API server` of the cluster. `service-account-issuer` specifies the issuer of the `serviceaccount token`, which is specified by using the `iss` field in the `token payload`.
+     * ServiceAccount is the access credential used by pods to communicate with the cluster API Server. The `service-account-issuer` is the issuer identity in the `serviceaccount token`, represented by the `iss` field in the `token payload`.
      *
-     * For more information about `ServiceAccount`, see [Enable service account token volume projection](https://help.aliyun.com/document_detail/160384.html).
+     * For more information about `ServiceAccount`, see [Deploy service account token volume projection](https://help.aliyun.com/document_detail/160384.html).
      *
      * @example
      * kubernetes.default.svc
@@ -1300,9 +1522,10 @@ export declare class CreateClusterRequest extends $dara.Model {
     serviceAccountIssuer?: string;
     /**
      * @remarks
-     * The Service CIDR block. Valid values: 10.0.0.0/16-24, 172.16-31.0.0/16-24, and 192.168.0.0/16-24. The Service CIDR block cannot overlap with the VPC CIDR block (10.1.0.0/21) or the CIDR blocks of existing clusters in the VPC. You cannot modify the Service CIDR block after the cluster is created.
+     * Service network CIDR block. Valid ranges: 10.0.0.0/16-24, 172.16.0.0/16-24 to 172.31.0.0/16-24, 192.168.0.0/16-24.
+     * It cannot overlap with the VPC CIDR block 10.1.0.0/21 or existing Kubernetes cluster CIDR blocks in the VPC. This cannot be modified after cluster creation.
      *
-     * By default, the Service CIDR block is set to 172.19.0.0/20.
+     * Default value: 172.19.0.0/20.
      *
      * @example
      * 172.21.0.0/20
@@ -1310,41 +1533,44 @@ export declare class CreateClusterRequest extends $dara.Model {
     serviceCidr?: string;
     /**
      * @remarks
-     * The methods for implementing service discovery in `ACK Serverless` clusters.
+     * **[Deprecated]** Service discovery type for the cluster, used to specify the service discovery method in `ACK Serverless` clusters.
+     *
+     * - `CoreDNS`: Uses the standard Kubernetes service discovery component CoreDNS. Requires deploying a set of containers for DNS resolution. Defaults to two ECI instances with 0.25 vCPU and 512 MiB memory each.
      *
-     * *   `CoreDNS`: a standard service discovery plug-in that is provided by open source Kubernetes. To use DNS resolution, you must provision pods. By default, two elastic container instances are used. The specification of each instance is 0.25 vCores and 512 MiB of memory.
-     * *   `PrivateZone`: a DNS resolution service provided by Alibaba Cloud. You must activate Alibaba Cloud DNS PrivateZone before you can use it for service discovery.
+     * - `PrivateZone`: Uses Alibaba Cloud PrivateZone for service discovery. Requires enabling the PrivateZone service.
      *
-     * By default, this parameter is not specified.
+     * Default value: Disabled.
      *
      * @deprecated
      */
     serviceDiscoveryTypes?: string[];
     /**
      * @remarks
-     * Specifies whether to configure SNAT rules for the VPC in which your cluster is deployed. Valid values:
+     * Configure SNAT for the VPC. Valid values:
      *
-     * *   `true`: automatically creates a NAT gateway and configures SNAT rules. Set the value to `true` if nodes and applications in the cluster need to access the Internet.
-     * *   `false`: does not create a NAT gateway or configure SNAT rules. In this case, nodes and applications in the cluster cannot access the Internet.
+     * - `true`: Automatically create a NAT Gateway and configure SNAT rules. Set this to `true` if nodes or applications in the cluster need public network access.
      *
-     * >  If this feature is disabled when you create the cluster, you can also manually enable this feature after you create the cluster. For more information, see [Enable an existing ACK cluster to access the Internet](https://help.aliyun.com/document_detail/178480.html).
+     * - `false`: Do not create a NAT Gateway or SNAT rules. Nodes and applications in the cluster cannot access the public network.
      *
-     * Default value: `true`.
+     * > If you do not enable this during cluster creation but later need public network access, you can [enable it manually](https://help.aliyun.com/document_detail/178480.html).
+     *
+     * Default value: `false`.
      *
      * @example
-     * true
+     * false
      */
     snatEntry?: boolean;
     /**
      * @remarks
-     * [**Deprecated**] When you configure the control plane, use the `soc_enabled` parameter in the `control_plane_config` section instead. When you configure a node pool, use the `soc_enabled` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For control plane node configuration, use the `soc_enabled` parameter under `control_plane_config`. For node pool configuration, use the `soc_enabled` parameter under `scaling_group` in `nodepool`.
      *
-     * Specifies whether to enable Multi-Level Protection Scheme (MLPS) security hardening. For more information, see [ACK security hardening based on MLPS](https://help.aliyun.com/document_detail/196148.html).
+     * MLPS 2.0 security hardening. For more information, see [Using MLPS 2.0 security hardening in ACK](https://help.aliyun.com/document_detail/196148.html).
      *
      * Valid values:
      *
-     * *   `true`: enables MLPS security hardening.
-     * *   `false`: disables MLPS security hardening.
+     * - `true`: Enable MLPS 2.0 security hardening.
+     *
+     * - `false`: Disable MLPS 2.0 security hardening.
      *
      * Default value: `false`.
      *
@@ -1356,10 +1582,11 @@ export declare class CreateClusterRequest extends $dara.Model {
     socEnabled?: boolean;
     /**
      * @remarks
-     * Specifies whether to enable SSH logon. If this parameter is set to true, you can log on to master nodes in an ACK dedicated cluster over the Internet. This parameter does not take effect for ACK managed clusters. Valid values:
+     * Whether to enable public SSH logon. Used to log on to master nodes of ACK dedicated clusters. This parameter does not take effect for managed clusters.
      *
-     * *   `true`: enables SSH logon.
-     * *   `false`: disables SSH logon.
+     * - `true`: Enable.
+     *
+     * - `false`: Disable.
      *
      * Default value: `false`.
      *
@@ -1369,26 +1596,27 @@ export declare class CreateClusterRequest extends $dara.Model {
     sshFlags?: boolean;
     /**
      * @remarks
-     * The labels that you want to add to nodes. You must add labels based on the following rules:
+     * Node labels. Label rules:
+     *
+     * - Labels consist of case-sensitive key-value pairs. You can add up to 20 tags.
      *
-     * *   A label is a case-sensitive key-value pair. You can add up to 20 labels.
-     * *   When you add a label, you must specify a unique key, but you can leave the value empty. A key cannot exceed 64 characters in length, and a value cannot exceed 128 characters in length. 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).
+     * - Tag keys must be unique and up to 64 characters long. Tag values can be empty and up to 128 characters long. Neither tag keys nor tag values can 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).
      */
     tags?: Tag[];
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `taints` parameter of the `kubernetes_config` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `taints` parameter under `kubernetes_config` in `nodepool`.
      *
-     * The taints that you want to add to nodes. Taints can be used together with tolerations to avoid scheduling pods to specific nodes. For more information, see [taint-and-toleration](https://kubernetes.io/zh/docs/concepts/scheduling-eviction/taint-and-toleration/).
+     * Node taint information. Taints and tolerations work together to prevent pods from being scheduled onto unsuitable nodes. For more information, see [taint-and-toleration](https://kubernetes.io/zh/docs/concepts/scheduling-eviction/taint-and-toleration/).
      *
      * @deprecated
      */
     taints?: Taint[];
     /**
      * @remarks
-     * [**Deprecated**] By default, the system does not perform a rollback when the cluster fails to be created. You must manually delete the cluster that fails to be created.
+     * **[Deprecated]** By default, clusters are not rolled back on creation failure. You must manually clean up failed clusters.
      *
-     * Specifies the timeout period of cluster creation. Unit: minutes.
+     * Cluster creation timeout in minutes.
      *
      * Default value: `60`.
      *
@@ -1400,7 +1628,7 @@ export declare class CreateClusterRequest extends $dara.Model {
     timeoutMins?: number;
     /**
      * @remarks
-     * The time zone of the cluster.
+     * Time zone used by the cluster. See [Supported time zones](https://help.aliyun.com/document_detail/354879.html).
      *
      * @example
      * Asia/Shanghai
@@ -1408,7 +1636,7 @@ export declare class CreateClusterRequest extends $dara.Model {
     timezone?: string;
     /**
      * @remarks
-     * The custom Certificate Authority (CA) certificate used by the cluster.
+     * Custom cluster CA.
      *
      * @example
      * -----BEGIN CERTIFICATE-----****
@@ -1416,7 +1644,7 @@ export declare class CreateClusterRequest extends $dara.Model {
     userCa?: string;
     /**
      * @remarks
-     * The user data of nodes.
+     * **[Deprecated]** Custom node data.
      *
      * @example
      * IyEvdXNyL2Jpbi9iYXNoCmVjaG8gIkhlbGxvIEFD****
@@ -1426,7 +1654,7 @@ export declare class CreateClusterRequest extends $dara.Model {
     userData?: string;
     /**
      * @remarks
-     * The virtual private cloud (VPC) in which you want to deploy the cluster. This parameter is required.
+     * The VPC used by the cluster. You must provide this when creating a cluster.
      *
      * @example
      * vpc-2zeik9h3ahvv2zz95****
@@ -1434,17 +1662,18 @@ export declare class CreateClusterRequest extends $dara.Model {
     vpcid?: string;
     /**
      * @remarks
-     * The vSwitches for nodes in the cluster. This parameter is required if you create an ACK managed cluster that does not contain nodes.
+     * Virtual switches for cluster nodes. This field is required when creating a zero-node managed cluster.
      */
     vswitchIds?: string[];
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `auto_renew` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `auto_renew` parameter under `scaling_group` in `nodepool`.
+     *
+     * Whether to enable auto-renewal for worker nodes. Valid only when `worker_instance_charge_type` is `PrePaid`. Valid values:
      *
-     * Specifies whether to enable auto-renewal for worker nodes. This parameter takes effect and is required only when `worker_instance_charge_type` is set to `PrePaid`. Valid values:
+     * - `true`: Enable auto-renewal.
      *
-     * *   `true`: enables auto-renewal.
-     * *   `false`: disables auto-renewal.
+     * - `false`: Disable auto-renewal.
      *
      * Default value: `true`.
      *
@@ -1456,11 +1685,11 @@ export declare class CreateClusterRequest extends $dara.Model {
     workerAutoRenew?: boolean;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `auto_renew_period` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `auto_renew_period` parameter under `scaling_group` in `nodepool`.
      *
-     * The auto-renewal duration of worker nodes. This parameter takes effect and is required only if the subscription billing method is selected for worker nodes.
+     * Auto-renewal period for worker nodes in months. Required and valid only when subscription billing is selected.
      *
-     * Valid values: 1, 2, 3, 6, and 12.
+     * Valid values: {1, 2, 3, 6, 12}.
      *
      * @example
      * 1
@@ -1470,23 +1699,24 @@ export declare class CreateClusterRequest extends $dara.Model {
     workerAutoRenewPeriod?: number;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `data_disks` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `data_disks` parameter under `scaling_group` in `nodepool`.
      *
-     * The configurations of the data disks that you want to mount to worker nodes. The configurations include the disk category and disk size.
+     * Configuration for worker node data disks, including type and size.
      *
      * @deprecated
      */
     workerDataDisks?: CreateClusterRequestWorkerDataDisks[];
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `instance_charge_type` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `instance_charge_type` parameter under `scaling_group` in `nodepool`.
      *
-     * The billing method of worker nodes. Valid values:
+     * Worker node billing type. Valid values:
      *
-     * *   `PrePaid`: subscription.
-     * *   `PostPaid`: pay-as-you-go.
+     * - `PrePaid`: Subscription.
      *
-     * Default value: PostPaid.
+     * - `PostPaid`: Pay-as-you-go.
+     *
+     * Default value: Pay-as-you-go.
      *
      * @example
      * PrePaid
@@ -1496,20 +1726,20 @@ export declare class CreateClusterRequest extends $dara.Model {
     workerInstanceChargeType?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `instance_types` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `instance_types` parameter under `scaling_group` in `nodepool`.
      *
-     * The instance configurations of worker nodes.
+     * Worker node instance configuration.
      *
      * @deprecated
      */
     workerInstanceTypes?: string[];
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `period` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `period` parameter under `scaling_group` in `nodepool`.
      *
-     * The subscription duration of worker nodes. This parameter takes effect and is required only when `worker_instance_charge_type` is set to `PrePaid`.
+     * Subscription duration for worker nodes in months. Required and valid only when `worker_instance_charge_type` is `PrePaid`.
      *
-     * Valid values: 1, 2, 3, 6, 12, 24, 36, 48, and 60.
+     * Valid values: {1, 2, 3, 6, 12, 24, 36, 48, 60}.
      *
      * Default value: 1.
      *
@@ -1521,11 +1751,11 @@ export declare class CreateClusterRequest extends $dara.Model {
     workerPeriod?: number;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `period_unit` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `period_unit` parameter under `scaling_group` in `nodepool`.
      *
-     * The billing cycle of worker nodes. This parameter is required if worker_instance_charge_type is set to `PrePaid`.
+     * Worker node billing cycle. Required when worker_instance_charge_type is `PrePaid`.
      *
-     * Valid value: `Month`, which indicates that worker nodes are billed only on a monthly basis.
+     * Valid value: `Month`. Only monthly billing is supported.
      *
      * @example
      * Month
@@ -1535,14 +1765,15 @@ export declare class CreateClusterRequest extends $dara.Model {
     workerPeriodUnit?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `system_disk_category` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `system_disk_category` parameter under `scaling_group` in `nodepool`.
      *
-     * The system disk category of worker nodes. For more information, see [Elastic Block Storage devices](https://help.aliyun.com/document_detail/63136.html).
+     * Worker node system disk type. For more information, see [Overview of Elastic Block Storage](https://help.aliyun.com/document_detail/63136.html).
      *
      * Valid values:
      *
-     * *   `cloud_efficiency`: ultra disk.
-     * *   `cloud_ssd`: standard SSD.
+     * - `cloud_efficiency`: Ultra disk.
+     *
+     * - `cloud_ssd`: Standard SSD.
      *
      * Default value: `cloud_ssd`.
      *
@@ -1554,16 +1785,19 @@ export declare class CreateClusterRequest extends $dara.Model {
     workerSystemDiskCategory?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `system_disk_performance_level` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `system_disk_performance_level` parameter under `scaling_group` in `nodepool`.
      *
-     * If the system disk is an ESSD, you can specify the PL of the ESSD. For more information, see [Enterprise SSDs](https://help.aliyun.com/document_detail/122389.html).
+     * When the system disk is an ESSD, you can set the performance level (PL). For more information, see [ESSD](https://help.aliyun.com/document_detail/122389.html).
      *
      * Valid values:
      *
-     * *   PL0
-     * *   PL1
-     * *   PL2
-     * *   PL3
+     * - PL0
+     *
+     * - PL1
+     *
+     * - PL2
+     *
+     * - PL3
      *
      * @example
      * PL1
@@ -1573,13 +1807,13 @@ export declare class CreateClusterRequest extends $dara.Model {
     workerSystemDiskPerformanceLevel?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `system_disk_size` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `system_disk_size` parameter under `scaling_group` in `nodepool`.
      *
-     * The system disk size of worker nodes. Unit: GiB.
+     * Worker node system disk size in GiB.
      *
-     * Valid values: 40 to 500.
+     * Valid range: [40,500].
      *
-     * The value of this parameter must be at least 40 and greater than or equal to the image size.
+     * This value must be greater than or equal to max{40, ImageSize}.
      *
      * Default value: `120`.
      *
@@ -1591,9 +1825,9 @@ export declare class CreateClusterRequest extends $dara.Model {
     workerSystemDiskSize?: number;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `system_disk_snapshot_policy_id` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `system_disk_snapshot_policy_id` parameter under `scaling_group` in `nodepool`.
      *
-     * The ID of the automatic snapshot policy that is used by the system disk specified for worker nodes.
+     * Automatic snapshot policy ID for worker node system disks.
      *
      * @example
      * sp-2zej1nogjvovnz4z****
@@ -1603,22 +1837,22 @@ export declare class CreateClusterRequest extends $dara.Model {
     workerSystemDiskSnapshotPolicyId?: string;
     /**
      * @remarks
-     * [**Deprecated**] When you configure a node pool, use the `vswitch_ids` parameter of the `scaling_group` field in the `nodepool` section instead.
+     * **[Deprecated]** For node pool configuration, use the `vswitch_ids` parameter under `scaling_group` in `nodepool`.
      *
-     * The vSwitches for worker nodes. Each worker node is allocated a vSwitch.
+     * List of vSwitches used by cluster nodes. One node corresponds to one value.
      *
-     * `worker_vswitch_ids` is optional, but `vswitch_ids` is required if you create an ACK managed cluster that does not contain nodes.
+     * When creating a zero-node managed cluster, `worker_vswitch_ids` is optional, but you must provide `vswitch_ids`.
      *
      * @deprecated
      */
     workerVswitchIds?: string[];
     /**
      * @remarks
-     * [Deprecated] Use the `zone_ids` parameter instead.
+     * **[Deprecated]** Use the `zone_ids` parameter instead.
      *
-     * The ID of the zone to which the cluster belongs. This parameter is specific to ACK Serverless clusters.
+     * The zone ID in the cluster region. This parameter applies only to ACK managed clusters.
      *
-     * When you create an ACK managed cluster, you must set the `zone_id` parameter if `vpc_id` and `vswitch_ids` are not specified. This way, the system automatically creates a VPC in the specified zone. This parameter is invalid if you specify the `vpc_id` and `vswitch_ids` parameters.
+     * When creating an ACK managed cluster, if you do not specify `vpc_id` and `vswitch_ids`, you must specify `zone_id` to automatically create VPC network resources in this zone. This parameter is ignored if you specify `vpc_id` and `vswitch_ids`.
      *
      * @example
      * cn-beiji****
@@ -1628,9 +1862,7 @@ export declare class CreateClusterRequest extends $dara.Model {
     zoneId?: string;
     /**
      * @remarks
-     * The IDs of the zone in which the cluster is deployed. This parameter is specific to ACK managed clusters.
-     *
-     * When you create an ACK managed cluster, you must set the `zone_id` parameter if `vpc_id` and `vswitch_ids` are not specified. This way, the system automatically creates a VPC in the specified zone. This parameter is invalid if you specify the `vpc_id` and `vswitch_ids` parameters.
+     * A list of zone IDs in the cluster region. This parameter applies only to ACK managed clusters.
      */
     zoneIds?: string[];
     static names(): {