forked from docs/doc-exports
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com> Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com> Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
11659 lines
366 KiB
JSON
11659 lines
366 KiB
JSON
[
|
||
{
|
||
"dockw":"User Guide"
|
||
},
|
||
{
|
||
"uri":"cce_productdesc_0000.html",
|
||
"node_id":"cce_productdesc_0000.xml",
|
||
"product_code":"cce",
|
||
"code":"1",
|
||
"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":"usermanual2",
|
||
"kw":"Service Overview",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual",
|
||
"opensource":"true",
|
||
"IsMulti":"Yes"
|
||
}
|
||
],
|
||
"title":"Service Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_productdesc_0001.html",
|
||
"node_id":"cce_productdesc_0001.xml",
|
||
"product_code":"cce",
|
||
"code":"2",
|
||
"des":"Cloud Container Engine (CCE) is a Kubernetes cluster hosting service for enterprises. It manages the enter lifecycle of containerized applications and delivers scalable, ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Is CCE?,Service Overview,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"What Is CCE?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_productdesc_0003.html",
|
||
"node_id":"cce_productdesc_0003.xml",
|
||
"product_code":"cce",
|
||
"code":"3",
|
||
"des":"CCE is a container service developed on Docker and Kubernetes. It offers a wide range of features that allow you to run containers on a large scale. CCE containers are hi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Product Advantages,Service Overview,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Product Advantages",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_productdesc_0004.html",
|
||
"node_id":"cce_productdesc_0004.xml",
|
||
"product_code":"cce",
|
||
"code":"4",
|
||
"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":"usermanual2",
|
||
"kw":"Application Scenarios",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Application Scenarios",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_productdesc_0007.html",
|
||
"node_id":"cce_productdesc_0007.xml",
|
||
"product_code":"cce",
|
||
"code":"5",
|
||
"des":"CCE clusters enable the management of both x86 and Arm resources. With CCE, you can effortlessly create Kubernetes clusters, deploy containerized applications, and effect",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Containerized Application Management,Application Scenarios,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Containerized Application Management",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_productdesc_0021.html",
|
||
"node_id":"cce_productdesc_0021.xml",
|
||
"product_code":"cce",
|
||
"code":"6",
|
||
"des":"Shopping apps and websites, especially during promotionsLive streaming, where service loads often fluctuateGames, where many players may go online in certain time periods",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Auto Scaling in Seconds,Application Scenarios,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Auto Scaling in Seconds",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_productdesc_0017.html",
|
||
"node_id":"cce_productdesc_0017.xml",
|
||
"product_code":"cce",
|
||
"code":"7",
|
||
"des":"You may receive a lot feedback and requirements for your apps or services. You may want to boost user experience with new features. Continuous integration (CI) and delive",
|
||
"doc_type":"usermanual2",
|
||
"kw":"DevOps and CI/CD,Application Scenarios,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"DevOps and CI/CD",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_productdesc_0018.html",
|
||
"node_id":"cce_productdesc_0018.xml",
|
||
"product_code":"cce",
|
||
"code":"8",
|
||
"des":"Multi-cloud deployment and disaster recoveryRunning apps in containers on different clouds can ensure high availability. When a cloud is down, other clouds respond and se",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Hybrid Cloud,Application Scenarios,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Hybrid Cloud",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_productdesc_0002.html",
|
||
"node_id":"cce_productdesc_0002.xml",
|
||
"product_code":"cce",
|
||
"code":"9",
|
||
"des":"CCE permissions management allows you to assign permissions to IAM users and user groups under your tenant accounts. CCE combines the advantages of IAM and RBAC to provid",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Permissions,Service Overview,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Permissions",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_productdesc_0005.html",
|
||
"node_id":"cce_productdesc_0005.xml",
|
||
"product_code":"cce",
|
||
"code":"10",
|
||
"des":"This section describes the notes and constraints on using CCE.After a cluster is created, the following items cannot be changed:Number of master nodes: For example, a non",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Storage Volumes,Data sharing,Notes and Constraints,Service Overview,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Notes and Constraints",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_productdesc_0008.html",
|
||
"node_id":"cce_productdesc_0008.xml",
|
||
"product_code":"cce",
|
||
"code":"11",
|
||
"des":"CCE needs to be interconnected with the following cloud services. It requires permissions to access these cloud services.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"ECS,VPC,ELB,SWR,EVS,OBS,cloud storage for data of any size,SFS,AOM,Related Services,Service Overview",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Related Services",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_productdesc_0012.html",
|
||
"node_id":"cce_productdesc_0012.xml",
|
||
"product_code":"cce",
|
||
"code":"12",
|
||
"des":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.Regions are divided based on geographical",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Regions and AZs,Service Overview,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Regions and AZs",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bulletin_0000.html",
|
||
"node_id":"cce_bulletin_0000.xml",
|
||
"product_code":"cce",
|
||
"code":"13",
|
||
"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":"usermanual2",
|
||
"kw":"Product Bulletin",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"opensource":"true",
|
||
"documenttype":"usermanual2",
|
||
"IsMulti":"Yes"
|
||
}
|
||
],
|
||
"title":"Product Bulletin",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bulletin_0033.html",
|
||
"node_id":"cce_bulletin_0033.xml",
|
||
"product_code":"cce",
|
||
"code":"14",
|
||
"des":"CCE provides highly scalable, high-performance, enterprise-class Kubernetes clusters. This section describes the Kubernetes version policy of CCE clusters.The CCE console",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Kubernetes Version Policy,Product Bulletin,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"opensource":"true",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes Version Policy",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bulletin_0098.html",
|
||
"node_id":"cce_bulletin_0098.xml",
|
||
"product_code":"cce",
|
||
"code":"15",
|
||
"des":"Released: Oct 23, 2024CentOS has reached its end of maintenance (EOM) date, which means it will no longer receive updates or support. The CentOS public images on CCE are ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"EOM of CentOS,Product Bulletin,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
|
||
}
|
||
],
|
||
"title":"EOM of CentOS",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bulletin_0169.html",
|
||
"node_id":"cce_bulletin_0169.xml",
|
||
"product_code":"cce",
|
||
"code":"16",
|
||
"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":"usermanual2",
|
||
"kw":"Security Vulnerability Responses",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"opensource":"true",
|
||
"documenttype":"usermanual2",
|
||
"IsMulti":"Yes"
|
||
}
|
||
],
|
||
"title":"Security Vulnerability Responses",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bulletin_0011.html",
|
||
"node_id":"cce_bulletin_0011.xml",
|
||
"product_code":"cce",
|
||
"code":"17",
|
||
"des":"High-risk vulnerabilities:CCE fixes vulnerabilities as soon as possible after the Kubernetes community detects them and releases fixing solutions. The fixing policies are",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Vulnerability Fixing Policies,Security Vulnerability Responses,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"opensource":"true",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Vulnerability Fixing Policies",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"CVE-2021-4034.html",
|
||
"node_id":"cve-2021-4034.xml",
|
||
"product_code":"cce",
|
||
"code":"18",
|
||
"des":"Recently, a security research team disclosed a privilege escalation vulnerability (CVE-2021-4034, also dubbed PwnKit) in PolKit's pkexec. Unprivileged users can gain full",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Linux Polkit Privilege Escalation Vulnerability (CVE-2021-4034),Security Vulnerability Responses,Use",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"opensource":"true",
|
||
"documenttype":"usermanual2",
|
||
"IsMulti":"Yes"
|
||
}
|
||
],
|
||
"title":"Linux Polkit Privilege Escalation Vulnerability (CVE-2021-4034)",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bulletin_0206.html",
|
||
"node_id":"cce_bulletin_0206.xml",
|
||
"product_code":"cce",
|
||
"code":"19",
|
||
"des":"The Linux Kernel SACK vulnerabilities have been fixed. This section describes the solution to these vulnerabilities.On June 18, 2019, Red Hat released a security notice, ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Notice on Fixing Linux Kernel SACK Vulnerabilities,Security Vulnerability Responses,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"opensource":"true",
|
||
"documenttype":"usermanual2",
|
||
"IsMulti":"Yes"
|
||
}
|
||
],
|
||
"title":"Notice on Fixing Linux Kernel SACK Vulnerabilities",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_qs_0000.html",
|
||
"node_id":"cce_qs_0000.xml",
|
||
"product_code":"cce",
|
||
"code":"20",
|
||
"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":"usermanual2",
|
||
"kw":"Getting Started",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual",
|
||
"opensource":"true",
|
||
"IsMulti":"Yes"
|
||
}
|
||
],
|
||
"title":"Getting Started",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_qs_0001.html",
|
||
"node_id":"cce_qs_0001.xml",
|
||
"product_code":"cce",
|
||
"code":"21",
|
||
"des":"This section describes how to use Cloud Container Engine (CCE) and provides frequently asked questions (FAQs) to help you quickly get started with CCE.Complete the follow",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Introduction,Getting Started,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual2",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Introduction",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_qs_0006.html",
|
||
"node_id":"cce_qs_0006.xml",
|
||
"product_code":"cce",
|
||
"code":"22",
|
||
"des":"Before using CCE, make the following preparations:Creating an IAM userObtaining Resource Permissions(Optional) Creating a VPC(Optional) Creating a Key PairIf you want to ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"VPC,Preparations,Getting Started,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual2",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Preparations",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_qs_0008.html",
|
||
"node_id":"cce_qs_0008.xml",
|
||
"product_code":"cce",
|
||
"code":"23",
|
||
"des":"This section describes how to quickly create a CCE cluster. In this example, the default or simple configurations are in use.If you have no clusters, click Create CCE Sta",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a Kubernetes Cluster,Getting Started,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual2",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Creating a Kubernetes Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_qs_0003.html",
|
||
"node_id":"cce_qs_0003.xml",
|
||
"product_code":"cce",
|
||
"code":"24",
|
||
"des":"You can use images to quickly create a single-pod workload that can be accessed from public networks. This section describes how to use CCE to quickly deploy an Nginx app",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a Deployment (Nginx),Getting Started,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual2",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Creating a Deployment (Nginx)",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_qs_0007.html",
|
||
"node_id":"cce_qs_0007.xml",
|
||
"product_code":"cce",
|
||
"code":"25",
|
||
"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":"usermanual2",
|
||
"kw":"Deploying WordPress and MySQL That Depend on Each Other",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual2",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Deploying WordPress and MySQL That Depend on Each Other",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_qs_0009.html",
|
||
"node_id":"cce_qs_0009.xml",
|
||
"product_code":"cce",
|
||
"code":"26",
|
||
"des":"WordPress was originally a blog platform based on PHP and MySQL. It is gradually evolved into a content management system. You can set up your own blog website on any ser",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Deploying WordPress and MySQL That Depend on Each Other,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual2",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_qs_0004.html",
|
||
"node_id":"cce_qs_0004.xml",
|
||
"product_code":"cce",
|
||
"code":"27",
|
||
"des":"WordPress must be used together with MySQL. WordPress runs the content management program while MySQL serves as a database to store data.You have created a CCE cluster th",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a MySQL Workload,Deploying WordPress and MySQL That Depend on Each Other,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual2",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Creating a MySQL Workload",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_qs_0005.html",
|
||
"node_id":"cce_qs_0005.xml",
|
||
"product_code":"cce",
|
||
"code":"28",
|
||
"des":"WordPress was originally a blog platform based on PHP and MySQL. It is gradually evolved into a content management system. You can set up your own blog website on any ser",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a WordPress Workload,Deploying WordPress and MySQL That Depend on Each Other,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"documenttype":"usermanual2",
|
||
"prodname":"cce"
|
||
}
|
||
],
|
||
"title":"Creating a WordPress Workload",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0054.html",
|
||
"node_id":"cce_10_0054.xml",
|
||
"product_code":"cce",
|
||
"code":"29",
|
||
"des":"During service deployment or running, you may trigger high-risk operations at different levels, causing service faults or interruption. To help you better estimate and av",
|
||
"doc_type":"usermanual2",
|
||
"kw":"High-Risk Operations,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"High-Risk Operations",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0091.html",
|
||
"node_id":"cce_10_0091.xml",
|
||
"product_code":"cce",
|
||
"code":"30",
|
||
"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":"usermanual2",
|
||
"kw":"Clusters",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Clusters",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0002.html",
|
||
"node_id":"cce_10_0002.xml",
|
||
"product_code":"cce",
|
||
"code":"31",
|
||
"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":"usermanual2",
|
||
"kw":"Cluster Overview",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cluster Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0430.html",
|
||
"node_id":"cce_10_0430.xml",
|
||
"product_code":"cce",
|
||
"code":"32",
|
||
"des":"Kubernetes is an open source container orchestration engine for automating deployment, scaling, and management of containerized applications.For developers, Kubernetes is",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Master Nodes,Basic Cluster Information,Cluster Overview,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Basic Cluster Information",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0068.html",
|
||
"node_id":"cce_10_0068.xml",
|
||
"product_code":"cce",
|
||
"code":"33",
|
||
"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":"usermanual2",
|
||
"kw":"Kubernetes Version Release Notes",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes Version Release Notes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bulletin_0095.html",
|
||
"node_id":"cce_bulletin_0095.xml",
|
||
"product_code":"cce",
|
||
"code":"34",
|
||
"des":"CCE allows you to create Kubernetes clusters 1.30. This section describes the changes made in Kubernetes 1.30.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Kubernetes 1.30 Release Notes,Kubernetes Version Release Notes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes 1.30 Release Notes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bulletin_0089.html",
|
||
"node_id":"cce_bulletin_0089.xml",
|
||
"product_code":"cce",
|
||
"code":"35",
|
||
"des":"CCE allows you to create Kubernetes clusters 1.29. This section describes the changes made in Kubernetes 1.29.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Kubernetes 1.29 Release Notes,Kubernetes Version Release Notes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes 1.29 Release Notes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bulletin_0068.html",
|
||
"node_id":"cce_bulletin_0068.xml",
|
||
"product_code":"cce",
|
||
"code":"36",
|
||
"des":"CCE allows you to create Kubernetes clusters 1.28. This section describes the changes made in Kubernetes 1.28.Important NotesNew and Enhanced FeaturesAPI Changes and Remo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Kubernetes 1.28 Release Notes,Kubernetes Version Release Notes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes 1.28 Release Notes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bulletin_0059.html",
|
||
"node_id":"cce_bulletin_0059.xml",
|
||
"product_code":"cce",
|
||
"code":"37",
|
||
"des":"CCE allows you to create clusters of Kubernetes 1.27. This section describes the changes made in Kubernetes 1.27 compared with Kubernetes 1.25.New FeaturesDeprecations an",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Kubernetes 1.27 Release Notes,Kubernetes Version Release Notes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes 1.27 Release Notes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bulletin_0058.html",
|
||
"node_id":"cce_bulletin_0058.xml",
|
||
"product_code":"cce",
|
||
"code":"38",
|
||
"des":"This section describes the changes made in Kubernetes 1.25 compared with Kubernetes 1.23.New FeaturesDeprecations and RemovalsEnhanced Kubernetes 1.25 on CCEReferencesKub",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Kubernetes 1.25 Release Notes,Kubernetes Version Release Notes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes 1.25 Release Notes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bulletin_0027.html",
|
||
"node_id":"cce_bulletin_0027.xml",
|
||
"product_code":"cce",
|
||
"code":"39",
|
||
"des":"This section describes the updates in CCE Kubernetes 1.23.Kubernetes 1.23 Release NotesFlexVolume is deprecated. Use CSI.HorizontalPodAutoscaler v2 is promoted to GA, and",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Kubernetes 1.23 Release Notes,Kubernetes Version Release Notes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes 1.23 Release Notes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bulletin_0026.html",
|
||
"node_id":"cce_bulletin_0026.xml",
|
||
"product_code":"cce",
|
||
"code":"40",
|
||
"des":"This section describes the updates in CCE Kubernetes 1.21.Kubernetes 1.21 Release NotesCronJob is now in the stable state, and the version number changes to batch/v1.The ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Kubernetes 1.21 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes 1.21 (EOM) Release Notes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_whsnew_0010.html",
|
||
"node_id":"cce_whsnew_0010.xml",
|
||
"product_code":"cce",
|
||
"code":"41",
|
||
"des":"This section describes the updates in CCE Kubernetes 1.19.Kubernetes v1.19 Release NotesvSphere in-tree volumes can be migrated to vSphere CSI drivers. The in-tree vSpher",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Kubernetes 1.19 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes 1.19 (EOM) Release Notes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_whsnew_0007.html",
|
||
"node_id":"cce_whsnew_0007.xml",
|
||
"product_code":"cce",
|
||
"code":"42",
|
||
"des":"This section describes the updates in CCE Kubernetes 1.17.All resources in the apps/v1beta1 and apps/v1beta2 API versions are no longer served. Migrate to use the apps/v1",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Kubernetes 1.17 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes 1.17 (EOM) Release Notes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0405.html",
|
||
"node_id":"cce_10_0405.xml",
|
||
"product_code":"cce",
|
||
"code":"43",
|
||
"des":"dockershim has been removed since Kubernetes v1.24, and Docker is not supported in v1.24 and later versions by default. Use containerd.All nodes in the CCE clusters of ve",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Patch Version Release Notes,Cluster Overview,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Patch Version Release Notes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0298.html",
|
||
"node_id":"cce_10_0298.xml",
|
||
"product_code":"cce",
|
||
"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":"usermanual2",
|
||
"kw":"Creating a Cluster",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0342.html",
|
||
"node_id":"cce_10_0342.xml",
|
||
"product_code":"cce",
|
||
"code":"45",
|
||
"des":"CCE provides different types of clusters for you to select. The following table lists the differences between them.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Comparison Between Cluster Types,Creating a Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Comparison Between Cluster Types",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0028.html",
|
||
"node_id":"cce_10_0028.xml",
|
||
"product_code":"cce",
|
||
"code":"46",
|
||
"des":"On the CCE console, you can easily create Kubernetes clusters. After a cluster is created, the master node is hosted by CCE. You only need to create worker nodes. In this",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a CCE Standard/Turbo Cluster,Creating a Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a CCE Standard/Turbo Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0349.html",
|
||
"node_id":"cce_10_0349.xml",
|
||
"product_code":"cce",
|
||
"code":"47",
|
||
"des":"kube-proxy is a key component of a Kubernetes cluster. It is used for load balancing and forwarding data between a Service and its backend pods.CCE supports the iptables ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"kube-proxy,iptables,IP Virtual Server (IPVS),forwarding modes,Comparing iptables and IPVS,Creating a",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Comparing iptables and IPVS",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0140.html",
|
||
"node_id":"cce_10_0140.xml",
|
||
"product_code":"cce",
|
||
"code":"48",
|
||
"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":"usermanual2",
|
||
"kw":"Connecting to a Cluster",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Connecting to a Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0107.html",
|
||
"node_id":"cce_10_0107.xml",
|
||
"product_code":"cce",
|
||
"code":"49",
|
||
"des":"This section uses a CCE standard cluster as an example to describe how to access a CCE cluster using kubectl.When you access a cluster using kubectl, CCE uses kubeconfig ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"kubectl,Intranet access,Two-Way Authentication for Domain Names,Error from server Forbidden,The conn",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Connecting to a Cluster Using kubectl",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0175.html",
|
||
"node_id":"cce_10_0175.xml",
|
||
"product_code":"cce",
|
||
"code":"50",
|
||
"des":"This section describes how to obtain the cluster certificate from the console and use it to access Kubernetes clusters.The downloaded certificate contains three files: cl",
|
||
"doc_type":"usermanual2",
|
||
"kw":"X.509 certificate,Accessing a Cluster Using an X.509 Certificate,Connecting to a Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Accessing a Cluster Using an X.509 Certificate",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0367.html",
|
||
"node_id":"cce_10_0367.xml",
|
||
"product_code":"cce",
|
||
"code":"51",
|
||
"des":"Subject Alternative Name (SAN) allows multiple values (including IP addresses, domain names, and so on) to be associated with certificates. A SAN is usually used by the c",
|
||
"doc_type":"usermanual2",
|
||
"kw":"SAN,X.509 certificate,Accessing a Cluster Using a Custom Domain Name,Connecting to a Cluster,User Gu",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Accessing a Cluster Using a Custom Domain Name",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0864.html",
|
||
"node_id":"cce_10_0864.xml",
|
||
"product_code":"cce",
|
||
"code":"52",
|
||
"des":"You can bind an EIP to an API server of a Kubernetes cluster so that the API server can access the Internet.Binding an EIP to an API server for Internet access can pose a",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring a Cluster's API Server for Internet Access,Connecting to a Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring a Cluster's API Server for Internet Access",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0744.html",
|
||
"node_id":"cce_10_0744.xml",
|
||
"product_code":"cce",
|
||
"code":"53",
|
||
"des":"In multi-tenant scenarios, CCE generates a credential (kubeconfig or X.509 certificate) for you to access the corresponding cluster. The credential contains user identity",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Revoking a Cluster Access Credential,Connecting to a Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Revoking a Cluster Access Credential",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0031.html",
|
||
"node_id":"cce_10_0031.xml",
|
||
"product_code":"cce",
|
||
"code":"54",
|
||
"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":"usermanual2",
|
||
"kw":"Managing a Cluster",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Managing a Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0213.html",
|
||
"node_id":"cce_10_0213.xml",
|
||
"product_code":"cce",
|
||
"code":"55",
|
||
"des":"CCE allows you to manage cluster parameters, through which you can let core components work under your requirements.kube-apiserverkube-controller-managerkube-scheduler",
|
||
"doc_type":"usermanual2",
|
||
"kw":"cluster parameters,kube-apiserver,kube-controller-manager,Modifying Cluster Configurations,Managing ",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Modifying Cluster Configurations",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0602.html",
|
||
"node_id":"cce_10_0602.xml",
|
||
"product_code":"cce",
|
||
"code":"56",
|
||
"des":"After overload control is enabled, the number of simultaneous requests is dynamically regulated according to the resource pressure on the master nodes. This ensures that ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"overload control,Enabling Overload Control for a Cluster,Managing a Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Enabling Overload Control for a Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0403.html",
|
||
"node_id":"cce_10_0403.xml",
|
||
"product_code":"cce",
|
||
"code":"57",
|
||
"des":"CCE allows you to change the number of nodes managed in a cluster.A cluster that has only one master node supports fewer than 1000 worker nodes.The number of master nodes",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Changing Cluster Scale,Managing a Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Changing Cluster Scale",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0426.html",
|
||
"node_id":"cce_10_0426.xml",
|
||
"product_code":"cce",
|
||
"code":"58",
|
||
"des":"When creating a cluster, you can customize a node security group to centrally manage network security policies. For a created cluster, you can change its default node sec",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Changing the Default Security Group of a Node,Managing a Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Changing the Default Security Group of a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0212.html",
|
||
"node_id":"cce_10_0212.xml",
|
||
"product_code":"cce",
|
||
"code":"59",
|
||
"des":"Deleting a cluster will delete the workloads and Services in the cluster, and the deleted data cannot be recovered. Before performing this operation, ensure that related ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Deleting a Cluster,Managing a Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Deleting a Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0927.html",
|
||
"node_id":"cce_10_0927.xml",
|
||
"product_code":"cce",
|
||
"code":"60",
|
||
"des":"Unexpected deletion of clusters can occur in practice, especially when multiple users share an account and accidentally delete clusters that do not belong to them. To pre",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Preventing Cluster Deletion,Managing a Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Preventing Cluster Deletion",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0214.html",
|
||
"node_id":"cce_10_0214.xml",
|
||
"product_code":"cce",
|
||
"code":"61",
|
||
"des":"If a cluster is not needed temporarily, hibernate it to reduce costs.After a cluster is hibernated, resources such as workloads cannot be created or managed in the cluste",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Hibernating or Waking Up a Cluster,Managing a Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Hibernating or Waking Up a Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0215.html",
|
||
"node_id":"cce_10_0215.xml",
|
||
"product_code":"cce",
|
||
"code":"62",
|
||
"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":"usermanual2",
|
||
"kw":"Upgrading a Cluster",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Upgrading a Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0197.html",
|
||
"node_id":"cce_10_0197.xml",
|
||
"product_code":"cce",
|
||
"code":"63",
|
||
"des":"CCE strictly complies with community consistency authentication. It releases three Kubernetes versions each year and offers a maintenance period of at least 24 months aft",
|
||
"doc_type":"usermanual2",
|
||
"kw":"cluster upgrade process,Node Priority,In-place upgrade,Process and Method of Upgrading a Cluster,Upg",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Process and Method of Upgrading a Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0302.html",
|
||
"node_id":"cce_10_0302.xml",
|
||
"product_code":"cce",
|
||
"code":"64",
|
||
"des":"Before the upgrade, you can check whether your cluster can be upgraded and which versions are available on the CCE console. For details, see Process and Method of Upgradi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Deprecated APIs,Before You Start,Upgrading a Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Before You Start",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0560.html",
|
||
"node_id":"cce_10_0560.xml",
|
||
"product_code":"cce",
|
||
"code":"65",
|
||
"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":"usermanual2",
|
||
"kw":"Performing Post-Upgrade Verification",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Performing Post-Upgrade Verification",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0568.html",
|
||
"node_id":"cce_10_0568.xml",
|
||
"product_code":"cce",
|
||
"code":"66",
|
||
"des":"After a cluster is upgraded, check whether the cluster is in the Running state.CCE automatically checks your cluster status. Go to the cluster list page and confirm the c",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Cluster Status Check,Performing Post-Upgrade Verification,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cluster Status Check",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0569.html",
|
||
"node_id":"cce_10_0569.xml",
|
||
"product_code":"cce",
|
||
"code":"67",
|
||
"des":"After a cluster is upgraded, check whether nodes in the cluster are in the Running state.CCE automatically checks your node statuses. Go to the node list page and confirm",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Status Check,Performing Post-Upgrade Verification,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Status Check",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0567.html",
|
||
"node_id":"cce_10_0567.xml",
|
||
"product_code":"cce",
|
||
"code":"68",
|
||
"des":"After a cluster is upgraded, check whether there are any nodes that skip the upgrade in the cluster. These nodes may affect the proper running of the cluster.CCE automati",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Skipping Check,Performing Post-Upgrade Verification,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Skipping Check",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0561.html",
|
||
"node_id":"cce_10_0561.xml",
|
||
"product_code":"cce",
|
||
"code":"69",
|
||
"des":"After a cluster is upgraded, check whether its services are running properly.Different services have different verification mode. Select a suitable one and verify the ser",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Service Check,Performing Post-Upgrade Verification,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Service Check",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0565.html",
|
||
"node_id":"cce_10_0565.xml",
|
||
"product_code":"cce",
|
||
"code":"70",
|
||
"des":"Check whether nodes can be created in the cluster.If nodes cannot be created in your cluster after the cluster is upgraded, contact technical support.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"New Node Check,Performing Post-Upgrade Verification,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"New Node Check",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0566.html",
|
||
"node_id":"cce_10_0566.xml",
|
||
"product_code":"cce",
|
||
"code":"71",
|
||
"des":"Check whether pods can be created on the existing nodes after the cluster is upgraded.Check whether pods can be created on new nodes after the cluster is upgraded.After c",
|
||
"doc_type":"usermanual2",
|
||
"kw":"New Pod Check,Performing Post-Upgrade Verification,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"New Pod Check",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0210.html",
|
||
"node_id":"cce_10_0210.xml",
|
||
"product_code":"cce",
|
||
"code":"72",
|
||
"des":"This section describes how to migrate services from a cluster of an earlier version to a cluster of a later version in CCE.This operation is applicable when a cross-versi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Migrating Services Across Clusters of Different Versions,Upgrading a Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Migrating Services Across Clusters of Different Versions",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0550.html",
|
||
"node_id":"cce_10_0550.xml",
|
||
"product_code":"cce",
|
||
"code":"73",
|
||
"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":"usermanual2",
|
||
"kw":"Troubleshooting for Pre-upgrade Check Exceptions",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Troubleshooting for Pre-upgrade Check Exceptions",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0549.html",
|
||
"node_id":"cce_10_0549.xml",
|
||
"product_code":"cce",
|
||
"code":"74",
|
||
"des":"The system automatically checks a cluster before its upgrade. If the cluster does not meet the pre-upgrade check conditions, the upgrade cannot continue. To avoid risks, ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Pre-upgrade Check,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Pre-upgrade Check",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0431.html",
|
||
"node_id":"cce_10_0431.xml",
|
||
"product_code":"cce",
|
||
"code":"75",
|
||
"des":"Check the following items:Check whether the node is available.Check whether the node OS supports the upgrade.Check whether the node is marked with unexpected node pool la",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Restrictions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Restrictions",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0432.html",
|
||
"node_id":"cce_10_0432.xml",
|
||
"product_code":"cce",
|
||
"code":"76",
|
||
"des":"Check whether the target cluster is under upgrade management.CCE may temporarily restrict the cluster upgrade due to the following reasons:The cluster is identified as th",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Upgrade Management,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Upgrade Management",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0433.html",
|
||
"node_id":"cce_10_0433.xml",
|
||
"product_code":"cce",
|
||
"code":"77",
|
||
"des":"Check the following items:Check whether the add-on status is normal.Check whether the add-on supports the target version.Scenario 1: The add-on malfunctions.Log in to the",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Add-ons,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Add-ons",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0434.html",
|
||
"node_id":"cce_10_0434.xml",
|
||
"product_code":"cce",
|
||
"code":"78",
|
||
"des":"Check whether the current HelmRelease record contains discarded Kubernetes APIs that are not supported by the target cluster version. If yes, the Helm chart may be unavai",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Helm Charts,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Helm Charts",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0435.html",
|
||
"node_id":"cce_10_0435.xml",
|
||
"product_code":"cce",
|
||
"code":"79",
|
||
"des":"Check whether your master nodes can be accessed using SSH.There is a low probability that the SSH connectivity check fails due to network fluctuations. Perform the pre-up",
|
||
"doc_type":"usermanual2",
|
||
"kw":"SSH Connectivity of Master Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"SSH Connectivity of Master Nodes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0436.html",
|
||
"node_id":"cce_10_0436.xml",
|
||
"product_code":"cce",
|
||
"code":"80",
|
||
"des":"Check the node pool status.Check whether the node pool OS or container runtime is supported after the upgrade.Scenario: The node pool malfunctions.Log in to the CCE conso",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Pools,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Pools",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0437.html",
|
||
"node_id":"cce_10_0437.xml",
|
||
"product_code":"cce",
|
||
"code":"81",
|
||
"des":"Check whether the Protocol & Port of the worker node security groups is set to ICMP: All and whether the security group with the source IP address set to the master node ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Security Groups,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Security Groups",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0439.html",
|
||
"node_id":"cce_10_0439.xml",
|
||
"product_code":"cce",
|
||
"code":"82",
|
||
"des":"Check whether nodes need to be migrated.This issue is caused by either an error in the node's package pull component or the absence of key system components on the node, ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Residual Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Residual Nodes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0440.html",
|
||
"node_id":"cce_10_0440.xml",
|
||
"product_code":"cce",
|
||
"code":"83",
|
||
"des":"Check whether there are discarded resources in the clusters.Scenario 1: The Service in the clusters of v1.25 or later has discarded annotation tolerate-unready-endpoints.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Discarded Kubernetes Resources,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Discarded Kubernetes Resources",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0441.html",
|
||
"node_id":"cce_10_0441.xml",
|
||
"product_code":"cce",
|
||
"code":"84",
|
||
"des":"Read the version compatibility differences and ensure that they are not affected. The patch upgrade does not involve version compatibility differences.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Compatibility Risks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Compatibility Risks",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0442.html",
|
||
"node_id":"cce_10_0442.xml",
|
||
"product_code":"cce",
|
||
"code":"85",
|
||
"des":"Check whether cce-agent on the current node is of the latest version.Scenario 1: The error message \"you cce-agent no update, please restart it\" is displayed.cce-agent doe",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CCE Agent Versions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CCE Agent Versions",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0443.html",
|
||
"node_id":"cce_10_0443.xml",
|
||
"product_code":"cce",
|
||
"code":"86",
|
||
"des":"Check whether the node's CPU usage is above 90%.Upgrade the cluster during off-peak hours.Check whether too many pods are deployed on the node. If yes, reschedule pods to",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node CPU Usage,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node CPU Usage",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0444.html",
|
||
"node_id":"cce_10_0444.xml",
|
||
"product_code":"cce",
|
||
"code":"87",
|
||
"des":"Check the following items:Check whether the key CRD packageversions.version.cce.io of the cluster is deleted.Check whether the cluster key CRD network-attachment-definiti",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CRDs,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CRDs",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0445.html",
|
||
"node_id":"cce_10_0445.xml",
|
||
"product_code":"cce",
|
||
"code":"88",
|
||
"des":"Check the following items:Check whether the key data disks on the node meet the upgrade requirements.Check whether the /tmp directory has 500 MB available space.During th",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Disks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Disks",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0446.html",
|
||
"node_id":"cce_10_0446.xml",
|
||
"product_code":"cce",
|
||
"code":"89",
|
||
"des":"Check the following items:Check whether the DNS configuration of the current node can resolve the OBS address.Check whether the current node can access the OBS address of",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node DNS,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node DNS",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0447.html",
|
||
"node_id":"cce_10_0447.xml",
|
||
"product_code":"cce",
|
||
"code":"90",
|
||
"des":"Check whether the owner and owner group of the files in the /var/paas directory used by the CCE are both paas.Scenario 1: The error message \"xx file permission has been c",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Key Directory File Permissions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Key Directory File Permissions",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0448.html",
|
||
"node_id":"cce_10_0448.xml",
|
||
"product_code":"cce",
|
||
"code":"91",
|
||
"des":"Check whether the kubelet on the node is running properly.Scenario 1: The kubelet status is abnormal.If the kubelet malfunctions, the node is unavailable. Restore the nod",
|
||
"doc_type":"usermanual2",
|
||
"kw":"kubelet,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"kubelet",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0449.html",
|
||
"node_id":"cce_10_0449.xml",
|
||
"product_code":"cce",
|
||
"code":"92",
|
||
"des":"Check whether the node's memory usage is above 90%.Upgrade the cluster during off-peak hours.Check whether too many pods are deployed on the node. If yes, reschedule pods",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Memory,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Memory",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0450.html",
|
||
"node_id":"cce_10_0450.xml",
|
||
"product_code":"cce",
|
||
"code":"93",
|
||
"des":"Check whether the clock synchronization server ntpd or chronyd of the node is running properly.Scenario 1: ntpd is running abnormally.Log in to the node and run the syste",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Clock Synchronization Server,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Clock Synchronization Server",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0451.html",
|
||
"node_id":"cce_10_0451.xml",
|
||
"product_code":"cce",
|
||
"code":"94",
|
||
"des":"Check whether the OS kernel version of the node is supported by CCE.Case 1: The node image is not a standard CCE image.CCE nodes run depending on the initial standard ker",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node OS,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node OS",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0452.html",
|
||
"node_id":"cce_10_0452.xml",
|
||
"product_code":"cce",
|
||
"code":"95",
|
||
"des":"Check and make sure that the master nodes in your cluster have more than 2 CPU cores.The number of CPU cores on the master nodes is 2, which may lead to a cluster upgrade",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node CPU Cores,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node CPU Cores",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0453.html",
|
||
"node_id":"cce_10_0453.xml",
|
||
"product_code":"cce",
|
||
"code":"96",
|
||
"des":"Check whether the Python commands are available on a node.If the command output is not 0, the check fails.Reset the node or manually install Python before attempting the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Python Commands,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Python Commands",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0455.html",
|
||
"node_id":"cce_10_0455.xml",
|
||
"product_code":"cce",
|
||
"code":"97",
|
||
"des":"Check whether the nodes in the cluster are ready.Scenario 1: The nodes are in the unavailable status.Log in to the CCE console and click the cluster name to access the cl",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Readiness,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Readiness",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0456.html",
|
||
"node_id":"cce_10_0456.xml",
|
||
"product_code":"cce",
|
||
"code":"98",
|
||
"des":"Check whether journald of a node is normal.Log in to the node and run the systemctl is-active systemd-journald command to obtain the running status of journald. If the co",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node journald,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node journald",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0457.html",
|
||
"node_id":"cce_10_0457.xml",
|
||
"product_code":"cce",
|
||
"code":"99",
|
||
"des":"Check whether the containerd.sock file is on the node. This file affects the startup of container runtime in the Euler OS.Scenario: The Docker used by the node is the cus",
|
||
"doc_type":"usermanual2",
|
||
"kw":"containerd.sock,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"containerd.sock",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0458.html",
|
||
"node_id":"cce_10_0458.xml",
|
||
"product_code":"cce",
|
||
"code":"100",
|
||
"des":"This check item is not typical and implies that an internal error was found during the pre-upgrade check.Perform the pre-upgrade check again.If it fails again, submit a s",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Internal Error,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Internal Error",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0459.html",
|
||
"node_id":"cce_10_0459.xml",
|
||
"product_code":"cce",
|
||
"code":"101",
|
||
"des":"Check whether there are inaccessible mount points on the node.Scenario: There are inaccessible mount points on the node.If NFS (such as obsfs or SFS) is used by the node ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Mount Points,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Mount Points",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0460.html",
|
||
"node_id":"cce_10_0460.xml",
|
||
"product_code":"cce",
|
||
"code":"102",
|
||
"des":"Check whether the taint needed for cluster upgrade exists on the node.Scenario 1: The node is skipped during the cluster upgrade.If the version of the node is different f",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Kubernetes Node Taints,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes Node Taints",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0478.html",
|
||
"node_id":"cce_10_0478.xml",
|
||
"product_code":"cce",
|
||
"code":"103",
|
||
"des":"Check whether there are any compatibility restrictions on the current Everest add-on.There are compatibility restrictions on the current Everest add-on and it cannot be u",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Everest Restrictions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Everest Restrictions",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0479.html",
|
||
"node_id":"cce_10_0479.xml",
|
||
"product_code":"cce",
|
||
"code":"104",
|
||
"des":"Check whether there are compatibility limitations between the current and target cce-controller-hpa add-on versions.There are compatibility limitations between the curren",
|
||
"doc_type":"usermanual2",
|
||
"kw":"cce-hpa-controller Limitations,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"cce-hpa-controller Limitations",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0480.html",
|
||
"node_id":"cce_10_0480.xml",
|
||
"product_code":"cce",
|
||
"code":"105",
|
||
"des":"Check whether the current cluster version and the target version support enhanced CPU policy.Scenario: Only the current cluster version supports the enhanced CPU policy f",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Enhanced CPU Policies,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Enhanced CPU Policies",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0484.html",
|
||
"node_id":"cce_10_0484.xml",
|
||
"product_code":"cce",
|
||
"code":"106",
|
||
"des":"Check whether the container runtime and network components on the worker nodes are healthy.Issue 1: CNI Agent is not active.If your cluster version is earlier than v1.17.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Health of Worker Node Components,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Health of Worker Node Components",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0485.html",
|
||
"node_id":"cce_10_0485.xml",
|
||
"product_code":"cce",
|
||
"code":"107",
|
||
"des":"Check whether cluster components such as the Kubernetes component, container runtime component, and network component are running properly before the upgrade.Perform the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Health of Master Node Components,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Health of Master Node Components",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0486.html",
|
||
"node_id":"cce_10_0486.xml",
|
||
"product_code":"cce",
|
||
"code":"108",
|
||
"des":"Check whether the resources of Kubernetes components, such as etcd and kube-controller-manager, exceed the upper limit.Solution 1: Reduce Kubernetes resources that are ne",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Memory Resource Limit of Kubernetes Components,Troubleshooting for Pre-upgrade Check Exceptions,User",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Memory Resource Limit of Kubernetes Components",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0487.html",
|
||
"node_id":"cce_10_0487.xml",
|
||
"product_code":"cce",
|
||
"code":"109",
|
||
"des":"The system scans the audit logs of the past day to check whether the user calls the deprecated APIs of the target Kubernetes version.Due to the limited time range of audi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Discarded Kubernetes APIs,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Discarded Kubernetes APIs",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0488.html",
|
||
"node_id":"cce_10_0488.xml",
|
||
"product_code":"cce",
|
||
"code":"110",
|
||
"des":"If IPv6 is enabled for a CCE Turbo cluster, check whether the target cluster version supports IPv6.CCE Turbo clusters support IPv6 since v1.23. This feature is available ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"IPv6 Support in CCE Turbo Clusters,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"IPv6 Support in CCE Turbo Clusters",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0489.html",
|
||
"node_id":"cce_10_0489.xml",
|
||
"product_code":"cce",
|
||
"code":"111",
|
||
"des":"Check whether NetworkManager of a node is normal.Log in to the node and run the systemctl is-active NetworkManager command to obtain the running status of NetworkManager.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"NetworkManager,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"NetworkManager",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0490.html",
|
||
"node_id":"cce_10_0490.xml",
|
||
"product_code":"cce",
|
||
"code":"112",
|
||
"des":"Check the ID file format.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node ID File,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node ID File",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0491.html",
|
||
"node_id":"cce_10_0491.xml",
|
||
"product_code":"cce",
|
||
"code":"113",
|
||
"des":"When you upgrade a cluster to v1.19 or later, the system checks whether the following configuration files have been modified on the backend:/opt/cloud/cce/kubernetes/kube",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Configuration Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Configuration Consistency",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0492.html",
|
||
"node_id":"cce_10_0492.xml",
|
||
"product_code":"cce",
|
||
"code":"114",
|
||
"des":"Check whether the configuration files of key components exist on the node.The following table lists the files to be checked.Reset the node. For details, see Resetting a N",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Configuration File,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Configuration File",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0493.html",
|
||
"node_id":"cce_10_0493.xml",
|
||
"product_code":"cce",
|
||
"code":"115",
|
||
"des":"Check whether the current CoreDNS key configuration Corefile is different from the Helm release record. The difference may be overwritten during the add-on upgrade, affec",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CoreDNS Configuration Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CoreDNS Configuration Consistency",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0494.html",
|
||
"node_id":"cce_10_0494.xml",
|
||
"product_code":"cce",
|
||
"code":"116",
|
||
"des":"Check whether the sudo commands and sudo-related files of the node are working.Scenario 1: The sudo command fails to be executed.During the in-place cluster upgrade, the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"sudo,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"sudo",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0495.html",
|
||
"node_id":"cce_10_0495.xml",
|
||
"product_code":"cce",
|
||
"code":"117",
|
||
"des":"Whether some key commands that the node upgrade depends on are workingScenario 1: Executing the package manager command failed.Executing the rpm or dpkg command failed. I",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Key Node Commands,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Key Node Commands",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0496.html",
|
||
"node_id":"cce_10_0496.xml",
|
||
"product_code":"cce",
|
||
"code":"118",
|
||
"des":"Check whether the docker/containerd.sock file is directly mounted to the pods on a node. During an upgrade, Docker or containerd restarts and the sock file on the host ch",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Mounting of a Sock File on a Node,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Mounting of a Sock File on a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0497.html",
|
||
"node_id":"cce_10_0497.xml",
|
||
"product_code":"cce",
|
||
"code":"119",
|
||
"des":"Check whether the certificate used by an HTTPS load balancer has been modified on ELB.The certificate referenced by an HTTPS ingress created on CCE is modified on the ELB",
|
||
"doc_type":"usermanual2",
|
||
"kw":"HTTPS Load Balancer Certificate Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Gu",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"HTTPS Load Balancer Certificate Consistency",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0498.html",
|
||
"node_id":"cce_10_0498.xml",
|
||
"product_code":"cce",
|
||
"code":"120",
|
||
"des":"Check whether the default mount directory and soft link on the node have been manually mounted or modified.Non-shared diskBy default, /var/lib/docker, containerd, or /mnt",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Mounting,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Mounting",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0499.html",
|
||
"node_id":"cce_10_0499.xml",
|
||
"product_code":"cce",
|
||
"code":"121",
|
||
"des":"Check whether user paas is allowed to log in to a node.Run the following command to check whether user paas is allowed to log in to a node:If the permissions assigned to ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Login Permissions of User paas on a Node,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Login Permissions of User paas on a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0500.html",
|
||
"node_id":"cce_10_0500.xml",
|
||
"product_code":"cce",
|
||
"code":"122",
|
||
"des":"Check whether the load balancer associated with a Service is allocated with a private IPv4 address.Solution 1: Delete the Service that is associated with a load balancer ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Private IPv4 Addresses of Load Balancers,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Private IPv4 Addresses of Load Balancers",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0501.html",
|
||
"node_id":"cce_10_0501.xml",
|
||
"product_code":"cce",
|
||
"code":"123",
|
||
"des":"Check the historical upgrade records of the cluster and confirm that the current version of the cluster meets the requirements for upgrading to the target version.Upgradi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Historical Upgrade Records,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Historical Upgrade Records",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0502.html",
|
||
"node_id":"cce_10_0502.xml",
|
||
"product_code":"cce",
|
||
"code":"124",
|
||
"des":"Check whether the CIDR block of the cluster management plane is the same as that configured on the backbone network.The CIDR block of the management plane has been modifi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CIDR Block of the Cluster Management Plane,Troubleshooting for Pre-upgrade Check Exceptions,User Gui",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CIDR Block of the Cluster Management Plane",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0503.html",
|
||
"node_id":"cce_10_0503.xml",
|
||
"product_code":"cce",
|
||
"code":"125",
|
||
"des":"The GPU add-on is involved in the upgrade, which may affect the GPU driver installation during the creation of a GPU node.The GPU add-on driver needs to be configured by ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"GPU Add-on,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"GPU Add-on",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0504.html",
|
||
"node_id":"cce_10_0504.xml",
|
||
"product_code":"cce",
|
||
"code":"126",
|
||
"des":"Check whether the default system parameter settings on your nodes are modified.If the MTU value of the bond0 network on your BMS node is not the default value 1500, this ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Nodes' System Parameters,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Nodes' System Parameters",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0505.html",
|
||
"node_id":"cce_10_0505.xml",
|
||
"product_code":"cce",
|
||
"code":"127",
|
||
"des":"Check whether there are residual package version data in the current cluster.A message is displayed indicating that there are residual 10.12.1.109 CRD resources in your c",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Residual Package Version Data,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Residual Package Version Data",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0506.html",
|
||
"node_id":"cce_10_0506.xml",
|
||
"product_code":"cce",
|
||
"code":"128",
|
||
"des":"Check whether the commands required for the upgrade are available on the node.The cluster upgrade failure is typically caused by the lack of key node commands that are re",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Commands,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Commands",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0507.html",
|
||
"node_id":"cce_10_0507.xml",
|
||
"product_code":"cce",
|
||
"code":"129",
|
||
"des":"Check whether swap has been enabled on CCE nodes.By default, swap is disabled on CCE nodes. Check the necessity of enabling swap manually and determine the impact of disa",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Swap,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Swap",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0508.html",
|
||
"node_id":"cce_10_0508.xml",
|
||
"product_code":"cce",
|
||
"code":"130",
|
||
"des":"Check item 1: Check whether there is an Nginx Ingress route whose ingress type is not specified (kubernetes.io/ingress.class: nginx is not added to annotations) in the cl",
|
||
"doc_type":"usermanual2",
|
||
"kw":"nginx-ingress Upgrade,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"nginx-ingress Upgrade",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0510.html",
|
||
"node_id":"cce_10_0510.xml",
|
||
"product_code":"cce",
|
||
"code":"131",
|
||
"des":"Check whether the service pods running on a containerd node are restarted when containerd is upgraded.containerd on your node may need to be restarted. To minimize the im",
|
||
"doc_type":"usermanual2",
|
||
"kw":"containerd Pod Restart Risks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"containerd Pod Restart Risks",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0511.html",
|
||
"node_id":"cce_10_0511.xml",
|
||
"product_code":"cce",
|
||
"code":"132",
|
||
"des":"Check whether the configuration of the CCE AI Suite add-on in a cluster has been intrusively modified. If so, upgrading the cluster may fail.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Key GPU Add-on Parameters,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Key GPU Add-on Parameters",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0512.html",
|
||
"node_id":"cce_10_0512.xml",
|
||
"product_code":"cce",
|
||
"code":"133",
|
||
"des":"Check whether GPU service pods are rebuilt in a cluster when kubelet is restarted during the upgrade of the cluster.Upgrade the cluster when the impact on services is con",
|
||
"doc_type":"usermanual2",
|
||
"kw":"GPU Pod Rebuild Risks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"GPU Pod Rebuild Risks",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0513.html",
|
||
"node_id":"cce_10_0513.xml",
|
||
"product_code":"cce",
|
||
"code":"134",
|
||
"des":"Check whether ELB listener access control has been configured for the Services in the current cluster using annotations.If so, check whether their configurations are corr",
|
||
"doc_type":"usermanual2",
|
||
"kw":"ELB Listener Access Control,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"ELB Listener Access Control",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0514.html",
|
||
"node_id":"cce_10_0514.xml",
|
||
"product_code":"cce",
|
||
"code":"135",
|
||
"des":"Check whether the flavor of the master nodes in the cluster is the same as the actual flavor of these nodes.This issue is typically caused by modifications made to the ma",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Master Node Flavor,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Master Node Flavor",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0515.html",
|
||
"node_id":"cce_10_0515.xml",
|
||
"product_code":"cce",
|
||
"code":"136",
|
||
"des":"Check whether the number of available IP addresses in the cluster subnet supports rolling upgrade.Rolling upgrade is not supported if there are not enough IP addresses in",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Subnet Quota of Master Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Subnet Quota of Master Nodes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0516.html",
|
||
"node_id":"cce_10_0516.xml",
|
||
"product_code":"cce",
|
||
"code":"137",
|
||
"des":"Check whether an alarm is generated when a cluster is upgraded to v1.27 or later. Do not use Docker in clusters of versions later than 1.27.If your node's runtime is not ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Runtime,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Runtime",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0517.html",
|
||
"node_id":"cce_10_0517.xml",
|
||
"product_code":"cce",
|
||
"code":"138",
|
||
"des":"Check whether an alarm is generated when a cluster is upgraded to v1.27 or later. Do not use Docker in clusters of versions later than 1.27.If your node pool's runtime is",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Pool Runtime,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Pool Runtime",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0518.html",
|
||
"node_id":"cce_10_0518.xml",
|
||
"product_code":"cce",
|
||
"code":"139",
|
||
"des":"Check the number of images on your node. If there are more than 1000 images, it takes a long time for Docker to start, affecting the standard Docker output and functions ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Number of Node Images,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Number of Node Images",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0520.html",
|
||
"node_id":"cce_10_0520.xml",
|
||
"product_code":"cce",
|
||
"code":"140",
|
||
"des":"Check whether the target version supports secret encryption. If it does not, clusters that have this feature enabled cannot be upgraded to the target version.Secret encry",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Compatibility Check of Secret Encryption,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Compatibility Check of Secret Encryption",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0521.html",
|
||
"node_id":"cce_10_0521.xml",
|
||
"product_code":"cce",
|
||
"code":"141",
|
||
"des":"Make sure that the GPU add-on and Ubuntu nodes are compatible before using them in a cluster. If the Ubuntu kernel is 5.15.0-113-generic, the driver of the GPU add-on mus",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Compatibility Between the Ubuntu Kernel and GPU Driver,Troubleshooting for Pre-upgrade Check Excepti",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Compatibility Between the Ubuntu Kernel and GPU Driver",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0522.html",
|
||
"node_id":"cce_10_0522.xml",
|
||
"product_code":"cce",
|
||
"code":"142",
|
||
"des":"An unfinished drainage task is detected in the cluster, which may resume after the upgrade. If this happens, running pods will be evicted, which could impact your service",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Drainage Tasks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Drainage Tasks",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0523.html",
|
||
"node_id":"cce_10_0523.xml",
|
||
"product_code":"cce",
|
||
"code":"143",
|
||
"des":"Check the number of image layers on your node. If there are more than 5000 layers, it will take a long time for Docker or containerd to start, affecting the stdout of Doc",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Image Layers on a Node,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Image Layers on a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0524.html",
|
||
"node_id":"cce_10_0524.xml",
|
||
"product_code":"cce",
|
||
"code":"144",
|
||
"des":"Check whether your cluster is eligible for a rolling upgrade. The result shows that the rolling upgrade is not supported.Rolling upgrades cannot be performed if the tenan",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Cluster Rolling Upgrade,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cluster Rolling Upgrade",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0525.html",
|
||
"node_id":"cce_10_0525.xml",
|
||
"product_code":"cce",
|
||
"code":"145",
|
||
"des":"Check whether the number of certificates on your node is greater than 1000. During an upgrade, certificate files will be processed in batches. An excessive number of cert",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Rotation Certificates,Troubleshooting for Pre-upgrade Check Exceptions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Rotation Certificates",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0526.html",
|
||
"node_id":"cce_10_0526.xml",
|
||
"product_code":"cce",
|
||
"code":"146",
|
||
"des":"Check whether any modifications have been made to the listener, forwarding policy, forwarding rule, backend cloud server group, backend cloud server, or certificate confi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Ingress and ELB Configuration Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Guid",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Ingress and ELB Configuration Consistency",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0183.html",
|
||
"node_id":"cce_10_0183.xml",
|
||
"product_code":"cce",
|
||
"code":"147",
|
||
"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":"usermanual2",
|
||
"kw":"Nodes",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Nodes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0180.html",
|
||
"node_id":"cce_10_0180.xml",
|
||
"product_code":"cce",
|
||
"code":"148",
|
||
"des":"A container cluster consists of a set of worker machines, called nodes, that run containerized applications. A node can be a virtual machine (VM) or a physical machine (P",
|
||
"doc_type":"usermanual2",
|
||
"kw":"paas,user group,Node Overview,Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0462.html",
|
||
"node_id":"cce_10_0462.xml",
|
||
"product_code":"cce",
|
||
"code":"149",
|
||
"des":"Container engines, one of the most important components of Kubernetes, manage the lifecycle of images and containers. The kubelet interacts with a container runtime throu",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Container Engines,Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Container Engines",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0476.html",
|
||
"node_id":"cce_10_0476.xml",
|
||
"product_code":"cce",
|
||
"code":"150",
|
||
"des":"This section describes the mappings between released cluster versions and OS versions.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node OSs,Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node OSs",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0363.html",
|
||
"node_id":"cce_10_0363.xml",
|
||
"product_code":"cce",
|
||
"code":"151",
|
||
"des":"At least one cluster has been created.A key pair has been created for identity authentication upon remote node login.The DNS configuration of a subnet where a node is loc",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a Node,Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0198.html",
|
||
"node_id":"cce_10_0198.xml",
|
||
"product_code":"cce",
|
||
"code":"152",
|
||
"des":"In CCE, you can create a node (Creating a Node) or add existing nodes (ECSs) to your cluster for management.When accepting an ECS, you can reset the ECS OS to a standard ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Accepting Nodes for Management,Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Accepting Nodes for Management",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0185.html",
|
||
"node_id":"cce_10_0185.xml",
|
||
"product_code":"cce",
|
||
"code":"153",
|
||
"des":"Before you log in to a node using SSH, ensure that the SSH port (22 by default) is enabled in the security group of the node.Before you log in to a node (an ECS) using SS",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Logging In to a Node,Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Logging In to a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0672.html",
|
||
"node_id":"cce_10_0672.xml",
|
||
"product_code":"cce",
|
||
"code":"154",
|
||
"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":"usermanual2",
|
||
"kw":"node labels",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Management Nodes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0004.html",
|
||
"node_id":"cce_10_0004.xml",
|
||
"product_code":"cce",
|
||
"code":"155",
|
||
"des":"You can add different labels to nodes and define different attributes for labels. By using these node labels, you can quickly understand the characteristics of each node.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"node labels,Inherent Label of a Node,Managing Node Labels,Management Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Managing Node Labels",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0352.html",
|
||
"node_id":"cce_10_0352.xml",
|
||
"product_code":"cce",
|
||
"code":"156",
|
||
"des":"Taints enable a node to repel specific pods to prevent these pods from being scheduled to the node.On the CCE console, you can also batch manage nodes' taints.Enter the k",
|
||
"doc_type":"usermanual2",
|
||
"kw":"NoSchedule,PreferNoSchedule,NoExecute,System Taints,Managing Node Taints,Management Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Managing Node Taints",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0003.html",
|
||
"node_id":"cce_10_0003.xml",
|
||
"product_code":"cce",
|
||
"code":"157",
|
||
"des":"You can reset a node to modify the node configuration, such as the node OS and login mode.Resetting a node will reinstall the node OS and the Kubernetes software on the n",
|
||
"doc_type":"usermanual2",
|
||
"kw":"reset a node,Resetting a Node,Management Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Resetting a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0338.html",
|
||
"node_id":"cce_10_0338.xml",
|
||
"product_code":"cce",
|
||
"code":"158",
|
||
"des":"Removing a node from a cluster will re-install the node OS and clear CCE components on the node.Removing a node will not delete the server corresponding to the node. You ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Removing a Node,Management Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Removing a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0184.html",
|
||
"node_id":"cce_10_0184.xml",
|
||
"product_code":"cce",
|
||
"code":"159",
|
||
"des":"Each node in a cluster is a cloud server or physical machine. After a cluster node is created, you can change the cloud server name or specifications as required. Modifyi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"synchronize the ECS,Synchronizing the Data of Cloud Servers,Management Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Synchronizing the Data of Cloud Servers",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0605.html",
|
||
"node_id":"cce_10_0605.xml",
|
||
"product_code":"cce",
|
||
"code":"160",
|
||
"des":"After you enable nodal drainage on the console, CCE configures the node to be non-schedulable and securely evicts all pods that comply with Rules for Draining Nodes on th",
|
||
"doc_type":"usermanual2",
|
||
"kw":"nodal drainage,nodal drainage,Draining a Node,Management Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Draining a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0186.html",
|
||
"node_id":"cce_10_0186.xml",
|
||
"product_code":"cce",
|
||
"code":"161",
|
||
"des":"You can delete a pay-per-use node that is not needed from the node list.Deleting or unsubscribing from a node in a CCE cluster will release the node and services running ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Deleting a Node,Management Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Deleting a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0036.html",
|
||
"node_id":"cce_10_0036.xml",
|
||
"product_code":"cce",
|
||
"code":"162",
|
||
"des":"When a node in the cluster is stopped, all services on that node will also be stopped, and the node will no longer be available for scheduling. Check if your services wil",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Stopping a Node,Management Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Stopping a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0276.html",
|
||
"node_id":"cce_10_0276.xml",
|
||
"product_code":"cce",
|
||
"code":"163",
|
||
"des":"In a rolling upgrade, a new node is created, existing workloads are migrated to the new node, and then the old node is deleted. Figure 1 shows the migration process.The o",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Performing Rolling Upgrade for Nodes,Management Nodes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Performing Rolling Upgrade for Nodes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0704.html",
|
||
"node_id":"cce_10_0704.xml",
|
||
"product_code":"cce",
|
||
"code":"164",
|
||
"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":"usermanual2",
|
||
"kw":"Node O&M",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node O&M",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0178.html",
|
||
"node_id":"cce_10_0178.xml",
|
||
"product_code":"cce",
|
||
"code":"165",
|
||
"des":"Some node resources are used to run mandatory Kubernetes system components and resources to make the node as part of your cluster. Therefore, the total number of node res",
|
||
"doc_type":"usermanual2",
|
||
"kw":"total number of node resources,Node Resource Reservation Policy,Node O&M,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Resource Reservation Policy",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0341.html",
|
||
"node_id":"cce_10_0341.xml",
|
||
"product_code":"cce",
|
||
"code":"166",
|
||
"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":"usermanual2",
|
||
"kw":"Data Disk Space Allocation,Container engine and container image space,container engine and container",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Space Allocation of a Data Disk",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0348.html",
|
||
"node_id":"cce_10_0348.xml",
|
||
"product_code":"cce",
|
||
"code":"167",
|
||
"des":"The maximum number of pods that can be created on a node is calculated based on the cluster type:When creating a cluster in the VPC network model, specify the number of c",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Maximum Number of Pods on a Node,alpha.cce/fixPoolMask,maximum number of pods,Maximum Number of Pods",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Maximum Number of Pods That Can Be Created on a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0883.html",
|
||
"node_id":"cce_10_0883.xml",
|
||
"product_code":"cce",
|
||
"code":"168",
|
||
"des":"To maintain the stability of nodes, CCE stores Kubernetes and container runtime components on separate data disks. Kubernetes uses the /mnt/paas/kubernetes directory, and",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Differences in kubelet and Runtime Component Configurations Between CCE and the Native Community,Nod",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Differences in kubelet and Runtime Component Configurations Between CCE and the Native Community",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0601.html",
|
||
"node_id":"cce_10_0601.xml",
|
||
"product_code":"cce",
|
||
"code":"169",
|
||
"des":"Kubernetes has removed dockershim from v1.24 and does not support Docker by default. CCE is going to stop the support for Docker. Change the node container engine from Do",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Migrating Nodes from Docker to containerd,Node O&M,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Migrating Nodes from Docker to containerd",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0659.html",
|
||
"node_id":"cce_10_0659.xml",
|
||
"product_code":"cce",
|
||
"code":"170",
|
||
"des":"The node fault detection function depends on the NPD add-on. The add-on instances run on nodes and monitor nodes. This section describes how to enable node fault detectio",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Fault Detection,Check Items,Configuring Node Fault Detection Policies,Node O&M,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Node Fault Detection Policies",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10020_0.html",
|
||
"node_id":"cce_bestpractice_10020_0.xml",
|
||
"product_code":"cce",
|
||
"code":"171",
|
||
"des":"When creating a node, use the pre- or -installation commands to install tools or perform security hardening on the node. This section provides guidance for you to correct",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Executing the Pre- or Post-installation Commands During Node Creation,Node O&M,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Executing the Pre- or Post-installation Commands During Node Creation",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0035.html",
|
||
"node_id":"cce_10_0035.xml",
|
||
"product_code":"cce",
|
||
"code":"172",
|
||
"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":"usermanual2",
|
||
"kw":"Node Pools",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Pools",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0081.html",
|
||
"node_id":"cce_10_0081.xml",
|
||
"product_code":"cce",
|
||
"code":"173",
|
||
"des":"CCE introduces node pools to help you better manage nodes in Kubernetes clusters. A node pool contains one node or a group of nodes with identical configuration in a clus",
|
||
"doc_type":"usermanual2",
|
||
"kw":"DefaultPool,DefaultPool,Deploying a Workload in a Specified Node Pool,Node Pool Overview,Node Pools,",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Pool Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0012.html",
|
||
"node_id":"cce_10_0012.xml",
|
||
"product_code":"cce",
|
||
"code":"174",
|
||
"des":"This section describes how to create a node pool and perform operations on the node pool. For details about how a node pool works, see Node Pool Overview.Basic SettingsCo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a Node Pool,Node Pools,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a Node Pool",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0658.html",
|
||
"node_id":"cce_10_0658.xml",
|
||
"product_code":"cce",
|
||
"code":"175",
|
||
"des":"You can specify a specification in a node pool for scaling.The default node pool does not support scaling. Use Creating a Node to add a node.Add or reduce nodes for scali",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Scaling a Node Pool,Node Pools,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Scaling a Node Pool",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0222.html",
|
||
"node_id":"cce_10_0222.xml",
|
||
"product_code":"cce",
|
||
"code":"176",
|
||
"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":"usermanual2",
|
||
"kw":"Managing a Node Pool",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Managing a Node Pool",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0653.html",
|
||
"node_id":"cce_10_0653.xml",
|
||
"product_code":"cce",
|
||
"code":"177",
|
||
"des":"Changes to the container engine, OS, or pre-/post-installation script in a node pool take effect only on new nodes. To synchronize the modification onto existing nodes, m",
|
||
"doc_type":"usermanual2",
|
||
"kw":"base size,Updating a Node Pool,Managing a Node Pool,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Updating a Node Pool",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0727.html",
|
||
"node_id":"cce_10_0727.xml",
|
||
"product_code":"cce",
|
||
"code":"178",
|
||
"des":"Auto Scaling (AS) enables elastic scaling of nodes in a node pool based on scaling policies. Without this function, you have to manually adjust the number of nodes in a n",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Updating an AS Configuration,Managing a Node Pool,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Updating an AS Configuration",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0652.html",
|
||
"node_id":"cce_10_0652.xml",
|
||
"product_code":"cce",
|
||
"code":"179",
|
||
"des":"The default node pool does not support the following management operations.CCE allows you to highly customize Kubernetes parameter settings on core components in a cluste",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Modifying Node Pool Configurations,Managing a Node Pool,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Modifying Node Pool Configurations",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0886.html",
|
||
"node_id":"cce_10_0886.xml",
|
||
"product_code":"cce",
|
||
"code":"180",
|
||
"des":"If you want to add a newly created ECS to a node pool in a cluster, or remove a node from a node pool and add it to the node pool again, accept the node.When an ECS is ac",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Accepting Nodes in a Node Pool,Managing a Node Pool,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Accepting Nodes in a Node Pool",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0655.html",
|
||
"node_id":"cce_10_0655.xml",
|
||
"product_code":"cce",
|
||
"code":"181",
|
||
"des":"You can copy the configuration of an existing node pool on the CCE console to create new node pools.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Copying a Node Pool,Managing a Node Pool,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Copying a Node Pool",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0654.html",
|
||
"node_id":"cce_10_0654.xml",
|
||
"product_code":"cce",
|
||
"code":"182",
|
||
"des":"After the configuration of a node pool is updated, some configurations cannot be automatically synchronized for existing nodes. You can manually synchronize configuration",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Synchronizing Node Pools,Managing a Node Pool,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Synchronizing Node Pools",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0660.html",
|
||
"node_id":"cce_10_0660.xml",
|
||
"product_code":"cce",
|
||
"code":"183",
|
||
"des":"After CCE releases a new OS image, if existing nodes cannot be automatically upgraded, you can manually upgrade them in batches.This section describes how to upgrade an O",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Upgrading an OS,Managing a Node Pool,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Upgrading an OS",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0656.html",
|
||
"node_id":"cce_10_0656.xml",
|
||
"product_code":"cce",
|
||
"code":"184",
|
||
"des":"You can migrate nodes between node pools within a cluster. Table 1 lists migration scenarios.Migration scenariosMigration ScenarioMigrationOperationSource Node PoolTarget",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Migrating a Node,Managing a Node Pool,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Migrating a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0657.html",
|
||
"node_id":"cce_10_0657.xml",
|
||
"product_code":"cce",
|
||
"code":"185",
|
||
"des":"Deleting a node pool will delete nodes in the pool. Pods on these nodes will be automatically migrated to available nodes in other node pools.Deleting a node pool will de",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Deleting a Node Pool,Managing a Node Pool,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Deleting a Node Pool",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0046.html",
|
||
"node_id":"cce_10_0046.xml",
|
||
"product_code":"cce",
|
||
"code":"186",
|
||
"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":"usermanual2",
|
||
"kw":"Workloads",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Workloads",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0006.html",
|
||
"node_id":"cce_10_0006.xml",
|
||
"product_code":"cce",
|
||
"code":"187",
|
||
"des":"A workload is an application running on Kubernetes. No matter how many components are there in your workload, you can run it in a group of Kubernetes pods. A workload is ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Deployments,StatefulSets,DaemonSets,jobs,cron jobs,Overview,Workloads,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0673.html",
|
||
"node_id":"cce_10_0673.xml",
|
||
"product_code":"cce",
|
||
"code":"188",
|
||
"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":"usermanual2",
|
||
"kw":"Creating a Workload",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a Workload",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0047.html",
|
||
"node_id":"cce_10_0047.xml",
|
||
"product_code":"cce",
|
||
"code":"189",
|
||
"des":"Deployments are workloads (for example, Nginx) that do not store any data or status. You can create Deployments on the CCE console or by running kubectl commands.Before c",
|
||
"doc_type":"usermanual2",
|
||
"kw":"create a workload using kubectl,Creating a Deployment,Creating a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a Deployment",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0048.html",
|
||
"node_id":"cce_10_0048.xml",
|
||
"product_code":"cce",
|
||
"code":"190",
|
||
"des":"StatefulSets are a type of workloads whose data or status is stored while they are running. For example, MySQL is a StatefulSet because it needs to store new data.A conta",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using kubectl,Creating a StatefulSet,Creating a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a StatefulSet",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0216.html",
|
||
"node_id":"cce_10_0216.xml",
|
||
"product_code":"cce",
|
||
"code":"191",
|
||
"des":"CCE provides deployment and management capabilities for multiple types of containers and supports features of container workloads, including creation, configuration, moni",
|
||
"doc_type":"usermanual2",
|
||
"kw":"create a workload using kubectl,Creating a DaemonSet,Creating a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a DaemonSet",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0150.html",
|
||
"node_id":"cce_10_0150.xml",
|
||
"product_code":"cce",
|
||
"code":"192",
|
||
"des":"Jobs are short-lived and run for a certain time to completion. They can be executed immediately after being deployed. It is completed after it exits normally (exit 0).A j",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a Job,Creating a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a Job",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0151.html",
|
||
"node_id":"cce_10_0151.xml",
|
||
"product_code":"cce",
|
||
"code":"193",
|
||
"des":"A cron job runs on a repeating schedule. You can perform time synchronization for all active nodes at a fixed time point.A cron job runs periodically at the specified tim",
|
||
"doc_type":"usermanual2",
|
||
"kw":"time synchronization,Creating a Cron Job,Creating a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a Cron Job",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0130.html",
|
||
"node_id":"cce_10_0130.xml",
|
||
"product_code":"cce",
|
||
"code":"194",
|
||
"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":"usermanual2",
|
||
"kw":"Configuring a Workload",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring a Workload",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0463.html",
|
||
"node_id":"cce_10_0463.xml",
|
||
"product_code":"cce",
|
||
"code":"195",
|
||
"des":"The most significant difference is that each Kata container (pod) runs on an independent micro-VM, has an independent OS kernel, and is securely isolated at the virtualiz",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Secure Runtime and Common Runtime,Configuring a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Secure Runtime and Common Runtime",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0354.html",
|
||
"node_id":"cce_10_0354.xml",
|
||
"product_code":"cce",
|
||
"code":"196",
|
||
"des":"When creating a workload, you can configure containers to use the same time zone as the node. You can enable time zone synchronization when creating a workload.The time z",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Time Zone Synchronization,Configuring a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Time Zone Synchronization",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0353.html",
|
||
"node_id":"cce_10_0353.xml",
|
||
"product_code":"cce",
|
||
"code":"197",
|
||
"des":"When a workload is created, the container image is pulled from the image repository to the node. The image is also pulled when the workload is restarted or upgraded.By de",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring an Image Pull Policy,Configuring a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring an Image Pull Policy",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0009.html",
|
||
"node_id":"cce_10_0009.xml",
|
||
"product_code":"cce",
|
||
"code":"198",
|
||
"des":"CCE allows you to create workloads using images pulled from third-party image repositories.Generally, a third-party image repository can be accessed only after authentica",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using Third-Party Images,Configuring a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using Third-Party Images",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0163.html",
|
||
"node_id":"cce_10_0163.xml",
|
||
"product_code":"cce",
|
||
"code":"199",
|
||
"des":"CCE allows you to set resource requirements and limits, such as CPU and RAM, for added containers during workload creation. Kubernetes also allows using YAML to set requi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"ephemeral storage,Configuring Container Specifications,Configuring a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Container Specifications",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0105.html",
|
||
"node_id":"cce_10_0105.xml",
|
||
"product_code":"cce",
|
||
"code":"200",
|
||
"des":"CCE provides callback functions for the lifecycle management of containerized applications. For example, if you want a container to perform a certain operation before sto",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Startup Command,Post-Start,Pre-Stop,Configuring Container Lifecycle Parameters,Configuring a Workloa",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Container Lifecycle Parameters",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0112.html",
|
||
"node_id":"cce_10_0112.xml",
|
||
"product_code":"cce",
|
||
"code":"201",
|
||
"des":"Health check regularly checks the health status of containers during container running. If the health check function is not configured, a pod cannot detect application ex",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Health check,HTTP request,TCP port,CLI,Configuring Container Health Check,Configuring a Workload,Use",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Container Health Check",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0113.html",
|
||
"node_id":"cce_10_0113.xml",
|
||
"product_code":"cce",
|
||
"code":"202",
|
||
"des":"An environment variable is a variable whose value can affect the way a running container will behave. You can modify environment variables even after workloads are deploy",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Environment Variables,Configuring a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Environment Variables",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0397.html",
|
||
"node_id":"cce_10_0397.xml",
|
||
"product_code":"cce",
|
||
"code":"203",
|
||
"des":"In actual applications, upgrade is a common operation. A Deployment, StatefulSet, or DaemonSet can easily support application upgrade.You can set different upgrade polici",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Workload Upgrade Policies,Configuring a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Workload Upgrade Policies",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0728.html",
|
||
"node_id":"cce_10_0728.xml",
|
||
"product_code":"cce",
|
||
"code":"204",
|
||
"des":"Tolerations allow the scheduler to schedule pods to nodes with target taints. Tolerances work with node taints. Each node allows one or more taints. If no tolerance is co",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Tolerance Policies,Configuring a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Tolerance Policies",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0386.html",
|
||
"node_id":"cce_10_0386.xml",
|
||
"product_code":"cce",
|
||
"code":"205",
|
||
"des":"CCE allows you to add annotations to a YAML file to realize some advanced pod functions. The following table describes the annotations you can add.When you create a workl",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Labels and Annotations,Configuring a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Labels and Annotations",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0889.html",
|
||
"node_id":"cce_10_0889.xml",
|
||
"product_code":"cce",
|
||
"code":"206",
|
||
"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":"usermanual2",
|
||
"kw":"Scheduling a Workload",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Scheduling a Workload",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0232.html",
|
||
"node_id":"cce_10_0232.xml",
|
||
"product_code":"cce",
|
||
"code":"207",
|
||
"des":"Kubernetes schedules workloads based on pods. After you create a workload, the scheduler automatically assigns pods. For example, the scheduler distributes pods to nodes ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Scheduling a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0891.html",
|
||
"node_id":"cce_10_0891.xml",
|
||
"product_code":"cce",
|
||
"code":"208",
|
||
"des":"To select a node for scheduling in Kubernetes, simply configure the nodeSelector field in the workload. This field allows you to configure the label of the desired node t",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Specified Node Scheduling (nodeSelector),Scheduling a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Specified Node Scheduling (nodeSelector)",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0892.html",
|
||
"node_id":"cce_10_0892.xml",
|
||
"product_code":"cce",
|
||
"code":"209",
|
||
"des":"Kubernetes can schedule workload pods to affinity nodes based on their labels and label values. For example, some nodes support GPU computing, and node affinity schedulin",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Affinity,Specified Node Pool Scheduling,Configuring Node Affinity Scheduling (nodeAffinity),Sch",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Node Affinity Scheduling (nodeAffinity)",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0893.html",
|
||
"node_id":"cce_10_0893.xml",
|
||
"product_code":"cce",
|
||
"code":"210",
|
||
"des":"Kubernetes offers workload affinity and anti-affinity scheduling, which allows for flexible scheduling of new workloads on either related or unrelated nodes. This results",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Workload Affinity or Anti-affinity Scheduling (podAffinity or podAntiAffinity),Schedulin",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Workload Affinity or Anti-affinity Scheduling (podAffinity or podAntiAffinity)",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_00356.html",
|
||
"node_id":"cce_10_00356.xml",
|
||
"product_code":"cce",
|
||
"code":"211",
|
||
"des":"If you encounter unexpected problems when using a container, you can log in to the container to debug it.When using CloudShell to access a CCE cluster or container, you c",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Logging In to a Container,Workloads,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Logging In to a Container",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0007.html",
|
||
"node_id":"cce_10_0007.xml",
|
||
"product_code":"cce",
|
||
"code":"212",
|
||
"des":"After a workload is created, you can upgrade, log, monitor, roll back, or delete the workload, as well as edit its YAML file.Workload/Job managementOperationDescriptionMo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Managing Workloads,Workloads,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Managing Workloads",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0833.html",
|
||
"node_id":"cce_10_0833.xml",
|
||
"product_code":"cce",
|
||
"code":"213",
|
||
"des":"Custom Resource Definition (CRD) is an extension of Kubernetes APIs. When default Kubernetes resources cannot meet service requirements, you can use CRDs to define new re",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Managing Custom Resources,Workloads,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Managing Custom Resources",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0465.html",
|
||
"node_id":"cce_10_0465.xml",
|
||
"product_code":"cce",
|
||
"code":"214",
|
||
"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":"usermanual2",
|
||
"kw":"Pod Security",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Pod Security",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0275.html",
|
||
"node_id":"cce_10_0275.xml",
|
||
"product_code":"cce",
|
||
"code":"215",
|
||
"des":"A pod security policy (PSP) is a cluster-level resource that controls sensitive security aspects of the pod specification. The PodSecurityPolicy object in Kubernetes defi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring a Pod Security Policy,Pod Security,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring a Pod Security Policy",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0466.html",
|
||
"node_id":"cce_10_0466.xml",
|
||
"product_code":"cce",
|
||
"code":"216",
|
||
"des":"Before using pod security admission, understand Kubernetes Pod Security Standards. These standards define different isolation levels for pods. They let you define how you",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Pod Security Admission,Pod Security,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Pod Security Admission",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0674.html",
|
||
"node_id":"cce_10_0674.xml",
|
||
"product_code":"cce",
|
||
"code":"217",
|
||
"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":"usermanual2",
|
||
"kw":"Scheduling",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Scheduling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0702.html",
|
||
"node_id":"cce_10_0702.xml",
|
||
"product_code":"cce",
|
||
"code":"218",
|
||
"des":"CCE supports different types of resource scheduling and task scheduling, improving application performance and overall cluster resource utilization. This section describe",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0551.html",
|
||
"node_id":"cce_10_0551.xml",
|
||
"product_code":"cce",
|
||
"code":"219",
|
||
"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":"usermanual2",
|
||
"kw":"CPU Scheduling",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CPU Scheduling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0351.html",
|
||
"node_id":"cce_10_0351.xml",
|
||
"product_code":"cce",
|
||
"code":"220",
|
||
"des":"By default, kubelet uses CFS quotas to enforce pod CPU limits. When a node runs many CPU-bound pods, the workload can move to different CPU cores depending on whether the",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CPU Policy,CPU Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CPU Policy",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0552.html",
|
||
"node_id":"cce_10_0552.xml",
|
||
"product_code":"cce",
|
||
"code":"221",
|
||
"des":"Kubernetes provides two CPU policies: none and static.none: The CPU policy is disabled by default, indicating the existing scheduling behavior.static: The static CPU core",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Enhanced CPU Policy,CPU Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Enhanced CPU Policy",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0720.html",
|
||
"node_id":"cce_10_0720.xml",
|
||
"product_code":"cce",
|
||
"code":"222",
|
||
"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":"usermanual2",
|
||
"kw":"GPU Scheduling",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"GPU Scheduling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0345.html",
|
||
"node_id":"cce_10_0345.xml",
|
||
"product_code":"cce",
|
||
"code":"223",
|
||
"des":"You can use GPUs in CCE containers.A GPU node has been created. For details, see Creating a Node.The CCE AI Suite (NVIDIA GPU) add-on has been installed. During the insta",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Default GPU Scheduling in Kubernetes,GPU Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Default GPU Scheduling in Kubernetes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0423.html",
|
||
"node_id":"cce_10_0423.xml",
|
||
"product_code":"cce",
|
||
"code":"224",
|
||
"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":"usermanual2",
|
||
"kw":"Volcano Scheduling",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Volcano Scheduling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0721.html",
|
||
"node_id":"cce_10_0721.xml",
|
||
"product_code":"cce",
|
||
"code":"225",
|
||
"des":"Volcano is a batch processing platform that runs on Kubernetes for machine learning, deep learning, bioinformatics, genomics, and other big data applications. It provides",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Volcano Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0722.html",
|
||
"node_id":"cce_10_0722.xml",
|
||
"product_code":"cce",
|
||
"code":"226",
|
||
"des":"Volcano is a Kubernetes-based batch processing platform with high-performance general computing capabilities like task scheduling engine, heterogeneous chip management, a",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Scheduling Workloads,Volcano Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Scheduling Workloads",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0768.html",
|
||
"node_id":"cce_10_0768.xml",
|
||
"product_code":"cce",
|
||
"code":"227",
|
||
"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":"usermanual2",
|
||
"kw":"Resource Usage-based Scheduling",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Resource Usage-based Scheduling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0773.html",
|
||
"node_id":"cce_10_0773.xml",
|
||
"product_code":"cce",
|
||
"code":"228",
|
||
"des":"Bin packing is an optimization algorithm that aims to properly allocate resources to each job and get the jobs done using the minimum amount of resources. After bin packi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Bin Packing,Resource Usage-based Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Bin Packing",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0766.html",
|
||
"node_id":"cce_10_0766.xml",
|
||
"product_code":"cce",
|
||
"code":"229",
|
||
"des":"Scheduling in a cluster is the process of binding pending pods to nodes, and is performed by a component called kube-scheduler or Volcano Scheduler. The scheduler uses a ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Descheduling,Resource Usage-based Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Descheduling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0767.html",
|
||
"node_id":"cce_10_0767.xml",
|
||
"product_code":"cce",
|
||
"code":"230",
|
||
"des":"In scenarios such as node pool replacement and rolling node upgrade, an old resource pool needs to be replaced with a new one. To prevent the node pool replacement from a",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Node Pool Affinity,Resource Usage-based Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Pool Affinity",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0789.html",
|
||
"node_id":"cce_10_0789.xml",
|
||
"product_code":"cce",
|
||
"code":"231",
|
||
"des":"Volcano Scheduler offers CPU and memory load-aware scheduling for pods and preferentially schedules pods to the node with the lightest load to balance node loads. This pr",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Load-aware Scheduling,Resource Usage-based Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Load-aware Scheduling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0813.html",
|
||
"node_id":"cce_10_0813.xml",
|
||
"product_code":"cce",
|
||
"code":"232",
|
||
"des":"Volcano scheduling involves node filtering and scoring, which is used to filter the nodes meeting scheduling conditions and score the filtered nodes to find the one with ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuration Cases for Resource Usage-based Scheduling,Resource Usage-based Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuration Cases for Resource Usage-based Scheduling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0774.html",
|
||
"node_id":"cce_10_0774.xml",
|
||
"product_code":"cce",
|
||
"code":"233",
|
||
"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":"usermanual2",
|
||
"kw":"Priority-based Scheduling",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Priority-based Scheduling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0775.html",
|
||
"node_id":"cce_10_0775.xml",
|
||
"product_code":"cce",
|
||
"code":"234",
|
||
"des":"A pod priority indicates the importance of a pod relative to other pods. Volcano supports pod PriorityClasses in Kubernetes. After PriorityClasses are configured, the sch",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Priority-based Scheduling,Priority-based Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Priority-based Scheduling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0776.html",
|
||
"node_id":"cce_10_0776.xml",
|
||
"product_code":"cce",
|
||
"code":"235",
|
||
"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":"usermanual2",
|
||
"kw":"AI Performance-based Scheduling",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"AI Performance-based Scheduling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0777.html",
|
||
"node_id":"cce_10_0777.xml",
|
||
"product_code":"cce",
|
||
"code":"236",
|
||
"des":"Dominant Resource Fairness (DRF) is a scheduling algorithm based on the dominant resource of a container group. DRF scheduling can be used to enhance the service throughp",
|
||
"doc_type":"usermanual2",
|
||
"kw":"DRF,AI Performance-based Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"DRF",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0778.html",
|
||
"node_id":"cce_10_0778.xml",
|
||
"product_code":"cce",
|
||
"code":"237",
|
||
"des":"Gang scheduling is a scheduling algorithm that schedules correlated processes or threads to run simultaneously on different processors. It meets the scheduling requiremen",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Gang,AI Performance-based Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Gang",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0425.html",
|
||
"node_id":"cce_10_0425.xml",
|
||
"product_code":"cce",
|
||
"code":"238",
|
||
"des":"In non-uniform memory access (NUMA) architecture, a NUMA node is a fundamental component that includes a processor and local memory. These nodes are physically separate b",
|
||
"doc_type":"usermanual2",
|
||
"kw":"NUMA Affinity Scheduling,Volcano Scheduling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"NUMA Affinity Scheduling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0709.html",
|
||
"node_id":"cce_10_0709.xml",
|
||
"product_code":"cce",
|
||
"code":"239",
|
||
"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":"usermanual2",
|
||
"kw":"Cloud Native Hybrid Deployment",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cloud Native Hybrid Deployment",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0384.html",
|
||
"node_id":"cce_10_0384.xml",
|
||
"product_code":"cce",
|
||
"code":"240",
|
||
"des":"Many services see surges in traffic. To ensure performance and stability, resources are often requested at the maximum needed. However, the surges may ebb very shortly an",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Dynamic Resource Oversubscription,Cloud Native Hybrid Deployment,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Dynamic Resource Oversubscription",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0020.html",
|
||
"node_id":"cce_10_0020.xml",
|
||
"product_code":"cce",
|
||
"code":"241",
|
||
"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":"usermanual2",
|
||
"kw":"Network",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Network",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0010.html",
|
||
"node_id":"cce_10_0010.xml",
|
||
"product_code":"cce",
|
||
"code":"242",
|
||
"des":"You can learn about a cluster network from the following two aspects:What is a cluster network like? A cluster consists of multiple nodes, and pods (or containers) are ru",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Network,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0280.html",
|
||
"node_id":"cce_10_0280.xml",
|
||
"product_code":"cce",
|
||
"code":"243",
|
||
"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":"usermanual2",
|
||
"kw":"Container Network",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Container Network",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0281.html",
|
||
"node_id":"cce_10_0281.xml",
|
||
"product_code":"cce",
|
||
"code":"244",
|
||
"des":"The container network assigns IP addresses to pods in a cluster and provides networking services. In CCE, you can select the following network models for your cluster:Clo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Container Network,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0678.html",
|
||
"node_id":"cce_10_0678.xml",
|
||
"product_code":"cce",
|
||
"code":"245",
|
||
"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":"usermanual2",
|
||
"kw":"Cloud Native Network 2.0 Settings",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cloud Native Network 2.0 Settings",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0284.html",
|
||
"node_id":"cce_10_0284.xml",
|
||
"product_code":"cce",
|
||
"code":"246",
|
||
"des":"Cloud Native 2.0 network model is a proprietary, next-generation container network model that combines the elastic network interfaces (ENIs) and supplementary network int",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Cloud Native 2.0 Network Model,Cloud Native Network 2.0 Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cloud Native 2.0 Network Model",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0906.html",
|
||
"node_id":"cce_10_0906.xml",
|
||
"product_code":"cce",
|
||
"code":"247",
|
||
"des":"If the pod subnet configured during CCE Turbo cluster creation cannot meet service expansion requirements, you can add a pod subnet for the cluster.This function is avail",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Pod Subnets of a Cluster,Cloud Native Network 2.0 Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Pod Subnets of a Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0897.html",
|
||
"node_id":"cce_10_0897.xml",
|
||
"product_code":"cce",
|
||
"code":"248",
|
||
"des":"In Cloud Native 2.0 network mode, pods use ENIs or sub-ENIs of the VPC. You can configure a security group for a pod using a pod's annotation.Configure a security group i",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Binding a Security Group to a Pod Using an Annotation,Cloud Native Network 2.0 Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Binding a Security Group to a Pod Using an Annotation",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0288.html",
|
||
"node_id":"cce_10_0288.xml",
|
||
"product_code":"cce",
|
||
"code":"249",
|
||
"des":"In Cloud Native Network 2.0, pods use VPC ENIs or sub-ENIs for networking. You can directly bind security groups and EIPs to pods. To bind CCE pods with security groups, ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Binding a Security Group to a Workload Using a Security Group Policy,Cloud Native Network 2.0 Settin",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Binding a Security Group to a Workload Using a Security Group Policy",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0196.html",
|
||
"node_id":"cce_10_0196.xml",
|
||
"product_code":"cce",
|
||
"code":"250",
|
||
"des":"In a CCE Turbo cluster, you can configure subnets and security groups for containers by namespace or workload using NetworkAttachmentDefinition CRDs. To configure a parti",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configurati",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configuration",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0603.html",
|
||
"node_id":"cce_10_0603.xml",
|
||
"product_code":"cce",
|
||
"code":"251",
|
||
"des":"In Cloud Native Network 2.0, each pod is associated with an ENI, providing a static IP address to the StatefulSet pods (container ENI). This is a common practice in acces",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring a Static IP Address for a Pod,Cloud Native Network 2.0 Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring a Static IP Address for a Pod",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0734.html",
|
||
"node_id":"cce_10_0734.xml",
|
||
"product_code":"cce",
|
||
"code":"252",
|
||
"des":"In Cloud Native Network 2.0, pods use VPC ENIs or sub-ENIs for networking. You can directly bind EIPs to pods.To associate an EIP with a pod, simply set the value of the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring an EIP for a Pod,Cloud Native Network 2.0 Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring an EIP for a Pod",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0651.html",
|
||
"node_id":"cce_10_0651.xml",
|
||
"product_code":"cce",
|
||
"code":"253",
|
||
"des":"In Cloud Native Network 2.0, static public IP addresses (EIPs) can be assigned to StatefulSets or pods created directly.You can configure a static EIP for a pod only in C",
|
||
"doc_type":"usermanual2",
|
||
"kw":"static EIPs,Configuring a Static EIP for a Pod,Cloud Native Network 2.0 Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring a Static EIP for a Pod",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0604.html",
|
||
"node_id":"cce_10_0604.xml",
|
||
"product_code":"cce",
|
||
"code":"254",
|
||
"des":"By default, pods with IPv6 dual-stack ENIs can access only the IPv6 private network. To access the public network, configure shared bandwidth for such pods.Only CCE Turbo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack ENIs,Cloud Native Network 2.0 Settings,U",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack ENIs",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0904.html",
|
||
"node_id":"cce_10_0904.xml",
|
||
"product_code":"cce",
|
||
"code":"255",
|
||
"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":"usermanual2",
|
||
"kw":"VPC Network Settings",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"VPC Network Settings",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0283.html",
|
||
"node_id":"cce_10_0283.xml",
|
||
"product_code":"cce",
|
||
"code":"256",
|
||
"des":"The VPC network model seamlessly combines VPC routing with the underlying network, making it ideal for high-performance scenarios. However, the maximum number of nodes al",
|
||
"doc_type":"usermanual2",
|
||
"kw":"VPC Network Model,VPC Network Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"VPC Network Model",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0680.html",
|
||
"node_id":"cce_10_0680.xml",
|
||
"product_code":"cce",
|
||
"code":"257",
|
||
"des":"If the container CIDR block configured during CCE cluster creation cannot meet service expansion requirements, you can add a container CIDR block for the cluster.This fun",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Adding a Container CIDR Block for a Cluster,VPC Network Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Adding a Container CIDR Block for a Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0677.html",
|
||
"node_id":"cce_10_0677.xml",
|
||
"product_code":"cce",
|
||
"code":"258",
|
||
"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":"usermanual2",
|
||
"kw":"Tunnel Network Settings",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Tunnel Network Settings",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0282.html",
|
||
"node_id":"cce_10_0282.xml",
|
||
"product_code":"cce",
|
||
"code":"259",
|
||
"des":"A container tunnel network creates a separate network plane for containers by using tunnel encapsulation on the host network plane. The container tunnel network of a CCE ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Tunnel Network Model,Tunnel Network Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Tunnel Network Model",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0675.html",
|
||
"node_id":"cce_10_0675.xml",
|
||
"product_code":"cce",
|
||
"code":"260",
|
||
"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":"usermanual2",
|
||
"kw":"Pod Network Settings",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Pod Network Settings",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0402.html",
|
||
"node_id":"cce_10_0402.xml",
|
||
"product_code":"cce",
|
||
"code":"261",
|
||
"des":"Kubernetes allows pods to directly use the host/node network. When a pod is configured with hostNetwork: true, applications running in the pod can directly view the netwo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring hostNetwork for Pods,Pod Network Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring hostNetwork for Pods",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0382.html",
|
||
"node_id":"cce_10_0382.xml",
|
||
"product_code":"cce",
|
||
"code":"262",
|
||
"des":"Bandwidth preemption occurs between different containers deployed on the same node, which may cause service jitter. You can configure QoS rate limiting for inter-pod acce",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring QoS for a Pod,Pod Network Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring QoS for a Pod",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0059.html",
|
||
"node_id":"cce_10_0059.xml",
|
||
"product_code":"cce",
|
||
"code":"263",
|
||
"des":"Network policies are designed by Kubernetes to restrict pod access. It is equivalent to a firewall at the application layer to enhance network security. The capabilities ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Network Policies to Restrict Pod Access,Pod Network Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Network Policies to Restrict Pod Access",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0247.html",
|
||
"node_id":"cce_10_0247.xml",
|
||
"product_code":"cce",
|
||
"code":"264",
|
||
"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":"usermanual2",
|
||
"kw":"Service",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0249.html",
|
||
"node_id":"cce_10_0249.xml",
|
||
"product_code":"cce",
|
||
"code":"265",
|
||
"des":"After a pod is created, the following problems may occur if you directly access the pod:The pod can be deleted and recreated at any time by a controller such as a Deploym",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0011.html",
|
||
"node_id":"cce_10_0011.xml",
|
||
"product_code":"cce",
|
||
"code":"266",
|
||
"des":"ClusterIP Services allow workloads in the same cluster to use their cluster-internal domain names to access each other.The cluster-internal domain name format is <Service",
|
||
"doc_type":"usermanual2",
|
||
"kw":"ClusterIP,Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"ClusterIP",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0142.html",
|
||
"node_id":"cce_10_0142.xml",
|
||
"product_code":"cce",
|
||
"code":"267",
|
||
"des":"A Service is exposed on each node's IP address at a static port (NodePort). When you create a NodePort Service, Kubernetes automatically allocates an internal IP address ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"NodePort,Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"NodePort",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0014.html",
|
||
"node_id":"cce_10_0014.xml",
|
||
"product_code":"cce",
|
||
"code":"268",
|
||
"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":"usermanual2",
|
||
"kw":"LoadBalancer",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"LoadBalancer",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0681.html",
|
||
"node_id":"cce_10_0681.xml",
|
||
"product_code":"cce",
|
||
"code":"269",
|
||
"des":"LoadBalancer Services can access workloads from the public network through a load balancer, which is more reliable than EIP-based access. The LoadBalancer access address ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a LoadBalancer Service,LoadBalancer,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a LoadBalancer Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0385.html",
|
||
"node_id":"cce_10_0385.xml",
|
||
"product_code":"cce",
|
||
"code":"270",
|
||
"des":"You can add annotations to a YAML file to use some CCE advanced functions. This section describes the available annotations when a LoadBalancer service is created.Interco",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring LoadBalancer Services Using Annotations,LoadBalancer,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring LoadBalancer Services Using Annotations",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0683.html",
|
||
"node_id":"cce_10_0683.xml",
|
||
"product_code":"cce",
|
||
"code":"271",
|
||
"des":"Only clusters of v1.19.16 or later support HTTP or HTTPS.Scenarios where a load balancer supports HTTP or HTTPSELB TypeApplication scenarioWhether to Support HTTP or HTTP",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring HTTP/HTTPS for a LoadBalancer Service,LoadBalancer,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring HTTP/HTTPS for a LoadBalancer Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0841.html",
|
||
"node_id":"cce_10_0841.xml",
|
||
"product_code":"cce",
|
||
"code":"272",
|
||
"des":"An SNI certificate is an extended server certificate that allows the same IP address and port number to provide multiple access domain names for external systems. Differe",
|
||
"doc_type":"usermanual2",
|
||
"kw":"SNI,Configuring SNI for a LoadBalancer Service,LoadBalancer,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring SNI for a LoadBalancer Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0842.html",
|
||
"node_id":"cce_10_0842.xml",
|
||
"product_code":"cce",
|
||
"code":"273",
|
||
"des":"Services can be exposed via HTTP/2. By default, HTTP/1.x is used between clients and load balancers. HTTP/2 can improve access performance between clients and load balanc",
|
||
"doc_type":"usermanual2",
|
||
"kw":"HTTP/2,Configuring HTTP/2 for a LoadBalancer Service,LoadBalancer,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring HTTP/2 for a LoadBalancer Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0729.html",
|
||
"node_id":"cce_10_0729.xml",
|
||
"product_code":"cce",
|
||
"code":"274",
|
||
"des":"LoadBalancer Services allow you to configure timeout, which is the maximum duration for keeping a connection if no request is received from the client. If no request is r",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Timeout for a LoadBalancer Service,LoadBalancer,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Timeout for a LoadBalancer Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0831.html",
|
||
"node_id":"cce_10_0831.xml",
|
||
"product_code":"cce",
|
||
"code":"275",
|
||
"des":"When using a LoadBalancer Service, you can configure a trustlist or blocklist to specify the IP addresses that are allowed or denied accessing a load balancer listener.Tr",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring a Blocklist/Trustlist Access Policy for a LoadBalancer Service,LoadBalancer,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring a Blocklist/Trustlist Access Policy for a LoadBalancer Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0684.html",
|
||
"node_id":"cce_10_0684.xml",
|
||
"product_code":"cce",
|
||
"code":"276",
|
||
"des":"The annotation field related to the health check of the LoadBalancer Service is upgraded from Kubernetes.io/elb.health-check-option to Kubernetes.io/elb.health-check-opti",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Health Check on Multiple Ports of a LoadBalancer Service,LoadBalancer,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Health Check on Multiple Ports of a LoadBalancer Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0355.html",
|
||
"node_id":"cce_10_0355.xml",
|
||
"product_code":"cce",
|
||
"code":"277",
|
||
"des":"kube-proxy, which is responsible for forwarding intra-cluster traffic, adds the IP addresses of load balancers associated with the LoadBalancer Services to nodes' local f",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Passthrough Networking for a LoadBalancer Service,LoadBalancer,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Passthrough Networking for a LoadBalancer Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0916.html",
|
||
"node_id":"cce_10_0916.xml",
|
||
"product_code":"cce",
|
||
"code":"278",
|
||
"des":"When creating a LoadBalancer Service using a shared load balancer, you can configure annotations for the load balancer listeners to obtain the client IP address.If a dedi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Enabling a LoadBalancer Service to Obtain the Client IP Address,LoadBalancer,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Enabling a LoadBalancer Service to Obtain the Client IP Address",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0924.html",
|
||
"node_id":"cce_10_0924.xml",
|
||
"product_code":"cce",
|
||
"code":"279",
|
||
"des":"You can customize the EIP bound to a load balancer that is automatically created by CCE by adding the kubernetes.io/elb.custom-eip-id annotation to a Service.A Kubernetes",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring a Custom EIP for a LoadBalancer Service,LoadBalancer,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring a Custom EIP for a LoadBalancer Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0685.html",
|
||
"node_id":"cce_10_0685.xml",
|
||
"product_code":"cce",
|
||
"code":"280",
|
||
"des":"The ready status of the pod is associated with the ELB health check. After the health check is successful, the pod is ready. This association works with the strategy.roll",
|
||
"doc_type":"usermanual2",
|
||
"kw":"readinessGates,Setting the Pod Ready Status Through the ELB Health Check,LoadBalancer,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Setting the Pod Ready Status Through the ELB Health Check",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0084.html",
|
||
"node_id":"cce_10_0084.xml",
|
||
"product_code":"cce",
|
||
"code":"281",
|
||
"des":"If a workload uses UDP for both load balancing and health check, enable ICMP security group rules for the backend servers.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Enabling ICMP Security Group Rules,LoadBalancer,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Enabling ICMP Security Group Rules",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0398.html",
|
||
"node_id":"cce_10_0398.xml",
|
||
"product_code":"cce",
|
||
"code":"282",
|
||
"des":"Services allow internal and external pod access, but not the following scenarios:Accessing all pods at the same timePods in a Service accessing each otherThis is where he",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Headless Services,Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Headless Services",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0248.html",
|
||
"node_id":"cce_10_0248.xml",
|
||
"product_code":"cce",
|
||
"code":"283",
|
||
"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":"usermanual2",
|
||
"kw":"Ingresses",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Ingresses",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0094.html",
|
||
"node_id":"cce_10_0094.xml",
|
||
"product_code":"cce",
|
||
"code":"284",
|
||
"des":"A Service is generally used to forward access requests based on TCP and UDP and provide layer-4 load balancing for clusters. However, in actual scenarios, if there is a l",
|
||
"doc_type":"usermanual2",
|
||
"kw":"distributes access traffic,Failed to access the dedicated load balancers because no ENI is bound to ",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0686.html",
|
||
"node_id":"cce_10_0686.xml",
|
||
"product_code":"cce",
|
||
"code":"285",
|
||
"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":"usermanual2",
|
||
"kw":"LoadBalancer Ingresses",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"LoadBalancer Ingresses",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0251.html",
|
||
"node_id":"cce_10_0251.xml",
|
||
"product_code":"cce",
|
||
"code":"286",
|
||
"des":"In Kubernetes, an ingress is a resource object that controls how Services within a cluster can be accessed from outside the cluster. You can use ingresses to configure di",
|
||
"doc_type":"usermanual2",
|
||
"kw":"LoadBalancer ingress,Creating a LoadBalancer Ingress on the Console,LoadBalancer Ingresses,User Guid",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a LoadBalancer Ingress on the Console",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0252.html",
|
||
"node_id":"cce_10_0252.xml",
|
||
"product_code":"cce",
|
||
"code":"287",
|
||
"des":"This section uses an Nginx workload as an example to describe how to create a LoadBalancer ingress using kubectl.If no load balancer is available in the same VPC, CCE can",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a LoadBalancer Ingress Using kubectl,LoadBalancer Ingresses,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a LoadBalancer Ingress Using kubectl",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0695.html",
|
||
"node_id":"cce_10_0695.xml",
|
||
"product_code":"cce",
|
||
"code":"288",
|
||
"des":"You can add annotations to a YAML file for more advanced ingress functions. This section describes the annotations that can be used when you create a LoadBalancer ingress",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Annotations for Configuring LoadBalancer Ingresses,LoadBalancer Ingresses,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Annotations for Configuring LoadBalancer Ingresses",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0935.html",
|
||
"node_id":"cce_10_0935.xml",
|
||
"product_code":"cce",
|
||
"code":"289",
|
||
"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":"usermanual2",
|
||
"kw":"Advanced Setting Examples of LoadBalancer Ingresses",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Advanced Setting Examples of LoadBalancer Ingresses",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0687.html",
|
||
"node_id":"cce_10_0687.xml",
|
||
"product_code":"cce",
|
||
"code":"290",
|
||
"des":"Ingresses support SSL or TLS certificates, allowing you to secure your Services with HTTPS.You are allowed to use either of the following ways to configure an ingress cer",
|
||
"doc_type":"usermanual2",
|
||
"kw":"kubernetes.io/tls,IngressTLS,IngressTLS,kubernetes.io/tls,Configuring an HTTPS Certificate for a Loa",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring an HTTPS Certificate for a LoadBalancer Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0930.html",
|
||
"node_id":"cce_10_0930.xml",
|
||
"product_code":"cce",
|
||
"code":"291",
|
||
"des":"If the HTTPS certificate for a LoadBalancer ingress is about to expire or has expired, follow the operations provided in this section to update it.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Updating the HTTPS Certificate for a LoadBalancer Ingress,Advanced Setting Examples of LoadBalancer ",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Updating the HTTPS Certificate for a LoadBalancer Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0688.html",
|
||
"node_id":"cce_10_0688.xml",
|
||
"product_code":"cce",
|
||
"code":"292",
|
||
"des":"An SNI certificate is an extended server certificate that allows the same IP address and port number to provide multiple access domain names for external systems. Differe",
|
||
"doc_type":"usermanual2",
|
||
"kw":"SNI,kubernetes.io/tls,IngressTLS,Configuring SNI for a LoadBalancer Ingress,Advanced Setting Example",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring SNI for a LoadBalancer Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0689.html",
|
||
"node_id":"cce_10_0689.xml",
|
||
"product_code":"cce",
|
||
"code":"293",
|
||
"des":"An ingress can route requests to multiple backend Services based on different matching policies. For example, requests can be routed to three different backend Services s",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Multiple Forwarding Policies for a LoadBalancer Ingress,Advanced Setting Examples of Loa",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Multiple Forwarding Policies for a LoadBalancer Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0694.html",
|
||
"node_id":"cce_10_0694.xml",
|
||
"product_code":"cce",
|
||
"code":"294",
|
||
"des":"Ingresses can use HTTP/2 to expose Services. Connections from the load balancer to your application use HTTP/1.x by default. If your application is capable of receiving H",
|
||
"doc_type":"usermanual2",
|
||
"kw":"HTTP/2,Configuring HTTP/2 for a LoadBalancer Ingress,Advanced Setting Examples of LoadBalancer Ingre",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring HTTP/2 for a LoadBalancer Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0691.html",
|
||
"node_id":"cce_10_0691.xml",
|
||
"product_code":"cce",
|
||
"code":"295",
|
||
"des":"Ingresses can interconnect with backend services of different protocols. By default, the backend proxy channel of an ingress is HTTP-compliant. To create an HTTPS channel",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring HTTPS Backend Services for a LoadBalancer Ingress,Advanced Setting Examples of LoadBalan",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring HTTPS Backend Services for a LoadBalancer Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0730.html",
|
||
"node_id":"cce_10_0730.xml",
|
||
"product_code":"cce",
|
||
"code":"296",
|
||
"des":"LoadBalancer ingresses support the following timeout settings:Idle timeout setting for client connections: maximum duration for keeping a connection when no client reques",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Timeout for a LoadBalancer Ingress,Advanced Setting Examples of LoadBalancer Ingresses,U",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Timeout for a LoadBalancer Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0735.html",
|
||
"node_id":"cce_10_0735.xml",
|
||
"product_code":"cce",
|
||
"code":"297",
|
||
"des":"With slow start configured, a load balancer linearly increases the proportion of requests to backend server pods. When the slow start duration elapses, the load balancer ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring a Slow Start for a LoadBalancer Ingress,Advanced Setting Examples of LoadBalancer Ingres",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring a Slow Start for a LoadBalancer Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0832.html",
|
||
"node_id":"cce_10_0832.xml",
|
||
"product_code":"cce",
|
||
"code":"298",
|
||
"des":"You can add IP addresses to a trustlist or blocklist to control access to a listener of a LoadBalancer ingress.Trustlist: Only the IP addresses in the list can access the",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring a Blocklist/Trustlist Access Policy for a LoadBalancer Ingress,Advanced Setting Examples",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring a Blocklist/Trustlist Access Policy for a LoadBalancer Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0937.html",
|
||
"node_id":"cce_10_0937.xml",
|
||
"product_code":"cce",
|
||
"code":"299",
|
||
"des":"Ingress allows you to customize listening ports. You can configure both HTTP and HTTPS listeners for a Service. For example, a Service can make available both HTTP port 8",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring a Range of Listening Ports for a LoadBalancer Ingress,Advanced Setting Examples of LoadB",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring a Range of Listening Ports for a LoadBalancer Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0939.html",
|
||
"node_id":"cce_10_0939.xml",
|
||
"product_code":"cce",
|
||
"code":"300",
|
||
"des":"When ingresses use the same load balancer listener, forwarding rules can be prioritized based on the following rules:Forwarding rules of different ingresses: The rules ar",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring the Priorities of Forwarding Rules for LoadBalancer Ingresses,Advanced Setting Examples ",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring the Priorities of Forwarding Rules for LoadBalancer Ingresses",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0896.html",
|
||
"node_id":"cce_10_0896.xml",
|
||
"product_code":"cce",
|
||
"code":"301",
|
||
"des":"Dedicated load balancer ingresses support custom header forwarding policies. You can configure different header key-value pairs to determine the backend Service to which ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring a Custom Header Forwarding Policy for a LoadBalancer Ingress,Advanced Setting Examples o",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring a Custom Header Forwarding Policy for a LoadBalancer Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0925.html",
|
||
"node_id":"cce_10_0925.xml",
|
||
"product_code":"cce",
|
||
"code":"302",
|
||
"des":"You can customize the EIP bound to a load balancer that is automatically created by CCE by adding the kubernetes.io/elb.custom-eip-id annotation to an ingress.A CCE stand",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring a Custom EIP for a LoadBalancer Ingress,Advanced Setting Examples of LoadBalancer Ingres",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring a Custom EIP for a LoadBalancer Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0940.html",
|
||
"node_id":"cce_10_0940.xml",
|
||
"product_code":"cce",
|
||
"code":"303",
|
||
"des":"Ingresses offer diverse forwarding rules that can match listeners based on different request parameters like HTTP request methods, headers, query strings, CIDR blocks, an",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Advanced Forwarding Rules for a LoadBalancer Ingress,Advanced Setting Examples of LoadBa",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Advanced Forwarding Rules for a LoadBalancer Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0692.html",
|
||
"node_id":"cce_10_0692.xml",
|
||
"product_code":"cce",
|
||
"code":"304",
|
||
"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":"usermanual2",
|
||
"kw":"Nginx Ingresses",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Nginx Ingresses",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0390.html",
|
||
"node_id":"cce_10_0390.xml",
|
||
"product_code":"cce",
|
||
"code":"305",
|
||
"des":"In Kubernetes, an ingress is a resource object that controls how Services within a cluster can be accessed from outside the cluster. You can use ingresses to configure di",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Nginx ingress,Creating an Nginx Ingress on the Console,Nginx Ingresses,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating an Nginx Ingress on the Console",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0364.html",
|
||
"node_id":"cce_10_0364.xml",
|
||
"product_code":"cce",
|
||
"code":"306",
|
||
"des":"This section uses an Nginx workload as an example to describe how to create an Nginx ingress using kubectl.In CCE clusters of v1.23 or later, the ingress version is switc",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating an Nginx Ingress Using kubectl,Nginx Ingresses,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating an Nginx Ingress Using kubectl",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0699.html",
|
||
"node_id":"cce_10_0699.xml",
|
||
"product_code":"cce",
|
||
"code":"307",
|
||
"des":"The nginx-ingress add-on in CCE uses the community chart and image. If the default add-on parameters cannot meet your demands, you can add annotations to define what you ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Annotations for Configuring Nginx Ingresses,Nginx Ingresses,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Annotations for Configuring Nginx Ingresses",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0936.html",
|
||
"node_id":"cce_10_0936.xml",
|
||
"product_code":"cce",
|
||
"code":"308",
|
||
"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":"usermanual2",
|
||
"kw":"Advanced Setting Examples of Nginx Ingresses",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Advanced Setting Examples of Nginx Ingresses",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0693.html",
|
||
"node_id":"cce_10_0693.xml",
|
||
"product_code":"cce",
|
||
"code":"309",
|
||
"des":"HTTPS certificates can be configured for ingresses to provide security services.Create a YAML file named ingress-test-secret.yaml. The file name can be customized.The YAM",
|
||
"doc_type":"usermanual2",
|
||
"kw":"kubernetes.io/tls,IngressTLS,IngressTLS,kubernetes.io/tls,Configuring an HTTPS Certificate for an Ng",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring an HTTPS Certificate for an Nginx Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0697.html",
|
||
"node_id":"cce_10_0697.xml",
|
||
"product_code":"cce",
|
||
"code":"310",
|
||
"des":"Ingress can function as a proxy for backend services using different protocols. By default, the backend proxy channel of an ingress is an HTTP channel. To create an HTTPS",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring HTTPS Backend Services for an Nginx Ingress,Advanced Setting Examples of Nginx Ingresses",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring HTTPS Backend Services for an Nginx Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0698.html",
|
||
"node_id":"cce_10_0698.xml",
|
||
"product_code":"cce",
|
||
"code":"311",
|
||
"des":"The native Nginx supports multiple load balancing rules, including weighted round robin and IP hash. Nginx Ingress supports load balancing by using consistent hashing bas",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Consistent Hashing for Load Balancing of an Nginx Ingress,Advanced Setting Examples of N",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Consistent Hashing for Load Balancing of an Nginx Ingress",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0359.html",
|
||
"node_id":"cce_10_0359.xml",
|
||
"product_code":"cce",
|
||
"code":"312",
|
||
"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":"usermanual2",
|
||
"kw":"DNS",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"DNS",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0360.html",
|
||
"node_id":"cce_10_0360.xml",
|
||
"product_code":"cce",
|
||
"code":"313",
|
||
"des":"When you create a cluster, the CoreDNS add-on is installed to resolve domain names in the cluster.You can view the pod of the CoreDNS add-on in the kube-system namespace.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,DNS,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0365.html",
|
||
"node_id":"cce_10_0365.xml",
|
||
"product_code":"cce",
|
||
"code":"314",
|
||
"des":"Every Kubernetes cluster has a built-in DNS add-on (Kube-DNS or CoreDNS) to provide domain name resolution for workloads in the cluster. When handling a high concurrency ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"DNS Configuration,DNS,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"DNS Configuration",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0361.html",
|
||
"node_id":"cce_10_0361.xml",
|
||
"product_code":"cce",
|
||
"code":"315",
|
||
"des":"When using CCE, you may need to resolve custom internal domain names in the following scenarios:In the legacy code, a fixed domain name is configured for calling other in",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using CoreDNS for Custom Domain Name Resolution,DNS,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using CoreDNS for Custom Domain Name Resolution",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0399.html",
|
||
"node_id":"cce_10_0399.xml",
|
||
"product_code":"cce",
|
||
"code":"316",
|
||
"des":"This section describes how to access an intranet from a container (outside the cluster in a VPC), including intra-VPC access and cross-VPC access.The performance of acces",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Intra-VPC Access,Network,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Intra-VPC Access",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0400.html",
|
||
"node_id":"cce_10_0400.xml",
|
||
"product_code":"cce",
|
||
"code":"317",
|
||
"des":"Containers can access the Internet in either of the following ways:Bind an EIP to the node where the container is located if the network model is VPC or tunnel.Bind an EI",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Accessing the Internet from a Container,Network,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Accessing the Internet from a Container",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0374.html",
|
||
"node_id":"cce_10_0374.xml",
|
||
"product_code":"cce",
|
||
"code":"318",
|
||
"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":"usermanual2",
|
||
"kw":"Storage",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Storage",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0307.html",
|
||
"node_id":"cce_10_0307.xml",
|
||
"product_code":"cce",
|
||
"code":"319",
|
||
"des":"CCE container storage is implemented based on Kubernetes container storage APIs (CSI). CCE integrates multiple types of cloud storage and covers different application sce",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Storage,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0378.html",
|
||
"node_id":"cce_10_0378.xml",
|
||
"product_code":"cce",
|
||
"code":"320",
|
||
"des":"On-disk files in a container are ephemeral, which presents the following problems to important applications running in the container:When a container is rebuilt, files in",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Statically creating storage volume,VolumeClaimTemplate,Storage Basics,Storage,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Storage Basics",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0044.html",
|
||
"node_id":"cce_10_0044.xml",
|
||
"product_code":"cce",
|
||
"code":"321",
|
||
"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":"usermanual2",
|
||
"kw":"Elastic Volume Service",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Elastic Volume Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0613.html",
|
||
"node_id":"cce_10_0613.xml",
|
||
"product_code":"cce",
|
||
"code":"322",
|
||
"des":"To achieve persistent storage, CCE allows you to mount the storage volumes created from Elastic Volume Service (EVS) disks to a path of a container. When the container is",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Elastic Volume Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0614.html",
|
||
"node_id":"cce_10_0614.xml",
|
||
"product_code":"cce",
|
||
"code":"323",
|
||
"des":"CCE allows you to create a PV using an existing EVS disk. After the PV is created, you can create a PVC and bind it to the PV. This mode applies if the underlying storage",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Data sharing,Using an Existing EVS Disk Through a Static PV,Elastic Volume Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using an Existing EVS Disk Through a Static PV",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0615.html",
|
||
"node_id":"cce_10_0615.xml",
|
||
"product_code":"cce",
|
||
"code":"324",
|
||
"des":"CCE allows you to specify a StorageClass to automatically create an EVS disk and the corresponding PV. This function is applicable when no underlying storage volume is av",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Data sharing,Expanding the capacity of an EVS disk,Using an EVS Disk Through a Dynamic PV,Elastic Vo",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using an EVS Disk Through a Dynamic PV",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0616.html",
|
||
"node_id":"cce_10_0616.xml",
|
||
"product_code":"cce",
|
||
"code":"325",
|
||
"des":"Dynamic mounting is available only for creating a StatefulSet. It is implemented through a volume claim template (volumeClaimTemplates field) and depends on dynamic creat",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Expanding the capacity of an EVS disk,Dynamically Mounting an EVS Disk to a StatefulSet,Elastic Volu",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Dynamically Mounting an EVS Disk to a StatefulSet",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0859.html",
|
||
"node_id":"cce_10_0859.xml",
|
||
"product_code":"cce",
|
||
"code":"326",
|
||
"des":"Encrypting cloud disks ensures data privacy and control, making it ideal for scenarios that demand high security or compliance standards. This section describes how to us",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Encrypting EVS Disks,Elastic Volume Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Encrypting EVS Disks",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0860.html",
|
||
"node_id":"cce_10_0860.xml",
|
||
"product_code":"cce",
|
||
"code":"327",
|
||
"des":"If the EVS disk attached to a workload does not have enough space, you can increase its capacity by expanding it. This section describes how to expand the capacity of an ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Expanding the Capacity of an EVS Disk,Elastic Volume Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Expanding the Capacity of an EVS Disk",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0381.html",
|
||
"node_id":"cce_10_0381.xml",
|
||
"product_code":"cce",
|
||
"code":"328",
|
||
"des":"CCE works with EVS to support snapshots. A snapshot is a complete copy or image of EVS disk data at a certain point of time, which can be used for data DR.You can create ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Snapshots and Backups,Elastic Volume Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Snapshots and Backups",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0111.html",
|
||
"node_id":"cce_10_0111.xml",
|
||
"product_code":"cce",
|
||
"code":"329",
|
||
"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":"usermanual2",
|
||
"kw":"Scalable File Service",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Scalable File Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0617.html",
|
||
"node_id":"cce_10_0617.xml",
|
||
"product_code":"cce",
|
||
"code":"330",
|
||
"des":"CCE allows you to mount a volume created from a Scalable File Service (SFS) file system to a container to store data persistently. SFS volumes are commonly used in ReadWr",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Scalable File Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0619.html",
|
||
"node_id":"cce_10_0619.xml",
|
||
"product_code":"cce",
|
||
"code":"331",
|
||
"des":"SFS is a network-attached storage (NAS) that provides shared, scalable, and high-performance file storage. It applies to large-capacity expansion and cost-sensitive servi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using an Existing SFS File System Through a Static PV,Scalable File Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using an Existing SFS File System Through a Static PV",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0620.html",
|
||
"node_id":"cce_10_0620.xml",
|
||
"product_code":"cce",
|
||
"code":"332",
|
||
"des":"This section describes how to use storage classes to dynamically create PVs and PVCs for data persistence and sharing in workloads.You have created a cluster and installe",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using an SFS File System Through a Dynamic PV,Scalable File Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using an SFS File System Through a Dynamic PV",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0337.html",
|
||
"node_id":"cce_10_0337.xml",
|
||
"product_code":"cce",
|
||
"code":"333",
|
||
"des":"This section describes how to configure SFS mount options. You can configure mount options in a PV and bind the PV to a PVC. Alternatively, configure mount options in a S",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring SFS Volume Mount Options,Scalable File Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring SFS Volume Mount Options",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0125.html",
|
||
"node_id":"cce_10_0125.xml",
|
||
"product_code":"cce",
|
||
"code":"334",
|
||
"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":"usermanual2",
|
||
"kw":"SFS Turbo",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"SFS Turbo",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0624.html",
|
||
"node_id":"cce_10_0624.xml",
|
||
"product_code":"cce",
|
||
"code":"335",
|
||
"des":"CCE allows you to mount storage volumes created by SFS Turbo file systems to a path of a container to meet data persistence requirements. SFS Turbo file systems are fast,",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,SFS Turbo,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0625.html",
|
||
"node_id":"cce_10_0625.xml",
|
||
"product_code":"cce",
|
||
"code":"336",
|
||
"des":"SFS Turbo is a shared file system with high availability and durability. It is suitable for applications that contain massive small files and require low latency, and hig",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Expanding the capacity of an SFS Turbo volume,Using an Existing SFS Turbo File System Through a Stat",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using an Existing SFS Turbo File System Through a Static PV",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0626.html",
|
||
"node_id":"cce_10_0626.xml",
|
||
"product_code":"cce",
|
||
"code":"337",
|
||
"des":"This section describes how to configure SFS Turbo mount options. For SFS Turbo, you can only set mount options in a PV and bind the PV by creating a PVC.The CCE Container",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring SFS Turbo Mount Options,SFS Turbo,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring SFS Turbo Mount Options",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0839.html",
|
||
"node_id":"cce_10_0839.xml",
|
||
"product_code":"cce",
|
||
"code":"338",
|
||
"des":"When an SFS Turbo volume is mounted to a workload container, the root directory is mounted to the container by default. However, the minimum capacity of an SFS Turbo volu",
|
||
"doc_type":"usermanual2",
|
||
"kw":"(Recommended) Creating an SFS Turbo Subdirectory Using a Dynamic PV,SFS Turbo,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"(Recommended) Creating an SFS Turbo Subdirectory Using a Dynamic PV",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00253_0.html",
|
||
"node_id":"cce_bestpractice_00253_0.xml",
|
||
"product_code":"cce",
|
||
"code":"339",
|
||
"des":"The minimum capacity of an SFS Turbo file system is 500 GiB. By default, the root directory of an SFS Turbo file system is mounted to a container which, in most case, doe",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Dynamically Creating an SFS Turbo Subdirectory Using StorageClass,SFS Turbo,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Dynamically Creating an SFS Turbo Subdirectory Using StorageClass",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0160.html",
|
||
"node_id":"cce_10_0160.xml",
|
||
"product_code":"cce",
|
||
"code":"340",
|
||
"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":"usermanual2",
|
||
"kw":"Object Storage Service",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Object Storage Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0628.html",
|
||
"node_id":"cce_10_0628.xml",
|
||
"product_code":"cce",
|
||
"code":"341",
|
||
"des":"Object Storage Service (OBS) provides massive, secure, and cost-effective data storage for you to store data of any type and size. You can use it in enterprise backup/arc",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Object Storage Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0379.html",
|
||
"node_id":"cce_10_0379.xml",
|
||
"product_code":"cce",
|
||
"code":"342",
|
||
"des":"This section describes how to use an existing Object Storage Service (OBS) bucket to statically create PVs and PVCs for data persistence and sharing in workloads.You have",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Updating an access key,Using an Existing OBS Bucket Through a Static PV,Object Storage Service,User ",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using an Existing OBS Bucket Through a Static PV",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0630.html",
|
||
"node_id":"cce_10_0630.xml",
|
||
"product_code":"cce",
|
||
"code":"343",
|
||
"des":"This section describes how to automatically create an OBS bucket. It is applicable when no underlying storage volume is available.If OBS volumes are used, the owner group",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Updating an access key,Using an OBS Bucket Through a Dynamic PV,Object Storage Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using an OBS Bucket Through a Dynamic PV",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0631.html",
|
||
"node_id":"cce_10_0631.xml",
|
||
"product_code":"cce",
|
||
"code":"344",
|
||
"des":"This section describes how to configure OBS volume mount options. You can configure mount options in a PV and bind the PV to a PVC. Alternatively, configure mount options",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring OBS Mount Options,Object Storage Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring OBS Mount Options",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0336.html",
|
||
"node_id":"cce_10_0336.xml",
|
||
"product_code":"cce",
|
||
"code":"345",
|
||
"des":"CCE Container Storage (Everest) of v1.2.8 or later supports custom access keys. In this way, IAM users can use their own custom access keys to mount an OBS volume.The CCE",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using a Custom Access Key (AK/SK) to Mount an OBS Volume,Object Storage Service,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using a Custom Access Key (AK/SK) to Mount an OBS Volume",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0391.html",
|
||
"node_id":"cce_10_0391.xml",
|
||
"product_code":"cce",
|
||
"code":"346",
|
||
"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":"usermanual2",
|
||
"kw":"Local PVs",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Local PVs",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0633.html",
|
||
"node_id":"cce_10_0633.xml",
|
||
"product_code":"cce",
|
||
"code":"347",
|
||
"des":"CCE allows you to use LVM to combine data volumes on nodes into a storage pool (VolumeGroup) and create LVs for containers to mount. A PV that uses a local persistent vol",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Local PVs,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0642.html",
|
||
"node_id":"cce_10_0642.xml",
|
||
"product_code":"cce",
|
||
"code":"348",
|
||
"des":"CCE allows you to use LVM to combine data volumes on nodes into a storage pool (VolumeGroup) and create LVs for containers to mount. Before creating a local PV, import th",
|
||
"doc_type":"usermanual2",
|
||
"kw":"storage pool,Importing a PV to a Storage Pool,Local PVs,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Importing a PV to a Storage Pool",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0634.html",
|
||
"node_id":"cce_10_0634.xml",
|
||
"product_code":"cce",
|
||
"code":"349",
|
||
"des":"You have created a cluster and installed the CSI add-on (Everest) in the cluster.To create a cluster using commands, ensure kubectl is used. For details, see Connecting t",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using a Local PV Through a Dynamic PV,Local PVs,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using a Local PV Through a Dynamic PV",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0635.html",
|
||
"node_id":"cce_10_0635.xml",
|
||
"product_code":"cce",
|
||
"code":"350",
|
||
"des":"Dynamic mounting is available only for creating a StatefulSet. It is implemented through a volume claim template (volumeClaimTemplates field) and depends on dynamic creat",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Dynamically Mounting a Local PV to a StatefulSet,Local PVs,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Dynamically Mounting a Local PV to a StatefulSet",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0636.html",
|
||
"node_id":"cce_10_0636.xml",
|
||
"product_code":"cce",
|
||
"code":"351",
|
||
"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":"usermanual2",
|
||
"kw":"Ephemeral Volumes",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Ephemeral Volumes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0637.html",
|
||
"node_id":"cce_10_0637.xml",
|
||
"product_code":"cce",
|
||
"code":"352",
|
||
"des":"Some applications require additional storage, but whether the data is still available after a restart is not important. For example, although cache services are limited b",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Ephemeral Volumes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0725.html",
|
||
"node_id":"cce_10_0725.xml",
|
||
"product_code":"cce",
|
||
"code":"353",
|
||
"des":"CCE allows you to use LVM to combine data volumes on nodes into a storage pool (VolumeGroup) and create LVs for containers to mount. Before creating a local EV, import th",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Importing an EV to a Storage Pool,Ephemeral Volumes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Importing an EV to a Storage Pool",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0726.html",
|
||
"node_id":"cce_10_0726.xml",
|
||
"product_code":"cce",
|
||
"code":"354",
|
||
"des":"Local Ephemeral Volumes (EVs) are stored in EV storage pools. Local EVs deliver better performance than the default storage medium of native emptyDir and support scale-ou",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using a Local EV,Ephemeral Volumes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using a Local EV",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0638.html",
|
||
"node_id":"cce_10_0638.xml",
|
||
"product_code":"cce",
|
||
"code":"355",
|
||
"des":"A temporary path is of the Kubernetes-native emptyDir type. Its lifecycle is the same as that of a pod. Memory can be specified as the storage medium. When the pod is del",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using a Temporary Path,Ephemeral Volumes,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using a Temporary Path",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0377.html",
|
||
"node_id":"cce_10_0377.xml",
|
||
"product_code":"cce",
|
||
"code":"356",
|
||
"des":"hostPath is used for mounting the file directory of the host where the container is located to the specified mount point of the container. If the container needs to acces",
|
||
"doc_type":"usermanual2",
|
||
"kw":"hostPath,Storage,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"hostPath",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0380.html",
|
||
"node_id":"cce_10_0380.xml",
|
||
"product_code":"cce",
|
||
"code":"357",
|
||
"des":"A StorageClass in Kubernetes is a resource that categorizes storage types in a cluster. It can also serve as a configuration template for creating PVs. When creating a PV",
|
||
"doc_type":"usermanual2",
|
||
"kw":"StorageClass,Storage,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"StorageClass",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0705.html",
|
||
"node_id":"cce_10_0705.xml",
|
||
"product_code":"cce",
|
||
"code":"358",
|
||
"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":"usermanual2",
|
||
"kw":"Observability",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Observability",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0553.html",
|
||
"node_id":"cce_10_0553.xml",
|
||
"product_code":"cce",
|
||
"code":"359",
|
||
"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":"usermanual2",
|
||
"kw":"Logging",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Logging",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0557.html",
|
||
"node_id":"cce_10_0557.xml",
|
||
"product_code":"cce",
|
||
"code":"360",
|
||
"des":"Kubernetes logs allow you to locate and rectify faults. This section describes how you can manage Kubernetes logs generated for CCE.Connect CCE to AOM. For details, see C",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Logging,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0182.html",
|
||
"node_id":"cce_10_0182.xml",
|
||
"product_code":"cce",
|
||
"code":"361",
|
||
"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":"usermanual2",
|
||
"kw":"Collecting Container Logs",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Collecting Container Logs",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0018.html",
|
||
"node_id":"cce_10_0018.xml",
|
||
"product_code":"cce",
|
||
"code":"362",
|
||
"des":"CCE works with AOM to collect workload logs. When a node is created, ICAgent (a DaemonSet named icagent in the kube-system namespace of a cluster) of AOM is installed by ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Pod,Pod,Collecting Container Logs Using ICAgent,Collecting Container Logs,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Collecting Container Logs Using ICAgent",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0024.html",
|
||
"node_id":"cce_10_0024.xml",
|
||
"product_code":"cce",
|
||
"code":"363",
|
||
"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":"usermanual2",
|
||
"kw":"Log Auditing",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Log Auditing",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0025.html",
|
||
"node_id":"cce_10_0025.xml",
|
||
"product_code":"cce",
|
||
"code":"364",
|
||
"des":"Cloud Trace Service (CTS) records operations on cloud service resources, allowing users to query, audit, and backtrack the resource operation requests initiated from the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CCE Operations Supported by Cloud Trace Service,Log Auditing,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CCE Operations Supported by Cloud Trace Service",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0026.html",
|
||
"node_id":"cce_10_0026.xml",
|
||
"product_code":"cce",
|
||
"code":"365",
|
||
"des":"After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. Cloud Trace Service (CTS) stores operation records (traces",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Viewing CTS Traces in the Trace List,Log Auditing,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Viewing CTS Traces in the Trace List",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0811.html",
|
||
"node_id":"cce_10_0811.xml",
|
||
"product_code":"cce",
|
||
"code":"366",
|
||
"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":"usermanual2",
|
||
"kw":"Best Practices",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Best Practices",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0373.html",
|
||
"node_id":"cce_10_0373.xml",
|
||
"product_code":"cce",
|
||
"code":"367",
|
||
"des":"CCE provides the Cloud Native Cluster Monitoring add-on to monitor custom metrics using Prometheus.The following procedure uses an Nginx application as an example to desc",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Monitoring Custom Metrics Using Cloud Native Cluster Monitoring,Best Practices,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Monitoring Custom Metrics Using Cloud Native Cluster Monitoring",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0201.html",
|
||
"node_id":"cce_10_0201.xml",
|
||
"product_code":"cce",
|
||
"code":"368",
|
||
"des":"CCE allows you to upload custom metrics to AOM. ICAgent on a node periodically calls the metric monitoring API configured on a workload to read monitoring data and then u",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Monitoring Custom Metrics on AOM,Best Practices,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Monitoring Custom Metrics on AOM",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0207.html",
|
||
"node_id":"cce_10_0207.xml",
|
||
"product_code":"cce",
|
||
"code":"369",
|
||
"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":"usermanual2",
|
||
"kw":"Auto Scaling",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Auto Scaling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0279.html",
|
||
"node_id":"cce_10_0279.xml",
|
||
"product_code":"cce",
|
||
"code":"370",
|
||
"des":"Auto scaling is a service that automatically and economically adjusts service resources based on your service requirements and configured policies.More and more applicati",
|
||
"doc_type":"usermanual2",
|
||
"kw":"auto scaling,Overview,Auto Scaling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0293.html",
|
||
"node_id":"cce_10_0293.xml",
|
||
"product_code":"cce",
|
||
"code":"371",
|
||
"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":"usermanual2",
|
||
"kw":"Scaling a Workload",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Scaling a Workload",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0290.html",
|
||
"node_id":"cce_10_0290.xml",
|
||
"product_code":"cce",
|
||
"code":"372",
|
||
"des":"CCE supports multiple workload scaling modes. Comparisons between the scaling policies are listed in the following table.Comparisons between auto scaling policiesItemHPAC",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Workload Scaling Rules,Scaling a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Workload Scaling Rules",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0208.html",
|
||
"node_id":"cce_10_0208.xml",
|
||
"product_code":"cce",
|
||
"code":"373",
|
||
"des":"Horizontal Pod Autoscaling (HPA) in Kubernetes implements horizontal scaling of pods. In a CCE HPA policy, you can configure different cooldown time windows and scaling t",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Horizontal Pod Autoscaling,horizontal scaling of pods,Creating an HPA Policy,Scaling a Workload,User",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating an HPA Policy",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0944.html",
|
||
"node_id":"cce_10_0944.xml",
|
||
"product_code":"cce",
|
||
"code":"374",
|
||
"des":"Kubernetes' default HPA policy only allows for auto scaling based on CPU and memory usage. However, in more complex service scenarios, this may not be sufficient to meet ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating an HPA Policy with Custom Metrics,Scaling a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating an HPA Policy with Custom Metrics",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0415.html",
|
||
"node_id":"cce_10_0415.xml",
|
||
"product_code":"cce",
|
||
"code":"375",
|
||
"des":"There are predictable and unpredictable traffic peaks for some services. For such services, CCE CronHPA allows you to scale resources in fixed periods. It can work with H",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a Scheduled CronHPA Policy,Scaling a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a Scheduled CronHPA Policy",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0934.html",
|
||
"node_id":"cce_10_0934.xml",
|
||
"product_code":"cce",
|
||
"code":"376",
|
||
"des":"The native Horizontal Pod Autoscaler (HPA) in Kubernetes can cause delays in scaling due to its passive triggering mechanism. To address this issue, the Advanced Horizont",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating an AHPA Policy,Scaling a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating an AHPA Policy",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0083.html",
|
||
"node_id":"cce_10_0083.xml",
|
||
"product_code":"cce",
|
||
"code":"377",
|
||
"des":"After a workload scaling policy is created, you can update and delete the policy, as well as edit the YAML file.You can view the rules, latest status, and events of a wor",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Managing Workload Scaling Policies,Scaling a Workload,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Managing Workload Scaling Policies",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0291.html",
|
||
"node_id":"cce_10_0291.xml",
|
||
"product_code":"cce",
|
||
"code":"378",
|
||
"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":"usermanual2",
|
||
"kw":"Scaling a Node",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Scaling a Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0296.html",
|
||
"node_id":"cce_10_0296.xml",
|
||
"product_code":"cce",
|
||
"code":"379",
|
||
"des":"HPA is designed for pod-level scaling and can dynamically adjust the number of replicas based on workload metrics. However, if cluster resources are insufficient and new ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"node scaling,Node Scaling Rules,Scaling a Node,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Scaling Rules",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0649.html",
|
||
"node_id":"cce_10_0649.xml",
|
||
"product_code":"cce",
|
||
"code":"380",
|
||
"des":"To use node flavor priorities, the Autoscaler version must be 1.19.35, 1.21.28, 1.23.30, 1.25.20, or later. To balance load among AZs, the version must be 1.23.122, 1.25.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Priorities for Scaling Node Pools,Scaling a Node,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Priorities for Scaling Node Pools",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0209.html",
|
||
"node_id":"cce_10_0209.xml",
|
||
"product_code":"cce",
|
||
"code":"381",
|
||
"des":"CCE provides auto scaling through the CCE Cluster Autoscaler add-on. Nodes with different flavors can be automatically added across AZs on demand.If both a node scaling p",
|
||
"doc_type":"usermanual2",
|
||
"kw":"node scaling,Creating a Node Scaling Policy,Scaling a Node,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a Node Scaling Policy",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0063.html",
|
||
"node_id":"cce_10_0063.xml",
|
||
"product_code":"cce",
|
||
"code":"382",
|
||
"des":"After a node scaling policy is created, you can delete, edit, disable, enable, or clone the policy.You can view the associated node pool, rules, and scaling history of a ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Managing Node Scaling Policies,Scaling a Node,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Managing Node Scaling Policies",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0300.html",
|
||
"node_id":"cce_10_0300.xml",
|
||
"product_code":"cce",
|
||
"code":"383",
|
||
"des":"The best way to handle surging traffic is to automatically adjust the number of machines based on the traffic volume or resource usage, which is called scaling.When deplo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using HPA and CA for Auto Scaling of Workloads and Nodes,Auto Scaling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using HPA and CA for Auto Scaling of Workloads and Nodes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0030.html",
|
||
"node_id":"cce_10_0030.xml",
|
||
"product_code":"cce",
|
||
"code":"384",
|
||
"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":"usermanual2",
|
||
"kw":"Namespaces",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Namespaces",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0278.html",
|
||
"node_id":"cce_10_0278.xml",
|
||
"product_code":"cce",
|
||
"code":"385",
|
||
"des":"A namespace is a collection of resources and objects. Multiple namespaces can be created inside a cluster and isolated from each other. This enables namespaces to share t",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a Namespace,Namespaces,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a Namespace",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0285.html",
|
||
"node_id":"cce_10_0285.xml",
|
||
"product_code":"cce",
|
||
"code":"386",
|
||
"des":"When creating a workload, you can select a namespace to isolate resources or users.When querying workloads, you can select a namespace to view all workloads in the namesp",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Managing Namespaces,Namespaces,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Managing Namespaces",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0287.html",
|
||
"node_id":"cce_10_0287.xml",
|
||
"product_code":"cce",
|
||
"code":"387",
|
||
"des":"Kubernetes provides namespaces for you to group resources in a cluster. Namespaces serve different purposes to meet the needs of multiple users, environments, and applica",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring Resource Quotas,Namespaces,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring Resource Quotas",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0045.html",
|
||
"node_id":"cce_10_0045.xml",
|
||
"product_code":"cce",
|
||
"code":"388",
|
||
"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":"usermanual2",
|
||
"kw":"ConfigMaps and Secrets",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"ConfigMaps and Secrets",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0152.html",
|
||
"node_id":"cce_10_0152.xml",
|
||
"product_code":"cce",
|
||
"code":"389",
|
||
"des":"A ConfigMap is a type of resource that stores configuration information required by a workload. Its content is user-defined. After creating ConfigMaps, you can use them a",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a ConfigMap,ConfigMaps and Secrets,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a ConfigMap",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0015.html",
|
||
"node_id":"cce_10_0015.xml",
|
||
"product_code":"cce",
|
||
"code":"390",
|
||
"des":"After a ConfigMap is created, it can be used in three workload scenarios: environment variables, command line parameters, and data volumes.Configuring Environment Variabl",
|
||
"doc_type":"usermanual2",
|
||
"kw":"environment variables,command line parameters,data volumes,Using a ConfigMap,ConfigMaps and Secrets,",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using a ConfigMap",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0153.html",
|
||
"node_id":"cce_10_0153.xml",
|
||
"product_code":"cce",
|
||
"code":"391",
|
||
"des":"A secret is a type of resource that holds sensitive data, such as authentication and key information. Its content is user-defined. After creating secrets, you can use the",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Opaque,kubernetes.io/dockerconfigjson,kubernetes.io/tls,Opaque,kubernetes.io/dockerconfigjson,kubern",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a Secret",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0016.html",
|
||
"node_id":"cce_10_0016.xml",
|
||
"product_code":"cce",
|
||
"code":"392",
|
||
"des":"After secrets are created, they can be mounted as data volumes or be exposed as environment variables to be used by a container in a pod.Do not perform any operation on t",
|
||
"doc_type":"usermanual2",
|
||
"kw":"data volumes,environment variables,Using a Secret,ConfigMaps and Secrets,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using a Secret",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0388.html",
|
||
"node_id":"cce_10_0388.xml",
|
||
"product_code":"cce",
|
||
"code":"393",
|
||
"des":"By default, CCE creates the following secrets in each namespace:default-secretpaas.elbdefault-token-xxxxx (xxxxx is a random number.)The functions of these secrets are de",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Cluster Secrets,ConfigMaps and Secrets,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cluster Secrets",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0064.html",
|
||
"node_id":"cce_10_0064.xml",
|
||
"product_code":"cce",
|
||
"code":"394",
|
||
"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":"usermanual2",
|
||
"kw":"Add-ons",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Add-ons",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0277.html",
|
||
"node_id":"cce_10_0277.xml",
|
||
"product_code":"cce",
|
||
"code":"395",
|
||
"des":"CCE provides multiple types of add-ons to extend cluster functions and meet feature requirements. You can install add-ons as required.CCE uses Helm charts to deploy add-o",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CoreDNS,DNS server,domain name resolution,Kubernetes,chain add-on,Overview,Add-ons,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0907.html",
|
||
"node_id":"cce_10_0907.xml",
|
||
"product_code":"cce",
|
||
"code":"396",
|
||
"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":"usermanual2",
|
||
"kw":"Scheduling and Elasticity Add-ons",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Scheduling and Elasticity Add-ons",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0193.html",
|
||
"node_id":"cce_10_0193.xml",
|
||
"product_code":"cce",
|
||
"code":"397",
|
||
"des":"Volcano is a batch processing platform based on Kubernetes. It provides a series of features required by machine learning, deep learning, bioinformatics, genomics, and ot",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Volcano Scheduler,Scheduling and Elasticity Add-ons,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Volcano Scheduler",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0154.html",
|
||
"node_id":"cce_10_0154.xml",
|
||
"product_code":"cce",
|
||
"code":"398",
|
||
"des":"Autoscaler is an important Kubernetes controller. It supports microservice scaling and is key to serverless design.When the CPU or memory usage of a microservice is too h",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CCE Cluster Autoscaler,Scheduling and Elasticity Add-ons,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CCE Cluster Autoscaler",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0240.html",
|
||
"node_id":"cce_10_0240.xml",
|
||
"product_code":"cce",
|
||
"code":"399",
|
||
"des":"CCE Advanced HPA (cce-hpa-controller) is a CCE-developed add-on, which can be used to flexibly scale in or out Deployments based on metrics such as CPU usage and memory u",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CCE Advanced HPA,Scheduling and Elasticity Add-ons,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CCE Advanced HPA",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0908.html",
|
||
"node_id":"cce_10_0908.xml",
|
||
"product_code":"cce",
|
||
"code":"400",
|
||
"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":"usermanual2",
|
||
"kw":"Cloud Native Observability Add-ons",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cloud Native Observability Add-ons",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0406.html",
|
||
"node_id":"cce_10_0406.xml",
|
||
"product_code":"cce",
|
||
"code":"401",
|
||
"des":"Cloud Native Cluster Monitoring (kube-prometheus-stack) uses Prometheus-operator and Prometheus to provide easy-to-use, end-to-end Kubernetes cluster monitoring.Open sour",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Cloud Native Cluster Monitoring,Cloud Native Observability Add-ons,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cloud Native Cluster Monitoring",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0132.html",
|
||
"node_id":"cce_10_0132.xml",
|
||
"product_code":"cce",
|
||
"code":"402",
|
||
"des":"CCE Node Problem Detector (NPD) is an add-on that monitors abnormal events of cluster nodes and connects to a third-party monitoring platform. It is a daemon running on e",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CCE Node Problem Detector,Cloud Native Observability Add-ons,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CCE Node Problem Detector",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0205.html",
|
||
"node_id":"cce_10_0205.xml",
|
||
"product_code":"cce",
|
||
"code":"403",
|
||
"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":"usermanual2",
|
||
"kw":"Kubernetes Metrics Server,Cloud Native Observability Add-ons,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes Metrics Server",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0909.html",
|
||
"node_id":"cce_10_0909.xml",
|
||
"product_code":"cce",
|
||
"code":"404",
|
||
"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":"usermanual2",
|
||
"kw":"Cloud Native Heterogeneous Computing Add-ons",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cloud Native Heterogeneous Computing Add-ons",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0141.html",
|
||
"node_id":"cce_10_0141.xml",
|
||
"product_code":"cce",
|
||
"code":"405",
|
||
"des":"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.The driver to be downloaded must b",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CCE AI Suite (NVIDIA GPU),Cloud Native Heterogeneous Computing Add-ons,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CCE AI Suite (NVIDIA GPU)",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0910.html",
|
||
"node_id":"cce_10_0910.xml",
|
||
"product_code":"cce",
|
||
"code":"406",
|
||
"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":"usermanual2",
|
||
"kw":"Container Network Add-ons",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Container Network Add-ons",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0129.html",
|
||
"node_id":"cce_10_0129.xml",
|
||
"product_code":"cce",
|
||
"code":"407",
|
||
"des":"CoreDNS is a DNS server that provides domain name resolution for Kubernetes clusters through a chain add-on.CoreDNS is an open-source software and has been a part of CNCF",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CoreDNS,CoreDNS,Container Network Add-ons,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CoreDNS",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0034.html",
|
||
"node_id":"cce_10_0034.xml",
|
||
"product_code":"cce",
|
||
"code":"408",
|
||
"des":"Kubernetes uses kube-proxy to expose Services and provide load balancing. The implementation is at the transport layer. When it comes to Internet applications, where a bu",
|
||
"doc_type":"usermanual2",
|
||
"kw":"NGINX Ingress Controller,Container Network Add-ons,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"NGINX Ingress Controller",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0911.html",
|
||
"node_id":"cce_10_0911.xml",
|
||
"product_code":"cce",
|
||
"code":"409",
|
||
"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":"usermanual2",
|
||
"kw":"Container Storage Add-ons",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Container Storage Add-ons",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0066.html",
|
||
"node_id":"cce_10_0066.xml",
|
||
"product_code":"cce",
|
||
"code":"410",
|
||
"des":"Everest is a cloud native container storage system, which enables clusters of Kubernetes v1.15.6 or later to access cloud storage services through the CSI.Everest is a sy",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CCE Container Storage (Everest),Container Storage Add-ons,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CCE Container Storage (Everest)",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0127.html",
|
||
"node_id":"cce_10_0127.xml",
|
||
"product_code":"cce",
|
||
"code":"411",
|
||
"des":"CCE Container Storage (FlexVolume), also called storage-driver, functions as a standard Kubernetes FlexVolume plugin to allow containers to use EVS, SFS, OBS, and SFS Tur",
|
||
"doc_type":"usermanual2",
|
||
"kw":"FlexVolume (Discarded),Container Storage Add-ons,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"FlexVolume (Discarded)",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0019.html",
|
||
"node_id":"cce_10_0019.xml",
|
||
"product_code":"cce",
|
||
"code":"412",
|
||
"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":"usermanual2",
|
||
"kw":"Helm Chart",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Helm Chart",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0191.html",
|
||
"node_id":"cce_10_0191.xml",
|
||
"product_code":"cce",
|
||
"code":"413",
|
||
"des":"CCE provides a console for managing Helm charts, helping you easily deploy applications using the charts and manage applications on the console.Helm is a package manager ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview of a Chart,Helm Chart,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview of a Chart",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0146.html",
|
||
"node_id":"cce_10_0146.xml",
|
||
"product_code":"cce",
|
||
"code":"414",
|
||
"des":"On the CCE console, you can upload a Helm chart package, deploy it, and manage the deployed pods.The number of charts that can be uploaded by a single user is limited. Th",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Deploying an Application from a Chart,Helm Chart,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Deploying an Application from a Chart",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0421.html",
|
||
"node_id":"cce_10_0421.xml",
|
||
"product_code":"cce",
|
||
"code":"415",
|
||
"des":"Helm v2 stops at version 2.17.0. Currently, Helm v3 is the standard in the Helm community. You are advised to switch your charts to Helm v3 format as soon as possible.Cha",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Differences Between Helm v2 and Helm v3 and Adaptation Solutions,Helm Chart,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Differences Between Helm v2 and Helm v3 and Adaptation Solutions",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0420.html",
|
||
"node_id":"cce_10_0420.xml",
|
||
"product_code":"cce",
|
||
"code":"416",
|
||
"des":"The Kubernetes cluster created on CCE has been connected to kubectl. For details, see Using kubectl.This section uses Helm v2.17.0 as an example.For other versions, visit",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Deploying an Application Through the Helm v2 Client,Helm Chart,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Deploying an Application Through the Helm v2 Client",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0144.html",
|
||
"node_id":"cce_10_0144.xml",
|
||
"product_code":"cce",
|
||
"code":"417",
|
||
"des":"The Kubernetes cluster created on CCE has been connected to kubectl. For details, see Using kubectl.To pull a public image when deploying Helm, ensure an EIP has been bou",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Deploying an Application Through the Helm v3 Client,Helm Chart,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Deploying an Application Through the Helm v3 Client",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0422.html",
|
||
"node_id":"cce_10_0422.xml",
|
||
"product_code":"cce",
|
||
"code":"418",
|
||
"des":"CCE fully supports Helm v3. This section guides you to convert a Helm v2 release to Helm v3. Helm v3 discards or reconstructs some Helm v2 functions at the bottom layer. ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Converting a Release from Helm v2 to v3,Helm Chart,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Converting a Release from Helm v2 to v3",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0164.html",
|
||
"node_id":"cce_10_0164.xml",
|
||
"product_code":"cce",
|
||
"code":"419",
|
||
"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":"usermanual2",
|
||
"kw":"Permissions",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Permissions",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0187.html",
|
||
"node_id":"cce_10_0187.xml",
|
||
"product_code":"cce",
|
||
"code":"420",
|
||
"des":"CCE permissions management allows you to assign permissions to IAM users and user groups under your tenant accounts. CCE combines the advantages of Identity and Access Ma",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Permissions Overview,Permissions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Permissions Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0188.html",
|
||
"node_id":"cce_10_0188.xml",
|
||
"product_code":"cce",
|
||
"code":"421",
|
||
"des":"CCE cluster-level permissions are assigned based on IAM system policies and custom policies. You can use user groups to assign permissions to IAM users.Cluster permission",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Granting Cluster Permissions to an IAM User,Permissions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Granting Cluster Permissions to an IAM User",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0189.html",
|
||
"node_id":"cce_10_0189.xml",
|
||
"product_code":"cce",
|
||
"code":"422",
|
||
"des":"You can regulate users' or user groups' access to Kubernetes resources in a single namespace based on their Kubernetes RBAC roles. The RBAC API declares four kinds of Kub",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Namespace Permissions (Kubernetes RBAC-based),Permissions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Namespace Permissions (Kubernetes RBAC-based)",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0245.html",
|
||
"node_id":"cce_10_0245.xml",
|
||
"product_code":"cce",
|
||
"code":"423",
|
||
"des":"The conventional distributed task scheduling mode is being replaced by Kubernetes. CCE allows you to easily deploy, manage, and scale containerized applications in the cl",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Example: Designing and Configuring Permissions for Users in a Department,Permissions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Example: Designing and Configuring Permissions for Users in a Department",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0190.html",
|
||
"node_id":"cce_10_0190.xml",
|
||
"product_code":"cce",
|
||
"code":"424",
|
||
"des":"Some CCE permissions policies depend on the policies of other cloud services. To view or use other cloud resources on the CCE console, enable the access control feature o",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Permission Dependency of the CCE Console,Permissions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Permission Dependency of the CCE Console",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0477.html",
|
||
"node_id":"cce_10_0477.xml",
|
||
"product_code":"cce",
|
||
"code":"425",
|
||
"des":"In clusters earlier than v1.21, a token is obtained by mounting the secret of the service account to a pod. Tokens obtained this way are permanent. This approach is no lo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Service Account Token Security Improvement,Permissions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Service Account Token Security Improvement",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0781.html",
|
||
"node_id":"cce_10_0781.xml",
|
||
"product_code":"cce",
|
||
"code":"426",
|
||
"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":"usermanual2",
|
||
"kw":"Settings",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Settings",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0782.html",
|
||
"node_id":"cce_10_0782.xml",
|
||
"product_code":"cce",
|
||
"code":"427",
|
||
"des":"Settings offers you an entry to check and modify the basic settings of clusters. It includes information from dimension like Cluster Information, Cluster Settings, Master",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Dashboard,Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Dashboard",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0783.html",
|
||
"node_id":"cce_10_0783.xml",
|
||
"product_code":"cce",
|
||
"code":"428",
|
||
"des":"kubectl: You need to download and configure the kubectl and kubeconfig configuration files first, and then use kubectl to access a Kubernetes cluster. For details, see Co",
|
||
"doc_type":"usermanual2",
|
||
"kw":"SAN,Cluster Access,Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cluster Access",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0784.html",
|
||
"node_id":"cce_10_0784.xml",
|
||
"product_code":"cce",
|
||
"code":"429",
|
||
"des":"You can configure a default security group and secondary CIDR block for your clusters.If a container CIDR block configured during cluster creation cannot meet service exp",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Associating a pod with a subnet,Associating a pod with a security group,Network,Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Network",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0785.html",
|
||
"node_id":"cce_10_0785.xml",
|
||
"product_code":"cce",
|
||
"code":"430",
|
||
"des":"Basic kube-scheduler configurations and Volcano-backed advanced scheduling are available. You can enable advanced scheduling functions such as bin packing, priority-based",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Scheduling,Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Scheduling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0786.html",
|
||
"node_id":"cce_10_0786.xml",
|
||
"product_code":"cce",
|
||
"code":"431",
|
||
"des":"CCE Cluster Autoscaler comprehensively checks the resource statuses of an entire cluster. When the load of a microservice is high (for example, the CPU or memory usage is",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Auto Scaling,Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Auto Scaling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0836.html",
|
||
"node_id":"cce_10_0836.xml",
|
||
"product_code":"cce",
|
||
"code":"432",
|
||
"des":"CCE monitors applications and resources and collects metrics and events to analyze application health status. You can choose Settings from the navigation pane, click the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Monitoring,Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Monitoring",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0787.html",
|
||
"node_id":"cce_10_0787.xml",
|
||
"product_code":"cce",
|
||
"code":"433",
|
||
"des":"Typical native configuration items are provided. You can configure native community management components such as kube-apiserver and kube-controller for the best cloud na",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Kubernetes,Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Kubernetes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_10_0788.html",
|
||
"node_id":"cce_10_0788.xml",
|
||
"product_code":"cce",
|
||
"code":"434",
|
||
"des":"Default Cluster Driver: specifies the default GPU driver version used by the GPU nodes in a cluster. To use a custom driver, enter the download link of the NVIDIA driver.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Heterogeneous Resources,Settings,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Heterogeneous Resources",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0000.html",
|
||
"node_id":"cce_bestpractice_0000.xml",
|
||
"product_code":"cce",
|
||
"code":"435",
|
||
"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":"usermanual2",
|
||
"kw":"Best Practice",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"opensource":"true",
|
||
"documenttype":"usermanual2",
|
||
"IsMulti":"Yes"
|
||
}
|
||
],
|
||
"title":"Best Practice",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00006.html",
|
||
"node_id":"cce_bestpractice_00006.xml",
|
||
"product_code":"cce",
|
||
"code":"436",
|
||
"des":"Security, efficiency, stability, and availability are common requirements on all cloud services. To meet these requirements, the system availability, data reliability, an",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Checklist for Deploying Containerized Applications in the Cloud,Best Practice,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Checklist for Deploying Containerized Applications in the Cloud",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0321.html",
|
||
"node_id":"cce_bestpractice_0321.xml",
|
||
"product_code":"cce",
|
||
"code":"437",
|
||
"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":"usermanual2",
|
||
"kw":"Containerization",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Containerization",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0001.html",
|
||
"node_id":"cce_bestpractice_0001.xml",
|
||
"product_code":"cce",
|
||
"code":"438",
|
||
"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":"usermanual2",
|
||
"kw":"Containerizing an Enterprise Application (ERP)",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Containerizing an Enterprise Application (ERP)",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0002.html",
|
||
"node_id":"cce_bestpractice_0002.xml",
|
||
"product_code":"cce",
|
||
"code":"439",
|
||
"des":"This chapter provides CCE best practices to walk you through the application containerization.A container is a lightweight high-performance resource isolation mechanism i",
|
||
"doc_type":"usermanual2",
|
||
"kw":"enterprise resource planning (ERP),Solution Overview,Containerizing an Enterprise Application (ERP),",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Solution Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0340.html",
|
||
"node_id":"cce_bestpractice_0340.xml",
|
||
"product_code":"cce",
|
||
"code":"440",
|
||
"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":"usermanual2",
|
||
"kw":"Procedure",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Procedure",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0003.html",
|
||
"node_id":"cce_bestpractice_0003.xml",
|
||
"product_code":"cce",
|
||
"code":"441",
|
||
"des":"This tutorial describes how to containerize an ERP system by migrating it from a VM to CCE.No recoding or re-architecting is required. You only need to pack the entire ap",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Containerizing an Entire Application,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Containerizing an Entire Application",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0004.html",
|
||
"node_id":"cce_bestpractice_0004.xml",
|
||
"product_code":"cce",
|
||
"code":"442",
|
||
"des":"To fully containerize an application, you must go through the entire process.This involves analyzing the application, setting up the runtime environment for the applicati",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Containerization Process,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Containerization Process",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0005.html",
|
||
"node_id":"cce_bestpractice_0005.xml",
|
||
"product_code":"cce",
|
||
"code":"443",
|
||
"des":"Before containerizing an application, analyze the running environment and dependencies of the application, and get familiar with the application deployment mode. For deta",
|
||
"doc_type":"usermanual2",
|
||
"kw":"containerizing an application,Analyzing the Application,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Analyzing the Application",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0006.html",
|
||
"node_id":"cce_bestpractice_0006.xml",
|
||
"product_code":"cce",
|
||
"code":"444",
|
||
"des":"After application analysis, you have gained the understanding of the OS and runtime required for running the application. Make the following preparations:Installing Docke",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Preparing the Application Runtime,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Preparing the Application Runtime",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0007.html",
|
||
"node_id":"cce_bestpractice_0007.xml",
|
||
"product_code":"cce",
|
||
"code":"445",
|
||
"des":"During application containerization, prepare a startup script. The method of compiling this script is the same as that of compiling a shell script. The startup script is ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Compiling a Startup Script,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Compiling a Startup Script",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0008.html",
|
||
"node_id":"cce_bestpractice_0008.xml",
|
||
"product_code":"cce",
|
||
"code":"446",
|
||
"des":"An image is the basis of a container. A container runs based on the content defined in the image. An image has multiple layers. Each layer includes the modifications made",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Compiling the Dockerfile,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Compiling the Dockerfile",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0009.html",
|
||
"node_id":"cce_bestpractice_0009.xml",
|
||
"product_code":"cce",
|
||
"code":"447",
|
||
"des":"This section describes how to build an entire application into a Docker image. After building an image, you can use the image to deploy and upgrade the application. This ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Building and Uploading an Image,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Building and Uploading an Image",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0010.html",
|
||
"node_id":"cce_bestpractice_0010.xml",
|
||
"product_code":"cce",
|
||
"code":"448",
|
||
"des":"This section describes how to deploy a workload on CCE. When using CCE for the first time, create an initial cluster and add a node into the cluster.Containerized workloa",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating a Container Workload,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating a Container Workload",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00237.html",
|
||
"node_id":"cce_bestpractice_00237.xml",
|
||
"product_code":"cce",
|
||
"code":"449",
|
||
"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":"usermanual2",
|
||
"kw":"Migration",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Migration",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0013.html",
|
||
"node_id":"cce_bestpractice_0013.xml",
|
||
"product_code":"cce",
|
||
"code":"450",
|
||
"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":"usermanual2",
|
||
"kw":"Migrating Kubernetes Clusters to CCE",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Migrating Kubernetes Clusters to CCE",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0307.html",
|
||
"node_id":"cce_bestpractice_0307.xml",
|
||
"product_code":"cce",
|
||
"code":"451",
|
||
"des":"Containers are growing in popularity and Kubernetes simplifies containerized deployment. Many companies choose to build their own Kubernetes clusters. However, the O&M wo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Solution Overview,Migrating Kubernetes Clusters to CCE,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Solution Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0014.html",
|
||
"node_id":"cce_bestpractice_0014.xml",
|
||
"product_code":"cce",
|
||
"code":"452",
|
||
"des":"CCE allows you to customize cluster resources to meet various service requirements. Table 1 lists the key performance parameters of a cluster and provides the planned val",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Planning Resources for the Target Cluster,Migrating Kubernetes Clusters to CCE,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Planning Resources for the Target Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0326.html",
|
||
"node_id":"cce_bestpractice_0326.xml",
|
||
"product_code":"cce",
|
||
"code":"453",
|
||
"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":"usermanual2",
|
||
"kw":"Procedure",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Procedure",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0059.html",
|
||
"node_id":"cce_bestpractice_0059.xml",
|
||
"product_code":"cce",
|
||
"code":"454",
|
||
"des":"If your migration does not involve resources outside a cluster listed in Table 1 or you do not need to use other services to update resources after the migration, skip th",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Migrating Resources Outside a Cluster,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Migrating Resources Outside a Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0310.html",
|
||
"node_id":"cce_bestpractice_0310.xml",
|
||
"product_code":"cce",
|
||
"code":"455",
|
||
"des":"Velero is an open-source backup and migration tool for Kubernetes clusters. With Restic's PV data backup capability integrated into it, Velero can back up Kubernetes reso",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Installing the Migration Tool,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Installing the Migration Tool",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0024.html",
|
||
"node_id":"cce_bestpractice_0024.xml",
|
||
"product_code":"cce",
|
||
"code":"456",
|
||
"des":"WordPress is used as an example to describe how to migrate an application from an on-premises Kubernetes cluster to a CCE cluster. The WordPress application consists of t",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Migrating Resources in a Cluster,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Migrating Resources in a Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0312.html",
|
||
"node_id":"cce_bestpractice_0312.xml",
|
||
"product_code":"cce",
|
||
"code":"457",
|
||
"des":"The WordPress and MySQL images used in this example can be pulled from SWR. Therefore, the image pull failure (ErrImagePull) will not occur. If the application to be migr",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Updating Resources Accordingly,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Updating Resources Accordingly",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0313.html",
|
||
"node_id":"cce_bestpractice_0313.xml",
|
||
"product_code":"cce",
|
||
"code":"458",
|
||
"des":"Cluster migration involves full migration of application data, which may cause intra-application adaptation problems. In this example, after the cluster is migrated, the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Performing Additional Tasks,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Performing Additional Tasks",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0314.html",
|
||
"node_id":"cce_bestpractice_0314.xml",
|
||
"product_code":"cce",
|
||
"code":"459",
|
||
"des":"Both HostPath and Local volumes are local storage volumes. However, the Restic tool integrated in Velero cannot back up the PVs of the HostPath type and supports only the",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Troubleshooting,Procedure,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Troubleshooting",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0322.html",
|
||
"node_id":"cce_bestpractice_0322.xml",
|
||
"product_code":"cce",
|
||
"code":"460",
|
||
"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":"usermanual2",
|
||
"kw":"DevOps",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"DevOps",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0324.html",
|
||
"node_id":"cce_bestpractice_0324.xml",
|
||
"product_code":"cce",
|
||
"code":"461",
|
||
"des":"GitLab is an open-source version management system developed with Ruby on Rails for Git project repository management. It supports web-based access to public and private ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Interconnecting GitLab with SWR and CCE for CI/CD,DevOps,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Interconnecting GitLab with SWR and CCE for CI/CD",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0323.html",
|
||
"node_id":"cce_bestpractice_0323.xml",
|
||
"product_code":"cce",
|
||
"code":"462",
|
||
"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":"usermanual2",
|
||
"kw":"Disaster Recovery",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Disaster Recovery",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10017.html",
|
||
"node_id":"cce_bestpractice_10017.xml",
|
||
"product_code":"cce",
|
||
"code":"463",
|
||
"des":"This section describes the recommended configurations for a Kubernetes cluster in which applications can run stably and reliably.Multiple regions are provided for you to ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Recommended Configurations for HA CCE Clusters,Disaster Recovery,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Recommended Configurations for HA CCE Clusters",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00220.html",
|
||
"node_id":"cce_bestpractice_00220.xml",
|
||
"product_code":"cce",
|
||
"code":"464",
|
||
"des":"To achieve high availability for your CCE containers, you can do as follows:Deploy three master nodes for the cluster.Create nodes in different AZs. When nodes are deploy",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Implementing High Availability for Applications in CCE,Disaster Recovery,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Implementing High Availability for Applications in CCE",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10027.html",
|
||
"node_id":"cce_bestpractice_10027.xml",
|
||
"product_code":"cce",
|
||
"code":"465",
|
||
"des":"CCE offers various add-ons that enhance the cloud native capabilities of clusters. These add-ons include features like container scheduling and elasticity, cloud native o",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Implementing High Availability for Add-ons in CCE,Disaster Recovery,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Implementing High Availability for Add-ons in CCE",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0315.html",
|
||
"node_id":"cce_bestpractice_0315.xml",
|
||
"product_code":"cce",
|
||
"code":"466",
|
||
"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":"usermanual2",
|
||
"kw":"Security",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Security",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0317.html",
|
||
"node_id":"cce_bestpractice_0317.xml",
|
||
"product_code":"cce",
|
||
"code":"467",
|
||
"des":"To ensure security, it is recommended that you configure a cluster in the following manner.Kubernetes releases a major version in about four months. CCE follows the same ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuration Suggestions on CCE Cluster Security,Security,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuration Suggestions on CCE Cluster Security",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0318.html",
|
||
"node_id":"cce_bestpractice_0318.xml",
|
||
"product_code":"cce",
|
||
"code":"468",
|
||
"des":"Do not bind an EIP to a node unless necessary to reduce the attack surface.If an EIP must be used, properly configure the firewall or security group rules to restrict acc",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuration Suggestions on CCE Node Security,Security,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuration Suggestions on CCE Node Security",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10046.html",
|
||
"node_id":"cce_bestpractice_10046.xml",
|
||
"product_code":"cce",
|
||
"code":"469",
|
||
"des":"Container technology uses Linux namespaces and cgroups to isolate and control resources between containers and nodes. Namespaces provide kernel-level isolation, allowing ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuration Suggestions on CCE Container Runtime Security,Security,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuration Suggestions on CCE Container Runtime Security",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0319.html",
|
||
"node_id":"cce_bestpractice_0319.xml",
|
||
"product_code":"cce",
|
||
"code":"470",
|
||
"des":"The nodeSelector or nodeAffinity is used to limit the range of nodes to which applications can be scheduled, preventing the entire cluster from being threatened due to th",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuration Suggestions on CCE Container Security,Security,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuration Suggestions on CCE Container Security",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10047.html",
|
||
"node_id":"cce_bestpractice_10047.xml",
|
||
"product_code":"cce",
|
||
"code":"471",
|
||
"des":"Container images are the primary defense against external attacks and are crucial for securing applications, systems, and the entire supply chain. If an image is insecure",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuration Suggestions on CCE Container Image Security,Security,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuration Suggestions on CCE Container Image Security",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0320.html",
|
||
"node_id":"cce_bestpractice_0320.xml",
|
||
"product_code":"cce",
|
||
"code":"472",
|
||
"des":"Currently, CCE has configured static encryption for secret resources. The secrets created by users will be encrypted and stored in etcd of the CCE cluster. Secrets can be",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuration Suggestions on CCE Secret Security,Security,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuration Suggestions on CCE Secret Security",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0333.html",
|
||
"node_id":"cce_bestpractice_0333.xml",
|
||
"product_code":"cce",
|
||
"code":"473",
|
||
"des":"A workload identity enables workloads within a cluster to act as IAM users, granting them access to cloud services without the need for an IAM account's AK and SK. This h",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuration Suggestions on CCE Workload Identity Security,Security,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuration Suggestions on CCE Workload Identity Security",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0090.html",
|
||
"node_id":"cce_bestpractice_0090.xml",
|
||
"product_code":"cce",
|
||
"code":"474",
|
||
"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":"usermanual2",
|
||
"kw":"Auto Scaling",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Auto Scaling",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00282.html",
|
||
"node_id":"cce_bestpractice_00282.xml",
|
||
"product_code":"cce",
|
||
"code":"475",
|
||
"des":"The best way to handle surging traffic is to automatically adjust the number of machines based on the traffic volume or resource usage, which is called scaling.When deplo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using HPA and CA for Auto Scaling of Workloads and Nodes,Auto Scaling,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using HPA and CA for Auto Scaling of Workloads and Nodes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10008.html",
|
||
"node_id":"cce_bestpractice_10008.xml",
|
||
"product_code":"cce",
|
||
"code":"476",
|
||
"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":"usermanual2",
|
||
"kw":"Monitoring",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Monitoring",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10009.html",
|
||
"node_id":"cce_bestpractice_10009.xml",
|
||
"product_code":"cce",
|
||
"code":"477",
|
||
"des":"Generally, a user has different clusters for different purposes, such as production, testing, and development. To monitor, collect, and view metrics of these clusters, yo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Monitoring Multiple Clusters Using Prometheus,Monitoring,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Monitoring Multiple Clusters Using Prometheus",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0050.html",
|
||
"node_id":"cce_bestpractice_0050.xml",
|
||
"product_code":"cce",
|
||
"code":"478",
|
||
"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":"usermanual2",
|
||
"kw":"Cluster",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10016.html",
|
||
"node_id":"cce_bestpractice_10016.xml",
|
||
"product_code":"cce",
|
||
"code":"479",
|
||
"des":"When you use CCE to create a Kubernetes cluster, there are multiple configuration options and terms. This section compares the key configurations for CCE clusters and pro",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Suggestions on CCE Cluster Selection,Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Suggestions on CCE Cluster Selection",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00222.html",
|
||
"node_id":"cce_bestpractice_00222.xml",
|
||
"product_code":"cce",
|
||
"code":"480",
|
||
"des":"This section describes how to set up a VPC with IPv6 CIDR block and create a cluster and nodes with an IPv6 address in the VPC, so that the nodes can access the Internet.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Creating an IPv4/IPv6 Dual-Stack Cluster in CCE,Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Creating an IPv4/IPv6 Dual-Stack Cluster in CCE",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10020.html",
|
||
"node_id":"cce_bestpractice_10020.xml",
|
||
"product_code":"cce",
|
||
"code":"481",
|
||
"des":"When creating a node, use the pre- or -installation commands to install tools or perform security hardening on the node. This section provides guidance for you to correct",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Executing the Pre- or Post-installation Commands During Node Creation,Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Executing the Pre- or Post-installation Commands During Node Creation",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00254.html",
|
||
"node_id":"cce_bestpractice_00254.xml",
|
||
"product_code":"cce",
|
||
"code":"482",
|
||
"des":"The kubectl command line tool relies on the kubeconfig configuration file to locate the necessary authentication information to select a cluster and communicate with its ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Connecting to Multiple Clusters Using kubectl,Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Connecting to Multiple Clusters Using kubectl",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10012.html",
|
||
"node_id":"cce_bestpractice_10012.xml",
|
||
"product_code":"cce",
|
||
"code":"483",
|
||
"des":"When a node is created, a data disk is attached by default for a container runtime and kubelet. The data disk used by the container runtime and kubelet cannot be detached",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Selecting a Data Disk for the Node,Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Selecting a Data Disk for the Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10024.html",
|
||
"node_id":"cce_bestpractice_10024.xml",
|
||
"product_code":"cce",
|
||
"code":"484",
|
||
"des":"As services grow, the Kubernetes cluster scales up, putting more pressure on the control plane. If the control plane cannot handle the load, clusters may fail to provide ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Protecting a CCE Cluster Against Overload,Cluster,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Protecting a CCE Cluster Against Overload",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0052.html",
|
||
"node_id":"cce_bestpractice_0052.xml",
|
||
"product_code":"cce",
|
||
"code":"485",
|
||
"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":"usermanual2",
|
||
"kw":"Networking",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Networking",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00004.html",
|
||
"node_id":"cce_bestpractice_00004.xml",
|
||
"product_code":"cce",
|
||
"code":"486",
|
||
"des":"Before creating a cluster on CCE, determine the number of VPCs, number of subnets, container CIDR blocks, and Services for access based on service requirements.This topic",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Planning CIDR Blocks for a Cluster,Networking,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Planning CIDR Blocks for a Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00162.html",
|
||
"node_id":"cce_bestpractice_00162.xml",
|
||
"product_code":"cce",
|
||
"code":"487",
|
||
"des":"CCE uses proprietary, high-performance container networking add-ons to support the tunnel network, Cloud Native 2.0 network, and VPC network models.After a cluster is cre",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Selecting a Network Model,Networking,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Selecting a Network Model",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00231.html",
|
||
"node_id":"cce_bestpractice_00231.xml",
|
||
"product_code":"cce",
|
||
"code":"488",
|
||
"des":"Sticky sessions ensure continuity and consistency when you access applications. If a load balancer is deployed between a client and backend servers, connections may be fo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Implementing Sticky Session Through Load Balancing,Networking,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Implementing Sticky Session Through Load Balancing",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00035.html",
|
||
"node_id":"cce_bestpractice_00035.xml",
|
||
"product_code":"cce",
|
||
"code":"489",
|
||
"des":"When using containers, clients may communicate with them through multiple proxy servers. However, this can cause issues with transferring the clients' source IP addresses",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Obtaining the Client Source IP Address for a Container,Networking,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Obtaining the Client Source IP Address for a Container",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10006.html",
|
||
"node_id":"cce_bestpractice_10006.xml",
|
||
"product_code":"cce",
|
||
"code":"490",
|
||
"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":"usermanual2",
|
||
"kw":"CoreDNS Configuration Optimization",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CoreDNS Configuration Optimization",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0346.html",
|
||
"node_id":"cce_bestpractice_0346.xml",
|
||
"product_code":"cce",
|
||
"code":"491",
|
||
"des":"DNS is one of the important basic services in Kubernetes. When the container DNS policy is not properly configured and the cluster scale is large, DNS resolution may time",
|
||
"doc_type":"usermanual2",
|
||
"kw":"CoreDNS Optimization Overview,CoreDNS Configuration Optimization,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"CoreDNS Optimization Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0347.html",
|
||
"node_id":"cce_bestpractice_0347.xml",
|
||
"product_code":"cce",
|
||
"code":"492",
|
||
"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":"usermanual2",
|
||
"kw":"Client",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Client",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0348.html",
|
||
"node_id":"cce_bestpractice_0348.xml",
|
||
"product_code":"cce",
|
||
"code":"493",
|
||
"des":"DNS resolution is frequently used in Kubernetes clusters. Based on the characteristics of DNS resolution in Kubernetes, you can optimize domain name resolution requests i",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Optimizing Domain Name Resolution Requests,Client,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Optimizing Domain Name Resolution Requests",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0349.html",
|
||
"node_id":"cce_bestpractice_0349.xml",
|
||
"product_code":"cce",
|
||
"code":"494",
|
||
"des":"The musl libc library of the Alpine container image differs from the standard glibc library in the following aspects:Alpine 3.3 and earlier versions do not support the se",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Selecting a Proper Image,Client,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Selecting a Proper Image",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0350.html",
|
||
"node_id":"cce_bestpractice_0350.xml",
|
||
"product_code":"cce",
|
||
"code":"495",
|
||
"des":"When kube-proxy uses IPVS load balancing, you may encounter DNS resolution timeout occasionally during CoreDNS scale-in or restart.This problem is caused by a Linux kerne",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Avoiding Occasional DNS Resolution Timeout Caused by IPVS Defects,Client,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Avoiding Occasional DNS Resolution Timeout Caused by IPVS Defects",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0352.html",
|
||
"node_id":"cce_bestpractice_0352.xml",
|
||
"product_code":"cce",
|
||
"code":"496",
|
||
"des":"CoreDNS provides simple functions and is compatible with different Kubernetes versions. CCE periodically synchronizes bugs from the community and upgrades the coredns add",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Upgrading the CoreDNS in the Cluster Timely,Client,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Upgrading the CoreDNS in the Cluster Timely",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0353.html",
|
||
"node_id":"cce_bestpractice_0353.xml",
|
||
"product_code":"cce",
|
||
"code":"497",
|
||
"des":"When the coredns add-on is started, it obtains the DNS configuration in the resolve.conf file from the deployed instance by default and uses the configuration as the upst",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Adjusting the DNS Configuration of the VPC and VM,Client,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Adjusting the DNS Configuration of the VPC and VM",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0354.html",
|
||
"node_id":"cce_bestpractice_0354.xml",
|
||
"product_code":"cce",
|
||
"code":"498",
|
||
"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":"usermanual2",
|
||
"kw":"Server",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Server",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0355.html",
|
||
"node_id":"cce_bestpractice_0355.xml",
|
||
"product_code":"cce",
|
||
"code":"499",
|
||
"des":"CoreDNS exposes health metrics such as resolution results through the standard Prometheus API to detect exceptions on the CoreDNS server or even upstream DNS server.Port ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Monitoring the coredns Add-on,Server,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Monitoring the coredns Add-on",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0356.html",
|
||
"node_id":"cce_bestpractice_0356.xml",
|
||
"product_code":"cce",
|
||
"code":"500",
|
||
"des":"In CCE clusters, the CoreDNS add-on is installed by default, and it can run on the same cluster nodes as your service containers. You need to pay attention to the followi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Adjusting the CoreDNS Deployment Status,Server,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Adjusting the CoreDNS Deployment Status",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0357.html",
|
||
"node_id":"cce_bestpractice_0357.xml",
|
||
"product_code":"cce",
|
||
"code":"501",
|
||
"des":"On the console, the CoreDNS add-on can only be configured with the preset specifications, which can satisfy most of the service requirements. In some scenarios where ther",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring CoreDNS,Server,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring CoreDNS",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10010.html",
|
||
"node_id":"cce_bestpractice_10010.xml",
|
||
"product_code":"cce",
|
||
"code":"502",
|
||
"des":"In the Cloud Native 2.0 network model, each pod is allocated an ENI or a sub-ENI (called container ENI). The speed of ENI creation and binding is slower than that of pod ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Pre-Binding Container ENI for CCE Turbo Clusters,Networking,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Pre-Binding Container ENI for CCE Turbo Clusters",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10041.html",
|
||
"node_id":"cce_bestpractice_10041.xml",
|
||
"product_code":"cce",
|
||
"code":"503",
|
||
"des":"In a CCE cluster that uses a VPC network, when pods try to communicate with external systems, CCE automatically translates the source IP addresses of the pods into the IP",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Accessing an IP Address Outside a Cluster That Uses a VPC Network Using Source Pod IP Addresses in t",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Accessing an IP Address Outside a Cluster That Uses a VPC Network Using Source Pod IP Addresses in the Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0053.html",
|
||
"node_id":"cce_bestpractice_0053.xml",
|
||
"product_code":"cce",
|
||
"code":"504",
|
||
"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":"usermanual2",
|
||
"kw":"Storage",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Storage",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00198.html",
|
||
"node_id":"cce_bestpractice_00198.xml",
|
||
"product_code":"cce",
|
||
"code":"505",
|
||
"des":"The storage classes that can be expanded for CCE nodes are as follows:EulerOS 2.9 is used as the sample OS. There is only one partition (/dev/vda1) with a capacity of 50 ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"base size,Expanding the Storage Space,Storage,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Expanding the Storage Space",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00199.html",
|
||
"node_id":"cce_bestpractice_00199.xml",
|
||
"product_code":"cce",
|
||
"code":"506",
|
||
"des":"Cross-account data sharing. For example, multiple teams within a company need to share data, but each team uses a different account.Cross-account data migration and backu",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Mounting Object Storage Across Accounts,Storage,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Mounting Object Storage Across Accounts",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00253.html",
|
||
"node_id":"cce_bestpractice_00253.xml",
|
||
"product_code":"cce",
|
||
"code":"507",
|
||
"des":"The minimum capacity of an SFS Turbo file system is 500 GiB. By default, the root directory of an SFS Turbo file system is mounted to a container which, in most case, doe",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Dynamically Creating an SFS Turbo Subdirectory Using StorageClass,Storage,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Dynamically Creating an SFS Turbo Subdirectory Using StorageClass",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0107.html",
|
||
"node_id":"cce_bestpractice_0107.xml",
|
||
"product_code":"cce",
|
||
"code":"508",
|
||
"des":"In clusters later than v1.15.11-r1, CSI (the everest add-on) has taken over all functions of fuxi FlexVolume (the storage-driver add-on) for managing container storage. Y",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Changing the Storage Class Used by a Cluster of v1.15 from FlexVolume to CSI Everest,Storage,User Gu",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Changing the Storage Class Used by a Cluster of v1.15 from FlexVolume to CSI Everest",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00281.html",
|
||
"node_id":"cce_bestpractice_00281.xml",
|
||
"product_code":"cce",
|
||
"code":"509",
|
||
"des":"When using storage resources in CCE, the most common method is to specify storageClassName to define the type of storage resources to be created when creating a PVC. The ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using Custom Storage Classes,Storage,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using Custom Storage Classes",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00284.html",
|
||
"node_id":"cce_bestpractice_00284.xml",
|
||
"product_code":"cce",
|
||
"code":"510",
|
||
"des":"EVS disks cannot be attached to a node deployed in another AZ. For example, the EVS disks in AZ 1 cannot be attached to a node in AZ 2. If the storage class csi-disk is u",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Scheduling EVS Disks Across AZs Using csi-disk-topology,Storage,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Scheduling EVS Disks Across AZs Using csi-disk-topology",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0051.html",
|
||
"node_id":"cce_bestpractice_0051.xml",
|
||
"product_code":"cce",
|
||
"code":"511",
|
||
"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":"usermanual2",
|
||
"kw":"Container",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Container",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00002.html",
|
||
"node_id":"cce_bestpractice_00002.xml",
|
||
"product_code":"cce",
|
||
"code":"512",
|
||
"des":"If a node has sufficient memory resources, a container on this node can use more memory resources than requested, but no more than limited. If the memory allocated to a c",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Properly Allocating Container Computing Resources,Container,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Properly Allocating Container Computing Resources",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00227.html",
|
||
"node_id":"cce_bestpractice_00227.xml",
|
||
"product_code":"cce",
|
||
"code":"513",
|
||
"des":"To access a Kubernetes cluster from a client, you can use the Kubernetes command line tool kubectl.Create a daemonSet file.vi daemonSet.yamlAn example YAML file is provid",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Modifying Kernel Parameters Using a Privileged Container,Container,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Modifying Kernel Parameters Using a Privileged Container",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00228.html",
|
||
"node_id":"cce_bestpractice_00228.xml",
|
||
"product_code":"cce",
|
||
"code":"514",
|
||
"des":"An init container is a type of container that starts and exits before the application containers start. If there are multiple init containers, they will be started in the",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using Init Containers to Initialize an Application,Container,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using Init Containers to Initialize an Application",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00226.html",
|
||
"node_id":"cce_bestpractice_00226.xml",
|
||
"product_code":"cce",
|
||
"code":"515",
|
||
"des":"If DNS or other related settings are inappropriate, you can use hostAliases to overwrite the resolution of the hostname at the pod level when adding entries to the /etc/h",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring the /etc/hosts File of a Pod Using hostAliases,Container,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring the /etc/hosts File of a Pod Using hostAliases",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0325.html",
|
||
"node_id":"cce_bestpractice_0325.xml",
|
||
"product_code":"cce",
|
||
"code":"516",
|
||
"des":"Linux allows you to create a core dump file if an application crashes, which contains the data the application had in memory at the time of the crash. You can analyze the",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Locating Container Faults Using the Core Dump File,Container,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Locating Container Faults Using the Core Dump File",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0055.html",
|
||
"node_id":"cce_bestpractice_0055.xml",
|
||
"product_code":"cce",
|
||
"code":"517",
|
||
"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":"usermanual2",
|
||
"kw":"Permission",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Permission",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_00221.html",
|
||
"node_id":"cce_bestpractice_00221.xml",
|
||
"product_code":"cce",
|
||
"code":"518",
|
||
"des":"By default, the kubeconfig file provided by CCE for users has permissions bound to the cluster-admin role, which are equivalent to the permissions of user root. It is dif",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Configuring kubeconfig for Fine-Grained Management on Cluster Resources,Permission,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Configuring kubeconfig for Fine-Grained Management on Cluster Resources",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_0300.html",
|
||
"node_id":"cce_bestpractice_0300.xml",
|
||
"product_code":"cce",
|
||
"code":"519",
|
||
"des":"CCE permissions are classified into cluster permissions and namespace permissions. Namespace permissions are based on Kubernetes RBAC and can be used to grant permissions",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Performing Cluster Namespace RBAC,Permission,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Performing Cluster Namespace RBAC",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10000.html",
|
||
"node_id":"cce_bestpractice_10000.xml",
|
||
"product_code":"cce",
|
||
"code":"520",
|
||
"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":"usermanual2",
|
||
"kw":"Release",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Release",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10001.html",
|
||
"node_id":"cce_bestpractice_10001.xml",
|
||
"product_code":"cce",
|
||
"code":"521",
|
||
"des":"When switching between old and new services, you may be challenged in ensuring the system service continuity. If a new service version is directly released to all users a",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Overview,Release,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Overview",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_bestpractice_10002.html",
|
||
"node_id":"cce_bestpractice_10002.xml",
|
||
"product_code":"cce",
|
||
"code":"522",
|
||
"des":"To implement grayscale release for a CCE cluster, deploy other open-source tools, such as Nginx Ingress, to the cluster or deploy services to a service mesh. These soluti",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Using Services to Implement Simple Grayscale Release and Blue-Green Deployment,Release,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Using Services to Implement Simple Grayscale Release and Blue-Green Deployment",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_0000.html",
|
||
"node_id":"cce_faq_0000.xml",
|
||
"product_code":"cce",
|
||
"code":"523",
|
||
"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":"usermanual2",
|
||
"kw":"FAQs",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
|
||
}
|
||
],
|
||
"title":"FAQs",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00006.html",
|
||
"node_id":"cce_faq_00006.xml",
|
||
"product_code":"cce",
|
||
"code":"524",
|
||
"des":"Why Cannot I Create a CCE Cluster?Is Management Scale of a Cluster Related to the Number of Master Nodes?How Do I Locate the Fault When a Cluster Is Unavailable?What Shou",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Common FAQ,FAQs,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Common FAQ",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00024.html",
|
||
"node_id":"cce_faq_00024.xml",
|
||
"product_code":"cce",
|
||
"code":"525",
|
||
"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":"usermanual2",
|
||
"kw":"Cluster",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cluster",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00278.html",
|
||
"node_id":"cce_faq_00278.xml",
|
||
"product_code":"cce",
|
||
"code":"526",
|
||
"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":"usermanual2",
|
||
"kw":"Cluster Creation",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cluster Creation",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00111.html",
|
||
"node_id":"cce_faq_00111.xml",
|
||
"product_code":"cce",
|
||
"code":"527",
|
||
"des":"This section describes how to locate and rectify the fault if you fail to create a CCE cluster.Possible causes:The Network Time Protocol daemon (ntpd) is not installed or",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Why Cannot I Create a CCE Cluster?,Cluster Creation,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Why Cannot I Create a CCE Cluster?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00090.html",
|
||
"node_id":"cce_faq_00090.xml",
|
||
"product_code":"cce",
|
||
"code":"528",
|
||
"des":"Management scale indicates the maximum number of nodes that can be managed by a cluster. If you select 50 nodes, the cluster can manage a maximum of 50 nodes.The number o",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Is Management Scale of a Cluster Related to the Number of Master Nodes?,Cluster Creation,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Is Management Scale of a Cluster Related to the Number of Master Nodes?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00154.html",
|
||
"node_id":"cce_faq_00154.xml",
|
||
"product_code":"cce",
|
||
"code":"529",
|
||
"des":"CCE restricts only the number of clusters. However, when using CCE, you may also be using other cloud services, such as Elastic Cloud Server (ECS), Elastic Volume Service",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Which Resource Quotas Should I Pay Attention To When Using CCE?,Cluster Creation,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Which Resource Quotas Should I Pay Attention To When Using CCE?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00279.html",
|
||
"node_id":"cce_faq_00279.xml",
|
||
"product_code":"cce",
|
||
"code":"530",
|
||
"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":"usermanual2",
|
||
"kw":"Cluster Running",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cluster Running",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00039.html",
|
||
"node_id":"cce_faq_00039.xml",
|
||
"product_code":"cce",
|
||
"code":"531",
|
||
"des":"If a cluster is unavailable, perform the following operations to locate the fault.The issues here are described in order of how likely they are to occur.Check these cause",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Locate the Fault When a Cluster Is Unavailable?,Cluster Running,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Locate the Fault When a Cluster Is Unavailable?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00040.html",
|
||
"node_id":"cce_faq_00040.xml",
|
||
"product_code":"cce",
|
||
"code":"532",
|
||
"des":"QuestionHow do I retrieve data after a CCE cluster is deleted?Answer:After a cluster is deleted, the workload on the cluster will also be deleted and cannot be restored. ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Retrieve Data After a CCE Cluster Is Deleted?,Cluster Running,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Retrieve Data After a CCE Cluster Is Deleted?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00309.html",
|
||
"node_id":"cce_faq_00309.xml",
|
||
"product_code":"cce",
|
||
"code":"533",
|
||
"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":"usermanual2",
|
||
"kw":"Cluster Deletion",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cluster Deletion",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00394.html",
|
||
"node_id":"cce_faq_00394.xml",
|
||
"product_code":"cce",
|
||
"code":"534",
|
||
"des":"When deleting a cluster, CCE obtains the cluster's resources through kube-apiserver of the cluster. If the cluster is unavailable, frozen, or hibernated, the resources ma",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Can I Do If a Cluster Deletion Fails Due to Residual Resources in the Security Group?,Cluster D",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Can I Do If a Cluster Deletion Fails Due to Residual Resources in the Security Group?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00413.html",
|
||
"node_id":"cce_faq_00413.xml",
|
||
"product_code":"cce",
|
||
"code":"535",
|
||
"des":"If a cluster is not in the running state (for example, frozen or unavailable), its resources such as PVCs, Services, and Ingresses cannot be obtained. After the cluster i",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Clear Residual Resources After Deleting a Non-Running Cluster?,Cluster Deletion,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Clear Residual Resources After Deleting a Non-Running Cluster?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00401.html",
|
||
"node_id":"cce_faq_00401.xml",
|
||
"product_code":"cce",
|
||
"code":"536",
|
||
"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":"usermanual2",
|
||
"kw":"Cluster Upgrade",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Cluster Upgrade",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00402.html",
|
||
"node_id":"cce_faq_00402.xml",
|
||
"product_code":"cce",
|
||
"code":"537",
|
||
"des":"This section describes how to locate and rectify the fault if you fail to upgrade an add-on during the CCE cluster upgrade.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Do I Do If a Cluster Add-On Fails to be Upgraded During the CCE Cluster Upgrade?,Cluster Upgrad",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Do I Do If a Cluster Add-On Fails to be Upgraded During the CCE Cluster Upgrade?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00021.html",
|
||
"node_id":"cce_faq_00021.xml",
|
||
"product_code":"cce",
|
||
"code":"538",
|
||
"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":"usermanual2",
|
||
"kw":"Node",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00280.html",
|
||
"node_id":"cce_faq_00280.xml",
|
||
"product_code":"cce",
|
||
"code":"539",
|
||
"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":"usermanual2",
|
||
"kw":"Node Creation",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Creation",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00027.html",
|
||
"node_id":"cce_faq_00027.xml",
|
||
"product_code":"cce",
|
||
"code":"540",
|
||
"des":"The node images in the same cluster must be the same. Pay attention to this when creating, adding, or accepting nodes in a cluster.If you need to allocate user space from",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Troubleshoot Problems Occurred When Adding Nodes to a CCE Cluster?,Node Creation,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Troubleshoot Problems Occurred When Adding Nodes to a CCE Cluster?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00097.html",
|
||
"node_id":"cce_faq_00097.xml",
|
||
"product_code":"cce",
|
||
"code":"541",
|
||
"des":"This section describes how to troubleshoot the problems occurred when you accept or add existing ECSs to a CCE cluster.While an ECS is being accepted into a cluster, the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Troubleshoot Problems Occurred When Accepting Nodes into a CCE Cluster?,Node Creation,User ",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Troubleshoot Problems Occurred When Accepting Nodes into a CCE Cluster?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00286.html",
|
||
"node_id":"cce_faq_00286.xml",
|
||
"product_code":"cce",
|
||
"code":"542",
|
||
"des":"A node fails to be accepted into a cluster.Log in to the node and check the /var/paas/sys/log/baseagent/baseagent.log installation log. The following error information is",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If a Node Fails to Be Accepted Because It Fails to Be Installed?,Node Creation,User",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Node Fails to Be Accepted Because It Fails to Be Installed?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00281.html",
|
||
"node_id":"cce_faq_00281.xml",
|
||
"product_code":"cce",
|
||
"code":"543",
|
||
"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":"usermanual2",
|
||
"kw":"Node Running",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Running",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00120.html",
|
||
"node_id":"cce_faq_00120.xml",
|
||
"product_code":"cce",
|
||
"code":"544",
|
||
"des":"If the cluster status is available but some nodes in the cluster are unavailable, perform the following operations to rectify the fault.Kubernetes provides the heartbeat ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"monitrc,What Should I Do If a Cluster Is Available But Some Nodes Are Unavailable?,Node Running,User",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Cluster Is Available But Some Nodes Are Unavailable?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00201.html",
|
||
"node_id":"cce_faq_00201.xml",
|
||
"product_code":"cce",
|
||
"code":"545",
|
||
"des":"The following tables list log files of CCE nodes.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Collect Logs of Nodes in a CCE Cluster?,Node Running,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Collect Logs of Nodes in a CCE Cluster?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00263.html",
|
||
"node_id":"cce_faq_00263.xml",
|
||
"product_code":"cce",
|
||
"code":"546",
|
||
"des":"The vdb disk of a node is damaged and the node cannot be recovered after reset.Error ScenariosOn a normal node, delete the LV and VG. The node is unavailable.Reset an abn",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If the vdb Disk of a Node Is Damaged and the Node Cannot Be Recovered After Reset?,",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If the vdb Disk of a Node Is Damaged and the Node Cannot Be Recovered After Reset?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00296.html",
|
||
"node_id":"cce_faq_00296.xml",
|
||
"product_code":"cce",
|
||
"code":"547",
|
||
"des":"When SCSI EVS disks are used and containers are created and deleted on a CentOS node, the disks are frequently mounted and unmounted. The read/write rate of the system di",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If I/O Suspension Occasionally Occurs When SCSI EVS Disks Are Used?,Node Running,Us",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If I/O Suspension Occasionally Occurs When SCSI EVS Disks Are Used?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00307.html",
|
||
"node_id":"cce_faq_00307.xml",
|
||
"product_code":"cce",
|
||
"code":"548",
|
||
"des":"When the disk space of a thin pool on a node is about to be used up, the following exceptions occasionally occur:Files or directories fail to be created in the container,",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Fix an Abnormal Container or Node Due to No Thin Pool Disk Space?,Node Running,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Fix an Abnormal Container or Node Due to No Thin Pool Disk Space?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00020.html",
|
||
"node_id":"cce_faq_00020.xml",
|
||
"product_code":"cce",
|
||
"code":"549",
|
||
"des":"SymptomA node is running properly and has GPU resources. However, the following error information is displayed:0/9 nodes are available: 9 insufficient nvidia.com/gpuAnaly",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Rectify Failures When the NVIDIA Driver Is Used to Start Containers on GPU Nodes?,Node Runn",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Rectify Failures When the NVIDIA Driver Is Used to Start Containers on GPU Nodes?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00282.html",
|
||
"node_id":"cce_faq_00282.xml",
|
||
"product_code":"cce",
|
||
"code":"550",
|
||
"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":"usermanual2",
|
||
"kw":"Specification Change",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Specification Change",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00030.html",
|
||
"node_id":"cce_faq_00030.xml",
|
||
"product_code":"cce",
|
||
"code":"551",
|
||
"des":"If the node whose specifications need to be changed is accepted into the cluster for management, remove the node from the cluster and then change the node specifications ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Change the Node Specifications in a CCE Cluster?,Specification Change,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Change the Node Specifications in a CCE Cluster?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00445.html",
|
||
"node_id":"cce_faq_00445.xml",
|
||
"product_code":"cce",
|
||
"code":"552",
|
||
"des":"After you change the flavor of a node in a CCE node pool on the ECS console and then synchronize the ECS status on the CCE console, the node flavor no longer matches the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Are the Impacts of Changing the Flavor of a Node in a CCE Node Pool?,Specification Change,User ",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Are the Impacts of Changing the Flavor of a Node in a CCE Node Pool?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00189.html",
|
||
"node_id":"cce_faq_00189.xml",
|
||
"product_code":"cce",
|
||
"code":"553",
|
||
"des":"The kubelet option cpu-manager-policy defaults to static, allowing pods with certain resource characteristics to be granted increased CPU affinity and exclusivity on the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If I Fail to Restart or Create Workloads on a Node After Modifying the Node Specifi",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If I Fail to Restart or Create Workloads on a Node After Modifying the Node Specifications?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00407.html",
|
||
"node_id":"cce_faq_00407.xml",
|
||
"product_code":"cce",
|
||
"code":"554",
|
||
"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":"usermanual2",
|
||
"kw":"OSs",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"OSs",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00409.html",
|
||
"node_id":"cce_faq_00409.xml",
|
||
"product_code":"cce",
|
||
"code":"555",
|
||
"des":"If the kernel version of a node is earlier than 5.9 and a CCE cluster runs in IPVS forwarding mode, there may be a service access failure after a backend service upgrade ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If There Is a Service Access Failure After a Backend Service Upgrade or a 1-Second ",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If There Is a Service Access Failure After a Backend Service Upgrade or a 1-Second Latency When a Service Accesses a CCE Cluster?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00163.html",
|
||
"node_id":"cce_faq_00163.xml",
|
||
"product_code":"cce",
|
||
"code":"556",
|
||
"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":"usermanual2",
|
||
"kw":"Node Pool",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Node Pool",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00440.html",
|
||
"node_id":"cce_faq_00440.xml",
|
||
"product_code":"cce",
|
||
"code":"557",
|
||
"des":"Locate the fault based on the status of the abnormal node pool, as shown in Table 1.",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If a Node Pool Is Abnormal?,Node Pool,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Node Pool Is Abnormal?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00127.html",
|
||
"node_id":"cce_faq_00127.xml",
|
||
"product_code":"cce",
|
||
"code":"558",
|
||
"des":"The node pool keeps being in the expanding state, but no node creation record is displayed in the operation record.Check and rectify the following faults:Whether the spec",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If No Node Creation Record Is Displayed When the Node Pool Is Being Expanding?,Node",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If No Node Creation Record Is Displayed When the Node Pool Is Being Expanding?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00432.html",
|
||
"node_id":"cce_faq_00432.xml",
|
||
"product_code":"cce",
|
||
"code":"559",
|
||
"des":"Locate the fault based on the events of the failure to scale out a node pool, as shown in Table 1.If a node pool scale-out fails, the event contains Ecs.0314. This error ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If a Node Pool Scale-Out Fails?,Node Pool,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Node Pool Scale-Out Fails?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00443.html",
|
||
"node_id":"cce_faq_00443.xml",
|
||
"product_code":"cce",
|
||
"code":"560",
|
||
"des":"If an ECS cannot be managed by a node pool due to the reasons listed in this section, you can modify the configuration to manage the ECS.The flavor of the ECS to be manag",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Modify ECS Configurations When an ECS Cannot Be Managed by a Node Pool?,Node Pool,User Guid",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Modify ECS Configurations When an ECS Cannot Be Managed by a Node Pool?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00028.html",
|
||
"node_id":"cce_faq_00028.xml",
|
||
"product_code":"cce",
|
||
"code":"561",
|
||
"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":"usermanual2",
|
||
"kw":"Workload",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Workload",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00029.html",
|
||
"node_id":"cce_faq_00029.xml",
|
||
"product_code":"cce",
|
||
"code":"562",
|
||
"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":"usermanual2",
|
||
"kw":"Workload Exception Troubleshooting",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Workload Exception Troubleshooting",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00134.html",
|
||
"node_id":"cce_faq_00134.xml",
|
||
"product_code":"cce",
|
||
"code":"563",
|
||
"des":"If a workload is abnormal, you can check the pod events first to locate the fault and then rectify the fault.To locate the fault of an abnormal workload, take the followi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Can I Find the Fault for an Abnormal Workload?,Workload Exception Troubleshooting,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Can I Find the Fault for an Abnormal Workload?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00098.html",
|
||
"node_id":"cce_faq_00098.xml",
|
||
"product_code":"cce",
|
||
"code":"564",
|
||
"des":"If the pod is in the Pending state and the event contains pod scheduling failure information, locate the cause based on the event information. For details about how to vi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If Pod Scheduling Fails?,Workload Exception Troubleshooting,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If Pod Scheduling Fails?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00015.html",
|
||
"node_id":"cce_faq_00015.xml",
|
||
"product_code":"cce",
|
||
"code":"565",
|
||
"des":"When a workload enters the state of \"Pod not ready: Back-off pulling image \"xxxxx\", a Kubernetes event of PodsFailed to pull image or Failed to re-pull image will be repo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If a Pod Fails to Pull the Image?,Workload Exception Troubleshooting,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Pod Fails to Pull the Image?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00018.html",
|
||
"node_id":"cce_faq_00018.xml",
|
||
"product_code":"cce",
|
||
"code":"566",
|
||
"des":"On the details page of a workload, if an event is displayed indicating that the container fails to be started, perform the following steps to locate the fault:Rectify the",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If Container Startup Fails?,Workload Exception Troubleshooting,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If Container Startup Fails?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00209.html",
|
||
"node_id":"cce_faq_00209.xml",
|
||
"product_code":"cce",
|
||
"code":"567",
|
||
"des":"When a node is abnormal, Kubernetes will evict pods on the node to ensure workload availability.In Kubernetes, both kube-controller-manager and kubelet can evict pods.Evi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If a Pod Fails to Be Evicted?,Workload Exception Troubleshooting,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Pod Fails to Be Evicted?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00200.html",
|
||
"node_id":"cce_faq_00200.xml",
|
||
"product_code":"cce",
|
||
"code":"568",
|
||
"des":"The issues here are described in order of how likely they are to occur.Check these causes one by one until you find the cause of the fault.Check Item 1: Whether EVS Volum",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If a Storage Volume Cannot Be Mounted or the Mounting Times Out?,Workload Exception",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Storage Volume Cannot Be Mounted or the Mounting Times Out?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00140.html",
|
||
"node_id":"cce_faq_00140.xml",
|
||
"product_code":"cce",
|
||
"code":"569",
|
||
"des":"The workload remains in the creating state.The issues here are described in order of how likely they are to occur.Check these causes one by one until you find the cause o",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If a Workload Remains in the Creating State?,Workload Exception Troubleshooting,Use",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Workload Remains in the Creating State?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00210.html",
|
||
"node_id":"cce_faq_00210.xml",
|
||
"product_code":"cce",
|
||
"code":"570",
|
||
"des":"When obtaining workloads in a namespace, you may come across pods that are in the Terminating state.For example, if you use the command below to obtain pods in the aos na",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If a Pod Remains in the Terminating State?,Workload Exception Troubleshooting,User ",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Pod Remains in the Terminating State?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00012.html",
|
||
"node_id":"cce_faq_00012.xml",
|
||
"product_code":"cce",
|
||
"code":"571",
|
||
"des":"A workload is in Stopped state.The metadata.enable field in the YAML file of the workload is false. As a result, the pod of the workload is deleted and the workload is in",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If a Workload Is Stopped Caused by Pod Deletion?,Workload Exception Troubleshooting",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Workload Is Stopped Caused by Pod Deletion?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00109.html",
|
||
"node_id":"cce_faq_00109.xml",
|
||
"product_code":"cce",
|
||
"code":"572",
|
||
"des":"The following exceptions occur when services are deployed on the GPU nodes in a CCE cluster:The GPU memory of containers cannot be queried.Seven GPU services are deployed",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If an Error Occurs When I Deploy a Service on the GPU Node?,Workload Exception Trou",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If an Error Occurs When I Deploy a Service on the GPU Node?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00095.html",
|
||
"node_id":"cce_faq_00095.xml",
|
||
"product_code":"cce",
|
||
"code":"573",
|
||
"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":"usermanual2",
|
||
"kw":"Container Configuration",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Container Configuration",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00159.html",
|
||
"node_id":"cce_faq_00159.xml",
|
||
"product_code":"cce",
|
||
"code":"574",
|
||
"des":"QuestionWhen is pre-stop processing used?AnswerService processing takes a long time. Pre-stop processing makes sure that during an upgrade, a pod is killed only when the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"When Is Pre-stop Processing Used?,Container Configuration,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"When Is Pre-stop Processing Used?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00261.html",
|
||
"node_id":"cce_faq_00261.xml",
|
||
"product_code":"cce",
|
||
"code":"575",
|
||
"des":"When creating a workload, users can specify a container, pod, and namespace as an FQDN for accessing the container in the same namespace.FQDN stands for Fully Qualified D",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Set an FQDN for Accessing a Specified Container in the Same Namespace?,Container Configurat",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Set an FQDN for Accessing a Specified Container in the Same Namespace?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00255.html",
|
||
"node_id":"cce_faq_00255.xml",
|
||
"product_code":"cce",
|
||
"code":"576",
|
||
"des":"When the liveness and readiness probes fail to perform the health check, locate the service fault first.Common causes are as follows:The service processing takes a long t",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If Health Check Probes Occasionally Fail?,Container Configuration,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If Health Check Probes Occasionally Fail?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00230.html",
|
||
"node_id":"cce_faq_00230.xml",
|
||
"product_code":"cce",
|
||
"code":"577",
|
||
"des":"A container is started in tailf /dev/null mode and the directory permission is 700 after the startup script is manually executed. If the container is started by Kubernete",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Set the umask Value for a Container?,Container Configuration,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Set the umask Value for a Container?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00004.html",
|
||
"node_id":"cce_faq_00004.xml",
|
||
"product_code":"cce",
|
||
"code":"578",
|
||
"des":"CCE is a fully managed Kubernetes service and is fully compatible with Kubernetes APIs and kubectl.In Kubernetes, the spec of a pod contains a restartPolicy field. The va",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Is the Retry Mechanism When CCE Fails to Start a Pod?,Container Configuration,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Is the Retry Mechanism When CCE Fails to Start a Pod?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00284.html",
|
||
"node_id":"cce_faq_00284.xml",
|
||
"product_code":"cce",
|
||
"code":"579",
|
||
"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":"usermanual2",
|
||
"kw":"Scheduling Policies",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Scheduling Policies",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00260.html",
|
||
"node_id":"cce_faq_00260.xml",
|
||
"product_code":"cce",
|
||
"code":"580",
|
||
"des":"The kube-scheduler component in Kubernetes is responsible for pod scheduling. For each newly created pod or other unscheduled pods, kube-scheduler selects an optimal node",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Evenly Distribute Multiple Pods to Each Node?,Scheduling Policies,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Evenly Distribute Multiple Pods to Each Node?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00262.html",
|
||
"node_id":"cce_faq_00262.xml",
|
||
"product_code":"cce",
|
||
"code":"581",
|
||
"des":"During workload scheduling, two containers on a node may compete for resources. As a result, kubelet evicts both containers. This section describes how to set a policy to",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Prevent a Container on a Node from Being Evicted?,Scheduling Policies,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Prevent a Container on a Node from Being Evicted?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00314.html",
|
||
"node_id":"cce_faq_00314.xml",
|
||
"product_code":"cce",
|
||
"code":"582",
|
||
"des":"The kube-scheduler component in Kubernetes is responsible for pod scheduling. For each newly created pod or other unscheduled pods, kube-scheduler selects an optimal node",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Why Are Pods Not Evenly Distributed on Nodes?,Scheduling Policies,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Why Are Pods Not Evenly Distributed on Nodes?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00326.html",
|
||
"node_id":"cce_faq_00326.xml",
|
||
"product_code":"cce",
|
||
"code":"583",
|
||
"des":"You can run the kubectl drain command to safely evict all pods from a node.By default, the kubectl drain command retains some system pods, for example, everest-csi-driver",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Evict All Pods on a Node?,Scheduling Policies,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Evict All Pods on a Node?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00293.html",
|
||
"node_id":"cce_faq_00293.xml",
|
||
"product_code":"cce",
|
||
"code":"584",
|
||
"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":"usermanual2",
|
||
"kw":"Why Cannot a Pod Be Scheduled to a Node?,Scheduling Policies,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Why Cannot a Pod Be Scheduled to a Node?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00186.html",
|
||
"node_id":"cce_faq_00186.xml",
|
||
"product_code":"cce",
|
||
"code":"585",
|
||
"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":"usermanual2",
|
||
"kw":"Others",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Others",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00213.html",
|
||
"node_id":"cce_faq_00213.xml",
|
||
"product_code":"cce",
|
||
"code":"586",
|
||
"des":"When a cron job is paused mid-execution and later resumed, the controller checks the number of missed scheduling times between the last scheduled time and the current tim",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If a Cron Job Cannot Be Restarted After Being Stopped for a Period of Time?,Others,",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Cron Job Cannot Be Restarted After Being Stopped for a Period of Time?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00289.html",
|
||
"node_id":"cce_faq_00289.xml",
|
||
"product_code":"cce",
|
||
"code":"587",
|
||
"des":"The inter-pod discovery service of CCE corresponds to the headless Service of Kubernetes. Headless Services specify None for the cluster IP (spec:clusterIP) in YAML, whic",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Is a Headless Service When I Create a StatefulSet?,Others,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Is a Headless Service When I Create a StatefulSet?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00106.html",
|
||
"node_id":"cce_faq_00106.xml",
|
||
"product_code":"cce",
|
||
"code":"588",
|
||
"des":"When you replace the image of a container in a created workload and use an uploaded image on the CCE console, an error message \"Auth is empty, only accept X-Auth-Token or",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If Error Message \"Auth is empty\" Is Displayed When a Private Image Is Pulled?,Other",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If Error Message \"Auth is empty\" Is Displayed When a Private Image Is Pulled?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00199.html",
|
||
"node_id":"cce_faq_00199.xml",
|
||
"product_code":"cce",
|
||
"code":"589",
|
||
"des":"A container image is required to create a container. Images may be stored locally or in a remote image repository.The imagePullPolicy field in the Kubernetes configuratio",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Is the Image Pull Policy for Containers in a CCE Cluster?,Others,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Is the Image Pull Policy for Containers in a CCE Cluster?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00319.html",
|
||
"node_id":"cce_faq_00319.xml",
|
||
"product_code":"cce",
|
||
"code":"590",
|
||
"des":"When containerd is used as the container engine, there is a possibility that the image layer is missing when an image is pulled to a node. As a result, the workload conta",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Can I Do If a Layer Is Missing During Image Pull?,Others,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Can I Do If a Layer Is Missing During Image Pull?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00141.html",
|
||
"node_id":"cce_faq_00141.xml",
|
||
"product_code":"cce",
|
||
"code":"591",
|
||
"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":"usermanual2",
|
||
"kw":"Networking",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Networking",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00205.html",
|
||
"node_id":"cce_faq_00205.xml",
|
||
"product_code":"cce",
|
||
"code":"592",
|
||
"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":"usermanual2",
|
||
"kw":"Network Exception Troubleshooting",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Network Exception Troubleshooting",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00202.html",
|
||
"node_id":"cce_faq_00202.xml",
|
||
"product_code":"cce",
|
||
"code":"593",
|
||
"des":"The issues here are described in order of how likely they are to occur.Check these causes one by one until you find the cause of the fault.Check Item 1: Container and Con",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Locate a Workload Networking Fault?,Network Exception Troubleshooting,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Locate a Workload Networking Fault?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00203.html",
|
||
"node_id":"cce_faq_00203.xml",
|
||
"product_code":"cce",
|
||
"code":"594",
|
||
"des":"CCE does not return any error code when you fail to access your applications using a browser. Check your services first.404 Not FoundIf the error code shown in the follow",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Why Does the Browser Return Error Code 404 When I Access a Deployed Application?,Network Exception T",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Why Does the Browser Return Error Code 404 When I Access a Deployed Application?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00204.html",
|
||
"node_id":"cce_faq_00204.xml",
|
||
"product_code":"cce",
|
||
"code":"595",
|
||
"des":"If a container cannot access the Internet, check whether the node where the container is located can access the Internet. Then check whether the network configuration of ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If a Container Fails to Access the Internet?,Network Exception Troubleshooting,User",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Container Fails to Access the Internet?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00022.html",
|
||
"node_id":"cce_faq_00022.xml",
|
||
"product_code":"cce",
|
||
"code":"596",
|
||
"des":"If a node fails to be connected to the Internet, perform the following operations:Log in to the ECS console and check whether an EIP has been bound to the ECS correspondi",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If a Node Fails to Connect to the Internet (Public Network)?,Network Exception Trou",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Node Fails to Connect to the Internet (Public Network)?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00146.html",
|
||
"node_id":"cce_faq_00146.xml",
|
||
"product_code":"cce",
|
||
"code":"597",
|
||
"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":"usermanual2",
|
||
"kw":"Network Planning",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Network Planning",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00266.html",
|
||
"node_id":"cce_faq_00266.xml",
|
||
"product_code":"cce",
|
||
"code":"598",
|
||
"des":"A VPC is similar to a private local area network (LAN) managed by a home gateway whose IP address is 192.168.0.0/16. A VPC is a private network built on the cloud and pro",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Is the Relationship Between Clusters, VPCs, and Subnets?,Network Planning,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Is the Relationship Between Clusters, VPCs, and Subnets?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00265.html",
|
||
"node_id":"cce_faq_00265.xml",
|
||
"product_code":"cce",
|
||
"code":"599",
|
||
"des":"CCE is a universal container platform. Its default security group rules apply to common scenarios. When a cluster is created, a security group is automatically created fo",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Can I Configure a Security Group Rule in a Cluster?,Network Planning,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Can I Configure a Security Group Rule in a Cluster?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00406.html",
|
||
"node_id":"cce_faq_00406.xml",
|
||
"product_code":"cce",
|
||
"code":"600",
|
||
"des":"To create an IPv4/IPv6 dual-stack CCE Turbo cluster, you need to set an IPv6 Service CIDR block. The default CIDR block is fc00::/112, which contains 65,536 IPv6 addresse",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Configure the IPv6 Service CIDR Block When Creating a CCE Turbo Cluster?,Network Planning,U",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Configure the IPv6 Service CIDR Block When Creating a CCE Turbo Cluster?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00264.html",
|
||
"node_id":"cce_faq_00264.xml",
|
||
"product_code":"cce",
|
||
"code":"601",
|
||
"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":"usermanual2",
|
||
"kw":"Security Hardening",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Security Hardening",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00267.html",
|
||
"node_id":"cce_faq_00267.xml",
|
||
"product_code":"cce",
|
||
"code":"602",
|
||
"des":"QuestionHow do I prevent cluster nodes from being exposed to public networks?SolutionIf access to port 22 of a cluster node is not required, you can define a security gro",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Prevent Cluster Nodes from Being Exposed to Public Networks?,Security Hardening,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Prevent Cluster Nodes from Being Exposed to Public Networks?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00417.html",
|
||
"node_id":"cce_faq_00417.xml",
|
||
"product_code":"cce",
|
||
"code":"603",
|
||
"des":"After the public API Server address is bound to the cluster, modify the security group rules of port 5443 on the master node to harden the access control policy of the cl",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Configure an Access Policy for a Cluster?,Security Hardening,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Configure an Access Policy for a Cluster?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00185.html",
|
||
"node_id":"cce_faq_00185.xml",
|
||
"product_code":"cce",
|
||
"code":"604",
|
||
"des":"If your ingress needs to use HTTPS, you must configure a secret of the IngressTLS or kubernetes.io/tls type when creating an ingress.The certificate file uploaded in the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Obtain a TLS Key Certificate?,Security Hardening,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Obtain a TLS Key Certificate?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00392.html",
|
||
"node_id":"cce_faq_00392.xml",
|
||
"product_code":"cce",
|
||
"code":"605",
|
||
"des":"Do not add more than 1000 instances to the same security group. Otherwise, the security group performance may deteriorate.You can change the maximum number of servers dis",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Change the Security Group of Nodes in a Cluster in Batches?,Security Hardening,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Change the Security Group of Nodes in a Cluster in Batches?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00275.html",
|
||
"node_id":"cce_faq_00275.xml",
|
||
"product_code":"cce",
|
||
"code":"606",
|
||
"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":"usermanual2",
|
||
"kw":"Network Configuration",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Network Configuration",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00192.html",
|
||
"node_id":"cce_faq_00192.xml",
|
||
"product_code":"cce",
|
||
"code":"607",
|
||
"des":"Add hostNetwork: true to the spec.spec. in the YAML file of the workload to which the containers will belong.Configure node affinity policies, in addition to perform the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Can Container IP Addresses Survive a Container Restart?,Network Configuration,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Can Container IP Addresses Survive a Container Restart?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00446.html",
|
||
"node_id":"cce_faq_00446.xml",
|
||
"product_code":"cce",
|
||
"code":"608",
|
||
"des":"Pod subnets can be deleted from CCE Turbo clusters of v1.23.17-r0, v1.25.12-r0, v1.27.9-r0, v1.28.7-r0, v1.29.3-r0, or later versions.Deleting a pod subnet from a cluster",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Can I Check Whether an ENI Is Used by a Cluster?,Network Configuration,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Can I Check Whether an ENI Is Used by a Cluster?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00447.html",
|
||
"node_id":"cce_faq_00447.xml",
|
||
"product_code":"cce",
|
||
"code":"609",
|
||
"des":"Pod subnets can be deleted from CCE Turbo clusters of v1.23.17-r0, v1.25.12-r0, v1.28.7-r0, or later versions.When you delete a subnet, CCE does not automatically remove ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Can I Delete a Security Group Rule Associated with a Deleted Subnet?,Network Configuration,User ",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Can I Delete a Security Group Rule Associated with a Deleted Subnet?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00460.html",
|
||
"node_id":"cce_faq_00460.xml",
|
||
"product_code":"cce",
|
||
"code":"610",
|
||
"des":"With CCE, you can associate multiple ingresses with a single load balancer listener and establish various forwarding policies. Listener configuration parameters are store",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Can I Determine Which Ingress the Listener Settings Have Been Applied To?,Network Configuration,",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Can I Determine Which Ingress the Listener Settings Have Been Applied To?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00037.html",
|
||
"node_id":"cce_faq_00037.xml",
|
||
"product_code":"cce",
|
||
"code":"611",
|
||
"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":"usermanual2",
|
||
"kw":"Storage",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Storage",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00224.html",
|
||
"node_id":"cce_faq_00224.xml",
|
||
"product_code":"cce",
|
||
"code":"612",
|
||
"des":"The default storage size of a container is 10 GiB. If a large volume of data is generated in the container, expand the capacity using the method described in this topic.R",
|
||
"doc_type":"usermanual2",
|
||
"kw":"base size,How Do I Expand the Storage Capacity of a Container?,Storage,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Expand the Storage Capacity of a Container?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00038.html",
|
||
"node_id":"cce_faq_00038.xml",
|
||
"product_code":"cce",
|
||
"code":"613",
|
||
"des":"Container storage provides storage for container workloads. It supports multiple storage classes. A pod can use any amount of storage.Currently, CCE supports local, EVS, ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Are the Differences Among CCE Storage Classes in Terms of Persistent Storage and Multi-Node Mou",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Are the Differences Among CCE Storage Classes in Terms of Persistent Storage and Multi-Node Mounting?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00089.html",
|
||
"node_id":"cce_faq_00089.xml",
|
||
"product_code":"cce",
|
||
"code":"614",
|
||
"des":"If System Component Storage is set to System Disk, you do not need to add a data disk.Data disks are required if System Component Storage is set to Data Disk.A data disk ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Can I Create a CCE Node Without Adding a Data Disk to the Node?,Storage,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Can I Create a CCE Node Without Adding a Data Disk to the Node?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00218.html",
|
||
"node_id":"cce_faq_00218.xml",
|
||
"product_code":"cce",
|
||
"code":"615",
|
||
"des":"When a Service deployed on CCE attempts to upload files to OBS after receiving an access request from an offline machine, an error message is displayed, indicating that t",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If the Host Cannot Be Found When Files Need to Be Uploaded to OBS During the Access",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If the Host Cannot Be Found When Files Need to Be Uploaded to OBS During the Access to the CCE Service from a Public Network?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00235.html",
|
||
"node_id":"cce_faq_00235.xml",
|
||
"product_code":"cce",
|
||
"code":"616",
|
||
"des":"The Kubernetes pod structure does not contain ExtendPathMode. Therefore, when a user calls the API for creating a pod or deployment by using client-go, the created pod do",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Can I Achieve Compatibility Between ExtendPathMode and Kubernetes client-go?,Storage,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Can I Achieve Compatibility Between ExtendPathMode and Kubernetes client-go?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00316.html",
|
||
"node_id":"cce_faq_00316.xml",
|
||
"product_code":"cce",
|
||
"code":"617",
|
||
"des":"CCE PersistentVolumeClaims (PVCs) are implemented as they are in Kubernetes. A PVC is defined as a storage declaration and is decoupled from underlying storage. It is not",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Can CCE PVCs Detect Underlying Storage Faults?,Storage,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Can CCE PVCs Detect Underlying Storage Faults?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00324.html",
|
||
"node_id":"cce_faq_00324.xml",
|
||
"product_code":"cce",
|
||
"code":"618",
|
||
"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":"usermanual2",
|
||
"kw":"Namespace",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Namespace",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00325.html",
|
||
"node_id":"cce_faq_00325.xml",
|
||
"product_code":"cce",
|
||
"code":"619",
|
||
"des":"The namespace remains in the Deleting state. The error message \"DiscoveryFailed\" is displayed in status in the YAML file.In the preceding figure, the full error message i",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If a Namespace Fails to Be Deleted Due to an APIService Object Access Failure?,Name",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If a Namespace Fails to Be Deleted Due to an APIService Object Access Failure?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00215.html",
|
||
"node_id":"cce_faq_00215.xml",
|
||
"product_code":"cce",
|
||
"code":"620",
|
||
"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":"usermanual2",
|
||
"kw":"Chart and Add-on",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Chart and Add-on",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00322.html",
|
||
"node_id":"cce_faq_00322.xml",
|
||
"product_code":"cce",
|
||
"code":"621",
|
||
"des":"When an add-on fails to be installed, the error message \"The release name is already exist\" is returned.The add-on release record remains in the Kubernetes cluster. Gener",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If Installation of an Add-on Fails and \"The release name is already exist\" Is Displ",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If Installation of an Add-on Fails and \"The release name is already exist\" Is Displayed?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00429.html",
|
||
"node_id":"cce_faq_00429.xml",
|
||
"product_code":"cce",
|
||
"code":"622",
|
||
"des":"After changing the cluster scale, adjust the add-on resource quotas based on the cluster scale to ensure that the add-on pods can run properly. For example, if you expand",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Configure the Add-on Resource Quotas Based on Cluster Scale?,Chart and Add-on,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Configure the Add-on Resource Quotas Based on Cluster Scale?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00438.html",
|
||
"node_id":"cce_faq_00438.xml",
|
||
"product_code":"cce",
|
||
"code":"623",
|
||
"des":"The NGINX Ingress Controller add-on is in the unknown state, and after this add-on is uninstalled, residual components still remain.Involved Kubernetes resources include:",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Can I Clean Up Residual Resources After the NGINX Ingress Controller Add-on in the Unknown State",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Can I Clean Up Residual Resources After the NGINX Ingress Controller Add-on in the Unknown State Is Deleted?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00207.html",
|
||
"node_id":"cce_faq_00207.xml",
|
||
"product_code":"cce",
|
||
"code":"624",
|
||
"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":"usermanual2",
|
||
"kw":"API & kubectl FAQs",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"API & kubectl FAQs",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00025.html",
|
||
"node_id":"cce_faq_00025.xml",
|
||
"product_code":"cce",
|
||
"code":"625",
|
||
"des":"You can use either of the following methods to access a cluster API server:(Recommended) Through the cluster API. This access mode uses certificate authentication. It is ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Can I Access a Cluster API Server?,API & kubectl FAQs,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Can I Access a Cluster API Server?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00208.html",
|
||
"node_id":"cce_faq_00208.xml",
|
||
"product_code":"cce",
|
||
"code":"626",
|
||
"des":"The CCE console does not support the display of the following Kubernetes resources: DaemonSets, ReplicationControllers, ReplicaSets, and endpoints.To query these resource",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Can the Resources Created Using APIs or kubectl Be Displayed on the CCE Console?,API & kubectl FAQs,",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Can the Resources Created Using APIs or kubectl Be Displayed on the CCE Console?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00041.html",
|
||
"node_id":"cce_faq_00041.xml",
|
||
"product_code":"cce",
|
||
"code":"627",
|
||
"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":"usermanual2",
|
||
"kw":"How Do I Download kubeconfig for Connecting to a Cluster Using kubectl?,API & kubectl FAQs,User Guid",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Download kubeconfig for Connecting to a Cluster Using kubectl?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00321.html",
|
||
"node_id":"cce_faq_00321.xml",
|
||
"product_code":"cce",
|
||
"code":"628",
|
||
"des":"The error message \"Error from server (ServiceUnavailable): the server is currently unable to handle the request (get nodes.metrics.k8s.io)\" is displayed after the kubectl",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Rectify the Error Reported When Running the kubectl top node Command?,API & kubectl FAQs,Us",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Rectify the Error Reported When Running the kubectl top node Command?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00311.html",
|
||
"node_id":"cce_faq_00311.xml",
|
||
"product_code":"cce",
|
||
"code":"629",
|
||
"des":"When you use kubectl to create or query Kubernetes resources, the following output is returned:# kubectl get deploy Error from server (Forbidden): deployments.apps is for",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Why Is \"Error from server (Forbidden)\" Displayed When I Use kubectl?,API & kubectl FAQs,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Why Is \"Error from server (Forbidden)\" Displayed When I Use kubectl?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00001.html",
|
||
"node_id":"cce_faq_00001.xml",
|
||
"product_code":"cce",
|
||
"code":"630",
|
||
"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":"usermanual2",
|
||
"kw":"DNS FAQs",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"DNS FAQs",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00197.html",
|
||
"node_id":"cce_faq_00197.xml",
|
||
"product_code":"cce",
|
||
"code":"631",
|
||
"des":"CoreDNS QPS is positively correlated with the CPU usage. If the QPS is high, adjust the coredns instance specifications based on the QPS.If the add-on performance reaches",
|
||
"doc_type":"usermanual2",
|
||
"kw":"What Should I Do If Domain Name Resolution Fails in a CCE Cluster?,DNS FAQs,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"What Should I Do If Domain Name Resolution Fails in a CCE Cluster?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00107.html",
|
||
"node_id":"cce_faq_00107.xml",
|
||
"product_code":"cce",
|
||
"code":"632",
|
||
"des":"A customer bound its domain name to the private domain names in the DNS service and also to a specific VPC. It is found that the ECSs in the VPC can properly resolve the ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Why Does a Container in a CCE Cluster Fail to Perform DNS Resolution?,DNS FAQs,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Why Does a Container in a CCE Cluster Fail to Perform DNS Resolution?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00195.html",
|
||
"node_id":"cce_faq_00195.xml",
|
||
"product_code":"cce",
|
||
"code":"633",
|
||
"des":"The following is an example resolv.conf file for a container in a workload:In the preceding information:nameserver: IP address of the DNS. Set this parameter to the clust",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Optimize the Configuration If the External Domain Name Resolution Is Slow or Times Out?,DNS",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Optimize the Configuration If the External Domain Name Resolution Is Slow or Times Out?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00194.html",
|
||
"node_id":"cce_faq_00194.xml",
|
||
"product_code":"cce",
|
||
"code":"634",
|
||
"des":"CCE uses dnsPolicy to identify different DNS policies for each pod. The value of dnsPolicy can be either of the following:None: No DNS policy is configured. In this mode,",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Configure a DNS Policy for a Container?,DNS FAQs,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Configure a DNS Policy for a Container?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00093.html",
|
||
"node_id":"cce_faq_00093.xml",
|
||
"product_code":"cce",
|
||
"code":"635",
|
||
"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":"usermanual2",
|
||
"kw":"Image Repository FAQs",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Image Repository FAQs",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00032.html",
|
||
"node_id":"cce_faq_00032.xml",
|
||
"product_code":"cce",
|
||
"code":"636",
|
||
"des":"SWR manages images for CCE. It provides the following ways to upload images:Uploading an Image Through the Client",
|
||
"doc_type":"usermanual2",
|
||
"kw":"How Do I Upload My Images to CCE?,Image Repository FAQs,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"How Do I Upload My Images to CCE?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00397.html",
|
||
"node_id":"cce_faq_00397.xml",
|
||
"product_code":"cce",
|
||
"code":"637",
|
||
"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":"usermanual2",
|
||
"kw":"Permissions",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Permissions",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00398.html",
|
||
"node_id":"cce_faq_00398.xml",
|
||
"product_code":"cce",
|
||
"code":"638",
|
||
"des":"Namespace permissions and cluster management permissions are independent and complementary to each other.Namespace permissions: apply to clusters and are used to manage o",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Can I Configure Only Namespace Permissions Without Cluster Management Permissions?,Permissions,User ",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Can I Configure Only Namespace Permissions Without Cluster Management Permissions?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00399.html",
|
||
"node_id":"cce_faq_00399.xml",
|
||
"product_code":"cce",
|
||
"code":"639",
|
||
"des":"CCE has cloud service APIs and cluster APIs.Cloud service APIs: You can perform operations on the infrastructure (such as creating nodes) and cluster resources (such as c",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Can I Use CCE APIs If the Cluster Management Permissions Are Not Configured?,Permissions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Can I Use CCE APIs If the Cluster Management Permissions Are Not Configured?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_faq_00400.html",
|
||
"node_id":"cce_faq_00400.xml",
|
||
"product_code":"cce",
|
||
"code":"640",
|
||
"des":"IAM authentication is not required for running kubectl commands. Therefore, you can run kubectl commands without configuring cluster management (IAM) permissions. However",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Can I Use kubectl If the Cluster Management Permissions Are Not Configured?,Permissions,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"documenttype":"usermanual"
|
||
}
|
||
],
|
||
"title":"Can I Use kubectl If the Cluster Management Permissions Are Not Configured?",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_01_9999.html",
|
||
"node_id":"cce_01_9999.xml",
|
||
"product_code":"cce",
|
||
"code":"641",
|
||
"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":"usermanual2",
|
||
"kw":"Migrating Data from CCE 1.0 to CCE 2.0",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"opensource":"true",
|
||
"documenttype":"usermanual2",
|
||
"IsMulti":"Yes"
|
||
}
|
||
],
|
||
"title":"Migrating Data from CCE 1.0 to CCE 2.0",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_01_9998.html",
|
||
"node_id":"cce_01_9998.xml",
|
||
"product_code":"cce",
|
||
"code":"642",
|
||
"des":"CCE 2.0 inherits and modifies the features of CCE 1.0, and release new features.Modified features:Clusters in CCE 1.0 are equivalent to Hybrid clusters in CCE 2.0.CCE 2.0",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Differences Between CCE 1.0 and CCE 2.0,Migrating Data from CCE 1.0 to CCE 2.0,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"opensource":"true",
|
||
"documenttype":"usermanual2",
|
||
"IsMulti":"Yes"
|
||
}
|
||
],
|
||
"title":"Differences Between CCE 1.0 and CCE 2.0",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_01_9997.html",
|
||
"node_id":"cce_01_9997.xml",
|
||
"product_code":"cce",
|
||
"code":"643",
|
||
"des":"Migrate the images stored in the image repository of CCE 1.0 to CCE 2.0.A VM is available. The VM is bound to a public IP address and can access the Internet. Docker (ear",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Migrating Images,Migrating Data from CCE 1.0 to CCE 2.0,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"opensource":"true",
|
||
"documenttype":"usermanual2",
|
||
"IsMulti":"Yes"
|
||
}
|
||
],
|
||
"title":"Migrating Images",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_01_9996.html",
|
||
"node_id":"cce_01_9996.xml",
|
||
"product_code":"cce",
|
||
"code":"644",
|
||
"des":"Create Hybrid clusters on the CCE 2.0 console. These new Hybrid clusters should have the same specifications with those created on CCE 1.0.To create clusters using APIs, ",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Migrating Clusters,Migrating Data from CCE 1.0 to CCE 2.0,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"opensource":"true",
|
||
"documenttype":"usermanual2",
|
||
"IsMulti":"Yes"
|
||
}
|
||
],
|
||
"title":"Migrating Clusters",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_01_9995.html",
|
||
"node_id":"cce_01_9995.xml",
|
||
"product_code":"cce",
|
||
"code":"645",
|
||
"des":"This section describes how to create a Deployment with the same specifications as that in CCE 1.0 on the CCE 2.0 console.It is advised to delete the applications on CCE 1",
|
||
"doc_type":"usermanual2",
|
||
"kw":"Migrating Applications,Migrating Data from CCE 1.0 to CCE 2.0,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"opensource":"true",
|
||
"documenttype":"usermanual2",
|
||
"IsMulti":"Yes"
|
||
}
|
||
],
|
||
"title":"Migrating Applications",
|
||
"githuburl":""
|
||
},
|
||
{
|
||
"uri":"cce_01_0300.html",
|
||
"node_id":"cce_01_0300.xml",
|
||
"product_code":"cce",
|
||
"code":"646",
|
||
"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":"usermanual2",
|
||
"kw":"Change History,User Guide",
|
||
"search_title":"",
|
||
"metedata":[
|
||
{
|
||
"prodname":"cce",
|
||
"opensource":"true",
|
||
"documenttype":"usermanual2",
|
||
"IsMulti":"Yes"
|
||
}
|
||
],
|
||
"title":"Change History",
|
||
"githuburl":""
|
||
}
|
||
] |