@alicloud/cs20151215 4.0.7 → 4.0.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/client.d.ts CHANGED
@@ -7326,916 +7326,2268 @@ export default class Client extends OpenApi {
7326
7326
  getEndpoint(productId: string, regionId: string, endpointRule: string, network: string, suffix: string, endpointMap: {
7327
7327
  [key: string]: string;
7328
7328
  }, endpoint: string): string;
7329
+ /**
7330
+ * @summary You can call the AttachInstances operation to add existing Elastic Compute Service (ECS) instances to a cluster.
7331
+ *
7332
+ * @param request AttachInstancesRequest
7333
+ * @param headers map
7334
+ * @param runtime runtime options for this request RuntimeOptions
7335
+ * @return AttachInstancesResponse
7336
+ */
7329
7337
  attachInstancesWithOptions(ClusterId: string, request: AttachInstancesRequest, headers: {
7330
7338
  [key: string]: string;
7331
7339
  }, runtime: $Util.RuntimeOptions): Promise<AttachInstancesResponse>;
7340
+ /**
7341
+ * @summary You can call the AttachInstances operation to add existing Elastic Compute Service (ECS) instances to a cluster.
7342
+ *
7343
+ * @param request AttachInstancesRequest
7344
+ * @return AttachInstancesResponse
7345
+ */
7332
7346
  attachInstances(ClusterId: string, request: AttachInstancesRequest): Promise<AttachInstancesResponse>;
7347
+ /**
7348
+ * @summary You can call the AttachInstancesToNodePool operation to add existing nodes to a node pool.
7349
+ *
7350
+ * @param request AttachInstancesToNodePoolRequest
7351
+ * @param headers map
7352
+ * @param runtime runtime options for this request RuntimeOptions
7353
+ * @return AttachInstancesToNodePoolResponse
7354
+ */
7333
7355
  attachInstancesToNodePoolWithOptions(ClusterId: string, NodepoolId: string, request: AttachInstancesToNodePoolRequest, headers: {
7334
7356
  [key: string]: string;
7335
7357
  }, runtime: $Util.RuntimeOptions): Promise<AttachInstancesToNodePoolResponse>;
7358
+ /**
7359
+ * @summary You can call the AttachInstancesToNodePool operation to add existing nodes to a node pool.
7360
+ *
7361
+ * @param request AttachInstancesToNodePoolRequest
7362
+ * @return AttachInstancesToNodePoolResponse
7363
+ */
7336
7364
  attachInstancesToNodePool(ClusterId: string, NodepoolId: string, request: AttachInstancesToNodePoolRequest): Promise<AttachInstancesToNodePoolResponse>;
7337
7365
  /**
7338
- * @deprecated
7339
- *
7340
- * @param headers map
7341
- * @param runtime runtime options for this request RuntimeOptions
7342
- * @return CancelClusterUpgradeResponse
7366
+ * @deprecated OpenAPI CancelClusterUpgrade is deprecated
7367
+ *
7368
+ * @summary You can call the CancelClusterUpgrade operation to cancel the update of a cluster.
7369
+ *
7370
+ * @param headers map
7371
+ * @param runtime runtime options for this request RuntimeOptions
7372
+ * @return CancelClusterUpgradeResponse
7343
7373
  */
7344
7374
  cancelClusterUpgradeWithOptions(ClusterId: string, headers: {
7345
7375
  [key: string]: string;
7346
7376
  }, runtime: $Util.RuntimeOptions): Promise<CancelClusterUpgradeResponse>;
7347
7377
  /**
7348
- * @deprecated
7349
- *
7350
- * @return CancelClusterUpgradeResponse
7378
+ * @deprecated OpenAPI CancelClusterUpgrade is deprecated
7379
+ *
7380
+ * @summary You can call the CancelClusterUpgrade operation to cancel the update of a cluster.
7381
+ *
7382
+ * @return CancelClusterUpgradeResponse
7351
7383
  */
7352
7384
  cancelClusterUpgrade(ClusterId: string): Promise<CancelClusterUpgradeResponse>;
7385
+ /**
7386
+ * @summary You can call the CancelComponentUpgrade operation to cancel the update of a component.
7387
+ *
7388
+ * @param headers map
7389
+ * @param runtime runtime options for this request RuntimeOptions
7390
+ * @return CancelComponentUpgradeResponse
7391
+ */
7353
7392
  cancelComponentUpgradeWithOptions(clusterId: string, componentId: string, headers: {
7354
7393
  [key: string]: string;
7355
7394
  }, runtime: $Util.RuntimeOptions): Promise<CancelComponentUpgradeResponse>;
7395
+ /**
7396
+ * @summary You can call the CancelComponentUpgrade operation to cancel the update of a component.
7397
+ *
7398
+ * @return CancelComponentUpgradeResponse
7399
+ */
7356
7400
  cancelComponentUpgrade(clusterId: string, componentId: string): Promise<CancelComponentUpgradeResponse>;
7401
+ /**
7402
+ * @summary 取消自动运维执行计划
7403
+ *
7404
+ * @param headers map
7405
+ * @param runtime runtime options for this request RuntimeOptions
7406
+ * @return CancelOperationPlanResponse
7407
+ */
7357
7408
  cancelOperationPlanWithOptions(planId: string, headers: {
7358
7409
  [key: string]: string;
7359
7410
  }, runtime: $Util.RuntimeOptions): Promise<CancelOperationPlanResponse>;
7411
+ /**
7412
+ * @summary 取消自动运维执行计划
7413
+ *
7414
+ * @return CancelOperationPlanResponse
7415
+ */
7360
7416
  cancelOperationPlan(planId: string): Promise<CancelOperationPlanResponse>;
7417
+ /**
7418
+ * @summary You can call the CancelTask operation to cancel a task.
7419
+ *
7420
+ * @param headers map
7421
+ * @param runtime runtime options for this request RuntimeOptions
7422
+ * @return CancelTaskResponse
7423
+ */
7361
7424
  cancelTaskWithOptions(taskId: string, headers: {
7362
7425
  [key: string]: string;
7363
7426
  }, runtime: $Util.RuntimeOptions): Promise<CancelTaskResponse>;
7427
+ /**
7428
+ * @summary You can call the CancelTask operation to cancel a task.
7429
+ *
7430
+ * @return CancelTaskResponse
7431
+ */
7364
7432
  cancelTask(taskId: string): Promise<CancelTaskResponse>;
7433
+ /**
7434
+ * @summary You can call the CancelWorkflow operation to cancel an ongoing workflow.
7435
+ *
7436
+ * @param request CancelWorkflowRequest
7437
+ * @param headers map
7438
+ * @param runtime runtime options for this request RuntimeOptions
7439
+ * @return CancelWorkflowResponse
7440
+ */
7365
7441
  cancelWorkflowWithOptions(workflowName: string, request: CancelWorkflowRequest, headers: {
7366
7442
  [key: string]: string;
7367
7443
  }, runtime: $Util.RuntimeOptions): Promise<CancelWorkflowResponse>;
7444
+ /**
7445
+ * @summary You can call the CancelWorkflow operation to cancel an ongoing workflow.
7446
+ *
7447
+ * @param request CancelWorkflowRequest
7448
+ * @return CancelWorkflowResponse
7449
+ */
7368
7450
  cancelWorkflow(workflowName: string, request: CancelWorkflowRequest): Promise<CancelWorkflowResponse>;
7451
+ /**
7452
+ * @summary Queries the current log configuration of control plane components, including the log retention period and the log collection component. Container Service for Kubernetes (ACK) managed clusters can collect the logs of control plane components and deliver the logs to projects in Simple Log Service. These control plane components include Kube API Server, Kube Scheduler, Kube Controller Manager, and Cloud Controller Manager.
7453
+ *
7454
+ * @param headers map
7455
+ * @param runtime runtime options for this request RuntimeOptions
7456
+ * @return CheckControlPlaneLogEnableResponse
7457
+ */
7369
7458
  checkControlPlaneLogEnableWithOptions(ClusterId: string, headers: {
7370
7459
  [key: string]: string;
7371
7460
  }, runtime: $Util.RuntimeOptions): Promise<CheckControlPlaneLogEnableResponse>;
7461
+ /**
7462
+ * @summary Queries the current log configuration of control plane components, including the log retention period and the log collection component. Container Service for Kubernetes (ACK) managed clusters can collect the logs of control plane components and deliver the logs to projects in Simple Log Service. These control plane components include Kube API Server, Kube Scheduler, Kube Controller Manager, and Cloud Controller Manager.
7463
+ *
7464
+ * @return CheckControlPlaneLogEnableResponse
7465
+ */
7372
7466
  checkControlPlaneLogEnable(ClusterId: string): Promise<CheckControlPlaneLogEnableResponse>;
7467
+ /**
7468
+ * @summary Creates a scaling configuration to allow the system to scale resources based on the given scaling rules. When you create a scaling configuration, you can specify the scaling metrics, thresholds, scaling order, and scaling interval.
7469
+ *
7470
+ * @param request CreateAutoscalingConfigRequest
7471
+ * @param headers map
7472
+ * @param runtime runtime options for this request RuntimeOptions
7473
+ * @return CreateAutoscalingConfigResponse
7474
+ */
7373
7475
  createAutoscalingConfigWithOptions(ClusterId: string, request: CreateAutoscalingConfigRequest, headers: {
7374
7476
  [key: string]: string;
7375
7477
  }, runtime: $Util.RuntimeOptions): Promise<CreateAutoscalingConfigResponse>;
7478
+ /**
7479
+ * @summary Creates a scaling configuration to allow the system to scale resources based on the given scaling rules. When you create a scaling configuration, you can specify the scaling metrics, thresholds, scaling order, and scaling interval.
7480
+ *
7481
+ * @param request CreateAutoscalingConfigRequest
7482
+ * @return CreateAutoscalingConfigResponse
7483
+ */
7376
7484
  createAutoscalingConfig(ClusterId: string, request: CreateAutoscalingConfigRequest): Promise<CreateAutoscalingConfigResponse>;
7377
7485
  /**
7378
- * This topic describes all parameters for creating an ACK cluster. You can create the following types of ACK clusters.
7379
- * * [Create an ACK managed cluster](~~90776~~)
7380
- * * [Create an ACK dedicated cluster](~~197620~~)
7381
- * * [Create an ACK Serverless cluster](~~144246~~)
7382
- * * [Create an ACK Edge cluster](~~128204~~)
7383
- * * [Create an ACK Basic cluster that supports sandboxed containers](~~196321~~)
7384
- * * [Create an ACK Pro cluster that supports sandboxed containers](~~140623~~)
7385
- *
7386
- * @param request CreateClusterRequest
7387
- * @param headers map
7388
- * @param runtime runtime options for this request RuntimeOptions
7389
- * @return CreateClusterResponse
7486
+ * @summary You can call the CreateCluster operation to create a Container Service for Kubernetes (ACK) cluster. ACK clusters include ACK managed clusters, ACK dedicated clusters, ACK Serverless clusters, ACK Edge clusters, ACK clusters that support sandboxed containers, and registered clusters. For more information about how to create different types of ACK clusters, see the following usage notes.
7487
+ *
7488
+ * @description This topic describes all parameters for creating an ACK cluster. You can create the following types of ACK clusters.
7489
+ * * [Create an ACK managed cluster](https://help.aliyun.com/document_detail/90776.html)
7490
+ * * [Create an ACK dedicated cluster](https://help.aliyun.com/document_detail/197620.html)
7491
+ * * [Create an ACK Serverless cluster](https://help.aliyun.com/document_detail/144246.html)
7492
+ * * [Create an ACK Edge cluster](https://help.aliyun.com/document_detail/128204.html)
7493
+ * * [Create an ACK Basic cluster that supports sandboxed containers](https://help.aliyun.com/document_detail/196321.html)
7494
+ * * [Create an ACK Pro cluster that supports sandboxed containers](https://help.aliyun.com/document_detail/140623.html)
7495
+ *
7496
+ * @param request CreateClusterRequest
7497
+ * @param headers map
7498
+ * @param runtime runtime options for this request RuntimeOptions
7499
+ * @return CreateClusterResponse
7390
7500
  */
7391
7501
  createClusterWithOptions(request: CreateClusterRequest, headers: {
7392
7502
  [key: string]: string;
7393
7503
  }, runtime: $Util.RuntimeOptions): Promise<CreateClusterResponse>;
7394
7504
  /**
7395
- * This topic describes all parameters for creating an ACK cluster. You can create the following types of ACK clusters.
7396
- * * [Create an ACK managed cluster](~~90776~~)
7397
- * * [Create an ACK dedicated cluster](~~197620~~)
7398
- * * [Create an ACK Serverless cluster](~~144246~~)
7399
- * * [Create an ACK Edge cluster](~~128204~~)
7400
- * * [Create an ACK Basic cluster that supports sandboxed containers](~~196321~~)
7401
- * * [Create an ACK Pro cluster that supports sandboxed containers](~~140623~~)
7402
- *
7403
- * @param request CreateClusterRequest
7404
- * @return CreateClusterResponse
7505
+ * @summary You can call the CreateCluster operation to create a Container Service for Kubernetes (ACK) cluster. ACK clusters include ACK managed clusters, ACK dedicated clusters, ACK Serverless clusters, ACK Edge clusters, ACK clusters that support sandboxed containers, and registered clusters. For more information about how to create different types of ACK clusters, see the following usage notes.
7506
+ *
7507
+ * @description This topic describes all parameters for creating an ACK cluster. You can create the following types of ACK clusters.
7508
+ * * [Create an ACK managed cluster](https://help.aliyun.com/document_detail/90776.html)
7509
+ * * [Create an ACK dedicated cluster](https://help.aliyun.com/document_detail/197620.html)
7510
+ * * [Create an ACK Serverless cluster](https://help.aliyun.com/document_detail/144246.html)
7511
+ * * [Create an ACK Edge cluster](https://help.aliyun.com/document_detail/128204.html)
7512
+ * * [Create an ACK Basic cluster that supports sandboxed containers](https://help.aliyun.com/document_detail/196321.html)
7513
+ * * [Create an ACK Pro cluster that supports sandboxed containers](https://help.aliyun.com/document_detail/140623.html)
7514
+ *
7515
+ * @param request CreateClusterRequest
7516
+ * @return CreateClusterResponse
7405
7517
  */
7406
7518
  createCluster(request: CreateClusterRequest): Promise<CreateClusterResponse>;
7519
+ /**
7520
+ * @summary You can call the CreateClusterNodePool operation to create a node pool for a Container Service for Kubernetes (ACK) cluster.
7521
+ *
7522
+ * @param request CreateClusterNodePoolRequest
7523
+ * @param headers map
7524
+ * @param runtime runtime options for this request RuntimeOptions
7525
+ * @return CreateClusterNodePoolResponse
7526
+ */
7407
7527
  createClusterNodePoolWithOptions(ClusterId: string, request: CreateClusterNodePoolRequest, headers: {
7408
7528
  [key: string]: string;
7409
7529
  }, runtime: $Util.RuntimeOptions): Promise<CreateClusterNodePoolResponse>;
7530
+ /**
7531
+ * @summary You can call the CreateClusterNodePool operation to create a node pool for a Container Service for Kubernetes (ACK) cluster.
7532
+ *
7533
+ * @param request CreateClusterNodePoolRequest
7534
+ * @return CreateClusterNodePoolResponse
7535
+ */
7410
7536
  createClusterNodePool(ClusterId: string, request: CreateClusterNodePoolRequest): Promise<CreateClusterNodePoolResponse>;
7537
+ /**
7538
+ * @summary You can call the CreateEdgeMachine operation to activate a cloud-native box.
7539
+ *
7540
+ * @param request CreateEdgeMachineRequest
7541
+ * @param headers map
7542
+ * @param runtime runtime options for this request RuntimeOptions
7543
+ * @return CreateEdgeMachineResponse
7544
+ */
7411
7545
  createEdgeMachineWithOptions(request: CreateEdgeMachineRequest, headers: {
7412
7546
  [key: string]: string;
7413
7547
  }, runtime: $Util.RuntimeOptions): Promise<CreateEdgeMachineResponse>;
7548
+ /**
7549
+ * @summary You can call the CreateEdgeMachine operation to activate a cloud-native box.
7550
+ *
7551
+ * @param request CreateEdgeMachineRequest
7552
+ * @return CreateEdgeMachineResponse
7553
+ */
7414
7554
  createEdgeMachine(request: CreateEdgeMachineRequest): Promise<CreateEdgeMachineResponse>;
7555
+ /**
7556
+ * @summary You can call the CreateKubernetesTrigger operation to create a trigger for an application.
7557
+ *
7558
+ * @param request CreateKubernetesTriggerRequest
7559
+ * @param headers map
7560
+ * @param runtime runtime options for this request RuntimeOptions
7561
+ * @return CreateKubernetesTriggerResponse
7562
+ */
7415
7563
  createKubernetesTriggerWithOptions(request: CreateKubernetesTriggerRequest, headers: {
7416
7564
  [key: string]: string;
7417
7565
  }, runtime: $Util.RuntimeOptions): Promise<CreateKubernetesTriggerResponse>;
7566
+ /**
7567
+ * @summary You can call the CreateKubernetesTrigger operation to create a trigger for an application.
7568
+ *
7569
+ * @param request CreateKubernetesTriggerRequest
7570
+ * @return CreateKubernetesTriggerResponse
7571
+ */
7418
7572
  createKubernetesTrigger(request: CreateKubernetesTriggerRequest): Promise<CreateKubernetesTriggerResponse>;
7573
+ /**
7574
+ * @summary Creates an orchestration template. An orchestration template defines and describes a group of Kubernetes resources. It declaratively describes the configuration of an application or how an application runs. You can use orchestration templates to manage resources in Kubernetes clusters and automate resource deployment, such as pods, Services, Deployments, ConfigMaps, and persistent volumes (PVs).
7575
+ *
7576
+ * @param request CreateTemplateRequest
7577
+ * @param headers map
7578
+ * @param runtime runtime options for this request RuntimeOptions
7579
+ * @return CreateTemplateResponse
7580
+ */
7419
7581
  createTemplateWithOptions(request: CreateTemplateRequest, headers: {
7420
7582
  [key: string]: string;
7421
7583
  }, runtime: $Util.RuntimeOptions): Promise<CreateTemplateResponse>;
7584
+ /**
7585
+ * @summary Creates an orchestration template. An orchestration template defines and describes a group of Kubernetes resources. It declaratively describes the configuration of an application or how an application runs. You can use orchestration templates to manage resources in Kubernetes clusters and automate resource deployment, such as pods, Services, Deployments, ConfigMaps, and persistent volumes (PVs).
7586
+ *
7587
+ * @param request CreateTemplateRequest
7588
+ * @return CreateTemplateResponse
7589
+ */
7422
7590
  createTemplate(request: CreateTemplateRequest): Promise<CreateTemplateResponse>;
7591
+ /**
7592
+ * @summary You can call the CreateTrigger operation to create a trigger for an application.
7593
+ *
7594
+ * @param request CreateTriggerRequest
7595
+ * @param headers map
7596
+ * @param runtime runtime options for this request RuntimeOptions
7597
+ * @return CreateTriggerResponse
7598
+ */
7423
7599
  createTriggerWithOptions(clusterId: string, request: CreateTriggerRequest, headers: {
7424
7600
  [key: string]: string;
7425
7601
  }, runtime: $Util.RuntimeOptions): Promise<CreateTriggerResponse>;
7602
+ /**
7603
+ * @summary You can call the CreateTrigger operation to create a trigger for an application.
7604
+ *
7605
+ * @param request CreateTriggerRequest
7606
+ * @return CreateTriggerResponse
7607
+ */
7426
7608
  createTrigger(clusterId: string, request: CreateTriggerRequest): Promise<CreateTriggerResponse>;
7609
+ /**
7610
+ * @param tmpReq DeleteAlertContactRequest
7611
+ * @param headers map
7612
+ * @param runtime runtime options for this request RuntimeOptions
7613
+ * @return DeleteAlertContactResponse
7614
+ */
7427
7615
  deleteAlertContactWithOptions(tmpReq: DeleteAlertContactRequest, headers: {
7428
7616
  [key: string]: string;
7429
7617
  }, runtime: $Util.RuntimeOptions): Promise<DeleteAlertContactResponse>;
7618
+ /**
7619
+ * @param request DeleteAlertContactRequest
7620
+ * @return DeleteAlertContactResponse
7621
+ */
7430
7622
  deleteAlertContact(request: DeleteAlertContactRequest): Promise<DeleteAlertContactResponse>;
7623
+ /**
7624
+ * @param tmpReq DeleteAlertContactGroupRequest
7625
+ * @param headers map
7626
+ * @param runtime runtime options for this request RuntimeOptions
7627
+ * @return DeleteAlertContactGroupResponse
7628
+ */
7431
7629
  deleteAlertContactGroupWithOptions(tmpReq: DeleteAlertContactGroupRequest, headers: {
7432
7630
  [key: string]: string;
7433
7631
  }, runtime: $Util.RuntimeOptions): Promise<DeleteAlertContactGroupResponse>;
7632
+ /**
7633
+ * @param request DeleteAlertContactGroupRequest
7634
+ * @return DeleteAlertContactGroupResponse
7635
+ */
7434
7636
  deleteAlertContactGroup(request: DeleteAlertContactGroupRequest): Promise<DeleteAlertContactGroupResponse>;
7637
+ /**
7638
+ * @summary You can call the DeleteCluster operation to delete a cluster by cluster ID and release all nodes in the cluster.
7639
+ *
7640
+ * @param tmpReq DeleteClusterRequest
7641
+ * @param headers map
7642
+ * @param runtime runtime options for this request RuntimeOptions
7643
+ * @return DeleteClusterResponse
7644
+ */
7435
7645
  deleteClusterWithOptions(ClusterId: string, tmpReq: DeleteClusterRequest, headers: {
7436
7646
  [key: string]: string;
7437
7647
  }, runtime: $Util.RuntimeOptions): Promise<DeleteClusterResponse>;
7648
+ /**
7649
+ * @summary You can call the DeleteCluster operation to delete a cluster by cluster ID and release all nodes in the cluster.
7650
+ *
7651
+ * @param request DeleteClusterRequest
7652
+ * @return DeleteClusterResponse
7653
+ */
7438
7654
  deleteCluster(ClusterId: string, request: DeleteClusterRequest): Promise<DeleteClusterResponse>;
7655
+ /**
7656
+ * @summary You can call the DeleteClusterNodepool operation to delete a node pool by node pool ID.
7657
+ *
7658
+ * @param request DeleteClusterNodepoolRequest
7659
+ * @param headers map
7660
+ * @param runtime runtime options for this request RuntimeOptions
7661
+ * @return DeleteClusterNodepoolResponse
7662
+ */
7439
7663
  deleteClusterNodepoolWithOptions(ClusterId: string, NodepoolId: string, request: DeleteClusterNodepoolRequest, headers: {
7440
7664
  [key: string]: string;
7441
7665
  }, runtime: $Util.RuntimeOptions): Promise<DeleteClusterNodepoolResponse>;
7666
+ /**
7667
+ * @summary You can call the DeleteClusterNodepool operation to delete a node pool by node pool ID.
7668
+ *
7669
+ * @param request DeleteClusterNodepoolRequest
7670
+ * @return DeleteClusterNodepoolResponse
7671
+ */
7442
7672
  deleteClusterNodepool(ClusterId: string, NodepoolId: string, request: DeleteClusterNodepoolRequest): Promise<DeleteClusterNodepoolResponse>;
7443
7673
  /**
7444
- * >
7445
- * * When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours. - The operation may have unexpected risks. Back up the data before you perform this operation. - When the system removes a node, it sets the status of the node to Unschedulable. - The system removes only worker nodes. It does not remove master nodes.
7446
- *
7447
- * @param request DeleteClusterNodesRequest
7448
- * @param headers map
7449
- * @param runtime runtime options for this request RuntimeOptions
7450
- * @return DeleteClusterNodesResponse
7674
+ * @summary Removes nodes from a Container Service for Kubernetes (ACK) cluster. When you remove nodes, you can specify whether to release the Elastic Compute Service (ECS) instances and drain the nodes. When you remove nodes, pods on the nodes are migrated. This may adversely affect your businesses. We recommend that you back up data and perform this operation during off-peak hours.
7675
+ *
7676
+ * @description >
7677
+ * * When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours. - The operation may have unexpected risks. Back up the data before you perform this operation. - When the system removes a node, it sets the status of the node to Unschedulable. - The system removes only worker nodes. It does not remove master nodes.
7678
+ *
7679
+ * @param request DeleteClusterNodesRequest
7680
+ * @param headers map
7681
+ * @param runtime runtime options for this request RuntimeOptions
7682
+ * @return DeleteClusterNodesResponse
7451
7683
  */
7452
7684
  deleteClusterNodesWithOptions(ClusterId: string, request: DeleteClusterNodesRequest, headers: {
7453
7685
  [key: string]: string;
7454
7686
  }, runtime: $Util.RuntimeOptions): Promise<DeleteClusterNodesResponse>;
7455
7687
  /**
7456
- * >
7457
- * * When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours. - The operation may have unexpected risks. Back up the data before you perform this operation. - When the system removes a node, it sets the status of the node to Unschedulable. - The system removes only worker nodes. It does not remove master nodes.
7458
- *
7459
- * @param request DeleteClusterNodesRequest
7460
- * @return DeleteClusterNodesResponse
7688
+ * @summary Removes nodes from a Container Service for Kubernetes (ACK) cluster. When you remove nodes, you can specify whether to release the Elastic Compute Service (ECS) instances and drain the nodes. When you remove nodes, pods on the nodes are migrated. This may adversely affect your businesses. We recommend that you back up data and perform this operation during off-peak hours.
7689
+ *
7690
+ * @description >
7691
+ * * When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours. - The operation may have unexpected risks. Back up the data before you perform this operation. - When the system removes a node, it sets the status of the node to Unschedulable. - The system removes only worker nodes. It does not remove master nodes.
7692
+ *
7693
+ * @param request DeleteClusterNodesRequest
7694
+ * @return DeleteClusterNodesResponse
7461
7695
  */
7462
7696
  deleteClusterNodes(ClusterId: string, request: DeleteClusterNodesRequest): Promise<DeleteClusterNodesResponse>;
7697
+ /**
7698
+ * @summary You can call the DeleteEdgeMachine operation to delete a cloud-native box.
7699
+ *
7700
+ * @param request DeleteEdgeMachineRequest
7701
+ * @param headers map
7702
+ * @param runtime runtime options for this request RuntimeOptions
7703
+ * @return DeleteEdgeMachineResponse
7704
+ */
7463
7705
  deleteEdgeMachineWithOptions(edgeMachineid: string, request: DeleteEdgeMachineRequest, headers: {
7464
7706
  [key: string]: string;
7465
7707
  }, runtime: $Util.RuntimeOptions): Promise<DeleteEdgeMachineResponse>;
7708
+ /**
7709
+ * @summary You can call the DeleteEdgeMachine operation to delete a cloud-native box.
7710
+ *
7711
+ * @param request DeleteEdgeMachineRequest
7712
+ * @return DeleteEdgeMachineResponse
7713
+ */
7466
7714
  deleteEdgeMachine(edgeMachineid: string, request: DeleteEdgeMachineRequest): Promise<DeleteEdgeMachineResponse>;
7715
+ /**
7716
+ * @summary You can call the DeleteKubernetesTrigger operation to delete an application trigger by trigger ID
7717
+ *
7718
+ * @param headers map
7719
+ * @param runtime runtime options for this request RuntimeOptions
7720
+ * @return DeleteKubernetesTriggerResponse
7721
+ */
7467
7722
  deleteKubernetesTriggerWithOptions(Id: string, headers: {
7468
7723
  [key: string]: string;
7469
7724
  }, runtime: $Util.RuntimeOptions): Promise<DeleteKubernetesTriggerResponse>;
7725
+ /**
7726
+ * @summary You can call the DeleteKubernetesTrigger operation to delete an application trigger by trigger ID
7727
+ *
7728
+ * @return DeleteKubernetesTriggerResponse
7729
+ */
7470
7730
  deleteKubernetesTrigger(Id: string): Promise<DeleteKubernetesTriggerResponse>;
7731
+ /**
7732
+ * @summary Deletes policy instances in a Container Service for Kubernetes (ACK) cluster.
7733
+ *
7734
+ * @param request DeletePolicyInstanceRequest
7735
+ * @param headers map
7736
+ * @param runtime runtime options for this request RuntimeOptions
7737
+ * @return DeletePolicyInstanceResponse
7738
+ */
7471
7739
  deletePolicyInstanceWithOptions(clusterId: string, policyName: string, request: DeletePolicyInstanceRequest, headers: {
7472
7740
  [key: string]: string;
7473
7741
  }, runtime: $Util.RuntimeOptions): Promise<DeletePolicyInstanceResponse>;
7742
+ /**
7743
+ * @summary Deletes policy instances in a Container Service for Kubernetes (ACK) cluster.
7744
+ *
7745
+ * @param request DeletePolicyInstanceRequest
7746
+ * @return DeletePolicyInstanceResponse
7747
+ */
7474
7748
  deletePolicyInstance(clusterId: string, policyName: string, request: DeletePolicyInstanceRequest): Promise<DeletePolicyInstanceResponse>;
7749
+ /**
7750
+ * @summary You can call the DeleteTemplate operation to delete an orchestration template by template ID.
7751
+ *
7752
+ * @param headers map
7753
+ * @param runtime runtime options for this request RuntimeOptions
7754
+ * @return DeleteTemplateResponse
7755
+ */
7475
7756
  deleteTemplateWithOptions(TemplateId: string, headers: {
7476
7757
  [key: string]: string;
7477
7758
  }, runtime: $Util.RuntimeOptions): Promise<DeleteTemplateResponse>;
7759
+ /**
7760
+ * @summary You can call the DeleteTemplate operation to delete an orchestration template by template ID.
7761
+ *
7762
+ * @return DeleteTemplateResponse
7763
+ */
7478
7764
  deleteTemplate(TemplateId: string): Promise<DeleteTemplateResponse>;
7765
+ /**
7766
+ * @summary You can call the DeleteTrigger operation to delete an application trigger.
7767
+ *
7768
+ * @param headers map
7769
+ * @param runtime runtime options for this request RuntimeOptions
7770
+ * @return DeleteTriggerResponse
7771
+ */
7479
7772
  deleteTriggerWithOptions(clusterId: string, Id: string, headers: {
7480
7773
  [key: string]: string;
7481
7774
  }, runtime: $Util.RuntimeOptions): Promise<DeleteTriggerResponse>;
7775
+ /**
7776
+ * @summary You can call the DeleteTrigger operation to delete an application trigger.
7777
+ *
7778
+ * @return DeleteTriggerResponse
7779
+ */
7482
7780
  deleteTrigger(clusterId: string, Id: string): Promise<DeleteTriggerResponse>;
7781
+ /**
7782
+ * @summary You can call the DeployPolicyInstance operation to deploy a policy instance in a cluster.
7783
+ *
7784
+ * @param request DeployPolicyInstanceRequest
7785
+ * @param headers map
7786
+ * @param runtime runtime options for this request RuntimeOptions
7787
+ * @return DeployPolicyInstanceResponse
7788
+ */
7483
7789
  deployPolicyInstanceWithOptions(clusterId: string, policyName: string, request: DeployPolicyInstanceRequest, headers: {
7484
7790
  [key: string]: string;
7485
7791
  }, runtime: $Util.RuntimeOptions): Promise<DeployPolicyInstanceResponse>;
7792
+ /**
7793
+ * @summary You can call the DeployPolicyInstance operation to deploy a policy instance in a cluster.
7794
+ *
7795
+ * @param request DeployPolicyInstanceRequest
7796
+ * @return DeployPolicyInstanceResponse
7797
+ */
7486
7798
  deployPolicyInstance(clusterId: string, policyName: string, request: DeployPolicyInstanceRequest): Promise<DeployPolicyInstanceResponse>;
7799
+ /**
7800
+ * @summary You can call the DescirbeWorkflow operation to query detailed information about a workflow.
7801
+ *
7802
+ * @param headers map
7803
+ * @param runtime runtime options for this request RuntimeOptions
7804
+ * @return DescirbeWorkflowResponse
7805
+ */
7487
7806
  descirbeWorkflowWithOptions(workflowName: string, headers: {
7488
7807
  [key: string]: string;
7489
7808
  }, runtime: $Util.RuntimeOptions): Promise<DescirbeWorkflowResponse>;
7809
+ /**
7810
+ * @summary You can call the DescirbeWorkflow operation to query detailed information about a workflow.
7811
+ *
7812
+ * @return DescirbeWorkflowResponse
7813
+ */
7490
7814
  descirbeWorkflow(workflowName: string): Promise<DescirbeWorkflowResponse>;
7815
+ /**
7816
+ * @summary 查询指定集群组件
7817
+ *
7818
+ * @param request DescribeAddonRequest
7819
+ * @param headers map
7820
+ * @param runtime runtime options for this request RuntimeOptions
7821
+ * @return DescribeAddonResponse
7822
+ */
7491
7823
  describeAddonWithOptions(addonName: string, request: DescribeAddonRequest, headers: {
7492
7824
  [key: string]: string;
7493
7825
  }, runtime: $Util.RuntimeOptions): Promise<DescribeAddonResponse>;
7826
+ /**
7827
+ * @summary 查询指定集群组件
7828
+ *
7829
+ * @param request DescribeAddonRequest
7830
+ * @return DescribeAddonResponse
7831
+ */
7494
7832
  describeAddon(addonName: string, request: DescribeAddonRequest): Promise<DescribeAddonResponse>;
7495
7833
  /**
7496
- * @deprecated
7497
- *
7498
- * @param request DescribeAddonsRequest
7499
- * @param headers map
7500
- * @param runtime runtime options for this request RuntimeOptions
7501
- * @return DescribeAddonsResponse
7834
+ * @deprecated OpenAPI DescribeAddons is deprecated
7835
+ *
7836
+ * @summary You can call the DescribeAddons operation to query the details about all components that are supported by Container Service for Kubernetes (ACK).
7837
+ *
7838
+ * @param request DescribeAddonsRequest
7839
+ * @param headers map
7840
+ * @param runtime runtime options for this request RuntimeOptions
7841
+ * @return DescribeAddonsResponse
7502
7842
  */
7503
7843
  describeAddonsWithOptions(request: DescribeAddonsRequest, headers: {
7504
7844
  [key: string]: string;
7505
7845
  }, runtime: $Util.RuntimeOptions): Promise<DescribeAddonsResponse>;
7506
7846
  /**
7507
- * @deprecated
7508
- *
7509
- * @param request DescribeAddonsRequest
7510
- * @return DescribeAddonsResponse
7847
+ * @deprecated OpenAPI DescribeAddons is deprecated
7848
+ *
7849
+ * @summary You can call the DescribeAddons operation to query the details about all components that are supported by Container Service for Kubernetes (ACK).
7850
+ *
7851
+ * @param request DescribeAddonsRequest
7852
+ * @return DescribeAddonsResponse
7511
7853
  */
7512
7854
  describeAddons(request: DescribeAddonsRequest): Promise<DescribeAddonsResponse>;
7513
7855
  /**
7514
- * @deprecated
7515
- *
7516
- * @param headers map
7517
- * @param runtime runtime options for this request RuntimeOptions
7518
- * @return DescribeClusterAddonInstanceResponse
7856
+ * @deprecated OpenAPI DescribeClusterAddonInstance is deprecated
7857
+ *
7858
+ * @summary You can call the DescribeClusterAddonInstance operation to query the information about a cluster component, including the version, status, and configuration of the component.
7859
+ *
7860
+ * @param headers map
7861
+ * @param runtime runtime options for this request RuntimeOptions
7862
+ * @return DescribeClusterAddonInstanceResponse
7519
7863
  */
7520
7864
  describeClusterAddonInstanceWithOptions(ClusterID: string, AddonName: string, headers: {
7521
7865
  [key: string]: string;
7522
7866
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterAddonInstanceResponse>;
7523
7867
  /**
7524
- * @deprecated
7525
- *
7526
- * @return DescribeClusterAddonInstanceResponse
7868
+ * @deprecated OpenAPI DescribeClusterAddonInstance is deprecated
7869
+ *
7870
+ * @summary You can call the DescribeClusterAddonInstance operation to query the information about a cluster component, including the version, status, and configuration of the component.
7871
+ *
7872
+ * @return DescribeClusterAddonInstanceResponse
7527
7873
  */
7528
7874
  describeClusterAddonInstance(ClusterID: string, AddonName: string): Promise<DescribeClusterAddonInstanceResponse>;
7529
7875
  /**
7530
- * @deprecated
7531
- *
7532
- * @param request DescribeClusterAddonMetadataRequest
7533
- * @param headers map
7534
- * @param runtime runtime options for this request RuntimeOptions
7535
- * @return DescribeClusterAddonMetadataResponse
7876
+ * @deprecated OpenAPI DescribeClusterAddonMetadata is deprecated
7877
+ *
7878
+ * @summary You can call the DescribeClusterAddonMetadata operation to query the metadata of a component version. The metadata includes the component version and available parameters.
7879
+ *
7880
+ * @param request DescribeClusterAddonMetadataRequest
7881
+ * @param headers map
7882
+ * @param runtime runtime options for this request RuntimeOptions
7883
+ * @return DescribeClusterAddonMetadataResponse
7536
7884
  */
7537
7885
  describeClusterAddonMetadataWithOptions(clusterId: string, componentId: string, request: DescribeClusterAddonMetadataRequest, headers: {
7538
7886
  [key: string]: string;
7539
7887
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterAddonMetadataResponse>;
7540
7888
  /**
7541
- * @deprecated
7542
- *
7543
- * @param request DescribeClusterAddonMetadataRequest
7544
- * @return DescribeClusterAddonMetadataResponse
7889
+ * @deprecated OpenAPI DescribeClusterAddonMetadata is deprecated
7890
+ *
7891
+ * @summary You can call the DescribeClusterAddonMetadata operation to query the metadata of a component version. The metadata includes the component version and available parameters.
7892
+ *
7893
+ * @param request DescribeClusterAddonMetadataRequest
7894
+ * @return DescribeClusterAddonMetadataResponse
7545
7895
  */
7546
7896
  describeClusterAddonMetadata(clusterId: string, componentId: string, request: DescribeClusterAddonMetadataRequest): Promise<DescribeClusterAddonMetadataResponse>;
7547
7897
  /**
7548
- * @deprecated
7549
- *
7550
- * @param headers map
7551
- * @param runtime runtime options for this request RuntimeOptions
7552
- * @return DescribeClusterAddonUpgradeStatusResponse
7898
+ * @deprecated OpenAPI DescribeClusterAddonUpgradeStatus is deprecated
7899
+ *
7900
+ * @summary You can call the DescribeClusterAddonUpgradeStatus operation to query the update progress of a cluster component.
7901
+ *
7902
+ * @param headers map
7903
+ * @param runtime runtime options for this request RuntimeOptions
7904
+ * @return DescribeClusterAddonUpgradeStatusResponse
7553
7905
  */
7554
7906
  describeClusterAddonUpgradeStatusWithOptions(ClusterId: string, ComponentId: string, headers: {
7555
7907
  [key: string]: string;
7556
7908
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterAddonUpgradeStatusResponse>;
7557
7909
  /**
7558
- * @deprecated
7559
- *
7560
- * @return DescribeClusterAddonUpgradeStatusResponse
7910
+ * @deprecated OpenAPI DescribeClusterAddonUpgradeStatus is deprecated
7911
+ *
7912
+ * @summary You can call the DescribeClusterAddonUpgradeStatus operation to query the update progress of a cluster component.
7913
+ *
7914
+ * @return DescribeClusterAddonUpgradeStatusResponse
7561
7915
  */
7562
7916
  describeClusterAddonUpgradeStatus(ClusterId: string, ComponentId: string): Promise<DescribeClusterAddonUpgradeStatusResponse>;
7563
7917
  /**
7564
- * @deprecated
7565
- *
7566
- * @param tmpReq DescribeClusterAddonsUpgradeStatusRequest
7567
- * @param headers map
7568
- * @param runtime runtime options for this request RuntimeOptions
7569
- * @return DescribeClusterAddonsUpgradeStatusResponse
7918
+ * @deprecated OpenAPI DescribeClusterAddonsUpgradeStatus is deprecated
7919
+ *
7920
+ * @summary You can call the DescribeClusterAddonsUpgradeStatus operation to query the update progress of a component by component name.
7921
+ *
7922
+ * @param tmpReq DescribeClusterAddonsUpgradeStatusRequest
7923
+ * @param headers map
7924
+ * @param runtime runtime options for this request RuntimeOptions
7925
+ * @return DescribeClusterAddonsUpgradeStatusResponse
7570
7926
  */
7571
7927
  describeClusterAddonsUpgradeStatusWithOptions(ClusterId: string, tmpReq: DescribeClusterAddonsUpgradeStatusRequest, headers: {
7572
7928
  [key: string]: string;
7573
7929
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterAddonsUpgradeStatusResponse>;
7574
7930
  /**
7575
- * @deprecated
7576
- *
7577
- * @param request DescribeClusterAddonsUpgradeStatusRequest
7578
- * @return DescribeClusterAddonsUpgradeStatusResponse
7931
+ * @deprecated OpenAPI DescribeClusterAddonsUpgradeStatus is deprecated
7932
+ *
7933
+ * @summary You can call the DescribeClusterAddonsUpgradeStatus operation to query the update progress of a component by component name.
7934
+ *
7935
+ * @param request DescribeClusterAddonsUpgradeStatusRequest
7936
+ * @return DescribeClusterAddonsUpgradeStatusResponse
7579
7937
  */
7580
7938
  describeClusterAddonsUpgradeStatus(ClusterId: string, request: DescribeClusterAddonsUpgradeStatusRequest): Promise<DescribeClusterAddonsUpgradeStatusResponse>;
7581
7939
  /**
7582
- * @deprecated
7583
- *
7584
- * @param headers map
7585
- * @param runtime runtime options for this request RuntimeOptions
7586
- * @return DescribeClusterAddonsVersionResponse
7940
+ * @deprecated OpenAPI DescribeClusterAddonsVersion is deprecated
7941
+ *
7942
+ * @summary You can call the DescribeClusterAddonsVersion operation to query the details about all components in a cluster by cluster ID.
7943
+ *
7944
+ * @param headers map
7945
+ * @param runtime runtime options for this request RuntimeOptions
7946
+ * @return DescribeClusterAddonsVersionResponse
7587
7947
  */
7588
7948
  describeClusterAddonsVersionWithOptions(ClusterId: string, headers: {
7589
7949
  [key: string]: string;
7590
7950
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterAddonsVersionResponse>;
7591
7951
  /**
7592
- * @deprecated
7593
- *
7594
- * @return DescribeClusterAddonsVersionResponse
7952
+ * @deprecated OpenAPI DescribeClusterAddonsVersion is deprecated
7953
+ *
7954
+ * @summary You can call the DescribeClusterAddonsVersion operation to query the details about all components in a cluster by cluster ID.
7955
+ *
7956
+ * @return DescribeClusterAddonsVersionResponse
7595
7957
  */
7596
7958
  describeClusterAddonsVersion(ClusterId: string): Promise<DescribeClusterAddonsVersionResponse>;
7959
+ /**
7960
+ * @summary Queries the script that is used to add existing nodes to a Container Service for Kubernetes (ACK) cluster. You can manually add existing Elastic Compute Service (ECS) instances to an ACK cluster as worker nodes or re-add the worker nodes that you have removed to a node pool.
7961
+ *
7962
+ * @param request DescribeClusterAttachScriptsRequest
7963
+ * @param headers map
7964
+ * @param runtime runtime options for this request RuntimeOptions
7965
+ * @return DescribeClusterAttachScriptsResponse
7966
+ */
7597
7967
  describeClusterAttachScriptsWithOptions(ClusterId: string, request: DescribeClusterAttachScriptsRequest, headers: {
7598
7968
  [key: string]: string;
7599
7969
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterAttachScriptsResponse>;
7970
+ /**
7971
+ * @summary Queries the script that is used to add existing nodes to a Container Service for Kubernetes (ACK) cluster. You can manually add existing Elastic Compute Service (ECS) instances to an ACK cluster as worker nodes or re-add the worker nodes that you have removed to a node pool.
7972
+ *
7973
+ * @param request DescribeClusterAttachScriptsRequest
7974
+ * @return DescribeClusterAttachScriptsResponse
7975
+ */
7600
7976
  describeClusterAttachScripts(ClusterId: string, request: DescribeClusterAttachScriptsRequest): Promise<DescribeClusterAttachScriptsResponse>;
7977
+ /**
7978
+ * @summary You can call the DescribeClusterDetail operation to query the details of a Container Service for Kubernetes (ACK) cluster by cluster ID.
7979
+ *
7980
+ * @param headers map
7981
+ * @param runtime runtime options for this request RuntimeOptions
7982
+ * @return DescribeClusterDetailResponse
7983
+ */
7601
7984
  describeClusterDetailWithOptions(ClusterId: string, headers: {
7602
7985
  [key: string]: string;
7603
7986
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterDetailResponse>;
7987
+ /**
7988
+ * @summary You can call the DescribeClusterDetail operation to query the details of a Container Service for Kubernetes (ACK) cluster by cluster ID.
7989
+ *
7990
+ * @return DescribeClusterDetailResponse
7991
+ */
7604
7992
  describeClusterDetail(ClusterId: string): Promise<DescribeClusterDetailResponse>;
7993
+ /**
7994
+ * @summary Queries events and event details in a Container Service for Kubernetes (ACK) cluster, including the severity level, status, and start time of each event. Events are generated when clusters created, modified, and updated, node pools are created and scaled out, and components are installed.
7995
+ *
7996
+ * @param request DescribeClusterEventsRequest
7997
+ * @param headers map
7998
+ * @param runtime runtime options for this request RuntimeOptions
7999
+ * @return DescribeClusterEventsResponse
8000
+ */
7605
8001
  describeClusterEventsWithOptions(ClusterId: string, request: DescribeClusterEventsRequest, headers: {
7606
8002
  [key: string]: string;
7607
8003
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterEventsResponse>;
8004
+ /**
8005
+ * @summary Queries events and event details in a Container Service for Kubernetes (ACK) cluster, including the severity level, status, and start time of each event. Events are generated when clusters created, modified, and updated, node pools are created and scaled out, and components are installed.
8006
+ *
8007
+ * @param request DescribeClusterEventsRequest
8008
+ * @return DescribeClusterEventsResponse
8009
+ */
7608
8010
  describeClusterEvents(ClusterId: string, request: DescribeClusterEventsRequest): Promise<DescribeClusterEventsResponse>;
8011
+ /**
8012
+ * @summary Queries the cluster log to help analyze cluster issues and locate the cause.
8013
+ *
8014
+ * @param headers map
8015
+ * @param runtime runtime options for this request RuntimeOptions
8016
+ * @return DescribeClusterLogsResponse
8017
+ */
7609
8018
  describeClusterLogsWithOptions(ClusterId: string, headers: {
7610
8019
  [key: string]: string;
7611
8020
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterLogsResponse>;
8021
+ /**
8022
+ * @summary Queries the cluster log to help analyze cluster issues and locate the cause.
8023
+ *
8024
+ * @return DescribeClusterLogsResponse
8025
+ */
7612
8026
  describeClusterLogs(ClusterId: string): Promise<DescribeClusterLogsResponse>;
8027
+ /**
8028
+ * @summary You can call the DescribeClusterNodePoolDetail.html operation to query the details about a node pool in a cluster by node pool ID.
8029
+ *
8030
+ * @param headers map
8031
+ * @param runtime runtime options for this request RuntimeOptions
8032
+ * @return DescribeClusterNodePoolDetailResponse
8033
+ */
7613
8034
  describeClusterNodePoolDetailWithOptions(ClusterId: string, NodepoolId: string, headers: {
7614
8035
  [key: string]: string;
7615
8036
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterNodePoolDetailResponse>;
8037
+ /**
8038
+ * @summary You can call the DescribeClusterNodePoolDetail.html operation to query the details about a node pool in a cluster by node pool ID.
8039
+ *
8040
+ * @return DescribeClusterNodePoolDetailResponse
8041
+ */
7616
8042
  describeClusterNodePoolDetail(ClusterId: string, NodepoolId: string): Promise<DescribeClusterNodePoolDetailResponse>;
8043
+ /**
8044
+ * @summary You can call the DescribeClusterNodePools operation to query node pools in a Container Service for Kubernetes (ACK) cluster.
8045
+ *
8046
+ * @param request DescribeClusterNodePoolsRequest
8047
+ * @param headers map
8048
+ * @param runtime runtime options for this request RuntimeOptions
8049
+ * @return DescribeClusterNodePoolsResponse
8050
+ */
7617
8051
  describeClusterNodePoolsWithOptions(ClusterId: string, request: DescribeClusterNodePoolsRequest, headers: {
7618
8052
  [key: string]: string;
7619
8053
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterNodePoolsResponse>;
8054
+ /**
8055
+ * @summary You can call the DescribeClusterNodePools operation to query node pools in a Container Service for Kubernetes (ACK) cluster.
8056
+ *
8057
+ * @param request DescribeClusterNodePoolsRequest
8058
+ * @return DescribeClusterNodePoolsResponse
8059
+ */
7620
8060
  describeClusterNodePools(ClusterId: string, request: DescribeClusterNodePoolsRequest): Promise<DescribeClusterNodePoolsResponse>;
8061
+ /**
8062
+ * @summary You can call the DescribeClusterNodes operation to query the details about all nodes in a cluster by cluster ID.
8063
+ *
8064
+ * @param request DescribeClusterNodesRequest
8065
+ * @param headers map
8066
+ * @param runtime runtime options for this request RuntimeOptions
8067
+ * @return DescribeClusterNodesResponse
8068
+ */
7621
8069
  describeClusterNodesWithOptions(ClusterId: string, request: DescribeClusterNodesRequest, headers: {
7622
8070
  [key: string]: string;
7623
8071
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterNodesResponse>;
8072
+ /**
8073
+ * @summary You can call the DescribeClusterNodes operation to query the details about all nodes in a cluster by cluster ID.
8074
+ *
8075
+ * @param request DescribeClusterNodesRequest
8076
+ * @return DescribeClusterNodesResponse
8077
+ */
7624
8078
  describeClusterNodes(ClusterId: string, request: DescribeClusterNodesRequest): Promise<DescribeClusterNodesResponse>;
8079
+ /**
8080
+ * @summary You can call the DescribeClusterResources operation to query all resources in a cluster by cluster ID.
8081
+ *
8082
+ * @param request DescribeClusterResourcesRequest
8083
+ * @param headers map
8084
+ * @param runtime runtime options for this request RuntimeOptions
8085
+ * @return DescribeClusterResourcesResponse
8086
+ */
7625
8087
  describeClusterResourcesWithOptions(ClusterId: string, request: DescribeClusterResourcesRequest, headers: {
7626
8088
  [key: string]: string;
7627
8089
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterResourcesResponse>;
8090
+ /**
8091
+ * @summary You can call the DescribeClusterResources operation to query all resources in a cluster by cluster ID.
8092
+ *
8093
+ * @param request DescribeClusterResourcesRequest
8094
+ * @return DescribeClusterResourcesResponse
8095
+ */
7628
8096
  describeClusterResources(ClusterId: string, request: DescribeClusterResourcesRequest): Promise<DescribeClusterResourcesResponse>;
8097
+ /**
8098
+ * @summary Queries tasks in a Container Service for Kubernetes (ACK) cluster.
8099
+ *
8100
+ * @param request DescribeClusterTasksRequest
8101
+ * @param headers map
8102
+ * @param runtime runtime options for this request RuntimeOptions
8103
+ * @return DescribeClusterTasksResponse
8104
+ */
7629
8105
  describeClusterTasksWithOptions(clusterId: string, request: DescribeClusterTasksRequest, headers: {
7630
8106
  [key: string]: string;
7631
8107
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterTasksResponse>;
8108
+ /**
8109
+ * @summary Queries tasks in a Container Service for Kubernetes (ACK) cluster.
8110
+ *
8111
+ * @param request DescribeClusterTasksRequest
8112
+ * @return DescribeClusterTasksResponse
8113
+ */
7632
8114
  describeClusterTasks(clusterId: string, request: DescribeClusterTasksRequest): Promise<DescribeClusterTasksResponse>;
7633
8115
  /**
7634
- * **
7635
- * ****The default validity period of a kubeconfig file is 3 years. Two months before a kubeconfig file expires, you can renew it in the Container Service for Kubernetes (ACK) console or by calling API operations. After a kubeconfig file is renewed, the secret is valid for 3 years. The previous kubeconfig secret remains valid until expiration. We recommend that you renew your kubeconfig file at the earliest opportunity.
7636
- *
7637
- * @param request DescribeClusterUserKubeconfigRequest
7638
- * @param headers map
7639
- * @param runtime runtime options for this request RuntimeOptions
7640
- * @return DescribeClusterUserKubeconfigResponse
8116
+ * @summary Kubeconfig files store identity and authentication information that is used by clients to access Container Service for Kubernetes (ACK) clusters. To use a kubectl client to manage an ACK cluster, you need to use the corresponding kubeconfig file to connect to the ACK cluster. We recommend that you keep kubeconfig files confidential and revoke kubeconfig files that are not in use. This helps prevent data leaks caused by the disclosure of kubeconfig files.
8117
+ *
8118
+ * @description **
8119
+ * ****The default validity period of a kubeconfig file is 3 years. Two months before a kubeconfig file expires, you can renew it in the Container Service for Kubernetes (ACK) console or by calling API operations. After a kubeconfig file is renewed, the secret is valid for 3 years. The previous kubeconfig secret remains valid until expiration. We recommend that you renew your kubeconfig file at the earliest opportunity.
8120
+ *
8121
+ * @param request DescribeClusterUserKubeconfigRequest
8122
+ * @param headers map
8123
+ * @param runtime runtime options for this request RuntimeOptions
8124
+ * @return DescribeClusterUserKubeconfigResponse
7641
8125
  */
7642
8126
  describeClusterUserKubeconfigWithOptions(ClusterId: string, request: DescribeClusterUserKubeconfigRequest, headers: {
7643
8127
  [key: string]: string;
7644
8128
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterUserKubeconfigResponse>;
7645
8129
  /**
7646
- * **
7647
- * ****The default validity period of a kubeconfig file is 3 years. Two months before a kubeconfig file expires, you can renew it in the Container Service for Kubernetes (ACK) console or by calling API operations. After a kubeconfig file is renewed, the secret is valid for 3 years. The previous kubeconfig secret remains valid until expiration. We recommend that you renew your kubeconfig file at the earliest opportunity.
7648
- *
7649
- * @param request DescribeClusterUserKubeconfigRequest
7650
- * @return DescribeClusterUserKubeconfigResponse
8130
+ * @summary Kubeconfig files store identity and authentication information that is used by clients to access Container Service for Kubernetes (ACK) clusters. To use a kubectl client to manage an ACK cluster, you need to use the corresponding kubeconfig file to connect to the ACK cluster. We recommend that you keep kubeconfig files confidential and revoke kubeconfig files that are not in use. This helps prevent data leaks caused by the disclosure of kubeconfig files.
8131
+ *
8132
+ * @description **
8133
+ * ****The default validity period of a kubeconfig file is 3 years. Two months before a kubeconfig file expires, you can renew it in the Container Service for Kubernetes (ACK) console or by calling API operations. After a kubeconfig file is renewed, the secret is valid for 3 years. The previous kubeconfig secret remains valid until expiration. We recommend that you renew your kubeconfig file at the earliest opportunity.
8134
+ *
8135
+ * @param request DescribeClusterUserKubeconfigRequest
8136
+ * @return DescribeClusterUserKubeconfigResponse
7651
8137
  */
7652
8138
  describeClusterUserKubeconfig(ClusterId: string, request: DescribeClusterUserKubeconfigRequest): Promise<DescribeClusterUserKubeconfigResponse>;
7653
8139
  /**
7654
- * @deprecated
7655
- *
7656
- * @param request DescribeClusterV2UserKubeconfigRequest
7657
- * @param headers map
7658
- * @param runtime runtime options for this request RuntimeOptions
7659
- * @return DescribeClusterV2UserKubeconfigResponse
8140
+ * @deprecated OpenAPI DescribeClusterV2UserKubeconfig is deprecated
8141
+ *
8142
+ * @summary 获取集群kubeconfig接口
8143
+ *
8144
+ * @param request DescribeClusterV2UserKubeconfigRequest
8145
+ * @param headers map
8146
+ * @param runtime runtime options for this request RuntimeOptions
8147
+ * @return DescribeClusterV2UserKubeconfigResponse
7660
8148
  */
7661
8149
  describeClusterV2UserKubeconfigWithOptions(ClusterId: string, request: DescribeClusterV2UserKubeconfigRequest, headers: {
7662
8150
  [key: string]: string;
7663
8151
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterV2UserKubeconfigResponse>;
7664
8152
  /**
7665
- * @deprecated
7666
- *
7667
- * @param request DescribeClusterV2UserKubeconfigRequest
7668
- * @return DescribeClusterV2UserKubeconfigResponse
8153
+ * @deprecated OpenAPI DescribeClusterV2UserKubeconfig is deprecated
8154
+ *
8155
+ * @summary 获取集群kubeconfig接口
8156
+ *
8157
+ * @param request DescribeClusterV2UserKubeconfigRequest
8158
+ * @return DescribeClusterV2UserKubeconfigResponse
7669
8159
  */
7670
8160
  describeClusterV2UserKubeconfig(ClusterId: string, request: DescribeClusterV2UserKubeconfigRequest): Promise<DescribeClusterV2UserKubeconfigResponse>;
8161
+ /**
8162
+ * @summary You can call the DescribeClusterVuls operation to query the vulnerability information of a cluster.
8163
+ *
8164
+ * @param headers map
8165
+ * @param runtime runtime options for this request RuntimeOptions
8166
+ * @return DescribeClusterVulsResponse
8167
+ */
7671
8168
  describeClusterVulsWithOptions(clusterId: string, headers: {
7672
8169
  [key: string]: string;
7673
8170
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClusterVulsResponse>;
8171
+ /**
8172
+ * @summary You can call the DescribeClusterVuls operation to query the vulnerability information of a cluster.
8173
+ *
8174
+ * @return DescribeClusterVulsResponse
8175
+ */
7674
8176
  describeClusterVuls(clusterId: string): Promise<DescribeClusterVulsResponse>;
7675
8177
  /**
7676
- * @deprecated
7677
- *
7678
- * @param request DescribeClustersRequest
7679
- * @param headers map
7680
- * @param runtime runtime options for this request RuntimeOptions
7681
- * @return DescribeClustersResponse
8178
+ * @deprecated OpenAPI DescribeClusters is deprecated
8179
+ *
8180
+ * @summary You can call the DescribeClusters operation to query all the clusters that belong to the current Alibaba Cloud account, including Kubernetes clusters and Swarm clusters.
8181
+ *
8182
+ * @param request DescribeClustersRequest
8183
+ * @param headers map
8184
+ * @param runtime runtime options for this request RuntimeOptions
8185
+ * @return DescribeClustersResponse
7682
8186
  */
7683
8187
  describeClustersWithOptions(request: DescribeClustersRequest, headers: {
7684
8188
  [key: string]: string;
7685
8189
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClustersResponse>;
7686
8190
  /**
7687
- * @deprecated
7688
- *
7689
- * @param request DescribeClustersRequest
7690
- * @return DescribeClustersResponse
8191
+ * @deprecated OpenAPI DescribeClusters is deprecated
8192
+ *
8193
+ * @summary You can call the DescribeClusters operation to query all the clusters that belong to the current Alibaba Cloud account, including Kubernetes clusters and Swarm clusters.
8194
+ *
8195
+ * @param request DescribeClustersRequest
8196
+ * @return DescribeClustersResponse
7691
8197
  */
7692
8198
  describeClusters(request: DescribeClustersRequest): Promise<DescribeClustersResponse>;
8199
+ /**
8200
+ * @summary You can call the DescribeClustersV1 operation to query the details about all Container Service for Kubernetes (ACK) clusters.
8201
+ *
8202
+ * @param request DescribeClustersV1Request
8203
+ * @param headers map
8204
+ * @param runtime runtime options for this request RuntimeOptions
8205
+ * @return DescribeClustersV1Response
8206
+ */
7693
8207
  describeClustersV1WithOptions(request: DescribeClustersV1Request, headers: {
7694
8208
  [key: string]: string;
7695
8209
  }, runtime: $Util.RuntimeOptions): Promise<DescribeClustersV1Response>;
8210
+ /**
8211
+ * @summary You can call the DescribeClustersV1 operation to query the details about all Container Service for Kubernetes (ACK) clusters.
8212
+ *
8213
+ * @param request DescribeClustersV1Request
8214
+ * @return DescribeClustersV1Response
8215
+ */
7696
8216
  describeClustersV1(request: DescribeClustersV1Request): Promise<DescribeClustersV1Response>;
8217
+ /**
8218
+ * @summary You can call the DescribeEdgeMachineActiveProcess operation to query the activation progress of a cloud-native box.
8219
+ *
8220
+ * @param headers map
8221
+ * @param runtime runtime options for this request RuntimeOptions
8222
+ * @return DescribeEdgeMachineActiveProcessResponse
8223
+ */
7697
8224
  describeEdgeMachineActiveProcessWithOptions(edgeMachineid: string, headers: {
7698
8225
  [key: string]: string;
7699
8226
  }, runtime: $Util.RuntimeOptions): Promise<DescribeEdgeMachineActiveProcessResponse>;
8227
+ /**
8228
+ * @summary You can call the DescribeEdgeMachineActiveProcess operation to query the activation progress of a cloud-native box.
8229
+ *
8230
+ * @return DescribeEdgeMachineActiveProcessResponse
8231
+ */
7700
8232
  describeEdgeMachineActiveProcess(edgeMachineid: string): Promise<DescribeEdgeMachineActiveProcessResponse>;
8233
+ /**
8234
+ * @summary You can call the DescribeEdgeMachineModels operation to query the cloud-native box models.
8235
+ *
8236
+ * @param headers map
8237
+ * @param runtime runtime options for this request RuntimeOptions
8238
+ * @return DescribeEdgeMachineModelsResponse
8239
+ */
7701
8240
  describeEdgeMachineModelsWithOptions(headers: {
7702
8241
  [key: string]: string;
7703
8242
  }, runtime: $Util.RuntimeOptions): Promise<DescribeEdgeMachineModelsResponse>;
8243
+ /**
8244
+ * @summary You can call the DescribeEdgeMachineModels operation to query the cloud-native box models.
8245
+ *
8246
+ * @return DescribeEdgeMachineModelsResponse
8247
+ */
7704
8248
  describeEdgeMachineModels(): Promise<DescribeEdgeMachineModelsResponse>;
8249
+ /**
8250
+ * @summary You can call the DescribeEdgeMachineTunnelConfigDetail operation to obtain the SSH token of a cloud-native box.
8251
+ *
8252
+ * @param headers map
8253
+ * @param runtime runtime options for this request RuntimeOptions
8254
+ * @return DescribeEdgeMachineTunnelConfigDetailResponse
8255
+ */
7705
8256
  describeEdgeMachineTunnelConfigDetailWithOptions(edgeMachineid: string, headers: {
7706
8257
  [key: string]: string;
7707
8258
  }, runtime: $Util.RuntimeOptions): Promise<DescribeEdgeMachineTunnelConfigDetailResponse>;
8259
+ /**
8260
+ * @summary You can call the DescribeEdgeMachineTunnelConfigDetail operation to obtain the SSH token of a cloud-native box.
8261
+ *
8262
+ * @return DescribeEdgeMachineTunnelConfigDetailResponse
8263
+ */
7708
8264
  describeEdgeMachineTunnelConfigDetail(edgeMachineid: string): Promise<DescribeEdgeMachineTunnelConfigDetailResponse>;
8265
+ /**
8266
+ * @summary You can call the DescribeEdgeMachines operation to query a list of cloud-native boxes.
8267
+ *
8268
+ * @param request DescribeEdgeMachinesRequest
8269
+ * @param headers map
8270
+ * @param runtime runtime options for this request RuntimeOptions
8271
+ * @return DescribeEdgeMachinesResponse
8272
+ */
7709
8273
  describeEdgeMachinesWithOptions(request: DescribeEdgeMachinesRequest, headers: {
7710
8274
  [key: string]: string;
7711
8275
  }, runtime: $Util.RuntimeOptions): Promise<DescribeEdgeMachinesResponse>;
8276
+ /**
8277
+ * @summary You can call the DescribeEdgeMachines operation to query a list of cloud-native boxes.
8278
+ *
8279
+ * @param request DescribeEdgeMachinesRequest
8280
+ * @return DescribeEdgeMachinesResponse
8281
+ */
7712
8282
  describeEdgeMachines(request: DescribeEdgeMachinesRequest): Promise<DescribeEdgeMachinesResponse>;
8283
+ /**
8284
+ * @summary Queries detailed information about a type of events, including the severity level, status, and start time of each event. Events are generated when clusters are created, modified, and updated, node pools are created and scaled out, and components are installed.
8285
+ *
8286
+ * @param request DescribeEventsRequest
8287
+ * @param headers map
8288
+ * @param runtime runtime options for this request RuntimeOptions
8289
+ * @return DescribeEventsResponse
8290
+ */
7713
8291
  describeEventsWithOptions(request: DescribeEventsRequest, headers: {
7714
8292
  [key: string]: string;
7715
8293
  }, runtime: $Util.RuntimeOptions): Promise<DescribeEventsResponse>;
8294
+ /**
8295
+ * @summary Queries detailed information about a type of events, including the severity level, status, and start time of each event. Events are generated when clusters are created, modified, and updated, node pools are created and scaled out, and components are installed.
8296
+ *
8297
+ * @param request DescribeEventsRequest
8298
+ * @return DescribeEventsResponse
8299
+ */
7716
8300
  describeEvents(request: DescribeEventsRequest): Promise<DescribeEventsResponse>;
7717
8301
  /**
7718
- * For more information, see [Register an external Kubernetes cluster](~~121053~~).
7719
- *
7720
- * @param request DescribeExternalAgentRequest
7721
- * @param headers map
7722
- * @param runtime runtime options for this request RuntimeOptions
7723
- * @return DescribeExternalAgentResponse
8302
+ * @summary You can call the DescribeExternalAgent operation to query the agent configurations of a registered cluster by cluster ID.
8303
+ *
8304
+ * @description For more information, see [Register an external Kubernetes cluster](https://help.aliyun.com/document_detail/121053.html).
8305
+ *
8306
+ * @param request DescribeExternalAgentRequest
8307
+ * @param headers map
8308
+ * @param runtime runtime options for this request RuntimeOptions
8309
+ * @return DescribeExternalAgentResponse
7724
8310
  */
7725
8311
  describeExternalAgentWithOptions(ClusterId: string, request: DescribeExternalAgentRequest, headers: {
7726
8312
  [key: string]: string;
7727
8313
  }, runtime: $Util.RuntimeOptions): Promise<DescribeExternalAgentResponse>;
7728
8314
  /**
7729
- * For more information, see [Register an external Kubernetes cluster](~~121053~~).
7730
- *
7731
- * @param request DescribeExternalAgentRequest
7732
- * @return DescribeExternalAgentResponse
8315
+ * @summary You can call the DescribeExternalAgent operation to query the agent configurations of a registered cluster by cluster ID.
8316
+ *
8317
+ * @description For more information, see [Register an external Kubernetes cluster](https://help.aliyun.com/document_detail/121053.html).
8318
+ *
8319
+ * @param request DescribeExternalAgentRequest
8320
+ * @return DescribeExternalAgentResponse
7733
8321
  */
7734
8322
  describeExternalAgent(ClusterId: string, request: DescribeExternalAgentRequest): Promise<DescribeExternalAgentResponse>;
8323
+ /**
8324
+ * @summary Queries the detailed information about Kubernetes versions, including the version number, release date, expiration date, compatible OSs, and runtime.
8325
+ *
8326
+ * @param request DescribeKubernetesVersionMetadataRequest
8327
+ * @param headers map
8328
+ * @param runtime runtime options for this request RuntimeOptions
8329
+ * @return DescribeKubernetesVersionMetadataResponse
8330
+ */
7735
8331
  describeKubernetesVersionMetadataWithOptions(request: DescribeKubernetesVersionMetadataRequest, headers: {
7736
8332
  [key: string]: string;
7737
8333
  }, runtime: $Util.RuntimeOptions): Promise<DescribeKubernetesVersionMetadataResponse>;
8334
+ /**
8335
+ * @summary Queries the detailed information about Kubernetes versions, including the version number, release date, expiration date, compatible OSs, and runtime.
8336
+ *
8337
+ * @param request DescribeKubernetesVersionMetadataRequest
8338
+ * @return DescribeKubernetesVersionMetadataResponse
8339
+ */
7738
8340
  describeKubernetesVersionMetadata(request: DescribeKubernetesVersionMetadataRequest): Promise<DescribeKubernetesVersionMetadataResponse>;
8341
+ /**
8342
+ * @summary Queries the vulnerability information of a node pool, such as vulnerability names and severity levels, by specifying the ID of the node pool. We recommend that you periodically scan node pools for vulnerabilities to enhance cluster security.
8343
+ *
8344
+ * @param request DescribeNodePoolVulsRequest
8345
+ * @param headers map
8346
+ * @param runtime runtime options for this request RuntimeOptions
8347
+ * @return DescribeNodePoolVulsResponse
8348
+ */
7739
8349
  describeNodePoolVulsWithOptions(clusterId: string, nodepoolId: string, request: DescribeNodePoolVulsRequest, headers: {
7740
8350
  [key: string]: string;
7741
8351
  }, runtime: $Util.RuntimeOptions): Promise<DescribeNodePoolVulsResponse>;
8352
+ /**
8353
+ * @summary Queries the vulnerability information of a node pool, such as vulnerability names and severity levels, by specifying the ID of the node pool. We recommend that you periodically scan node pools for vulnerabilities to enhance cluster security.
8354
+ *
8355
+ * @param request DescribeNodePoolVulsRequest
8356
+ * @return DescribeNodePoolVulsResponse
8357
+ */
7742
8358
  describeNodePoolVuls(clusterId: string, nodepoolId: string, request: DescribeNodePoolVulsRequest): Promise<DescribeNodePoolVulsResponse>;
8359
+ /**
8360
+ * @summary You can call the DescribePolicies operation to query a list of policies.
8361
+ *
8362
+ * @param headers map
8363
+ * @param runtime runtime options for this request RuntimeOptions
8364
+ * @return DescribePoliciesResponse
8365
+ */
7743
8366
  describePoliciesWithOptions(headers: {
7744
8367
  [key: string]: string;
7745
8368
  }, runtime: $Util.RuntimeOptions): Promise<DescribePoliciesResponse>;
8369
+ /**
8370
+ * @summary You can call the DescribePolicies operation to query a list of policies.
8371
+ *
8372
+ * @return DescribePoliciesResponse
8373
+ */
7746
8374
  describePolicies(): Promise<DescribePoliciesResponse>;
8375
+ /**
8376
+ * @summary Container security policies for Container Service for Kubernetes (ACK) clusters offer a variety of built-in policies, including cis-k8s, infra, k8s-general, and PodSecurityPolicy. You can use these policies to ensure the security of containers running in a production environment. You can call the DescribePolicyDetails operation to query information about a policy, such as the content, action, and severity level of the policy.
8377
+ *
8378
+ * @param headers map
8379
+ * @param runtime runtime options for this request RuntimeOptions
8380
+ * @return DescribePolicyDetailsResponse
8381
+ */
7747
8382
  describePolicyDetailsWithOptions(policyName: string, headers: {
7748
8383
  [key: string]: string;
7749
8384
  }, runtime: $Util.RuntimeOptions): Promise<DescribePolicyDetailsResponse>;
8385
+ /**
8386
+ * @summary Container security policies for Container Service for Kubernetes (ACK) clusters offer a variety of built-in policies, including cis-k8s, infra, k8s-general, and PodSecurityPolicy. You can use these policies to ensure the security of containers running in a production environment. You can call the DescribePolicyDetails operation to query information about a policy, such as the content, action, and severity level of the policy.
8387
+ *
8388
+ * @return DescribePolicyDetailsResponse
8389
+ */
7750
8390
  describePolicyDetails(policyName: string): Promise<DescribePolicyDetailsResponse>;
8391
+ /**
8392
+ * @summary You can call the DescribePolicyGovernanceInCluster operation to query information about policies in a Container Service for Kubernetes (ACK) cluster.
8393
+ *
8394
+ * @param headers map
8395
+ * @param runtime runtime options for this request RuntimeOptions
8396
+ * @return DescribePolicyGovernanceInClusterResponse
8397
+ */
7751
8398
  describePolicyGovernanceInClusterWithOptions(clusterId: string, headers: {
7752
8399
  [key: string]: string;
7753
8400
  }, runtime: $Util.RuntimeOptions): Promise<DescribePolicyGovernanceInClusterResponse>;
8401
+ /**
8402
+ * @summary You can call the DescribePolicyGovernanceInCluster operation to query information about policies in a Container Service for Kubernetes (ACK) cluster.
8403
+ *
8404
+ * @return DescribePolicyGovernanceInClusterResponse
8405
+ */
7754
8406
  describePolicyGovernanceInCluster(clusterId: string): Promise<DescribePolicyGovernanceInClusterResponse>;
8407
+ /**
8408
+ * @summary Queries the detailed information about policy instances of the specified type in a Container Service for Kubernetes (ACK) cluster, such as the policy description and severity level. You can choose a type of security policy for an ACK cluster, specify the action and applicable scope of the policy, and then create and deploy a policy instance.
8409
+ *
8410
+ * @param request DescribePolicyInstancesRequest
8411
+ * @param headers map
8412
+ * @param runtime runtime options for this request RuntimeOptions
8413
+ * @return DescribePolicyInstancesResponse
8414
+ */
7755
8415
  describePolicyInstancesWithOptions(clusterId: string, request: DescribePolicyInstancesRequest, headers: {
7756
8416
  [key: string]: string;
7757
8417
  }, runtime: $Util.RuntimeOptions): Promise<DescribePolicyInstancesResponse>;
8418
+ /**
8419
+ * @summary Queries the detailed information about policy instances of the specified type in a Container Service for Kubernetes (ACK) cluster, such as the policy description and severity level. You can choose a type of security policy for an ACK cluster, specify the action and applicable scope of the policy, and then create and deploy a policy instance.
8420
+ *
8421
+ * @param request DescribePolicyInstancesRequest
8422
+ * @return DescribePolicyInstancesResponse
8423
+ */
7758
8424
  describePolicyInstances(clusterId: string, request: DescribePolicyInstancesRequest): Promise<DescribePolicyInstancesResponse>;
8425
+ /**
8426
+ * @summary Queries the deployment of policy instances in the current Container Service for Kubernetes (ACK) cluster, including the number of policy instances of each type and the number of policy types of each severity level.
8427
+ *
8428
+ * @param headers map
8429
+ * @param runtime runtime options for this request RuntimeOptions
8430
+ * @return DescribePolicyInstancesStatusResponse
8431
+ */
7759
8432
  describePolicyInstancesStatusWithOptions(clusterId: string, headers: {
7760
8433
  [key: string]: string;
7761
8434
  }, runtime: $Util.RuntimeOptions): Promise<DescribePolicyInstancesStatusResponse>;
8435
+ /**
8436
+ * @summary Queries the deployment of policy instances in the current Container Service for Kubernetes (ACK) cluster, including the number of policy instances of each type and the number of policy types of each severity level.
8437
+ *
8438
+ * @return DescribePolicyInstancesStatusResponse
8439
+ */
7762
8440
  describePolicyInstancesStatus(clusterId: string): Promise<DescribePolicyInstancesStatusResponse>;
7763
8441
  /**
7764
- * **
7765
- * ****Only Alibaba Cloud accounts can call this API operation.
7766
- *
7767
- * @param request DescribeSubaccountK8sClusterUserConfigRequest
7768
- * @param headers map
7769
- * @param runtime runtime options for this request RuntimeOptions
7770
- * @return DescribeSubaccountK8sClusterUserConfigResponse
8442
+ * @summary You can use an Alibaba Cloud account to call the DescribeSubaccountK8sClusterUserConfig operation to obtain the cluster kubeconfig file of a RAM user or RAM role.
8443
+ *
8444
+ * @description **
8445
+ * ****Only Alibaba Cloud accounts can call this API operation.
8446
+ *
8447
+ * @param request DescribeSubaccountK8sClusterUserConfigRequest
8448
+ * @param headers map
8449
+ * @param runtime runtime options for this request RuntimeOptions
8450
+ * @return DescribeSubaccountK8sClusterUserConfigResponse
7771
8451
  */
7772
8452
  describeSubaccountK8sClusterUserConfigWithOptions(ClusterId: string, Uid: string, request: DescribeSubaccountK8sClusterUserConfigRequest, headers: {
7773
8453
  [key: string]: string;
7774
8454
  }, runtime: $Util.RuntimeOptions): Promise<DescribeSubaccountK8sClusterUserConfigResponse>;
7775
8455
  /**
7776
- * **
7777
- * ****Only Alibaba Cloud accounts can call this API operation.
7778
- *
7779
- * @param request DescribeSubaccountK8sClusterUserConfigRequest
7780
- * @return DescribeSubaccountK8sClusterUserConfigResponse
8456
+ * @summary You can use an Alibaba Cloud account to call the DescribeSubaccountK8sClusterUserConfig operation to obtain the cluster kubeconfig file of a RAM user or RAM role.
8457
+ *
8458
+ * @description **
8459
+ * ****Only Alibaba Cloud accounts can call this API operation.
8460
+ *
8461
+ * @param request DescribeSubaccountK8sClusterUserConfigRequest
8462
+ * @return DescribeSubaccountK8sClusterUserConfigResponse
7781
8463
  */
7782
8464
  describeSubaccountK8sClusterUserConfig(ClusterId: string, Uid: string, request: DescribeSubaccountK8sClusterUserConfigRequest): Promise<DescribeSubaccountK8sClusterUserConfigResponse>;
8465
+ /**
8466
+ * @summary Queries detailed information about a task, such as the task type, status, and progress.
8467
+ *
8468
+ * @param headers map
8469
+ * @param runtime runtime options for this request RuntimeOptions
8470
+ * @return DescribeTaskInfoResponse
8471
+ */
7783
8472
  describeTaskInfoWithOptions(taskId: string, headers: {
7784
8473
  [key: string]: string;
7785
8474
  }, runtime: $Util.RuntimeOptions): Promise<DescribeTaskInfoResponse>;
8475
+ /**
8476
+ * @summary Queries detailed information about a task, such as the task type, status, and progress.
8477
+ *
8478
+ * @return DescribeTaskInfoResponse
8479
+ */
7786
8480
  describeTaskInfo(taskId: string): Promise<DescribeTaskInfoResponse>;
8481
+ /**
8482
+ * @summary An orchestration template defines and describes a group of Kubernetes resources. It declaratively describes the configuration of an application or how an application runs. You can call the DescribeTemplates API operation to query orchestration templates and their detailed information, including access permissions, YAML content, and labels.
8483
+ *
8484
+ * @param request DescribeTemplateAttributeRequest
8485
+ * @param headers map
8486
+ * @param runtime runtime options for this request RuntimeOptions
8487
+ * @return DescribeTemplateAttributeResponse
8488
+ */
7787
8489
  describeTemplateAttributeWithOptions(TemplateId: string, request: DescribeTemplateAttributeRequest, headers: {
7788
8490
  [key: string]: string;
7789
8491
  }, runtime: $Util.RuntimeOptions): Promise<DescribeTemplateAttributeResponse>;
8492
+ /**
8493
+ * @summary An orchestration template defines and describes a group of Kubernetes resources. It declaratively describes the configuration of an application or how an application runs. You can call the DescribeTemplates API operation to query orchestration templates and their detailed information, including access permissions, YAML content, and labels.
8494
+ *
8495
+ * @param request DescribeTemplateAttributeRequest
8496
+ * @return DescribeTemplateAttributeResponse
8497
+ */
7790
8498
  describeTemplateAttribute(TemplateId: string, request: DescribeTemplateAttributeRequest): Promise<DescribeTemplateAttributeResponse>;
8499
+ /**
8500
+ * @summary An orchestration template defines and describes a group of Kubernetes resources. It declaratively describes the configuration of an application or how an application runs. You can call the DescribeTemplates API operation to query orchestration templates and their detailed information, including access permissions, YAML content, and labels.
8501
+ *
8502
+ * @param request DescribeTemplatesRequest
8503
+ * @param headers map
8504
+ * @param runtime runtime options for this request RuntimeOptions
8505
+ * @return DescribeTemplatesResponse
8506
+ */
7791
8507
  describeTemplatesWithOptions(request: DescribeTemplatesRequest, headers: {
7792
8508
  [key: string]: string;
7793
8509
  }, runtime: $Util.RuntimeOptions): Promise<DescribeTemplatesResponse>;
8510
+ /**
8511
+ * @summary An orchestration template defines and describes a group of Kubernetes resources. It declaratively describes the configuration of an application or how an application runs. You can call the DescribeTemplates API operation to query orchestration templates and their detailed information, including access permissions, YAML content, and labels.
8512
+ *
8513
+ * @param request DescribeTemplatesRequest
8514
+ * @return DescribeTemplatesResponse
8515
+ */
7794
8516
  describeTemplates(request: DescribeTemplatesRequest): Promise<DescribeTemplatesResponse>;
8517
+ /**
8518
+ * @summary You can call the DescribeTrigger operation to query triggers.
8519
+ *
8520
+ * @param request DescribeTriggerRequest
8521
+ * @param headers map
8522
+ * @param runtime runtime options for this request RuntimeOptions
8523
+ * @return DescribeTriggerResponse
8524
+ */
7795
8525
  describeTriggerWithOptions(clusterId: string, request: DescribeTriggerRequest, headers: {
7796
8526
  [key: string]: string;
7797
8527
  }, runtime: $Util.RuntimeOptions): Promise<DescribeTriggerResponse>;
8528
+ /**
8529
+ * @summary You can call the DescribeTrigger operation to query triggers.
8530
+ *
8531
+ * @param request DescribeTriggerRequest
8532
+ * @return DescribeTriggerResponse
8533
+ */
7798
8534
  describeTrigger(clusterId: string, request: DescribeTriggerRequest): Promise<DescribeTriggerResponse>;
8535
+ /**
8536
+ * @summary Queries the Role-Based Access Control (RBAC) permissions that are granted to the current Resource Access Management (RAM) user or RAM role on a Container Service for Kubernetes (ACK) cluster. You can use Kubernetes namespaces to limit users from accessing resources in an ACK cluster. Users that are granted RBAC permissions only on one namespace cannot access resources in other namespaces.
8537
+ *
8538
+ * @param headers map
8539
+ * @param runtime runtime options for this request RuntimeOptions
8540
+ * @return DescribeUserClusterNamespacesResponse
8541
+ */
7799
8542
  describeUserClusterNamespacesWithOptions(ClusterId: string, headers: {
7800
8543
  [key: string]: string;
7801
8544
  }, runtime: $Util.RuntimeOptions): Promise<DescribeUserClusterNamespacesResponse>;
8545
+ /**
8546
+ * @summary Queries the Role-Based Access Control (RBAC) permissions that are granted to the current Resource Access Management (RAM) user or RAM role on a Container Service for Kubernetes (ACK) cluster. You can use Kubernetes namespaces to limit users from accessing resources in an ACK cluster. Users that are granted RBAC permissions only on one namespace cannot access resources in other namespaces.
8547
+ *
8548
+ * @return DescribeUserClusterNamespacesResponse
8549
+ */
7802
8550
  describeUserClusterNamespaces(ClusterId: string): Promise<DescribeUserClusterNamespacesResponse>;
8551
+ /**
8552
+ * @summary In an Container Service for Kubernetes (ACK) cluster, you can create and specify different Resource Access Management (RAM) users or roles to have different access permissions. This ensures access control and resource isolation. You can call the DescribeUserPermission operation to query the permissions that are granted to a RAM user or RAM role on ACK clusters, including the resources that are allowed to access, the scope of the permissions, the predefined role, and the permission source.
8553
+ *
8554
+ * @param headers map
8555
+ * @param runtime runtime options for this request RuntimeOptions
8556
+ * @return DescribeUserPermissionResponse
8557
+ */
7803
8558
  describeUserPermissionWithOptions(uid: string, headers: {
7804
8559
  [key: string]: string;
7805
8560
  }, runtime: $Util.RuntimeOptions): Promise<DescribeUserPermissionResponse>;
8561
+ /**
8562
+ * @summary In an Container Service for Kubernetes (ACK) cluster, you can create and specify different Resource Access Management (RAM) users or roles to have different access permissions. This ensures access control and resource isolation. You can call the DescribeUserPermission operation to query the permissions that are granted to a RAM user or RAM role on ACK clusters, including the resources that are allowed to access, the scope of the permissions, the predefined role, and the permission source.
8563
+ *
8564
+ * @return DescribeUserPermissionResponse
8565
+ */
7806
8566
  describeUserPermission(uid: string): Promise<DescribeUserPermissionResponse>;
8567
+ /**
8568
+ * @summary Queries quotas related to Container Service for Kubernetes (ACK) clusters, node pools, and nodes. To increase a quota, submit an application in the Quota Center console.
8569
+ *
8570
+ * @param headers map
8571
+ * @param runtime runtime options for this request RuntimeOptions
8572
+ * @return DescribeUserQuotaResponse
8573
+ */
7807
8574
  describeUserQuotaWithOptions(headers: {
7808
8575
  [key: string]: string;
7809
8576
  }, runtime: $Util.RuntimeOptions): Promise<DescribeUserQuotaResponse>;
8577
+ /**
8578
+ * @summary Queries quotas related to Container Service for Kubernetes (ACK) clusters, node pools, and nodes. To increase a quota, submit an application in the Quota Center console.
8579
+ *
8580
+ * @return DescribeUserQuotaResponse
8581
+ */
7810
8582
  describeUserQuota(): Promise<DescribeUserQuotaResponse>;
8583
+ /**
8584
+ * @summary You can call the DescribeWorkflows operation to query all workflows.
8585
+ *
8586
+ * @param headers map
8587
+ * @param runtime runtime options for this request RuntimeOptions
8588
+ * @return DescribeWorkflowsResponse
8589
+ */
7811
8590
  describeWorkflowsWithOptions(headers: {
7812
8591
  [key: string]: string;
7813
8592
  }, runtime: $Util.RuntimeOptions): Promise<DescribeWorkflowsResponse>;
8593
+ /**
8594
+ * @summary You can call the DescribeWorkflows operation to query all workflows.
8595
+ *
8596
+ * @return DescribeWorkflowsResponse
8597
+ */
7814
8598
  describeWorkflows(): Promise<DescribeWorkflowsResponse>;
8599
+ /**
8600
+ * @summary You can call the EdgeClusterAddEdgeMachine operation to add a cloud-native box to a Container Service for Kubernetes (ACK) Edge cluster.
8601
+ *
8602
+ * @param request EdgeClusterAddEdgeMachineRequest
8603
+ * @param headers map
8604
+ * @param runtime runtime options for this request RuntimeOptions
8605
+ * @return EdgeClusterAddEdgeMachineResponse
8606
+ */
7815
8607
  edgeClusterAddEdgeMachineWithOptions(clusterid: string, edgeMachineid: string, request: EdgeClusterAddEdgeMachineRequest, headers: {
7816
8608
  [key: string]: string;
7817
8609
  }, runtime: $Util.RuntimeOptions): Promise<EdgeClusterAddEdgeMachineResponse>;
8610
+ /**
8611
+ * @summary You can call the EdgeClusterAddEdgeMachine operation to add a cloud-native box to a Container Service for Kubernetes (ACK) Edge cluster.
8612
+ *
8613
+ * @param request EdgeClusterAddEdgeMachineRequest
8614
+ * @return EdgeClusterAddEdgeMachineResponse
8615
+ */
7818
8616
  edgeClusterAddEdgeMachine(clusterid: string, edgeMachineid: string, request: EdgeClusterAddEdgeMachineRequest): Promise<EdgeClusterAddEdgeMachineResponse>;
7819
8617
  /**
7820
- * 1. The Common Vulnerabilities and Exposures (CVE) patching feature is developed based on Security Center. To use this feature, you must purchase the Security Center Ultimate Edition that supports Container Service for Kubernetes (ACK).
7821
- * 2. ACK may need to restart nodes to patch certain vulnerabilities. ACK drains a node before the node restarts. Make sure that the ACK cluster has sufficient idle nodes to host the pods evicted from the trained nodes. For example, you can scale out a node pool before you patch vulnerabilities for the nodes in the node pool.
7822
- * 3. Security Center ensures the compatibility of CVE patches. We recommend that you check the compatibility of a CVE patch with your application before you install the patch. You can pause or cancel a CVE patching task anytime.
7823
- * 4. CVE patching is a progressive task that consists of multiple batches. After you pause or cancel a CVE patching task, ACK continues to process the dispatched batches. Only the batches that have not been dispatched are paused or canceled.
7824
- *
7825
- * @param request FixNodePoolVulsRequest
7826
- * @param headers map
7827
- * @param runtime runtime options for this request RuntimeOptions
7828
- * @return FixNodePoolVulsResponse
8618
+ * @summary Patches node vulnerabilities in a node pool to enhance node security. Cloud Security provided by Alibaba Cloud periodically scans Elastic Compute Service (ECS) instances for vulnerabilities and provides suggestions on how to patch the detected vulnerabilities. Vulnerability patching may require node restarts. Make sure that your cluster has sufficient idle nodes for node draining.
8619
+ *
8620
+ * @description 1. The Common Vulnerabilities and Exposures (CVE) patching feature is developed based on Security Center. To use this feature, you must purchase the Security Center Ultimate Edition that supports Container Service for Kubernetes (ACK).
8621
+ * 2. ACK may need to restart nodes to patch certain vulnerabilities. ACK drains a node before the node restarts. Make sure that the ACK cluster has sufficient idle nodes to host the pods evicted from the trained nodes. For example, you can scale out a node pool before you patch vulnerabilities for the nodes in the node pool.
8622
+ * 3. Security Center ensures the compatibility of CVE patches. We recommend that you check the compatibility of a CVE patch with your application before you install the patch. You can pause or cancel a CVE patching task anytime.
8623
+ * 4. CVE patching is a progressive task that consists of multiple batches. After you pause or cancel a CVE patching task, ACK continues to process the dispatched batches. Only the batches that have not been dispatched are paused or canceled.
8624
+ *
8625
+ * @param request FixNodePoolVulsRequest
8626
+ * @param headers map
8627
+ * @param runtime runtime options for this request RuntimeOptions
8628
+ * @return FixNodePoolVulsResponse
7829
8629
  */
7830
8630
  fixNodePoolVulsWithOptions(clusterId: string, nodepoolId: string, request: FixNodePoolVulsRequest, headers: {
7831
8631
  [key: string]: string;
7832
8632
  }, runtime: $Util.RuntimeOptions): Promise<FixNodePoolVulsResponse>;
7833
8633
  /**
7834
- * 1. The Common Vulnerabilities and Exposures (CVE) patching feature is developed based on Security Center. To use this feature, you must purchase the Security Center Ultimate Edition that supports Container Service for Kubernetes (ACK).
7835
- * 2. ACK may need to restart nodes to patch certain vulnerabilities. ACK drains a node before the node restarts. Make sure that the ACK cluster has sufficient idle nodes to host the pods evicted from the trained nodes. For example, you can scale out a node pool before you patch vulnerabilities for the nodes in the node pool.
7836
- * 3. Security Center ensures the compatibility of CVE patches. We recommend that you check the compatibility of a CVE patch with your application before you install the patch. You can pause or cancel a CVE patching task anytime.
7837
- * 4. CVE patching is a progressive task that consists of multiple batches. After you pause or cancel a CVE patching task, ACK continues to process the dispatched batches. Only the batches that have not been dispatched are paused or canceled.
7838
- *
7839
- * @param request FixNodePoolVulsRequest
7840
- * @return FixNodePoolVulsResponse
8634
+ * @summary Patches node vulnerabilities in a node pool to enhance node security. Cloud Security provided by Alibaba Cloud periodically scans Elastic Compute Service (ECS) instances for vulnerabilities and provides suggestions on how to patch the detected vulnerabilities. Vulnerability patching may require node restarts. Make sure that your cluster has sufficient idle nodes for node draining.
8635
+ *
8636
+ * @description 1. The Common Vulnerabilities and Exposures (CVE) patching feature is developed based on Security Center. To use this feature, you must purchase the Security Center Ultimate Edition that supports Container Service for Kubernetes (ACK).
8637
+ * 2. ACK may need to restart nodes to patch certain vulnerabilities. ACK drains a node before the node restarts. Make sure that the ACK cluster has sufficient idle nodes to host the pods evicted from the trained nodes. For example, you can scale out a node pool before you patch vulnerabilities for the nodes in the node pool.
8638
+ * 3. Security Center ensures the compatibility of CVE patches. We recommend that you check the compatibility of a CVE patch with your application before you install the patch. You can pause or cancel a CVE patching task anytime.
8639
+ * 4. CVE patching is a progressive task that consists of multiple batches. After you pause or cancel a CVE patching task, ACK continues to process the dispatched batches. Only the batches that have not been dispatched are paused or canceled.
8640
+ *
8641
+ * @param request FixNodePoolVulsRequest
8642
+ * @return FixNodePoolVulsResponse
7841
8643
  */
7842
8644
  fixNodePoolVuls(clusterId: string, nodepoolId: string, request: FixNodePoolVulsRequest): Promise<FixNodePoolVulsResponse>;
8645
+ /**
8646
+ * @summary You can call the GetClusterAddonInstance operation to query the information of a component instance in a cluster, including the version, configurations, and log status of the component instance.
8647
+ *
8648
+ * @param headers map
8649
+ * @param runtime runtime options for this request RuntimeOptions
8650
+ * @return GetClusterAddonInstanceResponse
8651
+ */
7843
8652
  getClusterAddonInstanceWithOptions(clusterId: string, instanceName: string, headers: {
7844
8653
  [key: string]: string;
7845
8654
  }, runtime: $Util.RuntimeOptions): Promise<GetClusterAddonInstanceResponse>;
8655
+ /**
8656
+ * @summary You can call the GetClusterAddonInstance operation to query the information of a component instance in a cluster, including the version, configurations, and log status of the component instance.
8657
+ *
8658
+ * @return GetClusterAddonInstanceResponse
8659
+ */
7846
8660
  getClusterAddonInstance(clusterId: string, instanceName: string): Promise<GetClusterAddonInstanceResponse>;
8661
+ /**
8662
+ * @summary Queries a cluster check task by cluster ID and task ID. You can view the status, check items, creation time, and end time of the task. Container Intelligence Service (CIS) provides a variety of Kubernetes cluster check features, including cluster update check, cluster migration check, component installation check, component update check, and node pool check.
8663
+ *
8664
+ * @param headers map
8665
+ * @param runtime runtime options for this request RuntimeOptions
8666
+ * @return GetClusterCheckResponse
8667
+ */
7847
8668
  getClusterCheckWithOptions(clusterId: string, checkId: string, headers: {
7848
8669
  [key: string]: string;
7849
8670
  }, runtime: $Util.RuntimeOptions): Promise<GetClusterCheckResponse>;
8671
+ /**
8672
+ * @summary Queries a cluster check task by cluster ID and task ID. You can view the status, check items, creation time, and end time of the task. Container Intelligence Service (CIS) provides a variety of Kubernetes cluster check features, including cluster update check, cluster migration check, component installation check, component update check, and node pool check.
8673
+ *
8674
+ * @return GetClusterCheckResponse
8675
+ */
7850
8676
  getClusterCheck(clusterId: string, checkId: string): Promise<GetClusterCheckResponse>;
8677
+ /**
8678
+ * @summary You can call the GetKubernetesTrigger operationto query the triggers of an application by application name.
8679
+ *
8680
+ * @param request GetKubernetesTriggerRequest
8681
+ * @param headers map
8682
+ * @param runtime runtime options for this request RuntimeOptions
8683
+ * @return GetKubernetesTriggerResponse
8684
+ */
7851
8685
  getKubernetesTriggerWithOptions(ClusterId: string, request: GetKubernetesTriggerRequest, headers: {
7852
8686
  [key: string]: string;
7853
8687
  }, runtime: $Util.RuntimeOptions): Promise<GetKubernetesTriggerResponse>;
8688
+ /**
8689
+ * @summary You can call the GetKubernetesTrigger operationto query the triggers of an application by application name.
8690
+ *
8691
+ * @param request GetKubernetesTriggerRequest
8692
+ * @return GetKubernetesTriggerResponse
8693
+ */
7854
8694
  getKubernetesTrigger(ClusterId: string, request: GetKubernetesTriggerRequest): Promise<GetKubernetesTriggerResponse>;
8695
+ /**
8696
+ * @summary You can call the GetUpgradeStatus operation to query the update progress of a cluster by cluster ID.
8697
+ *
8698
+ * @param headers map
8699
+ * @param runtime runtime options for this request RuntimeOptions
8700
+ * @return GetUpgradeStatusResponse
8701
+ */
7855
8702
  getUpgradeStatusWithOptions(ClusterId: string, headers: {
7856
8703
  [key: string]: string;
7857
8704
  }, runtime: $Util.RuntimeOptions): Promise<GetUpgradeStatusResponse>;
8705
+ /**
8706
+ * @summary You can call the GetUpgradeStatus operation to query the update progress of a cluster by cluster ID.
8707
+ *
8708
+ * @return GetUpgradeStatusResponse
8709
+ */
7858
8710
  getUpgradeStatus(ClusterId: string): Promise<GetUpgradeStatusResponse>;
7859
8711
  /**
7860
- * ****
7861
- * * Make sure that you have granted the RAM user at least read-only permissions on the desired ACK clusters in the RAM console. Otherwise, the `ErrorRamPolicyConfig` error code is returned. For more information about how to authorize a RAM user by attaching RAM policies, see [Create a custom RAM policy](~~86485~~).
7862
- * * If you use a RAM user to call this API operation, make sure that the RAM user is authorized to modify the permissions of other RAM users on the desired ACK clusters. Otherwise, the `StatusForbidden` or `ForbiddenGrantPermissions` error code is returned. For more information, see [Use a RAM user to grant RBAC permissions to other RAM users](~~119035~~).
7863
- * * This operation overwrites the permissions that have been granted to the specified RAM user. When you call this operation, make sure that the required permissions are included.
7864
- *
7865
- * @param request GrantPermissionsRequest
7866
- * @param headers map
7867
- * @param runtime runtime options for this request RuntimeOptions
7868
- * @return GrantPermissionsResponse
8712
+ * @summary You can call the GrantPermissions operation to grant a Resource Access Management (RAM) user the permissions to manage Container Service for Kubernetes (ACK) clusters.
8713
+ *
8714
+ * @description ****
8715
+ * * Make sure that you have granted the RAM user at least read-only permissions on the desired ACK clusters in the RAM console. Otherwise, the `ErrorRamPolicyConfig` error code is returned. For more information about how to authorize a RAM user by attaching RAM policies, see [Create a custom RAM policy](https://help.aliyun.com/document_detail/86485.html).
8716
+ * * If you use a RAM user to call this API operation, make sure that the RAM user is authorized to modify the permissions of other RAM users on the desired ACK clusters. Otherwise, the `StatusForbidden` or `ForbiddenGrantPermissions` error code is returned. For more information, see [Use a RAM user to grant RBAC permissions to other RAM users](https://help.aliyun.com/document_detail/119035.html).
8717
+ * * This operation overwrites the permissions that have been granted to the specified RAM user. When you call this operation, make sure that the required permissions are included.
8718
+ *
8719
+ * @param request GrantPermissionsRequest
8720
+ * @param headers map
8721
+ * @param runtime runtime options for this request RuntimeOptions
8722
+ * @return GrantPermissionsResponse
7869
8723
  */
7870
8724
  grantPermissionsWithOptions(uid: string, request: GrantPermissionsRequest, headers: {
7871
8725
  [key: string]: string;
7872
8726
  }, runtime: $Util.RuntimeOptions): Promise<GrantPermissionsResponse>;
7873
8727
  /**
7874
- * ****
7875
- * * Make sure that you have granted the RAM user at least read-only permissions on the desired ACK clusters in the RAM console. Otherwise, the `ErrorRamPolicyConfig` error code is returned. For more information about how to authorize a RAM user by attaching RAM policies, see [Create a custom RAM policy](~~86485~~).
7876
- * * If you use a RAM user to call this API operation, make sure that the RAM user is authorized to modify the permissions of other RAM users on the desired ACK clusters. Otherwise, the `StatusForbidden` or `ForbiddenGrantPermissions` error code is returned. For more information, see [Use a RAM user to grant RBAC permissions to other RAM users](~~119035~~).
7877
- * * This operation overwrites the permissions that have been granted to the specified RAM user. When you call this operation, make sure that the required permissions are included.
7878
- *
7879
- * @param request GrantPermissionsRequest
7880
- * @return GrantPermissionsResponse
8728
+ * @summary You can call the GrantPermissions operation to grant a Resource Access Management (RAM) user the permissions to manage Container Service for Kubernetes (ACK) clusters.
8729
+ *
8730
+ * @description ****
8731
+ * * Make sure that you have granted the RAM user at least read-only permissions on the desired ACK clusters in the RAM console. Otherwise, the `ErrorRamPolicyConfig` error code is returned. For more information about how to authorize a RAM user by attaching RAM policies, see [Create a custom RAM policy](https://help.aliyun.com/document_detail/86485.html).
8732
+ * * If you use a RAM user to call this API operation, make sure that the RAM user is authorized to modify the permissions of other RAM users on the desired ACK clusters. Otherwise, the `StatusForbidden` or `ForbiddenGrantPermissions` error code is returned. For more information, see [Use a RAM user to grant RBAC permissions to other RAM users](https://help.aliyun.com/document_detail/119035.html).
8733
+ * * This operation overwrites the permissions that have been granted to the specified RAM user. When you call this operation, make sure that the required permissions are included.
8734
+ *
8735
+ * @param request GrantPermissionsRequest
8736
+ * @return GrantPermissionsResponse
7881
8737
  */
7882
8738
  grantPermissions(uid: string, request: GrantPermissionsRequest): Promise<GrantPermissionsResponse>;
8739
+ /**
8740
+ * @summary Installs a component by specifying the name and version of the component. To enhance Kubernetes capabilities, you can install a variety of components in Container Service for Kubernetes (ACK) clusters, such as fully-managed core components and application, logging and monitoring, network, storage, and security group components.
8741
+ *
8742
+ * @param request InstallClusterAddonsRequest
8743
+ * @param headers map
8744
+ * @param runtime runtime options for this request RuntimeOptions
8745
+ * @return InstallClusterAddonsResponse
8746
+ */
7883
8747
  installClusterAddonsWithOptions(ClusterId: string, request: InstallClusterAddonsRequest, headers: {
7884
8748
  [key: string]: string;
7885
8749
  }, runtime: $Util.RuntimeOptions): Promise<InstallClusterAddonsResponse>;
8750
+ /**
8751
+ * @summary Installs a component by specifying the name and version of the component. To enhance Kubernetes capabilities, you can install a variety of components in Container Service for Kubernetes (ACK) clusters, such as fully-managed core components and application, logging and monitoring, network, storage, and security group components.
8752
+ *
8753
+ * @param request InstallClusterAddonsRequest
8754
+ * @return InstallClusterAddonsResponse
8755
+ */
7886
8756
  installClusterAddons(ClusterId: string, request: InstallClusterAddonsRequest): Promise<InstallClusterAddonsResponse>;
8757
+ /**
8758
+ * @summary You can call the ListAddons operation to query all available components in a cluster. You can query all available components in a cluster by specifying the ID of the cluster. You can also specify parameters such as the region, cluster type, cluster subtype (profile), cluster specification, and cluster version to get a list of available components in clusters that meet the conditions.
8759
+ *
8760
+ * @param request ListAddonsRequest
8761
+ * @param headers map
8762
+ * @param runtime runtime options for this request RuntimeOptions
8763
+ * @return ListAddonsResponse
8764
+ */
7887
8765
  listAddonsWithOptions(request: ListAddonsRequest, headers: {
7888
8766
  [key: string]: string;
7889
8767
  }, runtime: $Util.RuntimeOptions): Promise<ListAddonsResponse>;
8768
+ /**
8769
+ * @summary You can call the ListAddons operation to query all available components in a cluster. You can query all available components in a cluster by specifying the ID of the cluster. You can also specify parameters such as the region, cluster type, cluster subtype (profile), cluster specification, and cluster version to get a list of available components in clusters that meet the conditions.
8770
+ *
8771
+ * @param request ListAddonsRequest
8772
+ * @return ListAddonsResponse
8773
+ */
7890
8774
  listAddons(request: ListAddonsRequest): Promise<ListAddonsResponse>;
8775
+ /**
8776
+ * @summary You can call the ListClusterAddonInstances operation to query information about the components that are installed in a cluster.
8777
+ *
8778
+ * @param headers map
8779
+ * @param runtime runtime options for this request RuntimeOptions
8780
+ * @return ListClusterAddonInstancesResponse
8781
+ */
7891
8782
  listClusterAddonInstancesWithOptions(clusterId: string, headers: {
7892
8783
  [key: string]: string;
7893
8784
  }, runtime: $Util.RuntimeOptions): Promise<ListClusterAddonInstancesResponse>;
8785
+ /**
8786
+ * @summary You can call the ListClusterAddonInstances operation to query information about the components that are installed in a cluster.
8787
+ *
8788
+ * @return ListClusterAddonInstancesResponse
8789
+ */
7894
8790
  listClusterAddonInstances(clusterId: string): Promise<ListClusterAddonInstancesResponse>;
8791
+ /**
8792
+ * @summary You can call the ListClusterChecks operation to query all the cluster check results of a cluster.
8793
+ *
8794
+ * @param request ListClusterChecksRequest
8795
+ * @param headers map
8796
+ * @param runtime runtime options for this request RuntimeOptions
8797
+ * @return ListClusterChecksResponse
8798
+ */
7895
8799
  listClusterChecksWithOptions(clusterId: string, request: ListClusterChecksRequest, headers: {
7896
8800
  [key: string]: string;
7897
8801
  }, runtime: $Util.RuntimeOptions): Promise<ListClusterChecksResponse>;
8802
+ /**
8803
+ * @summary You can call the ListClusterChecks operation to query all the cluster check results of a cluster.
8804
+ *
8805
+ * @param request ListClusterChecksRequest
8806
+ * @return ListClusterChecksResponse
8807
+ */
7898
8808
  listClusterChecks(clusterId: string, request: ListClusterChecksRequest): Promise<ListClusterChecksResponse>;
8809
+ /**
8810
+ * @summary 获取自动运维执行计划列表
8811
+ *
8812
+ * @param request ListOperationPlansRequest
8813
+ * @param headers map
8814
+ * @param runtime runtime options for this request RuntimeOptions
8815
+ * @return ListOperationPlansResponse
8816
+ */
7899
8817
  listOperationPlansWithOptions(request: ListOperationPlansRequest, headers: {
7900
8818
  [key: string]: string;
7901
8819
  }, runtime: $Util.RuntimeOptions): Promise<ListOperationPlansResponse>;
8820
+ /**
8821
+ * @summary 获取自动运维执行计划列表
8822
+ *
8823
+ * @param request ListOperationPlansRequest
8824
+ * @return ListOperationPlansResponse
8825
+ */
7902
8826
  listOperationPlans(request: ListOperationPlansRequest): Promise<ListOperationPlansResponse>;
8827
+ /**
8828
+ * @summary Queries resource labels and the detailed information, such as the key-value pairs of the labels and the clusters to which the labels are added. You can use labels to classify and manage Container Service for Kubernetes (ACK) clusters in order to meet monitoring, cost analysis, and tenant isolation requirements.
8829
+ *
8830
+ * @param tmpReq ListTagResourcesRequest
8831
+ * @param headers map
8832
+ * @param runtime runtime options for this request RuntimeOptions
8833
+ * @return ListTagResourcesResponse
8834
+ */
7903
8835
  listTagResourcesWithOptions(tmpReq: ListTagResourcesRequest, headers: {
7904
8836
  [key: string]: string;
7905
8837
  }, runtime: $Util.RuntimeOptions): Promise<ListTagResourcesResponse>;
8838
+ /**
8839
+ * @summary Queries resource labels and the detailed information, such as the key-value pairs of the labels and the clusters to which the labels are added. You can use labels to classify and manage Container Service for Kubernetes (ACK) clusters in order to meet monitoring, cost analysis, and tenant isolation requirements.
8840
+ *
8841
+ * @param request ListTagResourcesRequest
8842
+ * @return ListTagResourcesResponse
8843
+ */
7906
8844
  listTagResources(request: ListTagResourcesRequest): Promise<ListTagResourcesResponse>;
8845
+ /**
8846
+ * @summary Container Service for Kubernetes (ACK) Pro clusters are developed based on ACK Basic clusters. ACK Pro clusters provide all benefits of ACK managed clusters, such as fully-managed control planes and control plane high availability. In addition, ACK Pro clusters provide you with enhanced reliability, security, and schedulability. ACK Pro clusters are covered by the SLA that supports compensation clauses. ACK Pro clusters are suitable for large-scale businesses that require high stability and security in production environments. We recommend that you migrate from ACK Basic clusters to ACK Pro clusters.
8847
+ *
8848
+ * @param request MigrateClusterRequest
8849
+ * @param headers map
8850
+ * @param runtime runtime options for this request RuntimeOptions
8851
+ * @return MigrateClusterResponse
8852
+ */
7907
8853
  migrateClusterWithOptions(clusterId: string, request: MigrateClusterRequest, headers: {
7908
8854
  [key: string]: string;
7909
8855
  }, runtime: $Util.RuntimeOptions): Promise<MigrateClusterResponse>;
8856
+ /**
8857
+ * @summary Container Service for Kubernetes (ACK) Pro clusters are developed based on ACK Basic clusters. ACK Pro clusters provide all benefits of ACK managed clusters, such as fully-managed control planes and control plane high availability. In addition, ACK Pro clusters provide you with enhanced reliability, security, and schedulability. ACK Pro clusters are covered by the SLA that supports compensation clauses. ACK Pro clusters are suitable for large-scale businesses that require high stability and security in production environments. We recommend that you migrate from ACK Basic clusters to ACK Pro clusters.
8858
+ *
8859
+ * @param request MigrateClusterRequest
8860
+ * @return MigrateClusterResponse
8861
+ */
7910
8862
  migrateCluster(clusterId: string, request: MigrateClusterRequest): Promise<MigrateClusterResponse>;
8863
+ /**
8864
+ * @summary You can call the ModifyCluster operation to modify the cluster configurations by cluster ID.
8865
+ *
8866
+ * @param request ModifyClusterRequest
8867
+ * @param headers map
8868
+ * @param runtime runtime options for this request RuntimeOptions
8869
+ * @return ModifyClusterResponse
8870
+ */
7911
8871
  modifyClusterWithOptions(ClusterId: string, request: ModifyClusterRequest, headers: {
7912
8872
  [key: string]: string;
7913
8873
  }, runtime: $Util.RuntimeOptions): Promise<ModifyClusterResponse>;
8874
+ /**
8875
+ * @summary You can call the ModifyCluster operation to modify the cluster configurations by cluster ID.
8876
+ *
8877
+ * @param request ModifyClusterRequest
8878
+ * @return ModifyClusterResponse
8879
+ */
7914
8880
  modifyCluster(ClusterId: string, request: ModifyClusterRequest): Promise<ModifyClusterResponse>;
7915
8881
  /**
7916
- * You can use this API operation to modify the components in a Container Service for Kubernetes (ACK) cluster or the control plane components in an ACK Pro cluster.
7917
- * * To query the customizable parameters of a component, call the `DescribeClusterAddonMetadata` API operation. For more information, see [Query the metadata of a specified component version](https://www.alibabacloud.com/help/zh/container-service-for-kubernetes/latest/query).
7918
- * * For more information about the customizable parameters of control plane components in ACK Pro clusters, see [Customize the parameters of control plane components in ACK Pro clusters](https://www.alibabacloud.com/help/zh/container-service-for-kubernetes/latest/customize-control-plane-parameters-for-a-professional-kubernetes-cluster).
7919
- * After you call this operation, the component may be redeployed and restarted. We recommend that you assess the impact before you call this operation.
7920
- *
7921
- * @param request ModifyClusterAddonRequest
7922
- * @param headers map
7923
- * @param runtime runtime options for this request RuntimeOptions
7924
- * @return ModifyClusterAddonResponse
8882
+ * @summary Modifies the configuration of a cluster component. This operation may affect your businesses. We recommend that you assess the impact, back up data, and perform the operation during off-peak hours.
8883
+ *
8884
+ * @description You can use this API operation to modify the components in a Container Service for Kubernetes (ACK) cluster or the control plane components in an ACK Pro cluster.
8885
+ * * To query the customizable parameters of a component, call the `DescribeClusterAddonMetadata` API operation. For more information, see [Query the metadata of a specified component version](https://www.alibabacloud.com/help/zh/container-service-for-kubernetes/latest/query).
8886
+ * * For more information about the customizable parameters of control plane components in ACK Pro clusters, see [Customize the parameters of control plane components in ACK Pro clusters](https://www.alibabacloud.com/help/zh/container-service-for-kubernetes/latest/customize-control-plane-parameters-for-a-professional-kubernetes-cluster).
8887
+ * After you call this operation, the component may be redeployed and restarted. We recommend that you assess the impact before you call this operation.
8888
+ *
8889
+ * @param request ModifyClusterAddonRequest
8890
+ * @param headers map
8891
+ * @param runtime runtime options for this request RuntimeOptions
8892
+ * @return ModifyClusterAddonResponse
7925
8893
  */
7926
8894
  modifyClusterAddonWithOptions(clusterId: string, componentId: string, request: ModifyClusterAddonRequest, headers: {
7927
8895
  [key: string]: string;
7928
8896
  }, runtime: $Util.RuntimeOptions): Promise<ModifyClusterAddonResponse>;
7929
8897
  /**
7930
- * You can use this API operation to modify the components in a Container Service for Kubernetes (ACK) cluster or the control plane components in an ACK Pro cluster.
7931
- * * To query the customizable parameters of a component, call the `DescribeClusterAddonMetadata` API operation. For more information, see [Query the metadata of a specified component version](https://www.alibabacloud.com/help/zh/container-service-for-kubernetes/latest/query).
7932
- * * For more information about the customizable parameters of control plane components in ACK Pro clusters, see [Customize the parameters of control plane components in ACK Pro clusters](https://www.alibabacloud.com/help/zh/container-service-for-kubernetes/latest/customize-control-plane-parameters-for-a-professional-kubernetes-cluster).
7933
- * After you call this operation, the component may be redeployed and restarted. We recommend that you assess the impact before you call this operation.
7934
- *
7935
- * @param request ModifyClusterAddonRequest
7936
- * @return ModifyClusterAddonResponse
8898
+ * @summary Modifies the configuration of a cluster component. This operation may affect your businesses. We recommend that you assess the impact, back up data, and perform the operation during off-peak hours.
8899
+ *
8900
+ * @description You can use this API operation to modify the components in a Container Service for Kubernetes (ACK) cluster or the control plane components in an ACK Pro cluster.
8901
+ * * To query the customizable parameters of a component, call the `DescribeClusterAddonMetadata` API operation. For more information, see [Query the metadata of a specified component version](https://www.alibabacloud.com/help/zh/container-service-for-kubernetes/latest/query).
8902
+ * * For more information about the customizable parameters of control plane components in ACK Pro clusters, see [Customize the parameters of control plane components in ACK Pro clusters](https://www.alibabacloud.com/help/zh/container-service-for-kubernetes/latest/customize-control-plane-parameters-for-a-professional-kubernetes-cluster).
8903
+ * After you call this operation, the component may be redeployed and restarted. We recommend that you assess the impact before you call this operation.
8904
+ *
8905
+ * @param request ModifyClusterAddonRequest
8906
+ * @return ModifyClusterAddonResponse
7937
8907
  */
7938
8908
  modifyClusterAddon(clusterId: string, componentId: string, request: ModifyClusterAddonRequest): Promise<ModifyClusterAddonResponse>;
8909
+ /**
8910
+ * @summary This API operation applies only to Container Service for Kubernetes (ACK) managed clusters.
8911
+ *
8912
+ * @param request ModifyClusterConfigurationRequest
8913
+ * @param headers map
8914
+ * @param runtime runtime options for this request RuntimeOptions
8915
+ * @return ModifyClusterConfigurationResponse
8916
+ */
7939
8917
  modifyClusterConfigurationWithOptions(ClusterId: string, request: ModifyClusterConfigurationRequest, headers: {
7940
8918
  [key: string]: string;
7941
8919
  }, runtime: $Util.RuntimeOptions): Promise<ModifyClusterConfigurationResponse>;
8920
+ /**
8921
+ * @summary This API operation applies only to Container Service for Kubernetes (ACK) managed clusters.
8922
+ *
8923
+ * @param request ModifyClusterConfigurationRequest
8924
+ * @return ModifyClusterConfigurationResponse
8925
+ */
7942
8926
  modifyClusterConfiguration(ClusterId: string, request: ModifyClusterConfigurationRequest): Promise<ModifyClusterConfigurationResponse>;
8927
+ /**
8928
+ * @summary You can call the ModifyClusterNodePool operation to modify the configuration of a node pool with the specified node pool ID.
8929
+ *
8930
+ * @param request ModifyClusterNodePoolRequest
8931
+ * @param headers map
8932
+ * @param runtime runtime options for this request RuntimeOptions
8933
+ * @return ModifyClusterNodePoolResponse
8934
+ */
7943
8935
  modifyClusterNodePoolWithOptions(ClusterId: string, NodepoolId: string, request: ModifyClusterNodePoolRequest, headers: {
7944
8936
  [key: string]: string;
7945
8937
  }, runtime: $Util.RuntimeOptions): Promise<ModifyClusterNodePoolResponse>;
8938
+ /**
8939
+ * @summary You can call the ModifyClusterNodePool operation to modify the configuration of a node pool with the specified node pool ID.
8940
+ *
8941
+ * @param request ModifyClusterNodePoolRequest
8942
+ * @return ModifyClusterNodePoolResponse
8943
+ */
7946
8944
  modifyClusterNodePool(ClusterId: string, NodepoolId: string, request: ModifyClusterNodePoolRequest): Promise<ModifyClusterNodePoolResponse>;
8945
+ /**
8946
+ * @summary Modifies the labels of a Container Service for Kubernetes (ACK) cluster. You can use labels (key-value pairs) to classify and manage ACK clusters in order to meet monitoring, cost analysis, and tenant isolation requirements.
8947
+ *
8948
+ * @param request ModifyClusterTagsRequest
8949
+ * @param headers map
8950
+ * @param runtime runtime options for this request RuntimeOptions
8951
+ * @return ModifyClusterTagsResponse
8952
+ */
7947
8953
  modifyClusterTagsWithOptions(ClusterId: string, request: ModifyClusterTagsRequest, headers: {
7948
8954
  [key: string]: string;
7949
8955
  }, runtime: $Util.RuntimeOptions): Promise<ModifyClusterTagsResponse>;
8956
+ /**
8957
+ * @summary Modifies the labels of a Container Service for Kubernetes (ACK) cluster. You can use labels (key-value pairs) to classify and manage ACK clusters in order to meet monitoring, cost analysis, and tenant isolation requirements.
8958
+ *
8959
+ * @param request ModifyClusterTagsRequest
8960
+ * @return ModifyClusterTagsResponse
8961
+ */
7950
8962
  modifyClusterTags(ClusterId: string, request: ModifyClusterTagsRequest): Promise<ModifyClusterTagsResponse>;
7951
8963
  /**
7952
- * > Container Service for Kubernetes (ACK) allows you to modify the kubelet configuration of nodes in a node pool. After you modify the kubelet configuration, the new configuration immediately takes effect on existing nodes in the node pool and is automatically applied to newly added nodes.
7953
- *
7954
- * @param request ModifyNodePoolNodeConfigRequest
7955
- * @param headers map
7956
- * @param runtime runtime options for this request RuntimeOptions
7957
- * @return ModifyNodePoolNodeConfigResponse
8964
+ * @summary Modifies the configuration of a node pool, such as the kubelet configuration and node rolling update configuration. After you modify the node pool configuration, nodes are batch updated and the kubelet on each node is restarted. This may adversely affect the nodes and workloads. We recommend that you perform this operation during off-peak hours.
8965
+ *
8966
+ * @description > Container Service for Kubernetes (ACK) allows you to modify the kubelet configuration of nodes in a node pool. After you modify the kubelet configuration, the new configuration immediately takes effect on existing nodes in the node pool and is automatically applied to newly added nodes.
8967
+ *
8968
+ * @param request ModifyNodePoolNodeConfigRequest
8969
+ * @param headers map
8970
+ * @param runtime runtime options for this request RuntimeOptions
8971
+ * @return ModifyNodePoolNodeConfigResponse
7958
8972
  */
7959
8973
  modifyNodePoolNodeConfigWithOptions(ClusterId: string, NodepoolId: string, request: ModifyNodePoolNodeConfigRequest, headers: {
7960
8974
  [key: string]: string;
7961
8975
  }, runtime: $Util.RuntimeOptions): Promise<ModifyNodePoolNodeConfigResponse>;
7962
8976
  /**
7963
- * > Container Service for Kubernetes (ACK) allows you to modify the kubelet configuration of nodes in a node pool. After you modify the kubelet configuration, the new configuration immediately takes effect on existing nodes in the node pool and is automatically applied to newly added nodes.
7964
- *
7965
- * @param request ModifyNodePoolNodeConfigRequest
7966
- * @return ModifyNodePoolNodeConfigResponse
8977
+ * @summary Modifies the configuration of a node pool, such as the kubelet configuration and node rolling update configuration. After you modify the node pool configuration, nodes are batch updated and the kubelet on each node is restarted. This may adversely affect the nodes and workloads. We recommend that you perform this operation during off-peak hours.
8978
+ *
8979
+ * @description > Container Service for Kubernetes (ACK) allows you to modify the kubelet configuration of nodes in a node pool. After you modify the kubelet configuration, the new configuration immediately takes effect on existing nodes in the node pool and is automatically applied to newly added nodes.
8980
+ *
8981
+ * @param request ModifyNodePoolNodeConfigRequest
8982
+ * @return ModifyNodePoolNodeConfigResponse
7967
8983
  */
7968
8984
  modifyNodePoolNodeConfig(ClusterId: string, NodepoolId: string, request: ModifyNodePoolNodeConfigRequest): Promise<ModifyNodePoolNodeConfigResponse>;
8985
+ /**
8986
+ * @summary You can call the ModifyPolicyInstance operation to update policy instances in a Container Service for Kubernetes (ACK) cluster.
8987
+ *
8988
+ * @param request ModifyPolicyInstanceRequest
8989
+ * @param headers map
8990
+ * @param runtime runtime options for this request RuntimeOptions
8991
+ * @return ModifyPolicyInstanceResponse
8992
+ */
7969
8993
  modifyPolicyInstanceWithOptions(clusterId: string, policyName: string, request: ModifyPolicyInstanceRequest, headers: {
7970
8994
  [key: string]: string;
7971
8995
  }, runtime: $Util.RuntimeOptions): Promise<ModifyPolicyInstanceResponse>;
8996
+ /**
8997
+ * @summary You can call the ModifyPolicyInstance operation to update policy instances in a Container Service for Kubernetes (ACK) cluster.
8998
+ *
8999
+ * @param request ModifyPolicyInstanceRequest
9000
+ * @return ModifyPolicyInstanceResponse
9001
+ */
7972
9002
  modifyPolicyInstance(clusterId: string, policyName: string, request: ModifyPolicyInstanceRequest): Promise<ModifyPolicyInstanceResponse>;
7973
9003
  /**
7974
- * * You can activate ACK by using Alibaba Cloud accounts.
7975
- * * To activate ACK by using RAM users, you need to grant the AdministratorAccess permission to the RAM users.
7976
- *
7977
- * @param request OpenAckServiceRequest
7978
- * @param headers map
7979
- * @param runtime runtime options for this request RuntimeOptions
7980
- * @return OpenAckServiceResponse
9004
+ * @summary You can call the OpenAckService operation to activate Container Service for Kubernetes (ACK).
9005
+ *
9006
+ * @description * You can activate ACK by using Alibaba Cloud accounts.
9007
+ * * To activate ACK by using RAM users, you need to grant the AdministratorAccess permission to the RAM users.
9008
+ *
9009
+ * @param request OpenAckServiceRequest
9010
+ * @param headers map
9011
+ * @param runtime runtime options for this request RuntimeOptions
9012
+ * @return OpenAckServiceResponse
7981
9013
  */
7982
9014
  openAckServiceWithOptions(request: OpenAckServiceRequest, headers: {
7983
9015
  [key: string]: string;
7984
9016
  }, runtime: $Util.RuntimeOptions): Promise<OpenAckServiceResponse>;
7985
9017
  /**
7986
- * * You can activate ACK by using Alibaba Cloud accounts.
7987
- * * To activate ACK by using RAM users, you need to grant the AdministratorAccess permission to the RAM users.
7988
- *
7989
- * @param request OpenAckServiceRequest
7990
- * @return OpenAckServiceResponse
9018
+ * @summary You can call the OpenAckService operation to activate Container Service for Kubernetes (ACK).
9019
+ *
9020
+ * @description * You can activate ACK by using Alibaba Cloud accounts.
9021
+ * * To activate ACK by using RAM users, you need to grant the AdministratorAccess permission to the RAM users.
9022
+ *
9023
+ * @param request OpenAckServiceRequest
9024
+ * @return OpenAckServiceResponse
7991
9025
  */
7992
9026
  openAckService(request: OpenAckServiceRequest): Promise<OpenAckServiceResponse>;
7993
9027
  /**
7994
- * @deprecated
7995
- *
7996
- * @param headers map
7997
- * @param runtime runtime options for this request RuntimeOptions
7998
- * @return PauseClusterUpgradeResponse
9028
+ * @deprecated OpenAPI PauseClusterUpgrade is deprecated
9029
+ *
9030
+ * @summary You can call the PauseClusterUpgrade operation to pause the update of a Container Service for Kubernetes (ACK) cluster.
9031
+ *
9032
+ * @param headers map
9033
+ * @param runtime runtime options for this request RuntimeOptions
9034
+ * @return PauseClusterUpgradeResponse
7999
9035
  */
8000
9036
  pauseClusterUpgradeWithOptions(ClusterId: string, headers: {
8001
9037
  [key: string]: string;
8002
9038
  }, runtime: $Util.RuntimeOptions): Promise<PauseClusterUpgradeResponse>;
8003
9039
  /**
8004
- * @deprecated
8005
- *
8006
- * @return PauseClusterUpgradeResponse
9040
+ * @deprecated OpenAPI PauseClusterUpgrade is deprecated
9041
+ *
9042
+ * @summary You can call the PauseClusterUpgrade operation to pause the update of a Container Service for Kubernetes (ACK) cluster.
9043
+ *
9044
+ * @return PauseClusterUpgradeResponse
8007
9045
  */
8008
9046
  pauseClusterUpgrade(ClusterId: string): Promise<PauseClusterUpgradeResponse>;
9047
+ /**
9048
+ * @summary You can call the PauseComponentUpgrade operation to pause the update of a component.
9049
+ *
9050
+ * @param headers map
9051
+ * @param runtime runtime options for this request RuntimeOptions
9052
+ * @return PauseComponentUpgradeResponse
9053
+ */
8009
9054
  pauseComponentUpgradeWithOptions(clusterid: string, componentid: string, headers: {
8010
9055
  [key: string]: string;
8011
9056
  }, runtime: $Util.RuntimeOptions): Promise<PauseComponentUpgradeResponse>;
9057
+ /**
9058
+ * @summary You can call the PauseComponentUpgrade operation to pause the update of a component.
9059
+ *
9060
+ * @return PauseComponentUpgradeResponse
9061
+ */
8012
9062
  pauseComponentUpgrade(clusterid: string, componentid: string): Promise<PauseComponentUpgradeResponse>;
9063
+ /**
9064
+ * @summary Pauses an on-going task.
9065
+ *
9066
+ * @param headers map
9067
+ * @param runtime runtime options for this request RuntimeOptions
9068
+ * @return PauseTaskResponse
9069
+ */
8013
9070
  pauseTaskWithOptions(taskId: string, headers: {
8014
9071
  [key: string]: string;
8015
9072
  }, runtime: $Util.RuntimeOptions): Promise<PauseTaskResponse>;
9073
+ /**
9074
+ * @summary Pauses an on-going task.
9075
+ *
9076
+ * @return PauseTaskResponse
9077
+ */
8016
9078
  pauseTask(taskId: string): Promise<PauseTaskResponse>;
8017
9079
  /**
8018
- * @deprecated
8019
- * ****
8020
- * * When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours.
8021
- * * Unknown errors may occur when you remove nodes. Before you remove nodes, back up the data on the nodes.
8022
- * * Nodes remain in the Unschedulable state when they are being removed.
8023
- * * You can remove only worker nodes. You cannot remove master nodes.
8024
- *
8025
- * @param request RemoveClusterNodesRequest
8026
- * @param headers map
8027
- * @param runtime runtime options for this request RuntimeOptions
8028
- * @return RemoveClusterNodesResponse
9080
+ * @deprecated OpenAPI RemoveClusterNodes is deprecated
9081
+ *
9082
+ * @summary You can call the RemoveClusterNodes operation to remove nodes from a Container Service for Kubernetes (ACK) cluster.
9083
+ *
9084
+ * @description ****
9085
+ * * When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours.
9086
+ * * Unknown errors may occur when you remove nodes. Before you remove nodes, back up the data on the nodes.
9087
+ * * Nodes remain in the Unschedulable state when they are being removed.
9088
+ * * You can remove only worker nodes. You cannot remove master nodes.
9089
+ *
9090
+ * @param request RemoveClusterNodesRequest
9091
+ * @param headers map
9092
+ * @param runtime runtime options for this request RuntimeOptions
9093
+ * @return RemoveClusterNodesResponse
8029
9094
  */
8030
9095
  removeClusterNodesWithOptions(ClusterId: string, request: RemoveClusterNodesRequest, headers: {
8031
9096
  [key: string]: string;
8032
9097
  }, runtime: $Util.RuntimeOptions): Promise<RemoveClusterNodesResponse>;
8033
9098
  /**
8034
- * @deprecated
8035
- * ****
8036
- * * When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours.
8037
- * * Unknown errors may occur when you remove nodes. Before you remove nodes, back up the data on the nodes.
8038
- * * Nodes remain in the Unschedulable state when they are being removed.
8039
- * * You can remove only worker nodes. You cannot remove master nodes.
8040
- *
8041
- * @param request RemoveClusterNodesRequest
8042
- * @return RemoveClusterNodesResponse
9099
+ * @deprecated OpenAPI RemoveClusterNodes is deprecated
9100
+ *
9101
+ * @summary You can call the RemoveClusterNodes operation to remove nodes from a Container Service for Kubernetes (ACK) cluster.
9102
+ *
9103
+ * @description ****
9104
+ * * When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours.
9105
+ * * Unknown errors may occur when you remove nodes. Before you remove nodes, back up the data on the nodes.
9106
+ * * Nodes remain in the Unschedulable state when they are being removed.
9107
+ * * You can remove only worker nodes. You cannot remove master nodes.
9108
+ *
9109
+ * @param request RemoveClusterNodesRequest
9110
+ * @return RemoveClusterNodesResponse
8043
9111
  */
8044
9112
  removeClusterNodes(ClusterId: string, request: RemoveClusterNodesRequest): Promise<RemoveClusterNodesResponse>;
8045
9113
  /**
8046
- * **
8047
- * ****
8048
- * * When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours. - The operation may have unexpected risks. Back up the data before you perform this operation. - When the system removes a node, it sets the status of the node to Unschedulable. - The system removes only worker nodes. It does not remove master nodes.
8049
- *
8050
- * @param tmpReq RemoveNodePoolNodesRequest
8051
- * @param headers map
8052
- * @param runtime runtime options for this request RuntimeOptions
8053
- * @return RemoveNodePoolNodesResponse
9114
+ * @summary Removes nodes from a node pool.
9115
+ *
9116
+ * @description **
9117
+ * ****
9118
+ * * When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours. - The operation may have unexpected risks. Back up the data before you perform this operation. - When the system removes a node, it sets the status of the node to Unschedulable. - The system removes only worker nodes. It does not remove master nodes.
9119
+ *
9120
+ * @param tmpReq RemoveNodePoolNodesRequest
9121
+ * @param headers map
9122
+ * @param runtime runtime options for this request RuntimeOptions
9123
+ * @return RemoveNodePoolNodesResponse
8054
9124
  */
8055
9125
  removeNodePoolNodesWithOptions(ClusterId: string, NodepoolId: string, tmpReq: RemoveNodePoolNodesRequest, headers: {
8056
9126
  [key: string]: string;
8057
9127
  }, runtime: $Util.RuntimeOptions): Promise<RemoveNodePoolNodesResponse>;
8058
9128
  /**
8059
- * **
8060
- * ****
8061
- * * When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours. - The operation may have unexpected risks. Back up the data before you perform this operation. - When the system removes a node, it sets the status of the node to Unschedulable. - The system removes only worker nodes. It does not remove master nodes.
8062
- *
8063
- * @param request RemoveNodePoolNodesRequest
8064
- * @return RemoveNodePoolNodesResponse
9129
+ * @summary Removes nodes from a node pool.
9130
+ *
9131
+ * @description **
9132
+ * ****
9133
+ * * When you remove a node, the pods that run on the node are migrated to other nodes. This may cause service interruptions. We recommend that you remove nodes during off-peak hours. - The operation may have unexpected risks. Back up the data before you perform this operation. - When the system removes a node, it sets the status of the node to Unschedulable. - The system removes only worker nodes. It does not remove master nodes.
9134
+ *
9135
+ * @param request RemoveNodePoolNodesRequest
9136
+ * @return RemoveNodePoolNodesResponse
8065
9137
  */
8066
9138
  removeNodePoolNodes(ClusterId: string, NodepoolId: string, request: RemoveNodePoolNodesRequest): Promise<RemoveNodePoolNodesResponse>;
9139
+ /**
9140
+ * @summary You can call the RemoveWorkflow operation to delete a workflow.
9141
+ *
9142
+ * @param headers map
9143
+ * @param runtime runtime options for this request RuntimeOptions
9144
+ * @return RemoveWorkflowResponse
9145
+ */
8067
9146
  removeWorkflowWithOptions(workflowName: string, headers: {
8068
9147
  [key: string]: string;
8069
9148
  }, runtime: $Util.RuntimeOptions): Promise<RemoveWorkflowResponse>;
9149
+ /**
9150
+ * @summary You can call the RemoveWorkflow operation to delete a workflow.
9151
+ *
9152
+ * @return RemoveWorkflowResponse
9153
+ */
8070
9154
  removeWorkflow(workflowName: string): Promise<RemoveWorkflowResponse>;
9155
+ /**
9156
+ * @summary You can call the RepairClusterNodePool operation to fix issues on specified nodes in a managed node pool.
9157
+ *
9158
+ * @param request RepairClusterNodePoolRequest
9159
+ * @param headers map
9160
+ * @param runtime runtime options for this request RuntimeOptions
9161
+ * @return RepairClusterNodePoolResponse
9162
+ */
8071
9163
  repairClusterNodePoolWithOptions(clusterId: string, nodepoolId: string, request: RepairClusterNodePoolRequest, headers: {
8072
9164
  [key: string]: string;
8073
9165
  }, runtime: $Util.RuntimeOptions): Promise<RepairClusterNodePoolResponse>;
9166
+ /**
9167
+ * @summary You can call the RepairClusterNodePool operation to fix issues on specified nodes in a managed node pool.
9168
+ *
9169
+ * @param request RepairClusterNodePoolRequest
9170
+ * @return RepairClusterNodePoolResponse
9171
+ */
8074
9172
  repairClusterNodePool(clusterId: string, nodepoolId: string, request: RepairClusterNodePoolRequest): Promise<RepairClusterNodePoolResponse>;
9173
+ /**
9174
+ * @summary You can call the ResumeComponentUpgrade operation to resume the update of a component.
9175
+ *
9176
+ * @param headers map
9177
+ * @param runtime runtime options for this request RuntimeOptions
9178
+ * @return ResumeComponentUpgradeResponse
9179
+ */
8075
9180
  resumeComponentUpgradeWithOptions(clusterid: string, componentid: string, headers: {
8076
9181
  [key: string]: string;
8077
9182
  }, runtime: $Util.RuntimeOptions): Promise<ResumeComponentUpgradeResponse>;
9183
+ /**
9184
+ * @summary You can call the ResumeComponentUpgrade operation to resume the update of a component.
9185
+ *
9186
+ * @return ResumeComponentUpgradeResponse
9187
+ */
8078
9188
  resumeComponentUpgrade(clusterid: string, componentid: string): Promise<ResumeComponentUpgradeResponse>;
9189
+ /**
9190
+ * @summary You can call the ResumeTask operation to resume a task.
9191
+ *
9192
+ * @param headers map
9193
+ * @param runtime runtime options for this request RuntimeOptions
9194
+ * @return ResumeTaskResponse
9195
+ */
8079
9196
  resumeTaskWithOptions(taskId: string, headers: {
8080
9197
  [key: string]: string;
8081
9198
  }, runtime: $Util.RuntimeOptions): Promise<ResumeTaskResponse>;
9199
+ /**
9200
+ * @summary You can call the ResumeTask operation to resume a task.
9201
+ *
9202
+ * @return ResumeTaskResponse
9203
+ */
8082
9204
  resumeTask(taskId: string): Promise<ResumeTaskResponse>;
8083
9205
  /**
8084
- * @deprecated
8085
- *
8086
- * @param headers map
8087
- * @param runtime runtime options for this request RuntimeOptions
8088
- * @return ResumeUpgradeClusterResponse
9206
+ * @deprecated OpenAPI ResumeUpgradeCluster is deprecated
9207
+ *
9208
+ * @summary You can call the ResumeUpgradeCluster operation to resume the update of a cluster by cluster ID.
9209
+ *
9210
+ * @param headers map
9211
+ * @param runtime runtime options for this request RuntimeOptions
9212
+ * @return ResumeUpgradeClusterResponse
8089
9213
  */
8090
9214
  resumeUpgradeClusterWithOptions(ClusterId: string, headers: {
8091
9215
  [key: string]: string;
8092
9216
  }, runtime: $Util.RuntimeOptions): Promise<ResumeUpgradeClusterResponse>;
8093
9217
  /**
8094
- * @deprecated
8095
- *
8096
- * @return ResumeUpgradeClusterResponse
9218
+ * @deprecated OpenAPI ResumeUpgradeCluster is deprecated
9219
+ *
9220
+ * @summary You can call the ResumeUpgradeCluster operation to resume the update of a cluster by cluster ID.
9221
+ *
9222
+ * @return ResumeUpgradeClusterResponse
8097
9223
  */
8098
9224
  resumeUpgradeCluster(ClusterId: string): Promise<ResumeUpgradeClusterResponse>;
9225
+ /**
9226
+ * @summary You can call the RunClusterCheck operation to initiate cluster checks, such as cluster update prechecks.
9227
+ *
9228
+ * @param request RunClusterCheckRequest
9229
+ * @param headers map
9230
+ * @param runtime runtime options for this request RuntimeOptions
9231
+ * @return RunClusterCheckResponse
9232
+ */
8099
9233
  runClusterCheckWithOptions(clusterId: string, request: RunClusterCheckRequest, headers: {
8100
9234
  [key: string]: string;
8101
9235
  }, runtime: $Util.RuntimeOptions): Promise<RunClusterCheckResponse>;
9236
+ /**
9237
+ * @summary You can call the RunClusterCheck operation to initiate cluster checks, such as cluster update prechecks.
9238
+ *
9239
+ * @param request RunClusterCheckRequest
9240
+ * @return RunClusterCheckResponse
9241
+ */
8102
9242
  runClusterCheck(clusterId: string, request: RunClusterCheckRequest): Promise<RunClusterCheckResponse>;
8103
9243
  /**
8104
- * @deprecated
8105
- *
8106
- * @param request ScaleClusterRequest
8107
- * @param headers map
8108
- * @param runtime runtime options for this request RuntimeOptions
8109
- * @return ScaleClusterResponse
9244
+ * @deprecated OpenAPI ScaleCluster is deprecated
9245
+ *
9246
+ * @summary 扩容Kubernetes集群
9247
+ *
9248
+ * @param request ScaleClusterRequest
9249
+ * @param headers map
9250
+ * @param runtime runtime options for this request RuntimeOptions
9251
+ * @return ScaleClusterResponse
8110
9252
  */
8111
9253
  scaleClusterWithOptions(ClusterId: string, request: ScaleClusterRequest, headers: {
8112
9254
  [key: string]: string;
8113
9255
  }, runtime: $Util.RuntimeOptions): Promise<ScaleClusterResponse>;
8114
9256
  /**
8115
- * @deprecated
8116
- *
8117
- * @param request ScaleClusterRequest
8118
- * @return ScaleClusterResponse
9257
+ * @deprecated OpenAPI ScaleCluster is deprecated
9258
+ *
9259
+ * @summary 扩容Kubernetes集群
9260
+ *
9261
+ * @param request ScaleClusterRequest
9262
+ * @return ScaleClusterResponse
8119
9263
  */
8120
9264
  scaleCluster(ClusterId: string, request: ScaleClusterRequest): Promise<ScaleClusterResponse>;
9265
+ /**
9266
+ * @summary You can call the ScaleClusterNodePool operation to scale out a node pool by node pool ID.
9267
+ *
9268
+ * @param request ScaleClusterNodePoolRequest
9269
+ * @param headers map
9270
+ * @param runtime runtime options for this request RuntimeOptions
9271
+ * @return ScaleClusterNodePoolResponse
9272
+ */
8121
9273
  scaleClusterNodePoolWithOptions(ClusterId: string, NodepoolId: string, request: ScaleClusterNodePoolRequest, headers: {
8122
9274
  [key: string]: string;
8123
9275
  }, runtime: $Util.RuntimeOptions): Promise<ScaleClusterNodePoolResponse>;
9276
+ /**
9277
+ * @summary You can call the ScaleClusterNodePool operation to scale out a node pool by node pool ID.
9278
+ *
9279
+ * @param request ScaleClusterNodePoolRequest
9280
+ * @return ScaleClusterNodePoolResponse
9281
+ */
8124
9282
  scaleClusterNodePool(ClusterId: string, NodepoolId: string, request: ScaleClusterNodePoolRequest): Promise<ScaleClusterNodePoolResponse>;
8125
9283
  /**
8126
- * **
8127
- * ****The ScaleOutCluster API operation is phased out. You must call the node pool-related API operations to manage nodes. If you want to add worker nodes to a Container Service for Kubernetes (ACK) cluster, call the ScaleClusterNodePool API operation. For more information, see [ScaleClusterNodePool](~~184928~~).
8128
- *
8129
- * @param request ScaleOutClusterRequest
8130
- * @param headers map
8131
- * @param runtime runtime options for this request RuntimeOptions
8132
- * @return ScaleOutClusterResponse
9284
+ * @summary You can call the ScaleOutCluster operation to scale out a cluster by cluster ID.
9285
+ *
9286
+ * @description **
9287
+ * ****The ScaleOutCluster API operation is phased out. You must call the node pool-related API operations to manage nodes. If you want to add worker nodes to a Container Service for Kubernetes (ACK) cluster, call the ScaleClusterNodePool API operation. For more information, see [ScaleClusterNodePool](https://help.aliyun.com/document_detail/184928.html).
9288
+ *
9289
+ * @param request ScaleOutClusterRequest
9290
+ * @param headers map
9291
+ * @param runtime runtime options for this request RuntimeOptions
9292
+ * @return ScaleOutClusterResponse
8133
9293
  */
8134
9294
  scaleOutClusterWithOptions(ClusterId: string, request: ScaleOutClusterRequest, headers: {
8135
9295
  [key: string]: string;
8136
9296
  }, runtime: $Util.RuntimeOptions): Promise<ScaleOutClusterResponse>;
8137
9297
  /**
8138
- * **
8139
- * ****The ScaleOutCluster API operation is phased out. You must call the node pool-related API operations to manage nodes. If you want to add worker nodes to a Container Service for Kubernetes (ACK) cluster, call the ScaleClusterNodePool API operation. For more information, see [ScaleClusterNodePool](~~184928~~).
8140
- *
8141
- * @param request ScaleOutClusterRequest
8142
- * @return ScaleOutClusterResponse
9298
+ * @summary You can call the ScaleOutCluster operation to scale out a cluster by cluster ID.
9299
+ *
9300
+ * @description **
9301
+ * ****The ScaleOutCluster API operation is phased out. You must call the node pool-related API operations to manage nodes. If you want to add worker nodes to a Container Service for Kubernetes (ACK) cluster, call the ScaleClusterNodePool API operation. For more information, see [ScaleClusterNodePool](https://help.aliyun.com/document_detail/184928.html).
9302
+ *
9303
+ * @param request ScaleOutClusterRequest
9304
+ * @return ScaleOutClusterResponse
8143
9305
  */
8144
9306
  scaleOutCluster(ClusterId: string, request: ScaleOutClusterRequest): Promise<ScaleOutClusterResponse>;
9307
+ /**
9308
+ * @summary The cluster ID.
9309
+ *
9310
+ * @param headers map
9311
+ * @param runtime runtime options for this request RuntimeOptions
9312
+ * @return ScanClusterVulsResponse
9313
+ */
8145
9314
  scanClusterVulsWithOptions(clusterId: string, headers: {
8146
9315
  [key: string]: string;
8147
9316
  }, runtime: $Util.RuntimeOptions): Promise<ScanClusterVulsResponse>;
9317
+ /**
9318
+ * @summary The cluster ID.
9319
+ *
9320
+ * @return ScanClusterVulsResponse
9321
+ */
8148
9322
  scanClusterVuls(clusterId: string): Promise<ScanClusterVulsResponse>;
9323
+ /**
9324
+ * @param request StartAlertRequest
9325
+ * @param headers map
9326
+ * @param runtime runtime options for this request RuntimeOptions
9327
+ * @return StartAlertResponse
9328
+ */
8149
9329
  startAlertWithOptions(ClusterId: string, request: StartAlertRequest, headers: {
8150
9330
  [key: string]: string;
8151
9331
  }, runtime: $Util.RuntimeOptions): Promise<StartAlertResponse>;
9332
+ /**
9333
+ * @param request StartAlertRequest
9334
+ * @return StartAlertResponse
9335
+ */
8152
9336
  startAlert(ClusterId: string, request: StartAlertRequest): Promise<StartAlertResponse>;
9337
+ /**
9338
+ * @summary You can call the StartWorkflow operation to create a workflow.
9339
+ *
9340
+ * @param request StartWorkflowRequest
9341
+ * @param headers map
9342
+ * @param runtime runtime options for this request RuntimeOptions
9343
+ * @return StartWorkflowResponse
9344
+ */
8153
9345
  startWorkflowWithOptions(request: StartWorkflowRequest, headers: {
8154
9346
  [key: string]: string;
8155
9347
  }, runtime: $Util.RuntimeOptions): Promise<StartWorkflowResponse>;
9348
+ /**
9349
+ * @summary You can call the StartWorkflow operation to create a workflow.
9350
+ *
9351
+ * @param request StartWorkflowRequest
9352
+ * @return StartWorkflowResponse
9353
+ */
8156
9354
  startWorkflow(request: StartWorkflowRequest): Promise<StartWorkflowResponse>;
9355
+ /**
9356
+ * @summary You can call the StopAlert operation to disable an alert rule or an alert rule set in the alert center of Container Service for Kubernetes (ACK).
9357
+ *
9358
+ * @param request StopAlertRequest
9359
+ * @param headers map
9360
+ * @param runtime runtime options for this request RuntimeOptions
9361
+ * @return StopAlertResponse
9362
+ */
8157
9363
  stopAlertWithOptions(ClusterId: string, request: StopAlertRequest, headers: {
8158
9364
  [key: string]: string;
8159
9365
  }, runtime: $Util.RuntimeOptions): Promise<StopAlertResponse>;
9366
+ /**
9367
+ * @summary You can call the StopAlert operation to disable an alert rule or an alert rule set in the alert center of Container Service for Kubernetes (ACK).
9368
+ *
9369
+ * @param request StopAlertRequest
9370
+ * @return StopAlertResponse
9371
+ */
8160
9372
  stopAlert(ClusterId: string, request: StopAlertRequest): Promise<StopAlertResponse>;
9373
+ /**
9374
+ * @summary Synchronizes the information about a node pool, including the metadata and node information of the node pool.
9375
+ *
9376
+ * @param headers map
9377
+ * @param runtime runtime options for this request RuntimeOptions
9378
+ * @return SyncClusterNodePoolResponse
9379
+ */
8161
9380
  syncClusterNodePoolWithOptions(ClusterId: string, headers: {
8162
9381
  [key: string]: string;
8163
9382
  }, runtime: $Util.RuntimeOptions): Promise<SyncClusterNodePoolResponse>;
9383
+ /**
9384
+ * @summary Synchronizes the information about a node pool, including the metadata and node information of the node pool.
9385
+ *
9386
+ * @return SyncClusterNodePoolResponse
9387
+ */
8164
9388
  syncClusterNodePool(ClusterId: string): Promise<SyncClusterNodePoolResponse>;
9389
+ /**
9390
+ * @summary Adds labels to a Container Service for Kubernetes (ACK) cluster. You can use labels to classify and manage ACK clusters in order to meet monitoring, cost analysis, and tenant isolation requirements.
9391
+ *
9392
+ * @param request TagResourcesRequest
9393
+ * @param headers map
9394
+ * @param runtime runtime options for this request RuntimeOptions
9395
+ * @return TagResourcesResponse
9396
+ */
8165
9397
  tagResourcesWithOptions(request: TagResourcesRequest, headers: {
8166
9398
  [key: string]: string;
8167
9399
  }, runtime: $Util.RuntimeOptions): Promise<TagResourcesResponse>;
9400
+ /**
9401
+ * @summary Adds labels to a Container Service for Kubernetes (ACK) cluster. You can use labels to classify and manage ACK clusters in order to meet monitoring, cost analysis, and tenant isolation requirements.
9402
+ *
9403
+ * @param request TagResourcesRequest
9404
+ * @return TagResourcesResponse
9405
+ */
8168
9406
  tagResources(request: TagResourcesRequest): Promise<TagResourcesResponse>;
9407
+ /**
9408
+ * @summary You can call the UnInstallClusterAddons operation to uninstall the components in a cluster by component names.
9409
+ *
9410
+ * @param request UnInstallClusterAddonsRequest
9411
+ * @param headers map
9412
+ * @param runtime runtime options for this request RuntimeOptions
9413
+ * @return UnInstallClusterAddonsResponse
9414
+ */
8169
9415
  unInstallClusterAddonsWithOptions(ClusterId: string, request: UnInstallClusterAddonsRequest, headers: {
8170
9416
  [key: string]: string;
8171
9417
  }, runtime: $Util.RuntimeOptions): Promise<UnInstallClusterAddonsResponse>;
9418
+ /**
9419
+ * @summary You can call the UnInstallClusterAddons operation to uninstall the components in a cluster by component names.
9420
+ *
9421
+ * @param request UnInstallClusterAddonsRequest
9422
+ * @return UnInstallClusterAddonsResponse
9423
+ */
8172
9424
  unInstallClusterAddons(ClusterId: string, request: UnInstallClusterAddonsRequest): Promise<UnInstallClusterAddonsResponse>;
9425
+ /**
9426
+ * @summary Removes labels from a Container Service for Kubernetes (ACK) cluster.
9427
+ *
9428
+ * @param tmpReq UntagResourcesRequest
9429
+ * @param headers map
9430
+ * @param runtime runtime options for this request RuntimeOptions
9431
+ * @return UntagResourcesResponse
9432
+ */
8173
9433
  untagResourcesWithOptions(tmpReq: UntagResourcesRequest, headers: {
8174
9434
  [key: string]: string;
8175
9435
  }, runtime: $Util.RuntimeOptions): Promise<UntagResourcesResponse>;
9436
+ /**
9437
+ * @summary Removes labels from a Container Service for Kubernetes (ACK) cluster.
9438
+ *
9439
+ * @param request UntagResourcesRequest
9440
+ * @return UntagResourcesResponse
9441
+ */
8176
9442
  untagResources(request: UntagResourcesRequest): Promise<UntagResourcesResponse>;
9443
+ /**
9444
+ * @param headers map
9445
+ * @param runtime runtime options for this request RuntimeOptions
9446
+ * @return UpdateContactGroupForAlertResponse
9447
+ */
8177
9448
  updateContactGroupForAlertWithOptions(ClusterId: string, headers: {
8178
9449
  [key: string]: string;
8179
9450
  }, runtime: $Util.RuntimeOptions): Promise<UpdateContactGroupForAlertResponse>;
9451
+ /**
9452
+ * @return UpdateContactGroupForAlertResponse
9453
+ */
8180
9454
  updateContactGroupForAlert(ClusterId: string): Promise<UpdateContactGroupForAlertResponse>;
9455
+ /**
9456
+ * @summary You can call the UpdateControlPlaneLog operation to modify the log collection configurations for control plane components in a Container Service for Kubernetes (ACK) managed cluster.
9457
+ *
9458
+ * @param request UpdateControlPlaneLogRequest
9459
+ * @param headers map
9460
+ * @param runtime runtime options for this request RuntimeOptions
9461
+ * @return UpdateControlPlaneLogResponse
9462
+ */
8181
9463
  updateControlPlaneLogWithOptions(ClusterId: string, request: UpdateControlPlaneLogRequest, headers: {
8182
9464
  [key: string]: string;
8183
9465
  }, runtime: $Util.RuntimeOptions): Promise<UpdateControlPlaneLogResponse>;
9466
+ /**
9467
+ * @summary You can call the UpdateControlPlaneLog operation to modify the log collection configurations for control plane components in a Container Service for Kubernetes (ACK) managed cluster.
9468
+ *
9469
+ * @param request UpdateControlPlaneLogRequest
9470
+ * @return UpdateControlPlaneLogResponse
9471
+ */
8184
9472
  updateControlPlaneLog(ClusterId: string, request: UpdateControlPlaneLogRequest): Promise<UpdateControlPlaneLogResponse>;
8185
9473
  /**
8186
- * **
8187
- * ****
8188
- * * You can call this operation only with an Alibaba Cloud account. - If the kubeconfig file used by your cluster is revoked, the custom validity period of the kubeconfig file is reset. In this case, you need to call this API operation to reconfigure the validity period of the kubeconfig file.
8189
- *
8190
- * @param request UpdateK8sClusterUserConfigExpireRequest
8191
- * @param headers map
8192
- * @param runtime runtime options for this request RuntimeOptions
8193
- * @return UpdateK8sClusterUserConfigExpireResponse
9474
+ * @summary Sets the validity period of a kubeconfig file used by a Resource Access Management (RAM) user or RAM role to connect to a Container Service for Kubernetes (ACK) cluster. The validity period ranges from 1 to 876,000 hours. You can call this API operation when you customize configurations by using an Alibaba Cloud account. The default validity period of a kubeconfig file is three years.
9475
+ *
9476
+ * @description **
9477
+ * ****
9478
+ * * You can call this operation only with an Alibaba Cloud account. - If the kubeconfig file used by your cluster is revoked, the custom validity period of the kubeconfig file is reset. In this case, you need to call this API operation to reconfigure the validity period of the kubeconfig file.
9479
+ *
9480
+ * @param request UpdateK8sClusterUserConfigExpireRequest
9481
+ * @param headers map
9482
+ * @param runtime runtime options for this request RuntimeOptions
9483
+ * @return UpdateK8sClusterUserConfigExpireResponse
8194
9484
  */
8195
9485
  updateK8sClusterUserConfigExpireWithOptions(ClusterId: string, request: UpdateK8sClusterUserConfigExpireRequest, headers: {
8196
9486
  [key: string]: string;
8197
9487
  }, runtime: $Util.RuntimeOptions): Promise<UpdateK8sClusterUserConfigExpireResponse>;
8198
9488
  /**
8199
- * **
8200
- * ****
8201
- * * You can call this operation only with an Alibaba Cloud account. - If the kubeconfig file used by your cluster is revoked, the custom validity period of the kubeconfig file is reset. In this case, you need to call this API operation to reconfigure the validity period of the kubeconfig file.
8202
- *
8203
- * @param request UpdateK8sClusterUserConfigExpireRequest
8204
- * @return UpdateK8sClusterUserConfigExpireResponse
9489
+ * @summary Sets the validity period of a kubeconfig file used by a Resource Access Management (RAM) user or RAM role to connect to a Container Service for Kubernetes (ACK) cluster. The validity period ranges from 1 to 876,000 hours. You can call this API operation when you customize configurations by using an Alibaba Cloud account. The default validity period of a kubeconfig file is three years.
9490
+ *
9491
+ * @description **
9492
+ * ****
9493
+ * * You can call this operation only with an Alibaba Cloud account. - If the kubeconfig file used by your cluster is revoked, the custom validity period of the kubeconfig file is reset. In this case, you need to call this API operation to reconfigure the validity period of the kubeconfig file.
9494
+ *
9495
+ * @param request UpdateK8sClusterUserConfigExpireRequest
9496
+ * @return UpdateK8sClusterUserConfigExpireResponse
8205
9497
  */
8206
9498
  updateK8sClusterUserConfigExpire(ClusterId: string, request: UpdateK8sClusterUserConfigExpireRequest): Promise<UpdateK8sClusterUserConfigExpireResponse>;
9499
+ /**
9500
+ * @summary You can call the UpdateTemplate operation to update an orchestration template by template ID.
9501
+ *
9502
+ * @param request UpdateTemplateRequest
9503
+ * @param headers map
9504
+ * @param runtime runtime options for this request RuntimeOptions
9505
+ * @return UpdateTemplateResponse
9506
+ */
8207
9507
  updateTemplateWithOptions(TemplateId: string, request: UpdateTemplateRequest, headers: {
8208
9508
  [key: string]: string;
8209
9509
  }, runtime: $Util.RuntimeOptions): Promise<UpdateTemplateResponse>;
9510
+ /**
9511
+ * @summary You can call the UpdateTemplate operation to update an orchestration template by template ID.
9512
+ *
9513
+ * @param request UpdateTemplateRequest
9514
+ * @return UpdateTemplateResponse
9515
+ */
8210
9516
  updateTemplate(TemplateId: string, request: UpdateTemplateRequest): Promise<UpdateTemplateResponse>;
9517
+ /**
9518
+ * @summary 更新指定RAM用户/角色的RBAC权限
9519
+ *
9520
+ * @param request UpdateUserPermissionsRequest
9521
+ * @param headers map
9522
+ * @param runtime runtime options for this request RuntimeOptions
9523
+ * @return UpdateUserPermissionsResponse
9524
+ */
8211
9525
  updateUserPermissionsWithOptions(uid: string, request: UpdateUserPermissionsRequest, headers: {
8212
9526
  [key: string]: string;
8213
9527
  }, runtime: $Util.RuntimeOptions): Promise<UpdateUserPermissionsResponse>;
9528
+ /**
9529
+ * @summary 更新指定RAM用户/角色的RBAC权限
9530
+ *
9531
+ * @param request UpdateUserPermissionsRequest
9532
+ * @return UpdateUserPermissionsResponse
9533
+ */
8214
9534
  updateUserPermissions(uid: string, request: UpdateUserPermissionsRequest): Promise<UpdateUserPermissionsResponse>;
9535
+ /**
9536
+ * @summary You can call the UpgradeCluster operation to upgrade a cluster by cluster ID.
9537
+ *
9538
+ * @param request UpgradeClusterRequest
9539
+ * @param headers map
9540
+ * @param runtime runtime options for this request RuntimeOptions
9541
+ * @return UpgradeClusterResponse
9542
+ */
8215
9543
  upgradeClusterWithOptions(ClusterId: string, request: UpgradeClusterRequest, headers: {
8216
9544
  [key: string]: string;
8217
9545
  }, runtime: $Util.RuntimeOptions): Promise<UpgradeClusterResponse>;
9546
+ /**
9547
+ * @summary You can call the UpgradeCluster operation to upgrade a cluster by cluster ID.
9548
+ *
9549
+ * @param request UpgradeClusterRequest
9550
+ * @return UpgradeClusterResponse
9551
+ */
8218
9552
  upgradeCluster(ClusterId: string, request: UpgradeClusterRequest): Promise<UpgradeClusterResponse>;
9553
+ /**
9554
+ * @summary Updates cluster components to use new features and patch vulnerabilities. You must update cluster components one after one and update a component only after the previous one is successfully updated. Before you update a component, we recommend that you read the update notes for each component. Cluster component updates may affect your businesses. Assess the impact, back up data, and perform the update during off-peak hours.
9555
+ *
9556
+ * @param request UpgradeClusterAddonsRequest
9557
+ * @param headers map
9558
+ * @param runtime runtime options for this request RuntimeOptions
9559
+ * @return UpgradeClusterAddonsResponse
9560
+ */
8219
9561
  upgradeClusterAddonsWithOptions(ClusterId: string, request: UpgradeClusterAddonsRequest, headers: {
8220
9562
  [key: string]: string;
8221
9563
  }, runtime: $Util.RuntimeOptions): Promise<UpgradeClusterAddonsResponse>;
9564
+ /**
9565
+ * @summary Updates cluster components to use new features and patch vulnerabilities. You must update cluster components one after one and update a component only after the previous one is successfully updated. Before you update a component, we recommend that you read the update notes for each component. Cluster component updates may affect your businesses. Assess the impact, back up data, and perform the update during off-peak hours.
9566
+ *
9567
+ * @param request UpgradeClusterAddonsRequest
9568
+ * @return UpgradeClusterAddonsResponse
9569
+ */
8222
9570
  upgradeClusterAddons(ClusterId: string, request: UpgradeClusterAddonsRequest): Promise<UpgradeClusterAddonsResponse>;
8223
9571
  /**
8224
- * This operation allows you to update the Kubernetes version, OS version, or container runtime version of the nodes in a node pool.
8225
- *
8226
- * @param request UpgradeClusterNodepoolRequest
8227
- * @param headers map
8228
- * @param runtime runtime options for this request RuntimeOptions
8229
- * @return UpgradeClusterNodepoolResponse
9572
+ * @summary You can call the UpgradeClusterNodepool operation to update the Kubernetes version, OS version, or container runtime version of the nodes in a node pool.
9573
+ *
9574
+ * @description This operation allows you to update the Kubernetes version, OS version, or container runtime version of the nodes in a node pool.
9575
+ *
9576
+ * @param request UpgradeClusterNodepoolRequest
9577
+ * @param headers map
9578
+ * @param runtime runtime options for this request RuntimeOptions
9579
+ * @return UpgradeClusterNodepoolResponse
8230
9580
  */
8231
9581
  upgradeClusterNodepoolWithOptions(ClusterId: string, NodepoolId: string, request: UpgradeClusterNodepoolRequest, headers: {
8232
9582
  [key: string]: string;
8233
9583
  }, runtime: $Util.RuntimeOptions): Promise<UpgradeClusterNodepoolResponse>;
8234
9584
  /**
8235
- * This operation allows you to update the Kubernetes version, OS version, or container runtime version of the nodes in a node pool.
8236
- *
8237
- * @param request UpgradeClusterNodepoolRequest
8238
- * @return UpgradeClusterNodepoolResponse
9585
+ * @summary You can call the UpgradeClusterNodepool operation to update the Kubernetes version, OS version, or container runtime version of the nodes in a node pool.
9586
+ *
9587
+ * @description This operation allows you to update the Kubernetes version, OS version, or container runtime version of the nodes in a node pool.
9588
+ *
9589
+ * @param request UpgradeClusterNodepoolRequest
9590
+ * @return UpgradeClusterNodepoolResponse
8239
9591
  */
8240
9592
  upgradeClusterNodepool(ClusterId: string, NodepoolId: string, request: UpgradeClusterNodepoolRequest): Promise<UpgradeClusterNodepoolResponse>;
8241
9593
  }