diff --git a/docs/cce/api-ref/ALL_META.TXT.json b/docs/cce/api-ref/ALL_META.TXT.json index 2bc3b2ceb..6e501b255 100644 --- a/docs/cce/api-ref/ALL_META.TXT.json +++ b/docs/cce/api-ref/ALL_META.TXT.json @@ -596,11 +596,30 @@ "title":"Deleting a Node Pool", "githuburl":"" }, + { + "uri":"cce_02_0358.html", + "node_id":"cce_02_0358.xml", + "product_code":"cce", + "code":"34", + "des":"This API is used to synchronize node pool configurations to existing nodes.PUT /api/v3.1/projects/{project_id}/clusters/{cluster_id}/nodepool/{nodepool_id}/syncStatus cod", + "doc_type":"api2", + "kw":"Synchronizing Node Pool Configurations to Existing Nodes,Cluster Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api2", + "operation_id":"SyncNodePool" + } + ], + "title":"Synchronizing Node Pool Configurations to Existing Nodes", + "githuburl":"" + }, { "uri":"cce_02_0320.html", "node_id":"cce_02_0320.xml", "product_code":"cce", - "code":"34", + "code":"35", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api2", "kw":"Add-on Management", @@ -618,7 +637,7 @@ "uri":"cce_02_0322.html", "node_id":"cce_02_0322.xml", "product_code":"cce", - "code":"35", + "code":"36", "des":"This API is used to install an add-on instance by using the add-on template. One or more instances will be created for the installed add-on.The URL for add-on management ", "doc_type":"api2", "kw":"Installing an Add-on Instance,Add-on Management,API Reference", @@ -636,7 +655,7 @@ "uri":"cce_02_0321.html", "node_id":"cce_02_0321.xml", "product_code":"cce", - "code":"36", + "code":"37", "des":"This API is used to query add-on information.The URL for add-on management is in the format of https://{clusterid}.Endpoint/uri. In the URL, {clusterid} indicates the clu", "doc_type":"api2", "kw":"Reading Add-on Templates,Add-on Management,API Reference", @@ -654,7 +673,7 @@ "uri":"cce_02_0323.html", "node_id":"cce_02_0323.xml", "product_code":"cce", - "code":"37", + "code":"38", "des":"This API is used to update an add-on instance.The URL for add-on management is in the format of https://{clusterid}.Endpoint/uri. In the URL, {clusterid} indicates the cl", "doc_type":"api2", "kw":"Updating an Add-on Instance,Add-on Management,API Reference", @@ -672,7 +691,7 @@ "uri":"cce_02_0324.html", "node_id":"cce_02_0324.xml", "product_code":"cce", - "code":"38", + "code":"39", "des":"This API is used to delete an add-on instance.The URL for add-on management is in the format of https://{clusterid}.Endpoint/uri. In the URL, {clusterid} indicates the cl", "doc_type":"api2", "kw":"Deleting an Add-on Instance,Add-on Management,API Reference", @@ -690,7 +709,7 @@ "uri":"cce_02_0325.html", "node_id":"cce_02_0325.xml", "product_code":"cce", - "code":"39", + "code":"40", "des":"This API is used to obtain details about an add-on instance.The URL for add-on management is in the format of https://{clusterid}.Endpoint/uri. In the URL, {clusterid} in", "doc_type":"api2", "kw":"Reading an Add-on Instance,Add-on Management,API Reference", @@ -708,7 +727,7 @@ "uri":"cce_02_0326.html", "node_id":"cce_02_0326.xml", "product_code":"cce", - "code":"40", + "code":"41", "des":"This API is used to list all add-on instances in the cluster.The URL for add-on management is in the format of https://{clusterid}.Endpoint/uri. In the URL, {clusterid} i", "doc_type":"api2", "kw":"Listing Add-on Instances,Add-on Management,API Reference", @@ -722,11 +741,49 @@ "title":"Listing Add-on Instances", "githuburl":"" }, + { + "uri":"BatchCreateAddonPrecheck.html", + "node_id":"batchcreateaddonprecheck.xml", + "product_code":"cce", + "code":"42", + "des":"This API is used to create add-on check tasks in batches in a specified cluster.POST /api/v3/projects/{project_id}/clusters/{cluster_id}/addons/precheckStatus code: 201Cr", + "doc_type":"api2", + "kw":"Creating Add-on Check Tasks in Batches,Add-on Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api2", + "operation_id":"BatchCreateAddonPrecheck" + } + ], + "title":"Creating Add-on Check Tasks in Batches", + "githuburl":"" + }, + { + "uri":"ListAddonPrecheckTasks.html", + "node_id":"listaddonprechecktasks.xml", + "product_code":"cce", + "code":"43", + "des":"This API is used to obtain the results of the add-on check tasks in a cluster.GET /api/v3/projects/{project_id}/clusters/{cluster_id}/addons/precheck/tasksStatus code: 20", + "doc_type":"api2", + "kw":"Obtaining the Add-on Check Task Results,Add-on Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api2", + "operation_id":"ListAddonPrecheckTasks" + } + ], + "title":"Obtaining the Add-on Check Task Results", + "githuburl":"" + }, { "uri":"quota_lifecycle_management.html", "node_id":"quota_lifecycle_management.xml", "product_code":"cce", - "code":"41", + "code":"44", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api2", "kw":"Quota Management", @@ -744,7 +801,7 @@ "uri":"ShowQuotas.html", "node_id":"showquotas.xml", "product_code":"cce", - "code":"42", + "code":"45", "des":"This API is used to query CCE resource quotas.GET /api/v3/projects/{project_id}/quotasStatus code: 200NoneStatus code: 200The resource quotas are obtained successfully.Se", "doc_type":"api2", "kw":"Querying Resource Quotas,Quota Management,API Reference", @@ -762,7 +819,7 @@ "uri":"chart_lifecycle_management.html", "node_id":"chart_lifecycle_management.xml", "product_code":"cce", - "code":"43", + "code":"46", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api2", "kw":"Chart Management", @@ -780,7 +837,7 @@ "uri":"UploadChart.html", "node_id":"uploadchart.xml", "product_code":"cce", - "code":"44", + "code":"47", "des":"This API is used to upload a chart.POST /v2/chartsStatus code: 201If the FormDataparameter exists, the value of Content-Typemust be multipart/form-data, and the file path", "doc_type":"api2", "kw":"Uploading a Chart,Chart Management,API Reference", @@ -798,7 +855,7 @@ "uri":"ListCharts.html", "node_id":"listcharts.xml", "product_code":"cce", - "code":"45", + "code":"48", "des":"This API is used to obtain the chart list.GET /v2/chartsStatus code: 200NoneStatus code: 200OKSee Error Codes.", "doc_type":"api2", "kw":"Obtaining a Chart List,Chart Management,API Reference", @@ -816,7 +873,7 @@ "uri":"ListReleases.html", "node_id":"listreleases.xml", "product_code":"cce", - "code":"46", + "code":"49", "des":"This API is used to obtain a release list.GET /cce/cam/v3/clusters/{cluster_id}/releasesStatus code: 200NoneStatus code: 200OKSee Error Codes.", "doc_type":"api2", "kw":"Obtaining a Release List,Chart Management,API Reference", @@ -834,7 +891,7 @@ "uri":"UpdateChart.html", "node_id":"updatechart.xml", "product_code":"cce", - "code":"47", + "code":"50", "des":"This API is used to update a chart.PUT /v2/charts/{chart_id}Status code: 200If the FormDataparameter exists, the value of Content-Typemust be multipart/form-data, and the", "doc_type":"api2", "kw":"Updating a Chart,Chart Management,API Reference", @@ -852,7 +909,7 @@ "uri":"CreateRelease.html", "node_id":"createrelease.xml", "product_code":"cce", - "code":"48", + "code":"51", "des":"This API is used to create a release.POST /cce/cam/v3/clusters/{cluster_id}/releasesStatus code: 201Status code: 201CreatedSee Error Codes.", "doc_type":"api2", "kw":"Creating a Release,Chart Management,API Reference", @@ -870,7 +927,7 @@ "uri":"DeleteChart.html", "node_id":"deletechart.xml", "product_code":"cce", - "code":"49", + "code":"52", "des":"This API is used to delete a chart.DELETE /v2/charts/{chart_id}Status code: 200NoneStatus code: 200OKSee Error Codes.", "doc_type":"api2", "kw":"Deleting a Chart,Chart Management,API Reference", @@ -888,7 +945,7 @@ "uri":"UpdateRelease.html", "node_id":"updaterelease.xml", "product_code":"cce", - "code":"50", + "code":"53", "des":"This API is used to update a release.PUT /cce/cam/v3/clusters/{cluster_id}/namespace/{namespace}/releases/{name}Status code: 200Status code: 200OKSee Error Codes.", "doc_type":"api2", "kw":"Updating a Release,Chart Management,API Reference", @@ -906,7 +963,7 @@ "uri":"ShowChart.html", "node_id":"showchart.xml", "product_code":"cce", - "code":"51", + "code":"54", "des":"This API is used to obtain a chart.GET /v2/charts/{chart_id}Status code: 200NoneStatus code: 200OKSee Error Codes.", "doc_type":"api2", "kw":"Obtaining a Chart,Chart Management,API Reference", @@ -924,7 +981,7 @@ "uri":"DeleteRelease.html", "node_id":"deleterelease.xml", "product_code":"cce", - "code":"52", + "code":"55", "des":"This API is used to delete a release.DELETE /cce/cam/v3/clusters/{cluster_id}/namespace/{namespace}/releases/{name}Status code: 200NoneStatus code: 200OKSee Error Codes.", "doc_type":"api2", "kw":"Deleting a Release,Chart Management,API Reference", @@ -942,7 +999,7 @@ "uri":"DownloadChart.html", "node_id":"downloadchart.xml", "product_code":"cce", - "code":"53", + "code":"56", "des":"This API is used to download a chart.GET /v2/charts/{chart_id}/archiveStatus code: 200NoneStatus code: 200OKSee Error Codes.", "doc_type":"api2", "kw":"Downloading a Chart,Chart Management,API Reference", @@ -960,7 +1017,7 @@ "uri":"ShowRelease.html", "node_id":"showrelease.xml", "product_code":"cce", - "code":"54", + "code":"57", "des":"This API is used to obtain a release.GET /cce/cam/v3/clusters/{cluster_id}/namespace/{namespace}/releases/{name}Status code: 200NoneStatus code: 200OKSee Error Codes.", "doc_type":"api2", "kw":"Obtaining a Release,Chart Management,API Reference", @@ -978,7 +1035,7 @@ "uri":"ShowChartValues.html", "node_id":"showchartvalues.xml", "product_code":"cce", - "code":"55", + "code":"58", "des":"This API is used to obtain chart values.GET /v2/charts/{chart_id}/valuesStatus code: 200NoneStatus code: 200OKSee Error Codes.", "doc_type":"api2", "kw":"Obtaining Chart Values,Chart Management,API Reference", @@ -996,7 +1053,7 @@ "uri":"ShowReleaseHistory.html", "node_id":"showreleasehistory.xml", "product_code":"cce", - "code":"56", + "code":"59", "des":"This API is used to obtain historical records of a release.GET /cce/cam/v3/clusters/{cluster_id}/namespace/{namespace}/releases/{name}/historyStatus code: 200NoneStatus c", "doc_type":"api2", "kw":"Obtaining Historical Records of a Release,Chart Management,API Reference", @@ -1014,7 +1071,7 @@ "uri":"ShowUserChartsQuotas.html", "node_id":"showuserchartsquotas.xml", "product_code":"cce", - "code":"57", + "code":"60", "des":"This API is used to obtain the quota of a user chart.GET /v2/charts/{project_id}/quotasStatus code: 200NoneStatus code: 200OKSee Error Codes.", "doc_type":"api2", "kw":"Obtaining the Quota of a User Chart,Chart Management,API Reference", @@ -1032,7 +1089,7 @@ "uri":"configuration_lifecycle_management.html", "node_id":"configuration_lifecycle_management.xml", "product_code":"cce", - "code":"58", + "code":"61", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api2", "kw":"Configuration Management", @@ -1050,7 +1107,7 @@ "uri":"ShowNodePoolConfigurationDetails.html", "node_id":"shownodepoolconfigurationdetails.xml", "product_code":"cce", - "code":"59", + "code":"62", "des":"This API is used to obtain the list of parameters that can be configured for a CCE node pool.GET /api/v3/projects/{project_id}/clusters/{cluster_id}/nodepools/{nodepool_i", "doc_type":"api2", "kw":"Obtaining the List of Parameters That Can Be Configured for a Node Pool,Configuration Management,API", @@ -1068,7 +1125,7 @@ "uri":"ShowClusterConfigurationDetails.html", "node_id":"showclusterconfigurationdetails.xml", "product_code":"cce", - "code":"60", + "code":"63", "des":"This API is used to obtain the list of parameters that can be configured for a CCE cluster.GET /api/v3/projects/{project_id}/clusters/{cluster_id}/configuration/detailSta", "doc_type":"api2", "kw":"Obtaining the List of Parameters That Can Be Configured for a Cluster,Configuration Management,API R", @@ -1086,7 +1143,7 @@ "uri":"ShowNodePoolConfigurations.html", "node_id":"shownodepoolconfigurations.xml", "product_code":"cce", - "code":"61", + "code":"64", "des":"This API is used to obtain the parameters that can be configured for a node pool.GET /api/v3/projects/{project_id}/clusters/{cluster_id}/nodepools/{nodepool_id}/configura", "doc_type":"api2", "kw":"Obtaining the Parameters That Can Be Configured for a Node Pool,Configuration Management,API Referen", @@ -1104,7 +1161,7 @@ "uri":"UpdateNodePoolConfiguration.html", "node_id":"updatenodepoolconfiguration.xml", "product_code":"cce", - "code":"62", + "code":"65", "des":"This API is used to change the values of parameter configurations of a node pool in the CCE cluster.PUT /api/v3/projects/{project_id}/clusters/{cluster_id}/nodepools/{nod", "doc_type":"api2", "kw":"Changing the Values of Configuration Parameters of a Node Pool,Configuration Management,API Referenc", @@ -1122,7 +1179,7 @@ "uri":"tags_lifecycle_management.html", "node_id":"tags_lifecycle_management.xml", "product_code":"cce", - "code":"63", + "code":"66", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api2", "kw":"Tag Management", @@ -1140,7 +1197,7 @@ "uri":"BatchCreateClusterTags.html", "node_id":"batchcreateclustertags.xml", "product_code":"cce", - "code":"64", + "code":"67", "des":"This API is used to add resource tags for a specified cluster in batches.Each cluster supports a maximum of 20 resource tags.Each cluster supports a maximum of 20 resourc", "doc_type":"api2", "kw":"Adding Resource Tags to a Specified Cluster in Batches,Tag Management,API Reference", @@ -1158,7 +1215,7 @@ "uri":"BatchDeleteClusterTags.html", "node_id":"batchdeleteclustertags.xml", "product_code":"cce", - "code":"65", + "code":"68", "des":"This API is used to delete resource tags of a specified cluster in batches.This API is idempotent. If the tag key of the to-be-deleted tag does not exist, the tag will be", "doc_type":"api2", "kw":"Deleting Resource Tags of a Specified Cluster in Batches,Tag Management,API Reference", @@ -1176,7 +1233,7 @@ "uri":"GetResourceTags.html", "node_id":"getresourcetags.xml", "product_code":"cce", - "code":"66", + "code":"69", "des":"This API is used to obtain resource tags.GET /cce/v1/{project_id}/{resource_type}/{resource_id}/tagsStatus code: 200NoneStatus code: 200The resource tags have been obtain", "doc_type":"api2", "kw":"Obtaining Resource Tags,Tag Management,API Reference", @@ -1194,7 +1251,7 @@ "uri":"GetCustomizeTags.html", "node_id":"getcustomizetags.xml", "product_code":"cce", - "code":"67", + "code":"70", "des":"This API is used to obtain custom tags.GET /cce/v1/{project_id}/{resource_type}/tagsStatus code: 200NoneStatus code: 200The custom tags have been obtained.See Error Codes", "doc_type":"api2", "kw":"Obtaining Custom Tags,Tag Management,API Reference", @@ -1212,7 +1269,7 @@ "uri":"GetLabels.html", "node_id":"getlabels.xml", "product_code":"cce", - "code":"68", + "code":"71", "des":"This API is used to obtain the labels of all nodes in a cluster.GET /api/v3/projects/{project_id}/clusters/{cluster_id}/labelsStatus code: 200NoneStatus code: 200The node", "doc_type":"api2", "kw":"Obtaining Node Labels,Tag Management,API Reference", @@ -1230,7 +1287,7 @@ "uri":"cce_02_0366.html", "node_id":"cce_02_0366.xml", "product_code":"cce", - "code":"69", + "code":"72", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api2", "kw":"Add-on Instance Parameters", @@ -1248,7 +1305,7 @@ "uri":"cce_02_0407.html", "node_id":"cce_02_0407.xml", "product_code":"cce", - "code":"70", + "code":"73", "des":"CoreDNS is a DNS server that uses chain plug-ins to provide domain name resolution services for Kubernetes clusters. It is the recommended DNS server solution by the Kube", "doc_type":"api2", "kw":"CoreDNS,Add-on Instance Parameters,API Reference", @@ -1266,7 +1323,7 @@ "uri":"cce_02_0408.html", "node_id":"cce_02_0408.xml", "product_code":"cce", - "code":"71", + "code":"74", "des":"The CCE Container Storage (Everest) add-on uses the Container Storage Interface (CSI) to link Kubernetes clusters with cloud storage services.", "doc_type":"api2", "kw":"CCE Container Storage (Everest),Add-on Instance Parameters,API Reference", @@ -1284,7 +1341,7 @@ "uri":"cce_02_0409.html", "node_id":"cce_02_0409.xml", "product_code":"cce", - "code":"72", + "code":"75", "des":"CCE Node Problem Detector (node-problem-detector, NPD) is an add-on that monitors abnormal events of cluster nodes and connects to a third-party monitoring platform. It i", "doc_type":"api2", "kw":"CCE Node Problem Detector,Add-on Instance Parameters,API Reference", @@ -1302,7 +1359,7 @@ "uri":"cce_02_0411.html", "node_id":"cce_02_0411.xml", "product_code":"cce", - "code":"73", + "code":"76", "des":"The CCE Cluster Autoscaler (autoscaler) add-on enables node pools to be scaled in or out.", "doc_type":"api2", "kw":"CCE Cluster Autoscaler,Add-on Instance Parameters,API Reference", @@ -1320,7 +1377,7 @@ "uri":"cce_02_0412.html", "node_id":"cce_02_0412.xml", "product_code":"cce", - "code":"74", + "code":"77", "des":"The NGINX Ingress Controller add-on can automatically modify configurations when there are changes to pods in Services. This add-on uses Nginx's excellent stability, perf", "doc_type":"api2", "kw":"NGINX Ingress Controller,Add-on Instance Parameters,API Reference", @@ -1338,7 +1395,7 @@ "uri":"cce_02_0413.html", "node_id":"cce_02_0413.xml", "product_code":"cce", - "code":"75", + "code":"78", "des":"From version 1.8 onwards, Kubernetes provides resource usage metrics, such as the container CPU and memory usage, through the Metrics API. These metrics can be directly a", "doc_type":"api2", "kw":"Kubernetes Metrics Server,Add-on Instance Parameters,API Reference", @@ -1356,7 +1413,7 @@ "uri":"cce_02_0414.html", "node_id":"cce_02_0414.xml", "product_code":"cce", - "code":"76", + "code":"79", "des":"CCE Advanced HPA (cce-hpa-controller) is an in-house add-on, which can be used to flexibly scale in or out Deployments based on metrics such as CPU usage and memory usage", "doc_type":"api2", "kw":"CCE Advanced HPA,Add-on Instance Parameters,API Reference", @@ -1374,7 +1431,7 @@ "uri":"cce_02_0415.html", "node_id":"cce_02_0415.xml", "product_code":"cce", - "code":"77", + "code":"80", "des":"CCE AI Suite (NVIDIA GPU) is a device management add-on that supports GPUs in containers. To use GPU nodes in a cluster, this add-on must be installed.", "doc_type":"api2", "kw":"CCE AI Suite (NVIDIA GPU),Add-on Instance Parameters,API Reference", @@ -1392,7 +1449,7 @@ "uri":"cce_02_0417.html", "node_id":"cce_02_0417.xml", "product_code":"cce", - "code":"78", + "code":"81", "des":"Volcano is a batch scheduling platform based on Kubernetes. It provides a series of features required by machine learning, deep learning, bioinformatics, genomics, and ot", "doc_type":"api2", "kw":"Volcano Scheduler,Add-on Instance Parameters,API Reference", @@ -1410,7 +1467,7 @@ "uri":"cce_02_0421.html", "node_id":"cce_02_0421.xml", "product_code":"cce", - "code":"79", + "code":"82", "des":"The Cluster Native Cluster Monitoring add-on (kube-prometheus-stack) uses Prometheus-operator and Prometheus to provide easy-to-use, end-to-end Kubernetes cluster monitor", "doc_type":"api2", "kw":"Cloud Native Cluster Monitoring,Add-on Instance Parameters,API Reference", @@ -1428,7 +1485,7 @@ "uri":"cce_02_0422.html", "node_id":"cce_02_0422.xml", "product_code":"cce", - "code":"80", + "code":"83", "des":"The Cloud Native Logging add-on (log-agent) is developed based on Fluent Bit and OpenTelemetry for collecting logs and Kubernetes events. This add-on supports CRD-based l", "doc_type":"api2", "kw":"Cloud Native Log Collection,Add-on Instance Parameters,API Reference", @@ -1442,11 +1499,85 @@ "title":"Cloud Native Log Collection", "githuburl":"" }, + { + "uri":"job_lifecycle_management.html", + "node_id":"job_lifecycle_management.xml", + "product_code":"cce", + "code":"84", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"api2", + "kw":"Job Management", + "search_title":"", + "metedata":[ + { + "documenttype":"api2" + } + ], + "title":"Job Management", + "githuburl":"" + }, + { + "uri":"ListJobs.html", + "node_id":"listjobs.xml", + "product_code":"cce", + "code":"85", + "des":"This API is used to obtain all jobs in a specified project.GET /api/v2/projects/{project_id}/jobsStatus code: 200NoneStatus code: 200See Error Codes.", + "doc_type":"api2", + "kw":"Obtaining the Job List,Job Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api2", + "operation_id":"ListJobs" + } + ], + "title":"Obtaining the Job List", + "githuburl":"" + }, + { + "uri":"GetOneJob.html", + "node_id":"getonejob.xml", + "product_code":"cce", + "code":"86", + "des":"This API is used to obtain the details of a job in a specified project.GET /api/v2/projects/{project_id}/jobs/{job_id}Status code: 200NoneStatus code: 200See Error Codes.", + "doc_type":"api2", + "kw":"Obtaining Job Details,Job Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api2", + "operation_id":"GetOneJob" + } + ], + "title":"Obtaining Job Details", + "githuburl":"" + }, + { + "uri":"DeleteJob.html", + "node_id":"deletejob.xml", + "product_code":"cce", + "code":"87", + "des":"This API is used to delete a job in a specified project.DELETE /api/v2/projects/{project_id}/jobs/{job_id}Status code: 204The job has been deleted.NoneNoneNoneSee Error C", + "doc_type":"api2", + "kw":"Deleting a Job,Job Management,API Reference", + "search_title":"", + "metedata":[ + { + "opensource":"true", + "documenttype":"api2", + "operation_id":"DeleteJob" + } + ], + "title":"Deleting a Job", + "githuburl":"" + }, { "uri":"cce_02_0340.html", "node_id":"cce_02_0340.xml", "product_code":"cce", - "code":"81", + "code":"88", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api2", "kw":"Kubernetes APIs", @@ -1464,7 +1595,7 @@ "uri":"kubernetesapi.html", "node_id":"kubernetesapi.xml", "product_code":"cce", - "code":"82", + "code":"89", "des":"Kubernetes APIs are resource-based (RESTful) programming interfaces provided through HTTP. It supports query, creation, update, and deletion of various cluster resources ", "doc_type":"api2", "kw":"Overview,Kubernetes APIs,API Reference", @@ -1482,7 +1613,7 @@ "uri":"cce_02_0327.html", "node_id":"cce_02_0327.xml", "product_code":"cce", - "code":"83", + "code":"90", "des":"This chapter describes fine-grained permissions management for your CCE. If your cloud account does not need individual IAM users, then you may skip over this chapter.A p", "doc_type":"api2", "kw":"Permissions Policies and Supported Actions,API Reference", @@ -1500,7 +1631,7 @@ "uri":"cce_02_0083.html", "node_id":"cce_02_0083.xml", "product_code":"cce", - "code":"84", + "code":"91", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api2", "kw":"Appendix", @@ -1518,7 +1649,7 @@ "uri":"cce_02_0085.html", "node_id":"cce_02_0085.xml", "product_code":"cce", - "code":"85", + "code":"92", "des":"Kubernetes APIs use the HTTP header \"Content-Type\" to distinguish between patch request method operations.Currently, three types of patch request method operations are su", "doc_type":"api2", "kw":"Patch Request Method Operation Description,Appendix,API Reference", @@ -1536,7 +1667,7 @@ "uri":"cce_02_0086.html", "node_id":"cce_02_0086.xml", "product_code":"cce", - "code":"86", + "code":"93", "des":"This section provides examples of Merge Patch and Strategic Merge Patch method operations.By way of example, Merge Patch and Strategic Merge Patch method operations are p", "doc_type":"api2", "kw":"Patch Request Method Operation Example,Appendix,API Reference", @@ -1554,7 +1685,7 @@ "uri":"cce_02_0084.html", "node_id":"cce_02_0084.xml", "product_code":"cce", - "code":"87", + "code":"94", "des":"Table 1 describes the status codes.", "doc_type":"api2", "kw":"Status Code,Appendix,API Reference", @@ -1572,7 +1703,7 @@ "uri":"cce_02_0250.html", "node_id":"cce_02_0250.xml", "product_code":"cce", - "code":"88", + "code":"95", "des":"If an error occurs in API calling, no result is returned. Identify the cause based on the error code of each API. If an error occurs in API calling, HTTP status code 4xx ", "doc_type":"api2", "kw":"Error Codes,Appendix,API Reference", @@ -1590,7 +1721,7 @@ "uri":"cce_02_0341.html", "node_id":"cce_02_0341.xml", "product_code":"cce", - "code":"89", + "code":"96", "des":"You can obtain the project ID by calling the API used to query project information based on the specified criteria.The API used to obtain a project ID is GET https://{End", "doc_type":"api2", "kw":"Obtaining a Project ID,Appendix,API Reference", @@ -1608,7 +1739,7 @@ "uri":"cce_02_0342.html", "node_id":"cce_02_0342.xml", "product_code":"cce", - "code":"90", + "code":"97", "des":"An account ID is required for some URLs when an API is called. To obtain an account ID, perform the following operations:On the My Credentials page, view account IDs in t", "doc_type":"api2", "kw":"Obtaining the Account ID,Appendix,API Reference", @@ -1626,7 +1757,7 @@ "uri":"cce_02_0271.html", "node_id":"cce_02_0271.xml", "product_code":"cce", - "code":"91", + "code":"98", "des":"If you are using Google Chrome, press F12. On the pane displayed on the right, click the Network tab. Enter jobs in the Filter text box to filter the job list. Select a j", "doc_type":"api2", "kw":"How to Obtain Parameters in the API URI,Appendix,API Reference", @@ -1644,7 +1775,7 @@ "uri":"cce_02_0272.html", "node_id":"cce_02_0272.xml", "product_code":"cce", - "code":"92", + "code":"99", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api2", "kw":"API Permissions,Appendix,API Reference", @@ -1662,7 +1793,7 @@ "uri":"cce_02_0100.html", "node_id":"cce_02_0100.xml", "product_code":"cce", - "code":"93", + "code":"100", "des":"To provide a secure and isolated network environment for CCE, create a VPC before creating a cluster.If you have already created a VPC, you do not need to create it again", "doc_type":"api2", "kw":"Creating a VPC and Subnet,Appendix,API Reference", @@ -1680,7 +1811,7 @@ "uri":"cce_02_0101.html", "node_id":"cce_02_0101.xml", "product_code":"cce", - "code":"94", + "code":"101", "des":"Create a key pair before you create a container cluster. Key pairs are used for user identity authentication upon login to a node.If you have already created a key pair, ", "doc_type":"api2", "kw":"Creating a Key Pair,Appendix,API Reference", @@ -1698,7 +1829,7 @@ "uri":"cce_02_0368.html", "node_id":"cce_02_0368.xml", "product_code":"cce", - "code":"95", + "code":"102", "des":"Different regions support different node flavors, and node flavors may be changed. You are advised to log in to the CCE console and check whether the required node flavor", "doc_type":"api2", "kw":"Node Flavor Description,Appendix,API Reference", @@ -1716,7 +1847,7 @@ "uri":"node_storage_example.html", "node_id":"node_storage_example.xml", "product_code":"cce", - "code":"96", + "code":"103", "des":"In disk planning and striped logical disk creation, it is difficult for users to flexibly attach and partition disks when creating a node.During node creation, the storag", "doc_type":"api2", "kw":"Attaching Disks to a Node,Appendix,API Reference", @@ -1730,11 +1861,29 @@ "title":"Attaching Disks to a Node", "githuburl":"" }, + { + "uri":"cce_10_0341.html", + "node_id":"cce_10_0341.xml", + "product_code":"cce", + "code":"104", + "des":"This section describes how to allocate data disk space to nodes so that you can configure the data disk space accordingly.In clusters of a version earlier than v1.23.18-r", + "doc_type":"api2", + "kw":"Data Disk Space Allocation,Container engine and container image space,container engine and container", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"api2" + } + ], + "title":"Space Allocation of a Data Disk", + "githuburl":"" + }, { "uri":"cce_02_0273.html", "node_id":"cce_02_0273.xml", "product_code":"cce", - "code":"97", + "code":"105", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"api2", "kw":"Change History,API Reference", diff --git a/docs/cce/api-ref/AddNode.html b/docs/cce/api-ref/AddNode.html index ae5b71957..d5d935913 100644 --- a/docs/cce/api-ref/AddNode.html +++ b/docs/cce/api-ref/AddNode.html @@ -730,15 +730,26 @@ -
dockerBaseSize
+containerBaseSize
No
+No
Integer
+Integer
Available disk space of a single container on a node, in GB.
-If this parameter is left blank or is set to 0, the default value is used. In Device Mapper mode, the default value is 10. In OverlayFS mode, the available space of a single container is not limited by default, and the dockerBaseSize setting takes effect only on EulerOS nodes in the cluster of the new version.
-When Device Mapper is used, you are advised to set dockerBaseSize to a value less than or equal to 80 GB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device.
+Definition
+Available disk space of a single container on a node (unit: G).
+This parameter cannot be updated when a node pool is being updated.
+If this parameter is not specified or is set to 0, the default value is used. In OverlayFS mode, no fixed limit is imposed on the available space of a single container. In Device Mapper mode, the default value is 10, and the containerBaseSize setting takes effect only on nodes running EulerOS in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later.
+For details about how to allocate the space for the container runtime, see Data Disk Space Allocation.
+When Device Mapper is used, it is recommended that containerBaseSize be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to time-consuming initialization. If there are special requirements for the container disk space, you can mount external or local storage. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being discarded.
+This parameter cannot be updated when a node pool is being updated.
+Constraints
+Range
+N/A
+Default Value
+N/A
runtime
diff --git a/docs/cce/api-ref/BatchCreateAddonPrecheck.html b/docs/cce/api-ref/BatchCreateAddonPrecheck.html new file mode 100644 index 000000000..4be7f3a5a --- /dev/null +++ b/docs/cce/api-ref/BatchCreateAddonPrecheck.html @@ -0,0 +1,862 @@ + + +This API is used to create add-on check tasks in batches in a specified cluster.
+POST /api/v3/projects/{project_id}/clusters/{cluster_id}/addons/precheck
+ +Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
project_id + |
+Yes + |
+String + |
+Details: +Project ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI. +Constraints: +None +Options: +Project IDs of the account +Default value: +N/A + |
+
cluster_id + |
+Yes + |
+String + |
+Details: +Cluster ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI. +Constraints: +None +Options: +Cluster IDs +Default value: +N/A + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
Content-Type + |
+Yes + |
+String + |
+Details: +The request body type or format +Constraints: +The GET method is not verified. +Options: + +Default value: +N/A + |
+
X-Auth-Token + |
+Yes + |
+String + |
+Details: +Requests for calling an API can be authenticated using either a token or AK/SK. If token-based authentication is used, this parameter is mandatory and must be set to a user token. For details, see Obtaining a User Token. +Constraints: +None +Options: +N/A +Default value: +N/A + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
kind + |
+Yes + |
+String + |
+Definition +API type. +Constraints +The value cannot be changed. +Range +The value is fixed at AddonCheck. +Default Value +AddonCheck + |
+
apiVersion + |
+Yes + |
+String + |
+Definition +API version. +Constraints +The value cannot be changed. +Range +The value is fixed at v3. +Default Value +v3 + |
+
spec + |
+Yes + |
+AddonCheckSpec object + |
+Definition +Details of an add-on check. +Constraints +N/A + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
clusterID + |
+Yes + |
+String + |
+Definition +Cluster ID. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
addonList + |
+Yes + |
+Array of AddonInfo objects + |
+Definition +Add-on check information list, including the name of the add-on template to be checked, add-on instance ID, and add-on upgrade configuration. +Constraints +N/A + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
addonTemplateName + |
+Yes + |
+String + |
+Definition +Add-on template name. +Constraints +N/A +Range +Add-on template supported by CCE. +Default Value +N/A + |
+
addonInstanceID + |
+Yes + |
+String + |
+Definition +Add-on instance ID, which can be obtained from the items[].metadata.uid field in Listing Add-on Instances. +Constraints +This parameter is mandatory. +Range +N/A +Default Value +N/A + |
+
targetVersion + |
+No + |
+String + |
+Definition +Target version of an add-on upgrade. +Constraints +This parameter is mandatory in the add-on upgrade scenario. +Range +Add-on version provided by CCE. You can obtain the value from the items[].spec.versions.version field in Listing Add-on Templates. +Default Value +N/A + |
+
type + |
+Yes + |
+String + |
+Definition +Add-on check type. +Constraints +This parameter is mandatory. +Range +
Default Value +N/A + |
+
values + |
+No + |
+Map<String,Object> + |
+Definition +Add-on template edit or upgrade parameters (which vary depending on add-ons). Set the parameters accordingly. +Constraints +N/A + |
+
Status code: 201
+ +Parameter + |
+Type + |
+Description + |
+
|---|---|---|
kind + |
+String + |
+Definition +API type. +Constraints +The value cannot be changed. +Range +The value is fixed at AddonCheck. +Default Value +AddonCheck + |
+
apiVersion + |
+String + |
+Definition +API version. +Constraints +The value cannot be changed. +Range +The value is fixed at v3. +Default Value +v3 + |
+
spec + |
+AddonCheckSpec object + |
+Definition +Details of an add-on check. +Constraints +N/A + |
+
status + |
+AddonCheckStatus object + |
+Definition +Results of creating an add-on check task, including the task ID for querying the add-on check result. +Constraints +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
clusterID + |
+String + |
+Definition +Cluster ID. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
addonList + |
+Array of AddonInfo objects + |
+Definition +Add-on check information list, including the name of the add-on template to be checked, add-on instance ID, and add-on upgrade configuration. +Constraints +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
addonTemplateName + |
+String + |
+Definition +Add-on template name. +Constraints +N/A +Range +Add-on template supported by CCE. +Default Value +N/A + |
+
addonInstanceID + |
+String + |
+Definition +Add-on instance ID, which can be obtained from the items[].metadata.uid field in Listing Add-on Instances. +Constraints +This parameter is mandatory. +Range +N/A +Default Value +N/A + |
+
targetVersion + |
+String + |
+Definition +Target version of an add-on upgrade. +Constraints +This parameter is mandatory in the add-on upgrade scenario. +Range +Add-on version provided by CCE. You can obtain the value from the items[].spec.versions.version field in Listing Add-on Templates. +Default Value +N/A + |
+
type + |
+String + |
+Definition +Add-on check type. +Constraints +This parameter is mandatory. +Range +
Default Value +N/A + |
+
values + |
+Map<String,Object> + |
+Definition +Add-on template edit or upgrade parameters (which vary depending on add-ons). Set the parameters accordingly. +Constraints +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
items + |
+Array of AddonCheckTask objects + |
+Definition +Add-on check task list, including the add-on check task ID, add-on template name, and add-on instance ID. +Constraints +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
metadata + |
+CheckTaskMetadata object + |
+Definition +Basic information. Metadata is a collection of attributes. +Constraints +N/A + |
+
spec + |
+CheckTaskSpec object + |
+Definition +Target information of an add-on check, including the target version of an add-on upgrade. +Constraints +N/A + |
+
status + |
+CheckTaskStatus object + |
+Definition +Add-on check task status. +Constraints +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
type + |
+String + |
+Definition +Add-on check type. +Range + + |
+
taskID + |
+String + |
+Definition +Add-on check task ID, which is used to query the task check result. +Range +N/A + |
+
addonTemplateName + |
+String + |
+Definition +Add-on template name. +Range +Add-on template provided by CCE. You can obtain the value from the items[].metadata.name field in Listing Add-on Templates. + |
+
addonInstanceName + |
+String + |
+Definition +Add-on instance name. +Range +N/A + |
+
addonInstanceID + |
+String + |
+Definition +Add-on instance ID. +Range +N/A + |
+
createTimeStamp + |
+String + |
+Definition +Creation time of an add-on check task. +Range +N/A + |
+
expireTimeStamp + |
+String + |
+Definition +Timeout duration of an add-on check task. This field is available only for tasks in the Failed or Success state. +Range +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
addonTargetVersion + |
+String + |
+Definition +Target version of an add-on upgrade. +Range +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
status + |
+String + |
+Definition +Status of an add-on check. +Range + + |
+
message + |
+String + |
+Definition +Add-on check results. +Range +N/A + |
+
riskList + |
+Array of CheckTaskRisk objects + |
+Definition +List of risk items during an add-on check. The risk items vary according to add-ons. +Constraints +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
riskName + |
+String + |
+Definition +Risk item name. +Range +N/A + |
+
level + |
+String + |
+Definition +Risk level. +Range + + |
+
status + |
+String + |
+Definition +Risk item check status. +Range + + |
+
message + |
+String + |
+Definition +Risk check result description. +Range +N/A + |
+
Create a CoreDNS add-on check task and set the check type to add-on inspection.
+POST /api/v3/projects/{project_id}/clusters/{cluster_id}/addons/precheck
+
+{
+ "kind" : "AddonCheck",
+ "apiVersion" : "v3",
+ "spec" : {
+ "clusterID" : "6b400e1c-4368-11f0-ba56-0255ac100037",
+ "addonList" : [ {
+ "addonTemplateName" : "coredns",
+ "addonInstanceID" : "8fcaa506-809d-4f33-91b3-b27efcbeb540",
+ "type" : "addonStatic"
+ } ]
+ }
+}
+Status code: 201
+The add-on check tasks have been created in batches in the cluster.
+{
+ "kind" : "AddonCheck",
+ "apiVersion" : "v3",
+ "spec" : {
+ "clusterID" : "6b400e1c-4368-11f0-ba56-0255ac100037",
+ "addonList" : [ {
+ "addonTemplateName" : "coredns",
+ "addonInstanceID" : "8fcaa506-809d-4f33-91b3-b27efcbeb540",
+ "type" : "addonUpgrade",
+ "values" : {
+ "basic" : {
+ "cluster_ip" : "10.247.3.10",
+ "image_version" : "1.17.15",
+ "platform" : "linux-amd64",
+ "rbac_enabled" : true,
+ "swr_addr" : "",
+ "swr_user" : "hwofficial"
+ },
+ "custom" : {
+ "cluster_id" : "8fcaa506-809d-4f33-91b3-b27efcbeb540",
+ "stub_domains" : { },
+ "tenant_id" : "0504201b6c80256b2f08c0099f0c8fe4",
+ "upstream_nameservers" : [ ]
+ },
+ "flavor" : {
+ "name" : 2500,
+ "replicas" : 2,
+ "resources" : [ {
+ "limitsCpu" : "500m",
+ "limitsMem" : "512Mi",
+ "name" : "coredns",
+ "requestsCpu" : "500m",
+ "requestsMem" : "512Mi"
+ } ]
+ }
+ }
+ } ]
+ },
+ "status" : {
+ "items" : [ {
+ "metadata" : {
+ "type" : "addonUpgrade",
+ "taskID" : "22386048-d955-4409-bc71-20cc2b774245",
+ "addonTemplateName" : "coredns",
+ "addonInstanceName" : "cceaddon-coredns",
+ "addonInstanceID" : "8fcaa506-809d-4f33-91b3-b27efcbeb540",
+ "createTimeStamp" : "2025-08-13T11:24:37.312017086+08:00"
+ },
+ "spec" : {
+ "addonTargetVersion" : "1.27.1"
+ },
+ "status" : {
+ "status" : "Init",
+ "riskList" : [ {
+ "riskName" : "K8sResourceModified",
+ "status" : "Init",
+ "level" : "Warning"
+ }, {
+ "riskName" : "AddonValidate",
+ "status" : "Init",
+ "level" : "Warning"
+ }, {
+ "riskName" : "AddonStatus",
+ "status" : "Init",
+ "level" : "Warning"
+ } ]
+ }
+ } ]
+ }
+}
+Status Code + |
+Description + |
+
|---|---|
201 + |
+The add-on check tasks have been created in batches in the cluster. + |
+
See Error Codes.
+This API is used to delete a job in a specified project.
+DELETE /api/v2/projects/{project_id}/jobs/{job_id}
+ +Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
project_id + |
+Yes + |
+String + |
+Details: +Project ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI. +Constraints: +None +Options: +Project IDs of the account +Default value: +N/A + |
+
job_id + |
+Yes + |
+String + |
+Definition +Job ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
Content-Type + |
+Yes + |
+String + |
+Details: +The request body type or format +Constraints: +The GET method is not verified. +Options: + +Default value: +N/A + |
+
X-Auth-Token + |
+Yes + |
+String + |
+Details: +Requests for calling an API can be authenticated using either a token or AK/SK. If token-based authentication is used, this parameter is mandatory and must be set to a user token. For details, see Obtaining a User Token. +Constraints: +None +Options: +N/A +Default value: +N/A + |
+
Status code: 204
+The job has been deleted.
+None
+None
+None
+Status Code + |
+Description + |
+
|---|---|
204 + |
+The job has been deleted. + |
+
See Error Codes.
+This API is used to obtain the details of a job in a specified project.
+GET /api/v2/projects/{project_id}/jobs/{job_id}
+ +Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
project_id + |
+Yes + |
+String + |
+Details: +Project ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI. +Constraints: +None +Options: +Project IDs of the account +Default value: +N/A + |
+
job_id + |
+Yes + |
+String + |
+Definition +Job ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
Content-Type + |
+Yes + |
+String + |
+Details: +The request body type or format +Constraints: +The GET method is not verified. +Options: + +Default value: +N/A + |
+
X-Auth-Token + |
+Yes + |
+String + |
+Details: +Requests for calling an API can be authenticated using either a token or AK/SK. If token-based authentication is used, this parameter is mandatory and must be set to a user token. For details, see Obtaining a User Token. +Constraints: +None +Options: +N/A +Default value: +N/A + |
+
Status code: 200
+ +Parameter + |
+Type + |
+Description + |
+
|---|---|---|
kind + |
+String + |
+Definition +API type. +Constraints +N/A +Range +N/A +Default Value +Job + |
+
apiVersion + |
+String + |
+Definition +API version. +Constraints +N/A +Range +N/A +Default Value +v2 + |
+
metadata + |
+V2JobTypeObject object + |
+Definition +Job metadata. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
spec + |
+V2JobSpec object + |
+Definition +Job details. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
status + |
+V2JobStatus object + |
+Definition +Job status. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
type + |
+String + |
+Definition +Job type. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
clusteruid + |
+String + |
+Definition +Cluster ID. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
resourceid + |
+String + |
+Definition +Resource ID. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
resourcename + |
+String + |
+Definition +Resource name. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
extendparam + |
+Map<String,String> + |
+Definition +Job scale-out parameters. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
subjobs + |
+Array of V2Job objects + |
+Definition +Subjob details list. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
kind + |
+String + |
+Definition +API type. +Constraints +N/A +Range +N/A +Default Value +Job + |
+
apiVersion + |
+String + |
+Definition +API version. +Constraints +N/A +Range +N/A +Default Value +v2 + |
+
metadata + |
+V2JobTypeObject object + |
+Definition +Job metadata. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
spec + |
+V2JobSpec object + |
+Definition +Job details. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
status + |
+V2JobStatus object + |
+Definition +Job status. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
uid + |
+String + |
+Definition +Job UUID. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
creationTimestamp + |
+String + |
+Definition +Job creation time. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
updateTimestamp + |
+String + |
+Definition +Last update time of a job. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
status + |
+String + |
+Definition +Job status. +Constraints +N/A +Range +
Default Value +N/A + |
+
reason + |
+String + |
+Definition +Cause of a job execution failure. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
completionTime + |
+String + |
+Definition +Job completion time. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
None
+Status code: 200
+{
+ "kind" : "Job",
+ "apiVersion" : "v2",
+ "metadata" : {
+ "uid" : "e43c6f3b-87e6-11f0-be88-0255ac10003f",
+ "creationTimestamp" : "2025-09-02 10:23:38.987955 +0000 UTC",
+ "updateTimestamp" : "2025-09-02 11:26:03.218087 +0000 UTC"
+ },
+ "spec" : {
+ "type" : "ScaleupCluster",
+ "clusteruid" : "7ec8b73d-83db-11f0-8baa-0255ac10003e",
+ "resourceid" : "3b4410fa-87e6-11f0-be88-0255ac10003f",
+ "resourcename" : "node-iv28j9",
+ "extendparam" : {
+ "claimrollback" : "true",
+ "node.zone" : "",
+ "nodepooluid" : "",
+ "orderID" : "CS25090218238EI5V",
+ "v3-scaleup" : "true"
+ }
+ },
+ "status" : {
+ "status" : "Failed",
+ "reason" : "Something bad happened at server, recycle resource",
+ "completionTime" : "2025-09-02 11:26:03.218087 +0000 UTC"
+ }
+}
+Status Code + |
+Description + |
+
|---|---|
200 + |
+Successfully obtained job details. + |
+
See Error Codes.
+This API is used to obtain the results of the add-on check tasks in a cluster.
+GET /api/v3/projects/{project_id}/clusters/{cluster_id}/addons/precheck/tasks
+ +Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
project_id + |
+Yes + |
+String + |
+Details: +Project ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI. +Constraints: +None +Options: +Project IDs of the account +Default value: +N/A + |
+
cluster_id + |
+Yes + |
+String + |
+Details: +Cluster ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI. +Constraints: +None +Options: +Cluster IDs +Default value: +N/A + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
type + |
+No + |
+String + |
+Definition +Add-on check type-based result selection +Constraints +N/A +Range +
Default Value +N/A + |
+
task_id + |
+No + |
+String + |
+Definition +Add-on check task ID-based result selection. The ID can be obtained from the status.items[].metadata.taskID field in Creating Add-on Check Tasks in Batches. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
addon_instance_id + |
+No + |
+String + |
+Definition +Add-on instance ID-based result selection. The ID can be obtained from the items[].metadata.uid field in Listing Add-on Instances. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
Content-Type + |
+Yes + |
+String + |
+Details: +The request body type or format +Constraints: +The GET method is not verified. +Options: + +Default value: +N/A + |
+
X-Auth-Token + |
+Yes + |
+String + |
+Details: +Requests for calling an API can be authenticated using either a token or AK/SK. If token-based authentication is used, this parameter is mandatory and must be set to a user token. For details, see Obtaining a User Token. +Constraints: +None +Options: +N/A +Default value: +N/A + |
+
Status code: 200
+ +Parameter + |
+Type + |
+Description + |
+
|---|---|---|
kind + |
+String + |
+Definition +API type. +Range +The value is fixed at AddonCheck. + |
+
apiVersion + |
+String + |
+Definition +API version. +Range +The value is fixed at v3. + |
+
pageInfo + |
+PageInfo object + |
+Definition +Pagination information of the add-on check task list. +Constraints +N/A + |
+
items + |
+Array of AddonCheckTask objects + |
+Definition +Add-on check task list, including the add-on check task ID, add-on template name, and add-on instance ID. +Constraints +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
currentCount + |
+Integer + |
+Definition +Total number of all add-on check tasks. +Range +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
metadata + |
+CheckTaskMetadata object + |
+Definition +Basic information. Metadata is a collection of attributes. +Constraints +N/A + |
+
spec + |
+CheckTaskSpec object + |
+Definition +Target information of an add-on check, including the target version of an add-on upgrade. +Constraints +N/A + |
+
status + |
+CheckTaskStatus object + |
+Definition +Add-on check task status. +Constraints +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
type + |
+String + |
+Definition +Add-on check type. +Range + + |
+
taskID + |
+String + |
+Definition +Add-on check task ID, which is used to query the task check result. +Range +N/A + |
+
addonTemplateName + |
+String + |
+Definition +Add-on template name. +Range +Add-on template provided by CCE. You can obtain the value from the items[].metadata.name field in Listing Add-on Templates. + |
+
addonInstanceName + |
+String + |
+Definition +Add-on instance name. +Range +N/A + |
+
addonInstanceID + |
+String + |
+Definition +Add-on instance ID. +Range +N/A + |
+
createTimeStamp + |
+String + |
+Definition +Creation time of an add-on check task. +Range +N/A + |
+
expireTimeStamp + |
+String + |
+Definition +Timeout duration of an add-on check task. This field is available only for tasks in the Failed or Success state. +Range +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
addonTargetVersion + |
+String + |
+Definition +Target version of an add-on upgrade. +Range +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
status + |
+String + |
+Definition +Status of an add-on check. +Range + + |
+
message + |
+String + |
+Definition +Add-on check results. +Range +N/A + |
+
riskList + |
+Array of CheckTaskRisk objects + |
+Definition +List of risk items during an add-on check. The risk items vary according to add-ons. +Constraints +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
riskName + |
+String + |
+Definition +Risk item name. +Range +N/A + |
+
level + |
+String + |
+Definition +Risk level. +Range + + |
+
status + |
+String + |
+Definition +Risk item check status. +Range + + |
+
message + |
+String + |
+Definition +Risk check result description. +Range +N/A + |
+
None
+Status code: 200
+ok
+{
+ "kind" : "AddonCheck",
+ "apiVersion" : "v3",
+ "pageInfo" : {
+ "currentCount" : 1
+ },
+ "items" : {
+ "metadata" : {
+ "type" : "addonUpgrade",
+ "taskID" : "8ca259cc-553b-11e9-926f-0255ac101a31",
+ "addonTemplateName" : "coredns",
+ "addonInstanceName" : "cceaddon-coredns",
+ "addonInstanceID" : "1d43577d-4b50-4723-b05b-2121f47cb219",
+ "createTimestamp" : "2025-08-05T17:10:44.648388+08:00"
+ },
+ "spec" : {
+ "addonTargetVersion" : "3.0.4"
+ },
+ "status" : {
+ "status" : "Failed",
+ "message" : "Addon task check finish"
+ },
+ "riskList" : [ {
+ "riskName" : "AddonStatus",
+ "status" : "Failed",
+ "level" : "Warning",
+ "message" : "addon status(abnormal) is not running"
+ }, {
+ "riskName" : "AddonValidate",
+ "status" : "Failed",
+ "level" : "Fatal",
+ "message" : "configmap coredns had been modified, failed to ensure the consistency of corefile between current and recorded, the manually modified configuration by user may be lost if upgrade continue: 1. rollback current corefile; 2. set parameterSyncStrategy to force to force take over; 3. set parameterSyncStrategy to inherit to auto inherit your configuration; "
+ } ]
+ }
+}
+Status Code + |
+Description + |
+
|---|---|
200 + |
+ok + |
+
See Error Codes.
+This API is used to obtain all jobs in a specified project.
+GET /api/v2/projects/{project_id}/jobs
+ +Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
project_id + |
+Yes + |
+String + |
+Details: +Project ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI. +Constraints: +None +Options: +Project IDs of the account +Default value: +N/A + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
Content-Type + |
+Yes + |
+String + |
+Details: +The request body type or format +Constraints: +The GET method is not verified. +Options: + +Default value: +N/A + |
+
X-Auth-Token + |
+Yes + |
+String + |
+Details: +Requests for calling an API can be authenticated using either a token or AK/SK. If token-based authentication is used, this parameter is mandatory and must be set to a user token. For details, see Obtaining a User Token. +Constraints: +None +Options: +N/A +Default value: +N/A + |
+
Status code: 200
+ +Parameter + |
+Type + |
+Description + |
+
|---|---|---|
[items] + |
+Array of V2Job objects + |
+Definition +Job details list. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
kind + |
+String + |
+Definition +API type. +Constraints +N/A +Range +N/A +Default Value +Job + |
+
apiVersion + |
+String + |
+Definition +API version. +Constraints +N/A +Range +N/A +Default Value +v2 + |
+
metadata + |
+V2JobTypeObject object + |
+Definition +Job metadata. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
spec + |
+V2JobSpec object + |
+Definition +Job details. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
status + |
+V2JobStatus object + |
+Definition +Job status. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
uid + |
+String + |
+Definition +Job UUID. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
creationTimestamp + |
+String + |
+Definition +Job creation time. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
updateTimestamp + |
+String + |
+Definition +Last update time of a job. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
type + |
+String + |
+Definition +Job type. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
clusteruid + |
+String + |
+Definition +Cluster ID. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
resourceid + |
+String + |
+Definition +Resource ID. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
resourcename + |
+String + |
+Definition +Resource name. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
extendparam + |
+Map<String,String> + |
+Definition +Job scale-out parameters. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
subjobs + |
+Array of V2Job objects + |
+Definition +Subjob details list. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
status + |
+String + |
+Definition +Job status. +Constraints +N/A +Range +
Default Value +N/A + |
+
reason + |
+String + |
+Definition +Cause of a job execution failure. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
completionTime + |
+String + |
+Definition +Job completion time. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
None
+Status code: 200
+[ {
+ "kind" : "Job",
+ "apiVersion" : "v2",
+ "metadata" : {
+ "uid" : "e43c6f3b-87e6-11f0-be88-0255ac10003f",
+ "creationTimestamp" : "2025-09-02 10:23:38.987955 +0000 UTC",
+ "updateTimestamp" : "2025-09-02 11:26:03.218087 +0000 UTC"
+ },
+ "spec" : {
+ "type" : "ScaleupCluster",
+ "clusteruid" : "7ec8b73d-83db-11f0-8baa-0255ac10003e",
+ "resourceid" : "3b4410fa-87e6-11f0-be88-0255ac10003f",
+ "resourcename" : "node-iv28j9",
+ "extendparam" : {
+ "claimrollback" : "true",
+ "node.zone" : "",
+ "nodepooluid" : "",
+ "orderID" : "CS25090218238EI5V",
+ "v3-scaleup" : "true"
+ }
+ },
+ "status" : {
+ "status" : "Failed",
+ "reason" : "Something bad happened at server, recycle resource",
+ "completionTime" : "2025-09-02 11:26:03.218087 +0000 UTC"
+ }
+} ]
+Status Code + |
+Description + |
+
|---|---|
200 + |
+Definition +Job details list. +Constraints +N/A +Range +N/A +Default Value +N/A + |
+
See Error Codes.
+dockerBaseSize
+containerBaseSize
No
+No
Integer
+Integer
Available disk space of a single container on a node, in GB.
-If this parameter is left blank or is set to 0, the default value is used. In Device Mapper mode, the default value is 10. In OverlayFS mode, the available space of a single container is not limited by default, and the dockerBaseSize setting takes effect only on EulerOS nodes in the cluster of the new version.
-When Device Mapper is used, you are advised to set dockerBaseSize to a value less than or equal to 80 GB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device.
+Definition
+Available disk space of a single container on a node (unit: G).
+This parameter cannot be updated when a node pool is being updated.
+If this parameter is not specified or is set to 0, the default value is used. In OverlayFS mode, no fixed limit is imposed on the available space of a single container. In Device Mapper mode, the default value is 10, and the containerBaseSize setting takes effect only on nodes running EulerOS in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later.
+For details about how to allocate the space for the container runtime, see Data Disk Space Allocation.
+When Device Mapper is used, it is recommended that containerBaseSize be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to time-consuming initialization. If there are special requirements for the container disk space, you can mount external or local storage. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being discarded.
+This parameter cannot be updated when a node pool is being updated.
+Constraints
+Range
+N/A
+Default Value
+N/A
runtime
diff --git a/docs/cce/api-ref/cce_02_0083.html b/docs/cce/api-ref/cce_02_0083.html index 488b0c0d1..435771284 100644 --- a/docs/cce/api-ref/cce_02_0083.html +++ b/docs/cce/api-ref/cce_02_0083.html @@ -28,6 +28,8 @@Example response:
- "kind": "Cluster",
- "apiVersion": "v3",
- "metadata": {
- "name": "test-create-cluster",
- "uid": "d6a883a1-8529-11ea-8e34-0255ac101108",
- "creationTimestamp": "2020-04-23 06:15:32.974281119 +0000 UTC",
- "updateTimestamp": "2020-04-23 06:15:32.974281688 +0000 UTC",
- "labels": {
- "foo": "bar"
- },
- "annotations": {
- "foo2": "bar2"
- }
- "timezone" : "******"
+Example Responses
Status code: 201
+The cluster creation job is successfully delivered.
+{
+ "kind" : "Cluster",
+ "apiVersion" : "v3",
+ "metadata" : {
+ "name" : "cluster",
+ "uid" : "1df09f9a-5b9e-11ef-8f52-0255ac10003e",
+ "creationTimestamp" : "2024-08-16 07:06:53.704389459 +0000 UTC",
+ "updateTimestamp" : "2024-08-16 07:06:53.704389529 +0000 UTC",
+ "annotations" : {
+ "jobid" : "1e50bfbe-5b9e-11ef-8f52-0255ac10003e",
+ "resourceJobId" : "1df0ec6b-5b9e-11ef-8f52-0255ac10003e"
},
- "spec": {
- "type": "VirtualMachine",
- "flavor": "cce.s2.small",
- "version": "v1.17.9-r0",
- "description": "this is a demo cluster",
- "ipv6enable": false,
- "hostNetwork": {
- "vpc": "23d3725f-6ffe-400e-8fb6-b4f9a7b3e8c1",
- "subnet": "c90b3ce5-e1f1-4c87-a006-644d78846438"
- },
- "containerNetwork": {
- "mode": "overlay_l2",
- "cidr": "172.16.0.0/16"
- },
- "eniNetwork": {},
- "authentication": {
- "mode": "rbac",
- "authenticatingProxy": {}
- },
- "billingMode": 0,
- "extendParam": {
- "clusterAZ": "multi_az"
- },
- "kubernetesSvcIpRange": "10.247.0.0/16",
- "kubeProxyMode": "iptables"
+ "timezone" :
+ },
+ "spec" : {
+ "publicAccess" : { },
+ "category" : "CCE",
+ "type" : "VirtualMachine",
+ "enableAutopilot" : false,
+ "flavor" : "cce.s1.small",
+ "version" : "v1.29",
+ "platformVersion" : "cce.4.0",
+ "configurationsOverride" : [ {
+ "name" : "kube-apiserver",
+ "configurations" : [ {
+ "name" : "support-overload",
+ "value" : true
+ } ]
+ },{
+ "name": "eni",
+ "configurations": [ {
+ "name": "dataplane-v2",
+ "value": true
+ } ]
+ } ],
+ "hostNetwork" : {
+ "vpc" : "0538a5d0-9a65-4c1d-a8bf-e9acee237980",
+ "subnet" : "bc81be88-6e34-4b02-83bd-df0a1f7672c5"
},
- "status": {
- "phase": "Creating",
- "jobID": "d6bcbb0b-8529-11ea-8e34-0255ac101108"
+ "containerNetwork" : {
+ "mode" : "vpc-router",
+ "cidr" : "172.17.0.0/16",
+ "cidrs" : [ {
+ "cidr" : "172.17.0.0/16"
+ } ]
+ },
+ "eniNetwork" : { },
+ "serviceNetwork" : {
+ "IPv4CIDR" : "10.247.0.0/16"
+ },
+ "authentication" : {
+ "mode" : "rbac",
+ "authenticatingProxy" : { }
+ },
+ "billingMode" : 0,
+ "kubernetesSvcIpRange" : "10.247.0.0/16",
+ "kubeProxyMode" : "iptables",
+ "extendParam" : {
+ "alpha.cce/fixPoolMask" : "25",
+ "enterpriseProjectId" : "0",
+ "orderID" : ""
}
+ },
+ "status" : {
+ "phase" : "Creating",
+ "jobID" : "1e50bfbe-5b9e-11ef-8f52-0255ac10003e"
+ }
}
-Status Code
Table 29 describes the status code of this API.
-Table 29 Status code Status Code
+Table 29 Parameter Description Parameter
+
+Description
+
+
+
+support-overload
+
+Cluster overload control. After this function is enabled, CCE will dynamically adjust concurrent requests based on the resource demands received by master nodes to ensure the stability and reliability of the master nodes and the cluster.
+Configuration suggestion: Enable this function. In scenarios like short-term request bursts, a cluster may still become overloaded even with overload control enabled. In such cases, you are advised to manage and control access to the cluster promptly.
+Applicable cluster version: This parameter is available only in clusters v1.23 or later.
+
+
+dataplane-v2 (supported by clusters using the VPC networks)
+
+eBPF is used at the kernel layer for Kubernetes network acceleration, enhancing high-performance service communication through ClusterIP Services, precise traffic control via network policies, and intelligent bandwidth management with egress bandwidth.
+This function has the restrictions below.
+- Restrictions on clusters: This function can be enabled only for clusters v1.27.16-r30, v1.28.15-r20, v1.29.13-r0, v1.30.10-r0, v1.31.6-r0, or later that use VPC networks.
- Restrictions on memory: After this function is enabled, CCE will automatically deploy the cilium-agent on every node in a cluster. Each cilium-agent will use 80 MiB of memory, and the memory usage will increase by 10 KiB whenever a new pod is added.
- Restrictions on OSs: After a node is created, it can only use HCE OS 2.0.
+ NOTE: CCE DataPlane V2 is released with restrictions. To use this feature, submit a service ticket to CCE.
+
+
+
+
+
+
+
+Status Code
Table 30 describes the status code of this API.
+
+Table 30 Status code Status Code
Description
diff --git a/docs/cce/api-ref/cce_02_0242.html b/docs/cce/api-ref/cce_02_0242.html
index 0da83fe31..ca241de0a 100644
--- a/docs/cce/api-ref/cce_02_0242.html
+++ b/docs/cce/api-ref/cce_02_0242.html
@@ -525,13 +525,27 @@
Specifies the IAM agency name.
-dockerBaseSize
+containerBaseSize
-No
+No
-Integer
+Integer
-Available disk space of a single Docker container on the node using the device mapper.
+Details:
+Available disk space of a single container on a node (unit: G).
+For details about how to allocate the space for the container runtime, see Space Allocation of a Data Disk.
+Constraints:
+When Device Mapper is used, it is recommended that containerBaseSize be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being deprecated.
+The containerBaseSize setting takes effect only on nodes running EulerOS in clusters of the new version (v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0 or later).
+This parameter cannot be updated when a node pool is being updated.
+
+Options:
+10 to 500
+Default value:
+If the value is not specified or is set to 0, the default value is used.
+
alpha.cce/preInstall
@@ -1736,11 +1750,26 @@
Maximum number of pods on the node.
-dockerBaseSize
+containerBaseSize
-Integer
+No
-Available disk space of a single Docker container on the node using the device mapper.
+Integer
+Details:
+Available disk space of a single container on a node (unit: G).
+For details about how to allocate the space for the container runtime, see Space Allocation of a Data Disk.
+Constraints:
+When Device Mapper is used, it is recommended that containerBaseSize be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being deprecated.
+The containerBaseSize setting takes effect only on nodes running EulerOS in clusters of the new version (v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0 or later).
+This parameter cannot be updated when a node pool is being updated.
+
+Options:
+10 to 500
+Default value:
+If the value is not specified or is set to 0, the default value is used.
+
agency_name
diff --git a/docs/cce/api-ref/cce_02_0243.html b/docs/cce/api-ref/cce_02_0243.html
index dbe1b9a8d..ce302dc2b 100644
--- a/docs/cce/api-ref/cce_02_0243.html
+++ b/docs/cce/api-ref/cce_02_0243.html
@@ -505,11 +505,26 @@
Maximum number of pods on the node.
-dockerBaseSize
+containerBaseSize
-Integer
+No
-Available disk space of a single Docker container on the node using the device mapper.
+Integer
+Details:
+Available disk space of a single container on a node (unit: G).
+For details about how to allocate the space for the container runtime, see Space Allocation of a Data Disk.
+Constraints:
+When Device Mapper is used, it is recommended that containerBaseSize be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being deprecated.
+The containerBaseSize setting takes effect only on nodes running EulerOS in clusters of the new version (v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0 or later).
+This parameter cannot be updated when a node pool is being updated.
+
+Options:
+10 to 500
+Default value:
+If the value is not specified or is set to 0, the default value is used.
+
periodType
diff --git a/docs/cce/api-ref/cce_02_0269.html b/docs/cce/api-ref/cce_02_0269.html
index 82b7cec31..6f01c382f 100644
--- a/docs/cce/api-ref/cce_02_0269.html
+++ b/docs/cce/api-ref/cce_02_0269.html
@@ -444,7 +444,17 @@
- DockerLVMConfigOverride: Docker data disk configuration item. (This parameter has been discarded. Use the storage field instead.) The following is an example default configuration:
"DockerLVMConfigOverride":"dockerThinpool=vgpaas/90%VG;kubernetesLV=vgpaas/10%VG;diskType=evs;lvType=linear"
The configuration contains the following fields:
- userLV: size of the user space, for example, vgpaas/20%VG.
- userPath: mount path of the user space, for example, /home/wqt-test.
- diskType: disk type. Currently, only evs, hdd, and ssd are supported.
- lvType: type of a logic volume. Currently, the value can be linear or striped.
- dockerThinpool: Docker space size, for example, vgpaas/60%VG.
- kubernetesLV: kubelet space size, for example, vgpaas/20%VG.
- - dockerBaseSize: available disk space of a single Docker container on a node in Device Mapper mode. This field is not supported in OverlayFS mode (nodes that use Ubuntu 18.04 in CCE Turbo clusters and nodes that use Ubuntu 18.04 in CCE clusters).
- init-node-password: initial node password
- offloadNode: whether the node is a CCE Turbo cluster node. This parameter is not supported when you add a node to a node pool.
- publicKey: node public key. Used when creating a key pair.
- alpha.cce/preInstall: pre-installation script.
+containerBaseSize: Available disk space of a single container on a node (unit: G). For details about how to allocate the space for the container runtime, see Space Allocation of a Data Disk.- Constraints:
When Device Mapper is used, it is recommended that containerBaseSize be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being deprecated.
+
+ - Options:
10 to 500
+ - Default value:
If the value is not specified or is set to 0, the default value is used.
+
+
+ init-node-password: initial node password offloadNode: whether the node is a CCE Turbo cluster node. This parameter is not supported when you add a node to a node pool. publicKey: node public key. Used when creating a key pair. alpha.cce/preInstall: pre-installation script.
NOTE: The input value must be Base64-encoded. (Command: echo -n Content to be encoded | base64)
- alpha.cce/postInstall: post-installation script
diff --git a/docs/cce/api-ref/cce_02_0273.html b/docs/cce/api-ref/cce_02_0273.html
index a2e5c211a..23e8c790e 100644
--- a/docs/cce/api-ref/cce_02_0273.html
+++ b/docs/cce/api-ref/cce_02_0273.html
@@ -8,12 +8,31 @@
-2025-10-28
+2025-12-30
-Add:
-Added the alpha.cce/postInstall parameter in Updating a Specified Node Pool.
+Add:
+
+- Added Creating Add-on Check Tasks in Batches and Obtaining the Add-on Check Task Results.
- Added Job Management.
- Added the support-overload and dataplane-v2 parameter description in Creating a Cluster.
+
+
+2025-11-25
+
+Add:
+Added the userTags parameter in Updating a Specified Node Pool.
+
+
+2025-11-06
+
+Update:
+- Updated the parameter dockerBaseSize to containerBaseSize in Creating a Node , Reading a Specified Node , Accepting a Node , Resetting a Node , Listing All Node Pools in a Specified Cluster , Deleting a Node Pool.
+
+
+2025-10-28
+
+Add:
+- Added the alpha.cce/postInstall parameter in Updating a Specified Node Pool.
Delete:
-Removed the cluster_id from the URI in Deleting an Add-on Instance , Reading an Add-on Instance , Listing Add-on Instances.
+- Removed the cluster_id from the URI in Deleting an Add-on Instance , Reading an Add-on Instance , Listing Add-on Instances.
2025-09-12
diff --git a/docs/cce/api-ref/cce_02_0320.html b/docs/cce/api-ref/cce_02_0320.html
index c7096d8ae..4f21af2ab 100644
--- a/docs/cce/api-ref/cce_02_0320.html
+++ b/docs/cce/api-ref/cce_02_0320.html
@@ -16,6 +16,10 @@
Listing Add-on Instances
+Creating Add-on Check Tasks in Batches
+
+Obtaining the Add-on Check Task Results
+
diff --git a/docs/cce/api-ref/cce_02_0356.html b/docs/cce/api-ref/cce_02_0356.html
index 4ae00416d..f9026090b 100644
--- a/docs/cce/api-ref/cce_02_0356.html
+++ b/docs/cce/api-ref/cce_02_0356.html
@@ -251,7 +251,8 @@
No
-Object
+
+Map<String,String>
Kubernetes label, in the format of key-value pair. A maximum of 20 key-value pairs are allowed.
- Key: Enter 1 to 63 characters starting with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. A DNS subdomain can be prefixed to a key and contain a maximum of 253 characters. Example DNS subdomain: example.com/my-key.
- Value: The value can be left blank or a string of 1 to 63 characters starting with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed in the character string.
@@ -261,11 +262,26 @@
}
+userTags
+
+No
+
+Array of Table 9 objects
+
+Definition
+Cloud server resource tags
+Constraints
+The key of a tag must be unique. The maximum number of custom tags supported by CCE varies depending on regions and cannot exceed 8.
+If this parameter is not specified, the custom cloud server resource tags of the node pool will not be updated.
+If the parameter is left empty, the custom cloud server resource tags of the node pool will be deleted.
+
+
+
taints
No
-Object
+Array of Table 10 objects
Taints added to the created node to set anti-affinity. The following three parameters are contained in every taint:- Key: Enter 1 to 63 characters starting with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. A DNS subdomain can be prefixed to a key.
- Value: The value can be a string of 1 to 63 characters starting with a letter or digit. Letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.
- Effect: Set it to NoSchedule, PreferNoSchedule, or NoExecute.
@@ -399,6 +415,114 @@
+
+Table 9 UserTag Parameter
+
+Mandatory
+
+Type
+
+Description
+
+
+
+key
+
+No
+
+String
+
+Details:
+Key of the cloud server tag
+Constraints:
+The value cannot start with CCE-, __type_baremetal, or sys.
+Options:
+The value contains a maximum of 128 characters. The tag key must be unique and cannot start or end with a space. It cannot contain non-printable ASCII characters (0–31) or the following special characters: =*<>,|/
+Default value:
+N/A
+
+
+value
+
+No
+
+String
+
+Details:
+Value of the cloud server tag
+Constraints:
+None
+Options:
+The value contains a maximum of 255 characters. The tag value cannot start or end with a space. It cannot contain non-printable ASCII characters (0–31) or the following special characters: =*<>,|
+Default value:
+N/A
+
+
+
+
+
+
+Table 10 Taint Parameter
+
+Mandatory
+
+Type
+
+Description
+
+
+
+key
+
+Yes
+
+String
+
+Definition
+Key of a Kubernetes taint
+Constraints
+The value must contain 1 to 63 characters starting and ending with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.
+Range
+N/A
+Default Value
+N/A
+
+
+value
+
+No
+
+String
+
+Definition
+Value of a Kubernetes taint
+Constraints
+The value must contain 1 to 63 characters starting and ending with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.
+Range
+N/A
+Default Value
+N/A
+
+
+effect
+
+Yes
+
+String
+
+Definition
+Effect of a Kubernetes taint
+Constraints
+N/A
+Range
+NoSchedule, PreferNoSchedule, and NoExecute
+Default Value
+N/A
+
+
+
+
+
Example request:
{
"metadata" : {
@@ -548,9 +672,9 @@
}
}
-Status Code
Table 9 describes the status code of this API.
+Status Code
Table 11 describes the status code of this API.
-Table 9 Status code Status Code
+Table 11 Status code Status Code
Description
diff --git a/docs/cce/api-ref/cce_02_0357.html b/docs/cce/api-ref/cce_02_0357.html
index 2ebaa9457..4cbb27e64 100644
--- a/docs/cce/api-ref/cce_02_0357.html
+++ b/docs/cce/api-ref/cce_02_0357.html
@@ -384,7 +384,17 @@
- DockerLVMConfigOverride: Docker data disk configuration item. (This parameter has been discarded. Use the storage field instead.) The following is an example default configuration:
"DockerLVMConfigOverride":"dockerThinpool=vgpaas/90%VG;kubernetesLV=vgpaas/10%VG;diskType=evs;lvType=linear"
The configuration contains the following fields:
- userLV: size of the user space, for example, vgpaas/20%VG.
- userPath: mount path of the user space, for example, /home/wqt-test.
- diskType: disk type. Currently, only evs, hdd, and ssd are supported.
- lvType: type of a logic volume. Currently, the value can be linear or striped.
- dockerThinpool: Docker space size, for example, vgpaas/60%VG.
- kubernetesLV: kubelet space size, for example, vgpaas/20%VG.
- - dockerBaseSize: available disk space of a single Docker container on a node in Device Mapper mode. This field is not supported in OverlayFS mode (nodes that use Ubuntu 18.04 in CCE Turbo clusters and nodes that use Ubuntu 18.04 in CCE clusters).
- init-node-password: initial node password
- offloadNode: whether the node is a CCE Turbo cluster node.
- publicKey: node public key. Used when creating a key pair.
- alpha.cce/preInstall: pre-installation script.
+containerBaseSize: Available disk space of a single container on a node (unit: G). For details about how to allocate the space for the container runtime, see Space Allocation of a Data Disk.- Constraints:
When Device Mapper is used, it is recommended that containerBaseSize be set to a value less than or equal to 80 GiB. If the value is too large, the container runtime may fail to be started due to long initialization. If there are special requirements for the container disk space, you can mount an external or local storage device. In new versions, the Device Mapper mode is used only by BMSs in the same resource pool and is being deprecated.
+
+ - Options:
10 to 500
+ - Default value:
If the value is not specified or is set to 0, the default value is used.
+
+
+ init-node-password: initial node password offloadNode: whether the node is a CCE Turbo cluster node. publicKey: node public key. Used when creating a key pair. alpha.cce/preInstall: pre-installation script.
NOTE: The input value must be Base64-encoded. (Command: echo -n Content to be encoded | base64)
- alpha.cce/postInstall: post-installation script
diff --git a/docs/cce/api-ref/cce_02_0358.html b/docs/cce/api-ref/cce_02_0358.html
new file mode 100644
index 000000000..7a44c6d53
--- /dev/null
+++ b/docs/cce/api-ref/cce_02_0358.html
@@ -0,0 +1,170 @@
+
+
+Synchronizing Node Pool Configurations to Existing Nodes
+Function
This API is used to synchronize node pool configurations to existing nodes.
+
+URI
PUT /api/v3.1/projects/{project_id}/clusters/{cluster_id}/nodepool/{nodepool_id}/sync
+
+Table 1 Path Parameters Parameter
+
+Mandatory
+
+Type
+
+Description
+
+
+
+project_id
+
+Yes
+
+String
+
+Details:
+Project ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI.
+Constraints:
+None
+Options:
+Project IDs of the account
+Default value:
+N/A
+
+
+cluster_id
+
+Yes
+
+String
+
+Details:
+Cluster ID. For details about how to obtain the value, see How to Obtain Parameters in the API URI.
+Constraints:
+None
+Options:
+Cluster IDs
+Default value:
+N/A
+
+
+nodepool_id
+
+Yes
+
+String
+
+Details:
+Node pool ID. For details about how to obtain the ID, see How to Obtain Parameters in the API URI.
+Constraints:
+None
+Options:
+Cluster IDs
+Default value:
+N/A
+
+
+
+
+
+
+Request Parameters
+Table 2 Request header parameters Parameter
+
+Mandatory
+
+Type
+
+Description
+
+
+
+Content-Type
+
+Yes
+
+String
+
+Details:
+The request body type or format
+Constraints:
+The GET method is not verified.
+Options:
+
+Default value:
+N/A
+
+
+X-Auth-Token
+
+Yes
+
+String
+
+Details:
+Requests for calling an API can be authenticated using either a token or AK/SK. If token-based authentication is used, this parameter is mandatory and must be set to a user token. For details, see Obtaining a User Token.
+Constraints:
+None
+Options:
+N/A
+Default value:
+N/A
+
+
+
+
+
+
+Response Parameters
Status code: 200
+
+Table 3 Response body parameters Parameter
+
+Type
+
+Description
+
+
+
+-
+
+String
+
+-
+
+
+
+
+
+
+Example Requests
None
+
+Example Responses
None
+
+Status Codes
+Status Code
+
+Description
+
+
+
+200
+
+The node pool configurations are successfully synchronized to the existing nodes.
+
+
+
+
+
+
+Error Codes
See Error Codes.
+
+
+
+
+Parent topic: Cluster Management
+
+
+
diff --git a/docs/cce/api-ref/cce_10_0341.html b/docs/cce/api-ref/cce_10_0341.html
new file mode 100644
index 000000000..49d478471
--- /dev/null
+++ b/docs/cce/api-ref/cce_10_0341.html
@@ -0,0 +1,121 @@
+
+
+Space Allocation of a Data Disk
+This section describes how to allocate data disk space to nodes so that you can configure the data disk space accordingly.
+Allocating Default Data Disk Space
- In clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.29.4-r0, or v1.28.8-r0, a default data disk will be added to the node for the container runtime and kubelet components. You can customize the space allocation of the default data disk.
- In clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later, a default data disk will be added to the node for the container runtime and kubelet components only if System Component Storage is set to Data Disk. You can customize the space allocation of the default data disk.
+
+When creating a node, you can customize Data Disk Space Allocation in the expanded area of Data Disk.
+
+- Space Allocation for Container Engines
- Specified disk space: CCE divides the data disk space for two parts by default. One part is used to store the Docker/containerd working directories, container image data, and image metadata. The other is reserved for kubelet and emptyDir volumes. The available container engine space affects image pulls and container startup and running.
- Container engine and container image space (90% by default): stores the container runtime working directories, container image data, and image metadata.
- kubelet and emptyDir space (10% by default): stores pod configuration files, secrets, and mounted storage such as emptyDir volumes.
+
If the sum of the container engine and container image space and the kubelet and emptyDir space is less than 100%, the remaining space will be allocated for user data. You can mount the storage volume to a service path. Do not leave the path empty or set it to a key OS path such as the root directory.
+
+
+ - Space Allocation for Pods: indicates the basesize of a pod. You can set an upper limit for the disk space occupied by each workload pod (including the space occupied by container images). This setting prevents the pods from taking all the disk space available, which may cause service exceptions. It is recommended that the value is less than or equal to 80% of the container engine space. This parameter is related to the node OS and container storage Rootfs and is not supported in some scenarios. For details, see Mapping Between OS and Container Storage Rootfs.
- Write Mode
- Linear: A linear logical volume integrates one or more physical volumes. Data is written to the next physical volume when the previous one is used up.
- Striped: available only if there are at least two data disks. A striped logical volume stripes data into blocks of the same size and stores them in multiple physical volumes in sequence. This allows data to be concurrently read and written. A storage pool consisting of striped volumes cannot be scaled-out.
+
+
+Space Allocation for Container Engines
For a node using a non-shared data disk (100 GiB for example), the division of the disk space varies depending on the container storage Rootfs type Device Mapper or OverlayFS. For details about the container storage Rootfs corresponding to different OSs, see Mapping Between OS and Container Storage Rootfs.
+- Rootfs (Device Mapper)By default, the container engine and image space, occupying 90% of the data disk, can be divided into the following two parts:
- The /var/lib/docker directory is used as the Docker working directory and occupies 20% of the container engine and container image space by default. (Space size of the /var/lib/docker directory = Data disk space x 90% x 20%)
- The thin pool is used to store container image data, image metadata, and container data, and occupies 80% of the container engine and container image space by default. (Thin pool space = Data disk space x 90% x 80%)
The thin pool is dynamically mounted. You can view it by running the lsblk command on a node, but not the df -h command.
+
+
+Figure 1 Space allocation for container engines of Device Mapper
+
+- Rootfs (OverlayFS)
No separate thin pool. The entire container engine and container image space (90% of the data disk by default) are in the /var/lib/docker directory.
+Figure 2 Space allocation for container engines of OverlayFS
+
+
+Space Allocation for Pods
The customized pod container space (basesize) is related to the node OS and container storage Rootfs. For details about the container storage Rootfs, see Mapping Between OS and Container Storage Rootfs.
+- Device Mapper supports custom pod basesize. The default value is 10 GiB.
- In OverlayFS mode, the pod container space is not limited by default.
+When configuring basesize, consider the maximum number of pods allowed on one node. The container engine space should be greater than the total disk space used by containers. Formula: Container engine space and container image space (90% by default) > Number of containers x basesize. Otherwise, the container engine space allocated to the node may be insufficient and the container cannot be started.
+For nodes that support basesize, when Device Mapper is used, although you can limit the size of the /home directory of a single container (to 10 GiB by default), all containers on the node still share the thin pool of the node for storage. They are not completely isolated. When the sum of the thin pool space used by certain containers reaches the upper limit, other containers cannot run properly.
+In addition, after a file is deleted in the /home directory of the container, the thin pool space occupied by the file is not released immediately. Therefore, even if basesize is set to 10 GiB, the thin pool space occupied by files keeps increasing until 10 GiB when files are created in the container. The space released after file deletion will be reused but after a while. If the number of containers on the node multiplied by basesize is greater than the thin pool space size of the node, there is a possibility that the thin pool space has been used up.
+
+Mapping Between OS and Container Storage Rootfs
+Table 1 Node OSs and container engines in CCE clusters OS
+
+Container Storage Rootfs
+
+Custom Basesize
+
+
+
+EulerOS 2.9
+
+OverlayFS
+
+Supported by Docker clusters of v1.19.16-r0, v1.21.3-r0, v1.23.3-r0, or later. There are no limits by default.
+Supported by containerd clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later. There are no limits by default.
+Not supported by clusters of a version earlier than v1.19.16-r0, v1.21.3-r0, or v1.23.3-r0.
+
+
+Ubuntu 22.04
+
+OverlayFS
+
+Not supported
+
+
+HCE OS 2.0
+
+OverlayFS
+
+Supported only by Docker clusters of a version earlier than v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, or v1.28.4-r0. There are no limits by default.
+Supported by both Docker and containerd clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later. There are no limits by default.
+
+
+
+
+
+
+Table 2 Node OSs and container engines in CCE Turbo clusters OS
+
+Container Storage Rootfs
+
+Custom Basesize
+
+
+
+Ubuntu 22.04
+
+OverlayFS
+
+Not supported
+
+
+EulerOS 2.9
+
+OverlayFS
+
+Supported when Rootfs is set to OverlayFS and the runtime is Docker. There are no limits by default. Supported by both Docker and containerd clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later.
+
+
+HCE OS 2.0
+
+OverlayFS
+
+Supported only by Docker clusters of a version earlier than v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, or v1.28.4-r0. There are no limits by default.
+Supported by both Docker and containerd clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later. There are no limits by default.
+
+
+
+
+
+
+Garbage Collection Policies for Container Images
When the container engine space is insufficient, image garbage collection is triggered.
+The policy for garbage collecting images takes two factors into consideration: HighThresholdPercent and LowThresholdPercent. Disk usage exceeding the high threshold (default: 80%) will trigger garbage collection. The garbage collection will delete least recently used images until the low threshold (default: 70%) is met.
+
+Recommended Configuration for the Container Engine Space
- The container engine space should be greater than the total disk space used by containers. Formula: Container engine space > Number of containers x basesize
- You are advised to create and delete files of containerized services in local storage volumes (such as emptyDir and hostPath volumes) or cloud storage directories mounted to the containers. In this way, the thin pool space is not occupied. emptyDir volumes occupy the kubelet space. Therefore, properly plan the size of the kubelet space.
- You can deploy services on nodes that use the OverlayFS (for details, see Mapping Between OS and Container Storage Rootfs) so that the disk space occupied by files created or deleted in containers can be released immediately.
+
+
+
+
+Parent topic: Appendix
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/cce/api-ref/en-us_image_0000002434080444.png b/docs/cce/api-ref/en-us_image_0000002434080444.png
new file mode 100644
index 000000000..924bf4207
Binary files /dev/null and b/docs/cce/api-ref/en-us_image_0000002434080444.png differ
diff --git a/docs/cce/api-ref/en-us_image_0000002467718921.png b/docs/cce/api-ref/en-us_image_0000002467718921.png
new file mode 100644
index 000000000..3436be663
Binary files /dev/null and b/docs/cce/api-ref/en-us_image_0000002467718921.png differ
diff --git a/docs/cce/api-ref/job_lifecycle_management.html b/docs/cce/api-ref/job_lifecycle_management.html
new file mode 100644
index 000000000..1da07b43e
--- /dev/null
+++ b/docs/cce/api-ref/job_lifecycle_management.html
@@ -0,0 +1,20 @@
+
+
+Job Management
+
+
+
+
+
+
+Parent topic: APIs
+
+
+
diff --git a/docs/cce/api-ref/node_storage_example.html b/docs/cce/api-ref/node_storage_example.html
index 8a7b9722d..b0c45b9ee 100644
--- a/docs/cce/api-ref/node_storage_example.html
+++ b/docs/cce/api-ref/node_storage_example.html
@@ -15,7 +15,7 @@ storageDevice=/dev/vdb
vgcreate ${vgName} ${storageDevice}
EVS disks match the disks created in dataVolumes based on the settings of matchLabels.
-Policies have priorities to match matchLabels. The matchLabels policy nearest to storageSelectors has a higher priority and the disk nearest to dataVolumes will be preferentially matches. As matchLabels uses loose matching, you are advised to place the matchLabels policy with a small matching range on the top. For example:
- In step 1, the first disk in dataVolumes is matched by the EVS disk whose size is 100 GiB and storage class is SAS. In step 2, the second disk in dataVolumes is matched by the EVS disk whose size is 100 GiB because the first disk has been selected.
- In step 3, two disks in dataVolumes can be matched because volumeType or count is not specified in matchLabels. In this case, no disk is available for matching in step 4.
+Policies have priorities to match matchLabels. The matchLabels policy nearest to storageSelectors has a higher priority and the disk nearest to dataVolumes will be preferentially matches. As matchLabels uses loose matching, you are advised to place the matchLabels policy with a small matching range on the top. For example:
- In step 1, the first disk in dataVolumes is matched by the EVS disk whose size is 100 GiB and storage class is SAS. In step 2, the second disk in dataVolumes is matched by the EVS disk whose size is 100 GiB because the first disk has been selected.
- In step 3, two disks in dataVolumes can be matched because volumeType or count is not specified. In this case, no disk is available for matching in step 4.
storageGroups associates with storageSelectors based on selectorName. Finally, two 100 GiB disks are selected. The CCE backend groups the two PVs into a volume group (VG) and divides the VG into two logical volumes (LVs) in the ratio of 9:1. 10% of Kubernetes LVs are partitioned in striped mode. 90% runtime LVs are partitioned in linear mode by default because runtimeConfig is not configured.
@@ -218,7 +218,7 @@ vgcreate ${vgName} ${storageDevice}
Creating Striped LVs to Improve Disk Performance
Currently, the striped LV function is supported only by calling an API. The following is an example:

-- storageSelectors matches all EVS disks in dataVolumes because matchLabels is not contained in storageSelectors.
- Create a VG named vgpaas using LVM.
- Strip 90% of the vgpaas space into runtime LVs.
- Strip 10% of the vgpaas space into Kubernetes LVs.
+- If matchLabels in storageSelectors is empty, all EVS disks will be selected.
- Create a VG named vgpaas using LVM.
- Strip 90% of the vgpaas space into runtime LVs.
- Strip 10% of the vgpaas space into Kubernetes LVs.
- Two or more data disks are required for striping.
- When creating a striped LV, ensure that the types and sizes of the PVs added to the VG are the same. Otherwise, the creation will fail.
- When creating a striped LV, use the striping configuration for both the runtime LV and Kubernetes LV. Otherwise, the creation will fail.
Log in to the node and run the following command to view the striping result: