vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity

CCE UMN update -20240401 version

Browse Source 
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com>
Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
This commit is contained in:
Dong, Qiu Jian 2024-04-15 14:42:22 +00:00 committed by zuul
parent ecb5ee73d2
commit 6157284549
715 changed files with 13278 additions and 7993 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2186
docs/cce/umn/ALL_META.TXT.json
View File

File diff suppressed because it is too large Load Diff

2304
docs/cce/umn/CLASS.TXT.json
View File

File diff suppressed because it is too large Load Diff

16
docs/cce/umn/cce_01_0091.html
View File

@ -1,16 +0,0 @@
<a name="cce_01_0091"></a><a name="cce_01_0091"></a>
<h1 class="topictitle1">What Is Cloud Container Engine?</h1>
<div id="body32001227"><div class="section" id="cce_01_0091__en-us_topic_0000001499406010_section8343153913519"><h4 class="sectiontitle">Why CCE?</h4><p id="cce_01_0091__en-us_topic_0000001499406010_p72395598519">CCE is a one-stop platform integrating compute, networking, storage, and many other services. Supporting multi-AZ and multi-region disaster recovery, CCE ensures high availability of <a href="https://kubernetes.io/" target="_blank" rel="noopener noreferrer">Kubernetes</a> clusters.</p>
<p id="cce_01_0091__en-us_topic_0000001499406010_p1220816614522">For more information, see <a href="cce_productdesc_0003.html#cce_productdesc_0003">Product Advantages</a> and <a href="cce_productdesc_0007.html#cce_productdesc_0007">Application Scenarios</a>.</p>
</div>
<div class="section" id="cce_01_0091__en-us_topic_0000001499406010_section14578149155310"><h4 class="sectiontitle">Accessing CCE</h4><p id="cce_01_0091__en-us_topic_0000001499406010_p124041812145418">You can use CCE via the CCE console, kubectl, or Kubernetes APIs. <a href="#cce_01_0091__en-us_topic_0000001499406010_fig3404612135411">Figure 1</a> shows the process.</p>
<div class="fignone" id="cce_01_0091__en-us_topic_0000001499406010_fig3404612135411"><a name="cce_01_0091__en-us_topic_0000001499406010_fig3404612135411"></a><a name="en-us_topic_0000001499406010_fig3404612135411"></a><span class="figcap"><b>Figure 1 </b>Accessing CCE</span><br><span><img id="cce_01_0091__en-us_topic_0000001499406010_image104041112125417" src="en-us_image_0000001499565914.png"></span></div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_productdesc_0000.html">Service Overview</a></div>
</div>
</div>

7
docs/cce/umn/cce_01_0300.html
View File

@ -8,7 +8,12 @@
</th>
</tr>
</thead>
<tbody><tr id="cce_01_0300__row15301133891"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p16301431995">2024-01-29</p>
<tbody><tr id="cce_01_0300__row125431763718"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p175401713377">2024-03-29</p>
</td>
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><ul id="cce_01_0300__ul178522051143711"><li id="cce_01_0300__li157281413144019">Modified the console style.</li><li id="cce_01_0300__li11783163645218">Added <a href="cce_bulletin_0061.html">CCE Console Upgrade</a>.</li><li id="cce_01_0300__li1485265114379">HCE OS 2.0 is supported. For details, see <a href="cce_bulletin_0301.html">OS Patch Notes for Cluster Nodes</a>.</li><li id="cce_01_0300__li143973152818">Update <a href="cce_10_0405.html">Release Notes for CCE Cluster Versions</a>.</li><li id="cce_01_0300__li96317418918">Update <a href="cce_10_0423.html">Volcano Scheduling</a>.</li><li id="cce_01_0300__li12925155011536">Added the CCE Advanced HPA add-on.</li><li id="cce_01_0300__li19887214113914">Updated <a href="cce_bestpractice_0000.html">Best Practice</a>.</li><li id="cce_01_0300__li1963584304012">Updated <a href="cce_faq_0000.html">FAQs</a>.</li></ul>
</td>
</tr>
<tr id="cce_01_0300__row15301133891"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p16301431995">2024-01-29</p>
</td>
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><ul id="cce_01_0300__ul15421838121115"><li id="cce_01_0300__li142114389110">Supported the creation of clusters of v1.27.</li><li id="cce_01_0300__li9321143631220">Updated <a href="cce_10_0550.html">Troubleshooting for Pre-upgrade Check Exceptions</a>.</li><li id="cce_01_0300__li2036942911281">Replaced "CCE Cluster Version Release Notes" in section "Product Bulletin" with <a href="cce_10_0405.html">Release Notes for CCE Cluster Versions</a>.</li><li id="cce_01_0300__li68581132114010">Updated the kernel version of EulerOS 2.9.</li></ul>
</td>

72
docs/cce/umn/cce_10_0003.html
View File

File diff suppressed because it is too large Load Diff

4
docs/cce/umn/cce_10_0004.html
View File

@ -51,7 +51,7 @@
</tr>
<tr id="cce_10_0004__row15479121185815"><td class="cellrowborder" valign="top" width="45%" headers="mcps1.4.2.4.2.3.1.1 "><p id="cce_10_0004__p1931642055818">kubernetes.io/os</p>
</td>
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.4.2.4.2.3.1.2 "><p id="cce_10_0004__p7479101125812">OS type</p>
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.4.2.4.2.3.1.2 "><p id="cce_10_0004__p7479101125812">Node OS type</p>
</td>
</tr>
<tr id="cce_10_0004__row85011821447"><td class="cellrowborder" valign="top" width="45%" headers="mcps1.4.2.4.2.3.1.1 "><p id="cce_10_0004__p950218211147">node.kubernetes.io/subnetid</p>
@ -94,7 +94,7 @@
</table>
</div>
</div>
<div class="section" id="cce_10_0004__section33951611481"><h4 class="sectiontitle">Adding or Deleting a Node Label</h4><ol id="cce_10_0004__ol4618636938"><li id="cce_10_0004__li12107195613316"><span>Log in to the CCE console.</span></li><li id="cce_10_0004__li36690501449"><span>Click the cluster name, access the cluster details page, and choose <strong id="cce_10_0004__b1130441713441">Nodes</strong> in the navigation pane. On the page displayed, select a node and click <strong id="cce_10_0004__b1530481719449">Labels and Taints</strong> above the list.</span></li><li id="cce_10_0004__li2568164932420"><span>In the displayed dialog box, click <span class="uicontrol" id="cce_10_0004__uicontrol197381013144411"><b>Add Operation</b></span> under <span class="uicontrol" id="cce_10_0004__uicontrol147382132448"><b>Batch Operation</b></span>, and then choose <span class="uicontrol" id="cce_10_0004__uicontrol1973861354418"><b>Add/Update</b></span> or <span class="uicontrol" id="cce_10_0004__uicontrol2073819135443"><b>Delete</b></span>.</span><p><p id="cce_10_0004__p59891449182418">Enter the key and value of the label to be added or deleted, and click <strong id="cce_10_0004__b10531103420434">OK</strong>.</p>
<div class="section" id="cce_10_0004__section33951611481"><h4 class="sectiontitle">Adding or Deleting a Node Label</h4><ol id="cce_10_0004__ol4618636938"><li id="cce_10_0004__li56102343513"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0004__li12107195613316"><span>In the navigation pane, choose <strong id="cce_10_0004__b184671149151910">Nodes</strong>. On the displayed page, click the <strong id="cce_10_0004__b6486192182018">Nodes</strong> tab, select the target node and click <strong id="cce_10_0004__b186317458204">Labels and Taints</strong> in the upper left corner.</span></li><li id="cce_10_0004__li2568164932420"><span>In the displayed dialog box, click <span class="uicontrol" id="cce_10_0004__uicontrol197381013144411"><b>Add batch operations</b></span> under <span class="uicontrol" id="cce_10_0004__uicontrol147382132448"><b>Batch Operation</b></span>, and then choose <span class="uicontrol" id="cce_10_0004__uicontrol1973861354418"><b>Add/Update</b></span> or <span class="uicontrol" id="cce_10_0004__uicontrol2073819135443"><b>Delete</b></span>.</span><p><p id="cce_10_0004__p59891449182418">Enter the key and value of the label to be added or deleted, and click <strong id="cce_10_0004__b10531103420434">OK</strong>.</p>
<p id="cce_10_0004__p12647141114247">For example, the key is <strong id="cce_10_0004__b842352706145648">deploy_qa</strong> and the value is <strong id="cce_10_0004__b842352706145652">true</strong>, indicating that the node is used to deploy the QA (test) environment.</p>
</p></li><li id="cce_10_0004__li68199221571"><span>After the label is added, check the added label in node data.</span></li></ol>
</div>

26
docs/cce/umn/cce_10_0006.html
View File

@ -2,31 +2,31 @@
<h1 class="topictitle1">Overview</h1>
<div id="body1522665832344"><p id="cce_10_0006__p11116113204610">CCE provides Kubernetes-native container deployment and management and supports lifecycle management of container workloads, including creation, configuration, monitoring, auto scaling, upgrade, uninstall, service discovery, and load balancing.</p>
<div class="section" id="cce_10_0006__section9645114684816"><h4 class="sectiontitle">Pod</h4><p id="cce_10_0006__en-us_topic_0254767870_p356108173515">A pod is the smallest and simplest unit in the Kubernetes object model that you create or deploy. A pod encapsulates one or more containers, storage volumes, a unique network IP address, and options that govern how the containers should run.</p>
<div class="section" id="cce_10_0006__section9645114684816"><h4 class="sectiontitle">Overview of Pod</h4><p id="cce_10_0006__en-us_topic_0254767870_p356108173515">A pod is the smallest and simplest unit in the Kubernetes object model that you create or deploy. A pod is a group of one or more containers, with shared storage and network resources, and a specification for how to run the containers. Each pod has a separate IP address.</p>
<p id="cce_10_0006__en-us_topic_0254767870_p4629172611480">Pods can be used in either of the following ways:</p>
<ul id="cce_10_0006__en-us_topic_0254767870_ul062982617481"><li id="cce_10_0006__en-us_topic_0254767870_li1629172611482">A container is running in a pod. This is the most common usage of pods in Kubernetes. You can view the pod as a single encapsulated container, but Kubernetes directly manages pods instead of containers.</li><li id="cce_10_0006__en-us_topic_0254767870_li1962932615480">Multiple containers that need to be coupled and share resources run in a pod. In this scenario, an application contains a main container and several sidecar containers, as shown in <a href="#cce_10_0006__en-us_topic_0254767870_fig347141918551">Figure 1</a>. For example, the main container is a web server that provides file services from a fixed directory, and a sidecar container periodically downloads files to the directory.<div class="fignone" id="cce_10_0006__en-us_topic_0254767870_fig347141918551"><a name="cce_10_0006__en-us_topic_0254767870_fig347141918551"></a><a name="en-us_topic_0254767870_fig347141918551"></a><span class="figcap"><b>Figure 1 </b>Pod</span><br><span><img id="cce_10_0006__en-us_topic_0254767870_image1835215316361" src="en-us_image_0000001695896725.png"></span></div>
<ul id="cce_10_0006__en-us_topic_0254767870_ul062982617481"><li id="cce_10_0006__en-us_topic_0254767870_li1629172611482">A pod runs only one container. This is the most common usage of pods in Kubernetes. You can consider a pod as a container, but Kubernetes directly manages pods instead of containers.</li><li id="cce_10_0006__en-us_topic_0254767870_li1962932615480">A pod runs multiple containers that need to be tightly coupled. In this scenario, a pod contains a main container and several sidecar containers, as shown in <a href="#cce_10_0006__en-us_topic_0254767870_fig347141918551">Figure 1</a>. For example, the main container is a web server that provides file services from a fixed directory, and sidecar containers periodically download files to this fixed directory.<div class="fignone" id="cce_10_0006__en-us_topic_0254767870_fig347141918551"><a name="cce_10_0006__en-us_topic_0254767870_fig347141918551"></a><a name="en-us_topic_0254767870_fig347141918551"></a><span class="figcap"><b>Figure 1 </b>Pod running multiple containers</span><br><span><img id="cce_10_0006__en-us_topic_0254767870_image1835215316361" src="en-us_image_0258392378.png"></span></div>
</li></ul>
<p id="cce_10_0006__en-us_topic_0254767870_p9163143619182">In Kubernetes, pods are rarely created directly. Instead, controllers such as Deployments and Jobs, are used to manage pods. Controllers can create and manage multiple pods, and provide replica management, rolling upgrade, and self-healing capabilities. A controller typically uses a pod template to create corresponding pods.</p>
<p id="cce_10_0006__en-us_topic_0254767870_p9163143619182">In Kubernetes, pods are rarely created directly. Instead, Kubernetes controller manages pods through pod instances such as Deployments and jobs. A controller typically uses a pod template to create pods. The controller can also manage multiple pods and provide functions such as replica management, rolling upgrade, and self-healing.</p>
</div>
<div class="section" id="cce_10_0006__section1972719357496"><h4 class="sectiontitle">Deployment</h4><p id="cce_10_0006__en-us_topic_0249851113_p13243347131615">A pod is the smallest and simplest unit that you create or deploy in Kubernetes. It is designed to be an ephemeral, one-off entity. A pod can be evicted when node resources are insufficient and disappears along with a cluster node failure. Kubernetes provides controllers to manage pods. Controllers can create and manage pods, and provide replica management, rolling upgrade, and self-healing capabilities. The most commonly used controller is Deployment.</p>
<div class="fignone" id="cce_10_0006__en-us_topic_0249851113_fig12546173933714"><span class="figcap"><b>Figure 2 </b>Deployment</span><br><span><img id="cce_10_0006__en-us_topic_0249851113_image5671529113711" src="en-us_image_0000001695896721.png"></span></div>
<div class="section" id="cce_10_0006__section1972719357496"><h4 class="sectiontitle">Overview of Deployment</h4><p id="cce_10_0006__en-us_topic_0249851113_p13243347131615">A pod is the smallest and simplest unit that you create or deploy in Kubernetes. It is designed to be an ephemeral, one-off entity. A pod can be evicted when node resources are insufficient and disappears along with a cluster node failure. Kubernetes provides controllers to manage pods. Controllers can create and manage pods, and provide replica management, rolling upgrade, and self-healing capabilities. The most commonly used controller is Deployment.</p>
<div class="fignone" id="cce_10_0006__en-us_topic_0249851113_fig12546173933714"><span class="figcap"><b>Figure 2 </b>Relationship between a Deployment and pods</span><br><span><img id="cce_10_0006__en-us_topic_0249851113_image5671529113711" src="en-us_image_0258095884.png"></span></div>
<p id="cce_10_0006__en-us_topic_0249851113_p35371248184511">A Deployment can contain one or more pods. These pods have the same role. Therefore, the system automatically distributes requests to multiple pods of a Deployment.</p>
<p id="cce_10_0006__en-us_topic_0249851113_p11715188281">A Deployment integrates a lot of functions, including online deployment, rolling upgrade, replica creation, and restoration of online jobs. To some extent, Deployments can be used to realize unattended rollout, which greatly reduces difficulties and operation risks in the rollout process.</p>
</div>
<div class="section" id="cce_10_0006__section14888155424918"><h4 class="sectiontitle">StatefulSet</h4><p id="cce_10_0006__en-us_topic_0249896621_p12502102192418">All pods under a Deployment have the same characteristics except for the name and IP address. If required, a Deployment can use the pod template to create a new pod. If not required, the Deployment can delete any one of the pods.</p>
<div class="section" id="cce_10_0006__section14888155424918"><h4 class="sectiontitle">Overview of StatefulSet</h4><p id="cce_10_0006__en-us_topic_0249896621_p12502102192418">All pods under a Deployment have the same characteristics except for the name and IP address. If required, a Deployment can use a pod template to create new pods. If not required, the Deployment can delete any one of the pods.</p>
<p id="cce_10_0006__en-us_topic_0249896621_p2669143675415">However, Deployments cannot meet the requirements in some distributed scenarios when each pod requires its own status or in a distributed database where each pod requires independent storage.</p>
<p id="cce_10_0006__en-us_topic_0249896621_p97277467269">With detailed analysis, it is found that each part of distributed stateful applications plays a different role. For example, the database nodes are deployed in active/standby mode, and pods are dependent on each other. In this case, the pods need to meet the following requirements:</p>
<ul id="cce_10_0006__en-us_topic_0249896621_ul1181724132317"><li id="cce_10_0006__en-us_topic_0249896621_li10181102419231">A pod can be recognized by other pods. Therefore, a pod must have a fixed identifier.</li><li id="cce_10_0006__en-us_topic_0249896621_li81819249237">Each pod has an independent storage device. After a pod is deleted and then restored, the data read from the pod must be the same as the previous one. Otherwise, the pod status is inconsistent.</li></ul>
<p id="cce_10_0006__en-us_topic_0249896621_p97277467269">Distributed stateful applications involve different roles for different responsibilities. For example, databases work in active/standby mode, and pods depend on each other. To deploy stateful applications in Kubernetes, ensure pods meet the following requirements:</p>
<ul id="cce_10_0006__en-us_topic_0249896621_ul1181724132317"><li id="cce_10_0006__en-us_topic_0249896621_li10181102419231">Each pod must have a fixed identifier so that it can be recognized by other pods.</li><li id="cce_10_0006__en-us_topic_0249896621_li81819249237">Separate storage resources must be configured for each pod. In this way, the original data can be retrieved after a pod is deleted and restored. Otherwise, the pod status will be changed after the pod is rebuilt.</li></ul>
<p id="cce_10_0006__en-us_topic_0249896621_p929315724313">To address the preceding requirements, Kubernetes provides StatefulSets.</p>
<ol id="cce_10_0006__en-us_topic_0249896621_ol117020203559"><li id="cce_10_0006__en-us_topic_0249896621_li183871501692">A StatefulSet provides a fixed name for each pod following a fixed number ranging from 0 to N. After a pod is rescheduled, the pod name and the host name remain unchanged.</li><li id="cce_10_0006__en-us_topic_0249896621_li1789810518913">A StatefulSet provides a fixed access domain name for each pod through the headless Service (described in the following sections).</li><li id="cce_10_0006__en-us_topic_0249896621_li43183204569">The StatefulSet creates PersistentVolumeClaims (PVCs) with fixed identifiers to ensure that pods can access the same persistent data after being rescheduled.<p id="cce_10_0006__en-us_topic_0249896621_p8536185392116"><a name="cce_10_0006__en-us_topic_0249896621_li43183204569"></a><a name="en-us_topic_0249896621_li43183204569"></a><span><img id="cce_10_0006__en-us_topic_0249896621_image9125145402111" src="en-us_image_0000001647417792.png"></span></p>
<ol id="cce_10_0006__en-us_topic_0249896621_ol117020203559"><li id="cce_10_0006__en-us_topic_0249896621_li183871501692">StatefulSets provide a fixed name for each pod following a fixed number ranging from 0 to N. After a pod is rescheduled, the pod name and the hostname remain unchanged.</li><li id="cce_10_0006__en-us_topic_0249896621_li1789810518913">StatefulSets use a headless Service to allocate a fixed domain name for each pod.</li><li id="cce_10_0006__en-us_topic_0249896621_li43183204569">StatefulSets create PersistentVolumeClaims (PVCs) with fixed identifiers to ensure that pods can access the same persistent data after being rescheduled.<p id="cce_10_0006__en-us_topic_0249896621_p8536185392116"><a name="cce_10_0006__en-us_topic_0249896621_li43183204569"></a><a name="en-us_topic_0249896621_li43183204569"></a><span><img id="cce_10_0006__en-us_topic_0249896621_image9125145402111" src="en-us_image_0258203193.png"></span></p>
</li></ol>
</div>
<div class="section" id="cce_10_0006__section7846281504"><h4 class="sectiontitle">DaemonSet</h4><p id="cce_10_0006__en-us_topic_0249851114_p441104813815">A DaemonSet runs a pod on each node in a cluster and ensures that there is only one pod. This works well for certain system-level applications, such as log collection and resource monitoring, since they must run on each node and need only a few pods. A good example is kube-proxy.</p>
<div class="section" id="cce_10_0006__section7846281504"><h4 class="sectiontitle">Overview of DaemonSet</h4><p id="cce_10_0006__en-us_topic_0249851114_p441104813815">A DaemonSet runs a pod on each node in a cluster and ensures that there is only one pod. This works well for certain system-level applications such as log collection and resource monitoring since they must run on each node and need only a few pods. A good example is kube-proxy.</p>
<p id="cce_10_0006__en-us_topic_0249851114_p5986375820">DaemonSets are closely related to nodes. If a node becomes faulty, the DaemonSet will not create the same pods on other nodes.</p>
<div class="fignone" id="cce_10_0006__en-us_topic_0249851114_fig27588261914"><span class="figcap"><b>Figure 3 </b>DaemonSet</span><br><span><img id="cce_10_0006__en-us_topic_0249851114_image13336133243518" src="en-us_image_0000001647577048.png"></span></div>
<div class="fignone" id="cce_10_0006__en-us_topic_0249851114_fig27588261914"><span class="figcap"><b>Figure 3 </b>DaemonSet</span><br><span><img id="cce_10_0006__en-us_topic_0249851114_image13336133243518" src="en-us_image_0258871213.png"></span></div>
</div>
<div class="section" id="cce_10_0006__section153173319578"><h4 class="sectiontitle">Job and Cron Job</h4><p id="cce_10_0006__en-us_topic_0249851115_p10889736123218">Jobs and cron jobs allow you to run short lived, one-off tasks in batch. They ensure the task pods run to completion.</p>
<ul id="cce_10_0006__en-us_topic_0249851115_ul197714911354"><li id="cce_10_0006__en-us_topic_0249851115_li47711097352">A job is a resource object used by Kubernetes to control batch tasks. Jobs are different from long-term servo tasks (such as Deployments and StatefulSets). The former is started and terminated at specific times, while the latter runs unceasingly unless being terminated. The pods managed by a job will be automatically removed after completing tasks based on user configurations.</li><li id="cce_10_0006__en-us_topic_0249851115_li249061111353">A cron job runs a job periodically on a specified schedule. A cron job object is similar to a line of a crontab file in Linux.</li></ul>
<div class="section" id="cce_10_0006__section153173319578"><h4 class="sectiontitle">Overview of Job and CronJob</h4><p id="cce_10_0006__en-us_topic_0249851115_p10889736123218">Jobs and cron jobs allow you to run short lived, one-off tasks in batch. They ensure the task pods run to completion.</p>
<ul id="cce_10_0006__en-us_topic_0249851115_ul197714911354"><li id="cce_10_0006__en-us_topic_0249851115_li47711097352">A job is a resource object used by Kubernetes to control batch tasks. Jobs are different from long-term servo tasks (such as Deployments and StatefulSets). The former is started and terminated at specific times, while the latter runs unceasingly unless being terminated. The pods managed by a job will be automatically removed after successfully completing tasks based on user configurations.</li><li id="cce_10_0006__en-us_topic_0249851115_li249061111353">A cron job runs a job periodically on a specified schedule. A cron job object is similar to a line of a crontab file in Linux.</li></ul>
<p id="cce_10_0006__en-us_topic_0249851115_p166171774387">This run-to-completion feature of jobs is especially suitable for one-off tasks, such as continuous integration (CI).</p>
</div>
<div class="section" id="cce_10_0006__section3891192610218"><h4 class="sectiontitle">Workload Lifecycle</h4>

13
docs/cce/umn/cce_10_0007.html
View File

@ -25,7 +25,9 @@
</tr>
<tr id="cce_10_0007__en-us_topic_0107283638_row1657153916181"><td class="cellrowborder" valign="top" width="24.610000000000003%" headers="mcps1.3.1.2.1.2.3.1.1 "><p id="cce_10_0007__en-us_topic_0107283638_p1457639131817"><a href="#cce_10_0007__en-us_topic_0107283638_section21669213390">Edit YAML</a></p>
</td>
<td class="cellrowborder" valign="top" width="75.39%" headers="mcps1.3.1.2.1.2.3.1.2 "><p id="cce_10_0007__en-us_topic_0107283638_p11572397189">You can modify and download the YAML files of Deployments, StatefulSets, DaemonSets, and pods on the CCE console. YAML files of jobs and cron jobs can only be viewed, copied, and downloaded.</p>
<td class="cellrowborder" valign="top" width="75.39%" headers="mcps1.3.1.2.1.2.3.1.2 "><p id="cce_10_0007__en-us_topic_0107283638_p11572397189">You can modify and download YAML files of Deployments, StatefulSets, DaemonSets, CronJobs, and containers on the CCE console. YAML files of jobs can only be viewed, copied, and downloaded.</p>
<div class="note" id="cce_10_0007__note17426542882"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0007__p142618426810">If an existing CronJob is modified, the new configuration takes effect for the new pods, and the existing pod continues to run without any change.</p>
</div></div>
</td>
</tr>
<tr id="cce_10_0007__en-us_topic_0107283638_row1571539101815"><td class="cellrowborder" valign="top" width="24.610000000000003%" headers="mcps1.3.1.2.1.2.3.1.1 "><p id="cce_10_0007__en-us_topic_0107283638_p105743919187"><a href="#cce_10_0007__en-us_topic_0107283638_section13324541124815">Roll Back</a></p>
@ -74,8 +76,8 @@
<div class="section" id="cce_10_0007__en-us_topic_0107283638_section51511928173817"><a name="cce_10_0007__en-us_topic_0107283638_section51511928173817"></a><a name="en-us_topic_0107283638_section51511928173817"></a><h4 class="sectiontitle">Viewing Logs</h4><p id="cce_10_0007__en-us_topic_0107283638_p7643185724813">You can view logs of Deployments, StatefulSets, DaemonSets, and jobs. This section uses a Deployment as an example to describe how to view logs.</p>
<div class="notice" id="cce_10_0007__note177339212275"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cce_10_0007__p998763711231">Before viewing logs, ensure that the time of the browser is the same as that on the backend server.</p>
</div></div>
<ol id="cce_10_0007__en-us_topic_0107283638_ol14644105712488"><li id="cce_10_0007__en-us_topic_0107283638_li2619151017014"><span>Log in to the CCE console, go to an existing cluster, and choose <strong id="cce_10_0007__b153351729122716">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li1340513385528"><span>Click the <strong id="cce_10_0007__b24101331162716">Deployments</strong> tab and click the <span class="uicontrol" id="cce_10_0007__uicontrol741018314276"><b>View Log</b></span> of the target workload.</span><p><p id="cce_10_0007__en-us_topic_0107283638_p17548132715421">On the displayed <strong id="cce_10_0007__b793112517535">View Log</strong> window, you can view logs.</p>
<div class="note" id="cce_10_0007__en-us_topic_0107283638_note216713316213"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0007__en-us_topic_0107283638_p101679316212">The displayed logs are standard output logs of containers and do not have persistence and advanced O&amp;M capabilities. To use more comprehensive log capabilities, see <a href="cce_10_0553.html">Logs</a>. If the function of collecting standard output is enabled for the workload (enabled by default), you can go to AOM to view more workload logs. For details, see <a href="cce_10_0018.html">Using ICAgent to Collect Container Logs</a>.</p>
<ol id="cce_10_0007__en-us_topic_0107283638_ol14644105712488"><li id="cce_10_0007__en-us_topic_0107283638_li2619151017014"><span>Log in to the CCE console, go to an existing cluster, and choose <strong id="cce_10_0007__b153351729122716">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li1340513385528"><span>Click the <strong id="cce_10_0007__b24101331162716">Deployments</strong> tab and click the <span class="uicontrol" id="cce_10_0007__uicontrol741018314276"><b>View Log</b></span> of the target workload.</span><p><p id="cce_10_0007__en-us_topic_0107283638_p17548132715421">In the displayed <strong id="cce_10_0007__b793112517535">View Log</strong> window, you can view logs.</p>
<div class="note" id="cce_10_0007__en-us_topic_0107283638_note216713316213"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0007__en-us_topic_0107283638_p101679316212">The displayed logs are standard output logs of containers and do not have persistence and advanced O&amp;M capabilities. To use more comprehensive log capabilities, see <a href="cce_10_0553.html">Logs</a>. If the function of collecting standard output is enabled for the workload (enabled by default), you can go to AOM to view more workload logs. For details, see <a href="cce_10_0018.html">Connecting CCE to AOM</a>.</p>
</div></div>
</p></li></ol>
</div>
@ -86,12 +88,11 @@
</div></div>
</p></li><li id="cce_10_0007__en-us_topic_0107283638_li8831149194314"><span>Upgrade the workload based on service requirements. The method for setting parameter is the same as that for creating a workload.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li3833189134315"><span>After the update is complete, click <span class="uicontrol" id="cce_10_0007__uicontrol5311635122814"><b>Upgrade Workload</b></span>, manually confirm the YAML file, and submit the upgrade.</span></li></ol>
</div>
<div class="section" id="cce_10_0007__en-us_topic_0107283638_section21669213390"><a name="cce_10_0007__en-us_topic_0107283638_section21669213390"></a><a name="en-us_topic_0107283638_section21669213390"></a><h4 class="sectiontitle">Editing a YAML file</h4><p id="cce_10_0007__en-us_topic_0107283638_p879119319360">You can modify and download the YAML files of Deployments, StatefulSets, DaemonSets, and pods on the CCE console. YAML files of jobs and cron jobs can only be viewed, copied, and downloaded. This section uses a Deployment as an example to describe how to edit the YAML file.</p>
<div class="section" id="cce_10_0007__en-us_topic_0107283638_section21669213390"><a name="cce_10_0007__en-us_topic_0107283638_section21669213390"></a><a name="en-us_topic_0107283638_section21669213390"></a><h4 class="sectiontitle">Editing a YAML file</h4><p id="cce_10_0007__en-us_topic_0107283638_p879119319360">You can modify and download YAML files of Deployments, StatefulSets, DaemonSets, CronJobs, and containers on the CCE console. YAML files of jobs can only be viewed, copied, and downloaded. This section uses a Deployment as an example to describe how to edit the YAML file.</p>
<ol id="cce_10_0007__en-us_topic_0107283638_ol1879112311361"><li id="cce_10_0007__li635115103505"><span>Log in to the CCE console, go to an existing cluster, and choose <strong id="cce_10_0007__b95501137142817">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__li1335171017509"><span>Click the <strong id="cce_10_0007__b1413614042816">Deployments</strong> tab and choose <strong id="cce_10_0007__b413716406287">More</strong> &gt; <strong id="cce_10_0007__b18137240202819">Edit YAML</strong> in the <strong id="cce_10_0007__b21377402282">Operation</strong> column of the target workload. In the dialog box that is displayed, modify the YAML file.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li97921133367"><span>Click <strong id="cce_10_0007__b1165164173410">OK</strong>.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li87324268415"><span>(Optional) In the <strong id="cce_10_0007__en-us_topic_0107283638_b8257102371317">Edit YAML</strong> window, click <strong id="cce_10_0007__en-us_topic_0107283638_b13222327121315">Download</strong> to download the YAML file.</span></li></ol>
</div>
<div class="section" id="cce_10_0007__en-us_topic_0107283638_section13324541124815"><a name="cce_10_0007__en-us_topic_0107283638_section13324541124815"></a><a name="en-us_topic_0107283638_section13324541124815"></a><h4 class="sectiontitle">Rolling Back a Workload (Available Only for Deployments)</h4><p id="cce_10_0007__en-us_topic_0107283638_p252119142614">CCE records the release history of all Deployments. You can roll back a Deployment to a specified version.</p>
<ol id="cce_10_0007__en-us_topic_0107283638_ol165211495268"><li id="cce_10_0007__en-us_topic_0107283638_li0901438403"><span>Log in to the CCE console, go to an existing cluster, and choose <strong id="cce_10_0007__b1982864212286">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li1254215491914"><span>Click the <strong id="cce_10_0007__b0953744172818">Deployments</strong> tab, choose <span class="uicontrol" id="cce_10_0007__uicontrol1195354418284"><b>More &gt; Roll Back</b></span> in the <strong id="cce_10_0007__b8954204472812">Operation</strong> column of the target workload.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li383212838"><span>Switch to the <strong id="cce_10_0007__b9222047122811">Change History</strong> tab page, click <span class="uicontrol" id="cce_10_0007__uicontrol13223154715289"><b>Roll Back to This Version</b></span> of the target version, manually confirm the YAML file, and click <span class="uicontrol" id="cce_10_0007__uicontrol5223104722812"><b>OK</b></span>.</span><p><p id="cce_10_0007__p119891725195220"></p>
</p></li></ol>
<ol id="cce_10_0007__en-us_topic_0107283638_ol165211495268"><li id="cce_10_0007__en-us_topic_0107283638_li0901438403"><span>Log in to the CCE console, go to an existing cluster, and choose <strong id="cce_10_0007__b1982864212286">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li1254215491914"><span>Click the <strong id="cce_10_0007__b0953744172818">Deployments</strong> tab, choose <span class="uicontrol" id="cce_10_0007__uicontrol1195354418284"><b>More &gt; Roll Back</b></span> in the <strong id="cce_10_0007__b8954204472812">Operation</strong> column of the target workload.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li383212838"><span>Switch to the <strong id="cce_10_0007__b9222047122811">Change History</strong> tab page, click <span class="uicontrol" id="cce_10_0007__uicontrol13223154715289"><b>Roll Back to This Version</b></span> of the target version, manually confirm the YAML file, and click <span class="uicontrol" id="cce_10_0007__uicontrol5223104722812"><b>OK</b></span>.</span></li></ol>
</div>
<div class="section" id="cce_10_0007__section132451237607"><a name="cce_10_0007__section132451237607"></a><a name="section132451237607"></a><h4 class="sectiontitle">Redeploying a Workload</h4><p id="cce_10_0007__p15601819195812">After you redeploy a workload, all pods in the workload will be restarted. This section uses Deployments as an example to illustrate how to redeploy a workload.</p>
<ol id="cce_10_0007__ol0529114105916"><li id="cce_10_0007__li152911415912"><span>Log in to the CCE console, go to an existing cluster, and choose <strong id="cce_10_0007__b1861155692810">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__li2052917419597"><span>Click the <strong id="cce_10_0007__b13542145872817">Deployments</strong> tab and choose <strong id="cce_10_0007__b1454245820284">More</strong> &gt; <strong id="cce_10_0007__b6543165817284">Redeploy</strong> in the <strong id="cce_10_0007__b18543858112819">Operation</strong> column of the target workload.</span></li><li id="cce_10_0007__li052984175917"><span>In the dialog box that is displayed, click <span class="uicontrol" id="cce_10_0007__uicontrol8574100202910"><b>Yes</b></span> to redeploy the workload.</span></li></ol>

11
docs/cce/umn/cce_10_0009.html
View File

@ -6,14 +6,13 @@
</div>
<div class="section" id="cce_10_0009__section14876601632"><h4 class="sectiontitle">Prerequisites</h4><p id="cce_10_0009__p545510319312">The node where the workload is running is accessible from public networks.</p>
</div>
<div class="section" id="cce_10_0009__section0402183334411"><h4 class="sectiontitle">Using the Console</h4><ol id="cce_10_0009__ol1748117409446"><li id="cce_10_0009__li16481144064414"><a name="cce_10_0009__li16481144064414"></a><a name="li16481144064414"></a><span>Create a secret for accessing a third-party image repository.</span><p><p id="cce_10_0009__p75695254516">Click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0009__b361110141418">ConfigMaps and Secrets</strong>. On the <strong id="cce_10_0009__b146111414154116">Secrets</strong> tab, click <strong id="cce_10_0009__b9611714144114">Create Secret</strong> in the upper right corner. Set <strong id="cce_10_0009__b1161113140413">Secret Type</strong> to <strong id="cce_10_0009__b461115144411">kubernetes.io/dockerconfigjson</strong>. For details, see <a href="cce_10_0153.html">Creating a Secret</a>.</p>
<div class="section" id="cce_10_0009__section0402183334411"><h4 class="sectiontitle">Using the Console</h4><ol id="cce_10_0009__ol1748117409446"><li id="cce_10_0009__li16481144064414"><a name="cce_10_0009__li16481144064414"></a><a name="li16481144064414"></a><span>Create a secret for accessing a third-party image repository.</span><p><p id="cce_10_0009__p75695254516">Click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0009__b417271013498"><span id="cce_10_0009__text1266312153316">ConfigMaps and Secrets</span></strong>. On the <strong id="cce_10_0009__b0172121024918">Secrets</strong> tab page, click <strong id="cce_10_0009__b417381020492">Create Secret</strong> in the upper right corner. Set <strong id="cce_10_0009__b1717321018496">Secret Type</strong> to <strong id="cce_10_0009__b16174201034912">kubernetes.io/dockerconfigjson</strong>. For details, see <a href="cce_10_0153.html">Creating a Secret</a>.</p>
<p id="cce_10_0009__p819111064514">Enter the username and password used to access the third-party image repository.</p>
</p></li><li id="cce_10_0009__li13221161713456"><span>When creating a workload, you can enter a private image path in the format of <em id="cce_10_0009__i138551445252">domainname/namespace/imagename:tag</em> for <span class="uicontrol" id="cce_10_0009__uicontrol252303262917"><b>Image Name</b></span> and select the key created in <a href="#cce_10_0009__li16481144064414">1</a> for <span class="uicontrol" id="cce_10_0009__uicontrol1912713512391"><b>Image Access Credential</b></span>.</span><p><p id="cce_10_0009__p79771915112918"></p>
</p></li><li id="cce_10_0009__li1682113518595"><span>Set other parameters and click <span class="uicontrol" id="cce_10_0009__uicontrol14664142510020"><b>Create Workload</b></span>.</span></li></ol>
</p></li><li id="cce_10_0009__li13221161713456"><span>When creating a workload, enter a private image path in the format of <em id="cce_10_0009__i127371150203116">domainname/namespace/imagename:tag</em> in <span class="uicontrol" id="cce_10_0009__uicontrol153963238313"><b>Image Name</b></span> and select the key created in <a href="#cce_10_0009__li16481144064414">1</a>.</span></li><li id="cce_10_0009__li1682113518595"><span>Set other parameters and click <span class="uicontrol" id="cce_10_0009__uicontrol14664142510020"><b>Create Workload</b></span>.</span></li></ol>
</div>
<div class="section" id="cce_10_0009__section18217101117197"><h4 class="sectiontitle">Using kubectl</h4><ol id="cce_10_0009__ol84677271516"><li id="cce_10_0009__li2338171784610"><span>Use kubectl to connect to the cluster. For details, see <a href="cce_10_0107.html">Connecting to a Cluster Using kubectl</a>.</span></li><li id="cce_10_0009__li54671627213"><span>Use kubectl to create a secret of the kubernetes.io/dockerconfigjson.</span><p><pre class="screen" id="cce_10_0009__screen1466527017">kubectl create secret docker-registry <strong id="cce_10_0009__b184651127812"><i><span class="varname" id="cce_10_0009__varname20740165882418">myregistrykey</span></i> </strong> -n <strong id="cce_10_0009__b1984843918253"><i><span class="varname" id="cce_10_0009__varname846884372519">default</span></i></strong> --docker-server=<strong id="cce_10_0009__b124669278112"><i><span class="varname" id="cce_10_0009__varname153949106259">DOCKER_REGISTRY_SERVER</span></i></strong> --docker-username=<strong id="cce_10_0009__b9466927114"><i><span class="varname" id="cce_10_0009__varname6836161311251">DOCKER_USER</span></i></strong> --docker-password=<strong id="cce_10_0009__b1046662715116"><i><span class="varname" id="cce_10_0009__varname321011555243">DOCKER_PASSWORD</span></i></strong> --docker-email=<strong id="cce_10_0009__b54661627119"><i><span class="varname" id="cce_10_0009__varname17516111722514">DOCKER_EMAIL</span></i></strong></pre>
<div class="section" id="cce_10_0009__section18217101117197"><h4 class="sectiontitle">Using kubectl</h4><ol id="cce_10_0009__ol84677271516"><li id="cce_10_0009__li2338171784610"><span>Use kubectl to connect to the cluster. For details, see <a href="cce_10_0107.html">Connecting to a Cluster Using kubectl</a>.</span></li><li id="cce_10_0009__li54671627213"><span>Use kubectl to create a secret of the kubernetes.io/dockerconfigjson.</span><p><pre class="screen" id="cce_10_0009__screen1466527017">kubectl create secret docker-registry <i><span class="varname" id="cce_10_0009__varname20740165882418">myregistrykey</span></i> -n <i><span class="varname" id="cce_10_0009__varname846884372519">default</span></i> --docker-server=<i><span class="varname" id="cce_10_0009__varname153949106259">DOCKER_REGISTRY_SERVER</span></i> --docker-username=<i><span class="varname" id="cce_10_0009__varname6836161311251">DOCKER_USER</span></i> --docker-password=<i><span class="varname" id="cce_10_0009__varname321011555243">DOCKER_PASSWORD</span></i> --docker-email=<i><span class="varname" id="cce_10_0009__varname17516111722514">DOCKER_EMAIL</span></i></pre>
<p id="cce_10_0009__p164665271714">In the preceding command, <em id="cce_10_0009__i18443812102618">myregistrykey</em> indicates the key name, <em id="cce_10_0009__i8904529112612">default</em> indicates the namespace where the key is located, and other parameters are as follows:</p>
<ul id="cce_10_0009__ul84670278112"><li id="cce_10_0009__li4467142711112"><strong id="cce_10_0009__b640184594119">DOCKER_REGISTRY_SERVER</strong>: address of a third-party image repository, for example, <strong id="cce_10_0009__b240104584114">www.3rdregistry.com</strong> or <strong id="cce_10_0009__b1440215458415">10.10.10.10:443</strong></li><li id="cce_10_0009__li13467127716"><strong id="cce_10_0009__b625118469208">DOCKER_USER</strong>: account used for logging in to a third-party image repository</li><li id="cce_10_0009__li746782712110"><strong id="cce_10_0009__b1539245574117">DOCKER</strong><strong id="cce_10_0009__b4392185511418">_PASSWORD</strong>: password used for logging in to a third-party image repository</li><li id="cce_10_0009__li1546712278117"><strong id="cce_10_0009__b10402845154110">DOCKER_EMAIL</strong>: email of a third-party image repository</li></ul>
<ul id="cce_10_0009__ul84670278112"><li id="cce_10_0009__li4467142711112"><strong id="cce_10_0009__b640184594119">DOCKER_REGISTRY_SERVER</strong>: address of a third-party image repository, for example, <strong id="cce_10_0009__b240104584114">www.3rdregistry.com</strong> or <strong id="cce_10_0009__b1440215458415">10.10.10.10:443</strong></li><li id="cce_10_0009__li13467127716"><strong id="cce_10_0009__b164021745114117">DOCKER_USER</strong>: account used for logging in to a third-party image repository</li><li id="cce_10_0009__li746782712110"><strong id="cce_10_0009__b1539245574117">DOCKER</strong><strong id="cce_10_0009__b4392185511418">_PASSWORD</strong>: password used for logging in to a third-party image repository</li><li id="cce_10_0009__li1546712278117"><strong id="cce_10_0009__b10402845154110">DOCKER_EMAIL</strong>: email of a third-party image repository</li></ul>
</p></li><li id="cce_10_0009__li161523518110"><span>Use a third-party image to create a workload.</span><p><div class="p" id="cce_10_0009__p13583471429">A kubernetes.io/dockerconfigjson secret is used for authentication when you obtain a private image. The following is an example of using the myregistrykey for authentication.<pre class="screen" id="cce_10_0009__screen0583771125">apiVersion: v1
kind: Pod
metadata:
@ -24,7 +23,7 @@ spec:
- name: foo
image: www.3rdregistry.com/janedoe/awesomeapp:v1
imagePullSecrets:
- name: myregistrykey #Use the created secret.</pre>
- name: myregistrykey # Use the created secret.</pre>
</div>
</p></li></ol>
</div>

12
docs/cce/umn/cce_10_0010.html
View File

@ -4,30 +4,30 @@
<div id="body1522665832344"><p id="cce_10_0010__p13310145119810">You can learn about a cluster network from the following two aspects:</p>
<ul id="cce_10_0010__ul65247121891"><li id="cce_10_0010__li14524161214917">What is a cluster network like? A cluster consists of multiple nodes, and pods (or containers) are running on the nodes. Nodes and containers need to communicate with each other. For details about the cluster network types and their functions, see <a href="#cce_10_0010__section1131733719195">Cluster Network Structure</a>.</li><li id="cce_10_0010__li55241612391">How is pod access implemented in a cluster? Accessing a pod or container is a process of accessing services of a user. Kubernetes provides <a href="#cce_10_0010__section1860619221134">Service</a> and <a href="#cce_10_0010__section1248852094313">Ingress</a> to address pod access issues. This section summarizes common network access scenarios. You can select the proper scenario based on site requirements. For details about the network access scenarios, see <a href="#cce_10_0010__section1286493159">Access Scenarios</a>.</li></ul>
<div class="section" id="cce_10_0010__section1131733719195"><a name="cce_10_0010__section1131733719195"></a><a name="section1131733719195"></a><h4 class="sectiontitle">Cluster Network Structure</h4><p id="cce_10_0010__p3299181794916">All nodes in the cluster are located in a VPC and use the VPC network. The container network is managed by dedicated network add-ons.</p>
<p id="cce_10_0010__p452843519446"><span><img id="cce_10_0010__image94831936164418" src="en-us_image_0000001647576700.png"></span></p>
<p id="cce_10_0010__p452843519446"><span><img id="cce_10_0010__image94831936164418" src="en-us_image_0000001750950104.png"></span></p>
<ul id="cce_10_0010__ul1916179122617"><li id="cce_10_0010__li13455145754315"><strong id="cce_10_0010__b19468105563811">Node Network</strong><p id="cce_10_0010__p17682193014812">A node network assigns IP addresses to hosts (nodes in the figure above) in a cluster. Select a VPC subnet as the node network of the CCE cluster. The number of available IP addresses in a subnet determines the maximum number of nodes (including master nodes and worker nodes) that can be created in a cluster. This quantity is also affected by the container network. For details, see the container network model.</p>
</li><li id="cce_10_0010__li16131141644715"><strong id="cce_10_0010__b1975815172433">Container Network</strong><p id="cce_10_0010__p523322010499">A container network assigns IP addresses to containers in a cluster. CCE inherits the IP-Per-Pod-Per-Network network model of Kubernetes. That is, each pod has an independent IP address on a network plane and all containers in a pod share the same network namespace. All pods in a cluster exist in a directly connected flat network. They can access each other through their IP addresses without using NAT. Kubernetes only provides a network mechanism for pods, but does not directly configure pod networks. The configuration of pod networks is implemented by specific container network add-ons. The container network add-ons are responsible for configuring networks for pods and managing container IP addresses.</p>
<p id="cce_10_0010__p3753153443514">Currently, CCE supports the following container network models:</p>
<ul id="cce_10_0010__ul1751111534368"><li id="cce_10_0010__li133611549182410">Container tunnel network: The container tunnel network is constructed on but independent of the node network through tunnel encapsulation. This network model uses VXLAN to encapsulate Ethernet packets into UDP packets and transmits them in tunnels. Open vSwitch serves as the backend virtual switch.</li><li id="cce_10_0010__li285944033514">VPC network: The VPC network uses VPC routing to integrate with the underlying network. This network model applies to performance-intensive scenarios. The maximum number of nodes allowed in a cluster depends on the route quota in a VPC network. Each node is assigned a CIDR block of a fixed size. This networking model is free from tunnel encapsulation overhead and outperforms the container tunnel network model. In addition, as VPC routing includes routes to node IP addresses and the container CIDR block, container pods in a cluster can be directly accessed from outside the cluster.</li><li id="cce_10_0010__li5395140132618">Developed by CCE, Cloud Native Network 2.0 deeply integrates Elastic Network Interfaces (ENIs) and Sub Network Interfaces (sub-ENIs) of VPC. Container IP addresses are allocated from the VPC CIDR block. ELB passthrough networking is supported to direct access requests to containers. Security groups and elastic IPs (EIPs) are bound to deliver high performance.</li></ul>
<ul id="cce_10_0010__ul1751111534368"><li id="cce_10_0010__li133611549182410">Container tunnel network: The container tunnel network is constructed on but independent of the node network through tunnel encapsulation. This network model uses VXLAN to encapsulate Ethernet packets into UDP packets and transmits them in tunnels. Open vSwitch serves as the backend virtual switch.</li><li id="cce_10_0010__li285944033514">VPC network: The VPC network uses VPC routing to integrate with the underlying network. This network model applies to performance-intensive scenarios. The maximum number of nodes allowed in a cluster depends on the route quota in a VPC network. Each node is assigned a CIDR block of a fixed size. This networking model is free from tunnel encapsulation overhead and outperforms the container tunnel network model. In addition, as VPC routing includes routes to node IP addresses and the container CIDR block, container pods in a cluster can be directly accessed from outside the cluster.</li><li id="cce_10_0010__li5395140132618">Developed by CCE, Cloud Native 2.0 network deeply integrates Elastic Network Interfaces (ENIs) and Sub Network Interfaces (sub-ENIs) of VPC. Container IP addresses are allocated from the VPC CIDR block. ELB passthrough networking is supported to direct access requests to containers. Security groups and elastic IPs (EIPs) are bound to deliver high performance.</li></ul>
<p id="cce_10_0010__p397482011109">The performance, networking scale, and application scenarios of a container network vary according to the container network model. For details about the functions and features of different container network models, see <a href="cce_10_0281.html">Overview</a>.</p>
</li><li id="cce_10_0010__li9139522183714"><strong id="cce_10_0010__b1885317214113">Service Network</strong><p id="cce_10_0010__p584703114499">Service is also a Kubernetes object. Each Service has a static IP address. When creating a cluster on CCE, you can specify the Service CIDR block. The Service CIDR block cannot overlap with the node or container CIDR block. The Service CIDR block can be used only within a cluster.</p>
</li></ul>
</div>
<div class="section" id="cce_10_0010__section1860619221134"><a name="cce_10_0010__section1860619221134"></a><a name="section1860619221134"></a><h4 class="sectiontitle">Service</h4><p id="cce_10_0010__p314709111318">A Service is used for pod access. With a static IP address, a Service forwards access traffic to pods and performs load balancing for these pods.</p>
<div class="fignone" id="cce_10_0010__en-us_topic_0249851121_fig163156154816"><span class="figcap"><b>Figure 1 </b>Accessing pods through a Service</span><br><span><img id="cce_10_0010__en-us_topic_0249851121_image1926812771312" src="en-us_image_0000001695896373.png"></span></div>
<div class="fignone" id="cce_10_0010__en-us_topic_0249851121_fig163156154816"><span class="figcap"><b>Figure 1 </b>Accessing pods through a Service</span><br><span><img id="cce_10_0010__en-us_topic_0249851121_image1926812771312" src="en-us_image_0258889981.png"></span></div>
<p id="cce_10_0010__p831948183818">You can configure the following types of Services:</p>
<ul id="cce_10_0010__ul953218444116"><li id="cce_10_0010__li87791418174620">ClusterIP: used to make the Service only reachable from within a cluster.</li><li id="cce_10_0010__li17876227144612">NodePort: used for access from outside a cluster. A NodePort Service is accessed through the port on the node.</li><li id="cce_10_0010__li94953274615">LoadBalancer: used for access from outside a cluster. It is an extension of NodePort, to which a load balancer routes, and external systems only need to access the load balancer.</li></ul>
<p id="cce_10_0010__p1677717174140">For details about the Service, see <a href="cce_10_0249.html">Overview</a>.</p>
</div>
<div class="section" id="cce_10_0010__section1248852094313"><a name="cce_10_0010__section1248852094313"></a><a name="section1248852094313"></a><h4 class="sectiontitle">Ingress</h4><p id="cce_10_0010__p96672218193">Services forward requests using layer-4 TCP and UDP protocols. Ingresses forward requests using layer-7 HTTP and HTTPS protocols. Domain names and paths can be used to achieve finer granularities.</p>
<div class="fignone" id="cce_10_0010__fig816719454212"><span class="figcap"><b>Figure 2 </b>Ingress-Service</span><br><span><img id="cce_10_0010__en-us_topic_0249851122_image8371183511310" src="en-us_image_0000001647417440.png"></span></div>
<div class="fignone" id="cce_10_0010__fig816719454212"><span class="figcap"><b>Figure 2 </b>Ingress and Service</span><br><span><img id="cce_10_0010__en-us_topic_0249851122_image8371183511310" src="en-us_image_0258961458.png"></span></div>
<p id="cce_10_0010__p174691141141410">For details about the ingress, see <a href="cce_10_0094.html">Overview</a>.</p>
</div>
<div class="section" id="cce_10_0010__section1286493159"><a name="cce_10_0010__section1286493159"></a><a name="section1286493159"></a><h4 class="sectiontitle">Access Scenarios</h4><p id="cce_10_0010__p1558001514155">Workload access scenarios can be categorized as follows:</p>
<ul id="cce_10_0010__ul125010117542"><li id="cce_10_0010__li1466355519018">Intra-cluster access: A ClusterIP Service is used for workloads in the same cluster to access each other.</li><li id="cce_10_0010__li1014011111110">Access from outside a cluster: A Service (NodePort or LoadBalancer type) or an ingress is recommended for a workload outside a cluster to access workloads in the cluster.<ul id="cce_10_0010__ul101426119117"><li id="cce_10_0010__li8904911447">Access through the public network: An EIP should be bound to the node or load balancer.</li><li id="cce_10_0010__li2501311125411">Access through the private network: The workload can be accessed through the internal IP address of the node or load balancer. If workloads are located in different VPCs, a peering connection is required to enable communication between different VPCs.</li></ul>
</li><li id="cce_10_0010__li1066365520014">The workload can access the external network as follows:<ul id="cce_10_0010__ul17529512239"><li id="cce_10_0010__li26601017165619">Accessing an intranet: The workload accesses the intranet address, but the implementation method varies depending on container network models. Ensure that the peer security group allows the access requests from the container CIDR block. </li><li id="cce_10_0010__li8257105318237">Accessing a public network: Assign an EIP to the node where the workload runs (when the VPC network or tunnel network model is used), bind an EIP to the pod IP address (when the Cloud Native Network 2.0 model is used), or configure SNAT rules through the NAT gateway. For details, see <a href="cce_10_0400.html">Accessing Public Networks from a Container</a>.</li></ul>
</li><li id="cce_10_0010__li1066365520014">The workload can access the external network as follows:<ul id="cce_10_0010__ul17529512239"><li id="cce_10_0010__li26601017165619">Accessing an intranet: The workload accesses the intranet address, but the implementation method varies depending on container network models. Ensure that the peer security group allows the access requests from the container CIDR block.</li><li id="cce_10_0010__li8257105318237">Accessing a public network: Assign an EIP to the node where the workload runs (when the VPC network or tunnel network model is used), bind an EIP to the pod IP address (when the Cloud Native Network 2.0 model is used), or configure SNAT rules through the NAT gateway. For details, see <a href="cce_10_0400.html">Accessing Public Networks from a Container</a>.</li></ul>
</li></ul>
<div class="fignone" id="cce_10_0010__fig13795829151515"><span class="figcap"><b>Figure 3 </b>Network access diagram</span><br><span><img id="cce_10_0010__image445972519529" src="en-us_image_0000001647576708.png"></span></div>
<div class="fignone" id="cce_10_0010__fig13795829151515"><span class="figcap"><b>Figure 3 </b>Network access diagram</span><br><span><img id="cce_10_0010__image445972519529" src="en-us_image_0000001797909889.png"></span></div>
</div>
</div>
<div>

4
docs/cce/umn/cce_10_0011.html
View File

@ -4,9 +4,9 @@
<div id="body1522736584192"><div class="section" id="cce_10_0011__section13559184110492"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0011__p32401248184910">ClusterIP Services allow workloads in the same cluster to use their cluster-internal domain names to access each other.</p>
<p id="cce_10_0011__p653753053815">The cluster-internal domain name format is <em id="cce_10_0011__i8179113533712">&lt;Service name&gt;</em>.<em id="cce_10_0011__i14179133519374">&lt;Namespace of the workload&gt;</em><strong id="cce_10_0011__b164892813716">.svc.cluster.local:</strong><em id="cce_10_0011__i19337102815712">&lt;Port&gt;</em>, for example, <strong id="cce_10_0011__b8115811381">nginx.default.svc.cluster.local:80</strong>.</p>
<p id="cce_10_0011__p1778412445517"><a href="#cce_10_0011__fig192245420557">Figure 1</a> shows the mapping relationships between access channels, container ports, and access ports.</p>
<div class="fignone" id="cce_10_0011__fig192245420557"><a name="cce_10_0011__fig192245420557"></a><a name="fig192245420557"></a><span class="figcap"><b>Figure 1 </b>Intra-cluster access (ClusterIP)</span><br><span><img id="cce_10_0011__image1942163010278" src="en-us_image_0000001647417816.png"></span></div>
<div class="fignone" id="cce_10_0011__fig192245420557"><a name="cce_10_0011__fig192245420557"></a><a name="fig192245420557"></a><span class="figcap"><b>Figure 1 </b>Intra-cluster access (ClusterIP)</span><br><span><img id="cce_10_0011__image1942163010278" src="en-us_image_0000001750791656.png"></span></div>
</div>
<div class="section" id="cce_10_0011__section51925078171335"><h4 class="sectiontitle">Creating a ClusterIP Service</h4><ol id="cce_10_0011__ol1321170617144"><li id="cce_10_0011__li41731123658"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0011__li836916478329"><span>Choose <strong id="cce_10_0011__b85507206148">Networking</strong> in the navigation pane and click <strong id="cce_10_0011__b1938115214148">Create Service</strong> in the upper right corner.</span></li><li id="cce_10_0011__li3476651017144"><span>Set intra-cluster access parameters.</span><p><ul id="cce_10_0011__ul4446314017144"><li id="cce_10_0011__li6462394317144"><strong id="cce_10_0011__b181470402505">Service Name</strong>: Service name, which can be the same as the workload name.</li><li id="cce_10_0011__li89543531070"><strong id="cce_10_0011__b2091115317145">Service Type</strong>: Select <strong id="cce_10_0011__b291265312145">ClusterIP</strong>.</li><li id="cce_10_0011__li4800017144"><strong id="cce_10_0011__b3997151161512">Namespace</strong>: Namespace to which the workload belongs.</li><li id="cce_10_0011__li43200017144"><strong id="cce_10_0011__b1758945315469">Selector</strong>: Add a label and click <strong id="cce_10_0011__b195891153164610">Confirm</strong>. A Service selects a pod based on the added label. You can also click <strong id="cce_10_0011__b796831114161">Reference Workload Label</strong> to reference the label of an existing workload. In the dialog box that is displayed, select a workload and click <strong id="cce_10_0011__b1117311264160">OK</strong>.</li><li id="cce_10_0011__li388800117144"><strong id="cce_10_0011__b102328496354">Port</strong><ul id="cce_10_0011__ul13757123384316"><li id="cce_10_0011__li475711338435"><strong id="cce_10_0011__b712192113108">Protocol</strong>: protocol used by the Service.</li><li id="cce_10_0011__li353122153610"><strong id="cce_10_0011__b2766425101013">Service Port</strong>: port used by the Service. The port number ranges from 1 to 65535.</li><li id="cce_10_0011__li177581033194316"><strong id="cce_10_0011__b2045852761014">Container Port</strong>: port on which the workload listens. For example, Nginx uses port 80 by default.</li></ul>
<div class="section" id="cce_10_0011__section51925078171335"><h4 class="sectiontitle">Creating a ClusterIP Service</h4><ol id="cce_10_0011__ol1321170617144"><li id="cce_10_0011__li41731123658"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0011__li836916478329"><span>In the navigation pane, choose <strong id="cce_10_0011__b18658321171411"><span id="cce_10_0011__text9765124722315">Services &amp; Ingresses</span></strong>. In the upper right corner, click <span class="uicontrol" id="cce_10_0011__uicontrol132971717714"><b>Create Service</b></span>.</span></li><li id="cce_10_0011__li3476651017144"><span>Set intra-cluster access parameters.</span><p><ul id="cce_10_0011__ul4446314017144"><li id="cce_10_0011__li6462394317144"><strong id="cce_10_0011__b181470402505">Service Name</strong>: Service name, which can be the same as the workload name.</li><li id="cce_10_0011__li89543531070"><strong id="cce_10_0011__b2091115317145">Service Type</strong>: Select <strong id="cce_10_0011__b291265312145">ClusterIP</strong>.</li><li id="cce_10_0011__li4800017144"><strong id="cce_10_0011__b3997151161512">Namespace</strong>: Namespace to which the workload belongs.</li><li id="cce_10_0011__li43200017144"><strong id="cce_10_0011__b16251723161514">Selector</strong>: Add a label and click <strong id="cce_10_0011__b157041550131611">Confirm</strong>. A Service selects a pod based on the added label. You can also click <strong id="cce_10_0011__b796831114161">Reference Workload Label</strong> to reference the label of an existing workload. In the dialog box that is displayed, select a workload and click <strong id="cce_10_0011__b1117311264160">OK</strong>.</li><li id="cce_10_0011__li388800117144"><strong id="cce_10_0011__b150413392315954">Port Settings</strong><ul id="cce_10_0011__ul13757123384316"><li id="cce_10_0011__li475711338435"><strong id="cce_10_0011__b712192113108">Protocol</strong>: protocol used by the Service.</li><li id="cce_10_0011__li353122153610"><strong id="cce_10_0011__b2766425101013">Service Port</strong>: port used by the Service. The port number ranges from 1 to 65535.</li><li id="cce_10_0011__li177581033194316"><strong id="cce_10_0011__b2045852761014">Container Port</strong>: port on which the workload listens. For example, Nginx uses port 80 by default.</li></ul>
</li></ul>
</p></li><li id="cce_10_0011__li5563226917144"><span>Click <strong id="cce_10_0011__b15590122052614">OK</strong>.</span></li></ol>
</div>

115
docs/cce/umn/cce_10_0012.html
View File

File diff suppressed because it is too large Load Diff

4
docs/cce/umn/cce_10_0014.html
View File

@ -8,10 +8,12 @@
</li>
<li class="ulchildlink"><strong><a href="cce_10_0385.html">Using Annotations to Configure Load Balancing</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0683.html">Service Using HTTP</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0683.html">Service Using HTTP or HTTPS</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0684.html">Configuring Health Check for Multiple Ports</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0685.html">Setting the Pod Ready Status Through the ELB Health Check</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0729.html">Configuring Timeout for a LoadBalancer Service</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0355.html">Enabling Passthrough Networking for LoadBalancer Services</a></strong><br>

63
docs/cce/umn/cce_10_0015.html
View File

File diff suppressed because it is too large Load Diff

56
docs/cce/umn/cce_10_0016.html
View File

File diff suppressed because it is too large Load Diff

42
docs/cce/umn/cce_10_0018.html
View File

File diff suppressed because it is too large Load Diff

4
docs/cce/umn/cce_10_0024.html
View File

@ -1,10 +1,10 @@
<a name="cce_10_0024"></a><a name="cce_10_0024"></a>
<h1 class="topictitle1">CTS Logs</h1>
<h1 class="topictitle1">Cloud Trace Service</h1>
<div id="body1525226397666"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="cce_10_0025.html">CCE Operations Supported by CTS</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0025.html">CCE Operations Supported by Cloud Trace Service</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0026.html">Querying Real-Time Traces</a></strong><br>
</li>

6
docs/cce/umn/cce_10_0025.html
View File

@ -1,8 +1,8 @@
<a name="cce_10_0025"></a><a name="cce_10_0025"></a>
<h1 class="topictitle1">CCE Operations Supported by CTS</h1>
<h1 class="topictitle1">CCE Operations Supported by Cloud Trace Service</h1>
<div id="body1525226397666">
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0025__table10122133613599" frame="border" border="1" rules="all"><caption><b>Table 1 </b>CCE operations supported by CTS</caption><thead align="left"><tr id="cce_10_0025__row1612243618593"><th align="left" class="cellrowborder" valign="top" width="28.37%" id="mcps1.4.1.2.4.1.1"><p id="cce_10_0025__p5122153665915">Operation</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0025__table10122133613599" frame="border" border="1" rules="all"><caption><b>Table 1 </b>CCE Operations Supported by CTS</caption><thead align="left"><tr id="cce_10_0025__row1612243618593"><th align="left" class="cellrowborder" valign="top" width="28.37%" id="mcps1.4.1.2.4.1.1"><p id="cce_10_0025__p5122153665915">Operation</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="25.230000000000004%" id="mcps1.4.1.2.4.1.2"><p id="cce_10_0025__p11394135314515">Resource Type</p>
</th>
@ -590,7 +590,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0024.html">CTS Logs</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0024.html">Cloud Trace Service</a></div>
</div>
</div>

26
docs/cce/umn/cce_10_0026.html
View File

@ -1,25 +1,25 @@
<a name="cce_10_0026"></a><a name="cce_10_0026"></a>
<h1 class="topictitle1">Querying Real-Time Traces</h1>
<div id="body1525226397666"><div class="section" id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_section5470822195238"><h4 class="sectiontitle">Scenarios</h4><p id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p333055219577">After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records generated in the last seven days.</p>
<p id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p3008599195238">This section describes how to query and export operation records of the last seven days on the CTS console.</p>
<ul id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_ul17577535194620"><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li201409184718"><a href="#cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_section19271975203">Viewing Real-Time Traces in the Trace List</a></li></ul>
<div id="body1525226397666"><div class="section" id="cce_10_0026__en-us_topic_0179639644_section5470822195238"><h4 class="sectiontitle">Scenarios</h4><p id="cce_10_0026__en-us_topic_0179639644_p333055219577">After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records generated in the last seven days.</p>
<p id="cce_10_0026__en-us_topic_0179639644_p3008599195238">This section describes how to query and export operation records of the last seven days on the CTS console.</p>
<ul id="cce_10_0026__en-us_topic_0179639644_ul17577535194620"><li id="cce_10_0026__en-us_topic_0179639644_li201409184718"><a href="#cce_10_0026__en-us_topic_0179639644_section19271975203">Viewing Real-Time Traces in the Trace List</a></li></ul>
</div>
<div class="section" id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_section19271975203"><a name="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_section19271975203"></a><a name="en-us_topic_0000001244101043_en-us_topic_0179639644_section19271975203"></a><h4 class="sectiontitle">Viewing Real-Time Traces in the Trace List</h4><ol id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_ol4845175152710"><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li791871844313">Log in to the management console.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li79188188435">Click <span><img id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_image2107213105014" src="en-us_image_0000001696838310.png"></span> in the upper left corner and choose <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b1810717138505">Management &amp; Deployment</strong> &gt; <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b1310871313509">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li591831894316">Choose <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b09819412220">Trace List</strong> in the navigation pane on the left.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li6936134194312">Set filters to search for your desired traces, as shown in <a href="#cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_fig139361441134311">Figure 1</a>. The following filters are available:<div class="fignone" id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_fig139361441134311"><a name="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_fig139361441134311"></a><a name="en-us_topic_0000001244101043_en-us_topic_0179639644_fig139361441134311"></a><span class="figcap"><b>Figure 1 </b>Filters</span><br><span><img id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_image14936144112433" src="en-us_image_0000001744598325.png"></span></div>
<div class="p" id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p15936134119435"><ul class="subitemlist" id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_ul20936164174314"><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li99361417432"><strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b179671714141513">Trace Type</strong>, <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b179671014191515">Trace Source</strong>, <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b4968714141517">Resource Type</strong>, and <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b14968101411516">Search By</strong>: Select a filter from the drop-down list.<ul id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_ul158893433010"><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li12760183118301">If you select <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b389315891511">Resource ID</strong> for <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b3893858131515">Search By</strong>, specify a resource ID.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li12760203115305">If you select <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b8997941831">Trace name</strong> for <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b199981541317">Search By</strong>, specify a trace name.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li197601031193019">If you select <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b196612501258">Resource name</strong> for <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b177275015252">Search By</strong>, specify a resource name.</li></ul>
</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li15936204184311"><strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b98151395276">Operator</strong>: Select a user.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li6936184119437"><strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b6981161112286">Trace Status</strong>: Select <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b1298716111281">All trace statuses</strong>, <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b7987181115281">Normal</strong>, <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b2988181112810">Warning</strong>, or <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b99881511132820">Incident</strong>.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li1993654144315">Time range: You can query traces generated during any time range in the last seven days.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li8936104118436">Click <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b861150123114">Export</strong> to export all traces in the query result as a CSV file. The file can contain up to 5000 records.</li></ul>
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section19271975203"><a name="cce_10_0026__en-us_topic_0179639644_section19271975203"></a><a name="en-us_topic_0179639644_section19271975203"></a><h4 class="sectiontitle">Viewing Real-Time Traces in the Trace List</h4><ol id="cce_10_0026__en-us_topic_0179639644_ol4845175152710"><li id="cce_10_0026__en-us_topic_0179639644_li791871844313">Log in to the management console.</li><li id="cce_10_0026__en-us_topic_0179639644_li79188188435">Click <span><img id="cce_10_0026__en-us_topic_0179639644_image2107213105014" src="en-us_image_0000001696838310.png"></span> in the upper left corner and choose <strong id="cce_10_0026__en-us_topic_0179639644_b1810717138505">Management &amp; Deployment</strong> &gt; <strong id="cce_10_0026__en-us_topic_0179639644_b1310871313509">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cce_10_0026__en-us_topic_0179639644_li591831894316">Choose <strong id="cce_10_0026__en-us_topic_0179639644_b09819412220">Trace List</strong> in the navigation pane on the left.</li><li id="cce_10_0026__en-us_topic_0179639644_li6936134194312">Set filters to search for your desired traces, as shown in <a href="#cce_10_0026__en-us_topic_0179639644_fig139361441134311">Figure 1</a>. The following filters are available:<div class="fignone" id="cce_10_0026__en-us_topic_0179639644_fig139361441134311"><a name="cce_10_0026__en-us_topic_0179639644_fig139361441134311"></a><a name="en-us_topic_0179639644_fig139361441134311"></a><span class="figcap"><b>Figure 1 </b>Filters</span><br><span><img id="cce_10_0026__en-us_topic_0179639644_image14936144112433" src="en-us_image_0000001744598325.png"></span></div>
<div class="p" id="cce_10_0026__en-us_topic_0179639644_p15936134119435"><ul class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_ul20936164174314"><li id="cce_10_0026__en-us_topic_0179639644_li99361417432"><strong id="cce_10_0026__en-us_topic_0179639644_b179671714141513">Trace Type</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b179671014191515">Trace Source</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b4968714141517">Resource Type</strong>, and <strong id="cce_10_0026__en-us_topic_0179639644_b14968101411516">Search By</strong>: Select a filter from the drop-down list.<ul id="cce_10_0026__en-us_topic_0179639644_ul158893433010"><li id="cce_10_0026__en-us_topic_0179639644_li12760183118301">If you select <strong id="cce_10_0026__en-us_topic_0179639644_b389315891511">Resource ID</strong> for <strong id="cce_10_0026__en-us_topic_0179639644_b3893858131515">Search By</strong>, specify a resource ID.</li><li id="cce_10_0026__en-us_topic_0179639644_li12760203115305">If you select <strong id="cce_10_0026__en-us_topic_0179639644_b8997941831">Trace name</strong> for <strong id="cce_10_0026__en-us_topic_0179639644_b199981541317">Search By</strong>, specify a trace name.</li><li id="cce_10_0026__en-us_topic_0179639644_li197601031193019">If you select <strong id="cce_10_0026__en-us_topic_0179639644_b196612501258">Resource name</strong> for <strong id="cce_10_0026__en-us_topic_0179639644_b177275015252">Search By</strong>, specify a resource name.</li></ul>
</li><li id="cce_10_0026__en-us_topic_0179639644_li15936204184311"><strong id="cce_10_0026__en-us_topic_0179639644_b98151395276">Operator</strong>: Select a user.</li><li id="cce_10_0026__en-us_topic_0179639644_li6936184119437"><strong id="cce_10_0026__en-us_topic_0179639644_b6981161112286">Trace Status</strong>: Select <strong id="cce_10_0026__en-us_topic_0179639644_b1298716111281">All trace statuses</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b7987181115281">Normal</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b2988181112810">Warning</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b99881511132820">Incident</strong>.</li><li id="cce_10_0026__en-us_topic_0179639644_li1993654144315">Time range: You can query traces generated during any time range in the last seven days.</li><li id="cce_10_0026__en-us_topic_0179639644_li8936104118436">Click <strong id="cce_10_0026__en-us_topic_0179639644_b861150123114">Export</strong> to export all traces in the query result as a CSV file. The file can contain up to 5000 records.</li></ul>
</div>
</li><li class="subitemlist" id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li094111715448">Click <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b55732514186">Query</strong>.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li29410170448">On the <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b176911834143214">Trace List</strong> page, you can also export and refresh the trace list.<ul id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_ul119414175448"><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li12946170445">Click <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b8907168171714">Export</strong> to export all traces in the query result as a CSV file. The file can contain up to 5000 records.</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li394151717445">Click <span><img id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_image109421716440" src="en-us_image_0000001696678850.png"></span> to view the latest information about traces.</li></ul>
</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li169491744418">Click <span><img id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_image9947176447" src="en-us_image_0000001744678489.jpg"></span> on the left of a trace to expand its details.<p id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p1294101714446"></p>
<p id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p1694171715446"><span><img id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_image49418175441" src="en-us_image_0000001696838318.png"></span></p>
<p id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p109481744411"></p>
</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li1094161784410">Click <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b139145611337">View Trace</strong> in the <strong id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_b1591756103313">Operation</strong> column. The trace details are displayed.<p id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_p1695161714447"><span><img id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_image1904172011220" src="en-us_image_0000001758618249.png"></span></p>
</li><li id="cce_10_0026__en-us_topic_0000001244101043_en-us_topic_0179639644_li129561719446">For details about key fields in the trace structure, see section "Trace References" &gt; "Trace Structure" and section "Trace References" &gt; "Example Traces".</li></ol>
</li><li class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_li094111715448">Click <strong id="cce_10_0026__en-us_topic_0179639644_b55732514186">Query</strong>.</li><li id="cce_10_0026__en-us_topic_0179639644_li29410170448">On the <strong id="cce_10_0026__en-us_topic_0179639644_b176911834143214">Trace List</strong> page, you can also export and refresh the trace list.<ul id="cce_10_0026__en-us_topic_0179639644_ul119414175448"><li id="cce_10_0026__en-us_topic_0179639644_li12946170445">Click <strong id="cce_10_0026__en-us_topic_0179639644_b8907168171714">Export</strong> to export all traces in the query result as a CSV file. The file can contain up to 5000 records.</li><li id="cce_10_0026__en-us_topic_0179639644_li394151717445">Click <span><img id="cce_10_0026__en-us_topic_0179639644_image109421716440" src="en-us_image_0000001696678850.png"></span> to view the latest information about traces.</li></ul>
</li><li id="cce_10_0026__en-us_topic_0179639644_li169491744418">Click <span><img id="cce_10_0026__en-us_topic_0179639644_image9947176447" src="en-us_image_0000001744678489.jpg"></span> on the left of a trace to expand its details.<p id="cce_10_0026__en-us_topic_0179639644_p1294101714446"></p>
<p id="cce_10_0026__en-us_topic_0179639644_p1694171715446"><span><img id="cce_10_0026__en-us_topic_0179639644_image49418175441" src="en-us_image_0000001696838318.png"></span></p>
<p id="cce_10_0026__en-us_topic_0179639644_p109481744411"></p>
</li><li id="cce_10_0026__en-us_topic_0179639644_li1094161784410">Click <strong id="cce_10_0026__en-us_topic_0179639644_b139145611337">View Trace</strong> in the <strong id="cce_10_0026__en-us_topic_0179639644_b1591756103313">Operation</strong> column. The trace details are displayed.<p id="cce_10_0026__en-us_topic_0179639644_p1695161714447"><span><img id="cce_10_0026__en-us_topic_0179639644_image1904172011220" src="en-us_image_0000001758618249.png"></span></p>
</li><li id="cce_10_0026__en-us_topic_0179639644_li129561719446">For details about key fields in the trace structure, see section "Trace References" &gt; "Trace Structure" and section "Trace References" &gt; "Example Traces".</li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0024.html">CTS Logs</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0024.html">Cloud Trace Service</a></div>
</div>
</div>

272
docs/cce/umn/cce_10_0028.html
View File

File diff suppressed because it is too large Load Diff

2
docs/cce/umn/cce_10_0030.html
View File

@ -8,7 +8,7 @@
</li>
<li class="ulchildlink"><strong><a href="cce_10_0285.html">Managing Namespaces</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0287.html">Setting a Resource Quota</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0287.html">Configuring Resource Quotas</a></strong><br>
</li>
</ul>
</div>

4
docs/cce/umn/cce_10_0036.html
View File

@ -3,9 +3,9 @@
<h1 class="topictitle1">Stopping a Node</h1>
<div id="body1564130562761"><div class="section" id="cce_10_0036__section127213017388"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0036__p866311509249">After a node in the cluster is stopped, services on the node are also stopped. Before stopping a node, ensure that discontinuity of the services on the node will not result in adverse impacts.</p>
</div>
<div class="section" id="cce_10_0036__section1489437103610"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0036__ul0917755162415"><li id="cce_10_0036__li1891719552246">Deleting a node will lead to pod migration, which may affect services. Therefore, delete nodes during off-peak hours.</li><li id="cce_10_0036__li791875552416">Unexpected risks may occur during node deletion. Back up related data in advance.</li><li id="cce_10_0036__li15918105582417">While the node is being deleted, the backend will set the node to the unschedulable state.</li><li id="cce_10_0036__li12918145520241">Only worker nodes can be stopped.</li></ul>
<div class="section" id="cce_10_0036__section1489437103610"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0036__ul0917755162415"><li id="cce_10_0036__li1891719552246">Deleting a node will lead to pod migration, which may affect services. Therefore, delete nodes during off-peak hours.</li><li id="cce_10_0036__li791875552416">Unexpected risks may occur during the operation. Back up related data in advance.</li><li id="cce_10_0036__li15918105582417">While the node is being deleted, the backend will set the node to the unschedulable state.</li><li id="cce_10_0036__li12918145520241">Only worker nodes can be stopped.</li></ul>
</div>
<div class="section" id="cce_10_0036__section14341135612442"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0036__ol5687174923613"><li id="cce_10_0036__li133915311359"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0036__li6687049203616"><span>In the navigation pane, choose <strong id="cce_10_0036__b0764291362">Nodes</strong>. In the right pane, click the name of the node to be stopped.</span></li><li id="cce_10_0036__li117301253183717"><span>In the upper right corner of the ECS details page, click <strong id="cce_10_0036__b109484372618">Stop</strong>. In the displayed dialog box, click <strong id="cce_10_0036__b29489372612">Yes</strong>.</span><p><div class="fignone" id="cce_10_0036__fig19269101385311"><span class="figcap"><b>Figure 1 </b>ECS details page</span><br><span><img id="cce_10_0036__image124001418192" src="en-us_image_0000001782097306.png"></span></div>
<div class="section" id="cce_10_0036__section14341135612442"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0036__ol5687174923613"><li id="cce_10_0036__li133915311359"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0036__li159521745431"><span>In the navigation pane, choose <span class="uicontrol" id="cce_10_0036__uicontrol378153945103635"><b>Nodes</b></span>. On the displayed page, click the <strong id="cce_10_0036__b1786259085103635">Nodes</strong> tab.</span></li><li id="cce_10_0036__li224719151931"><span>Locate the target node and click its name.</span></li><li id="cce_10_0036__li117301253183717"><span>In the upper right corner of the ECS details page, click <strong id="cce_10_0036__b2347626195316">Stop</strong>. In the displayed dialog box, click <strong id="cce_10_0036__b434722605318">Yes</strong>.</span><p><div class="fignone" id="cce_10_0036__fig19269101385311"><span class="figcap"><b>Figure 1 </b>ECS details page</span><br><span><img id="cce_10_0036__image124001418192" src="en-us_image_0000001817324166.png"></span></div>
</p></li></ol>
</div>
</div>

2
docs/cce/umn/cce_10_0044.html
View File

@ -1,6 +1,6 @@
<a name="cce_10_0044"></a><a name="cce_10_0044"></a>
<h1 class="topictitle1">Elastic Volume Service (EVS)</h1>
<h1 class="topictitle1">Elastic Volume Service</h1>
<div id="body0000001487281736"></div>
<div>
<ul class="ullinks">

159
docs/cce/umn/cce_10_0047.html
View File

File diff suppressed because it is too large Load Diff

75
docs/cce/umn/cce_10_0048.html
View File

File diff suppressed because it is too large Load Diff

149
docs/cce/umn/cce_10_0054.html
View File

File diff suppressed because it is too large Load Diff

38
docs/cce/umn/cce_10_0059.html
View File

@ -6,29 +6,29 @@
<p id="cce_10_0059__p1463183603211">Network policies are classified into the following types:</p>
<ul id="cce_10_0059__ul13161939133212"><li id="cce_10_0059__li18351124913218"><strong id="cce_10_0059__b6606312280">namespaceSelector</strong>: selects particular namespaces for which all pods should be allowed as ingress sources or egress destinations.</li><li id="cce_10_0059__li5998840163217"><strong id="cce_10_0059__b36551310112810">podSelector</strong>: selects particular pods in the same namespace as the network policy which should be allowed as ingress sources or egress destinations.</li><li id="cce_10_0059__li08641649183212"><strong id="cce_10_0059__b116215248286">ipBlock</strong>: selects particular IP blocks to allow as ingress sources or egress destinations. (Only egress rules support IP blocks.)</li></ul>
<div class="section" id="cce_10_0059__section332285584912"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0059__ul178821748131512"><li id="cce_10_0059__li1388224818153">Only clusters that use the tunnel network model support network policies. Network policies are classified into the following types:<ul id="cce_10_0059__ul7256209500"><li id="cce_10_0059__li1392310594496">Ingress: All versions support this type.</li><li id="cce_10_0059__en-us_topic_0000001199501178_li570615420397">Egress: Only the following OSs and cluster versions support egress rules.
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0059__table12813218163117" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0059__row11813218183120"><th align="left" class="cellrowborder" valign="top" width="17.03%" id="mcps1.3.5.2.1.1.2.1.1.4.1.1"><p id="cce_10_0059__p18132189316">OS</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0059__table12813218163117" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0059__row11813218183120"><th align="left" class="cellrowborder" valign="top" width="14.000000000000002%" id="mcps1.3.5.2.1.1.2.1.1.4.1.1"><p id="cce_10_0059__p18132189316">OS</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="18.59%" id="mcps1.3.5.2.1.1.2.1.1.4.1.2"><p id="cce_10_0059__p294822455516">Cluster Version</p>
<th align="left" class="cellrowborder" valign="top" width="22%" id="mcps1.3.5.2.1.1.2.1.1.4.1.2"><p id="cce_10_0059__p294822455516">Cluster Version</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="64.38000000000001%" id="mcps1.3.5.2.1.1.2.1.1.4.1.3"><p id="cce_10_0059__p1581381817312">Verified Kernel Version</p>
<th align="left" class="cellrowborder" valign="top" width="64%" id="mcps1.3.5.2.1.1.2.1.1.4.1.3"><p id="cce_10_0059__p1581381817312">Verified Kernel Version</p>
</th>
</tr>
</thead>
<tbody><tr id="cce_10_0059__row18814118153114"><td class="cellrowborder" valign="top" width="17.03%" headers="mcps1.3.5.2.1.1.2.1.1.4.1.1 "><p id="cce_10_0059__p481431810315">EulerOS 2.5</p>
<tbody><tr id="cce_10_0059__row18814118153114"><td class="cellrowborder" valign="top" width="14.000000000000002%" headers="mcps1.3.5.2.1.1.2.1.1.4.1.1 "><p id="cce_10_0059__p481431810315">EulerOS 2.5</p>
</td>
<td class="cellrowborder" valign="top" width="18.59%" headers="mcps1.3.5.2.1.1.2.1.1.4.1.2 "><p id="cce_10_0059__p209546245557">v1.23 or later</p>
<td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.5.2.1.1.2.1.1.4.1.2 "><p id="cce_10_0059__p209546245557">v1.23 or later</p>
</td>
<td class="cellrowborder" valign="top" width="64.38000000000001%" headers="mcps1.3.5.2.1.1.2.1.1.4.1.3 "><p id="cce_10_0059__p188141518133118">3.10.0-862.14.1.5.h591.eulerosv2r7.x86_64</p>
<td class="cellrowborder" valign="top" width="64%" headers="mcps1.3.5.2.1.1.2.1.1.4.1.3 "><p id="cce_10_0059__p188141518133118">3.10.0-862.14.1.5.h591.eulerosv2r7.x86_64</p>
<p id="cce_10_0059__p123044913199">3.10.0-862.14.1.5.h687.eulerosv2r7.x86_64</p>
</td>
</tr>
<tr id="cce_10_0059__row115473572295"><td class="cellrowborder" valign="top" width="17.03%" headers="mcps1.3.5.2.1.1.2.1.1.4.1.1 "><p id="cce_10_0059__p1181481843113">EulerOS 2.9</p>
<tr id="cce_10_0059__row115473572295"><td class="cellrowborder" valign="top" width="14.000000000000002%" headers="mcps1.3.5.2.1.1.2.1.1.4.1.1 "><p id="cce_10_0059__p1181481843113">EulerOS 2.9</p>
</td>
<td class="cellrowborder" valign="top" width="18.59%" headers="mcps1.3.5.2.1.1.2.1.1.4.1.2 "><p id="cce_10_0059__p3954224155512">v1.23 or later</p>
<td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.5.2.1.1.2.1.1.4.1.2 "><p id="cce_10_0059__p3954224155512">v1.23 or later</p>
</td>
<td class="cellrowborder" valign="top" width="64.38000000000001%" headers="mcps1.3.5.2.1.1.2.1.1.4.1.3 "><p id="cce_10_0059__p181413185315">4.18.0-147.5.1.6.h541.eulerosv2r9.x86_64</p>
<td class="cellrowborder" valign="top" width="64%" headers="mcps1.3.5.2.1.1.2.1.1.4.1.3 "><p id="cce_10_0059__p181413185315">4.18.0-147.5.1.6.h541.eulerosv2r9.x86_64</p>
<p id="cce_10_0059__p1589920212208">4.18.0-147.5.1.6.h766.eulerosv2r9.x86_64</p>
<p id="cce_10_0059__p175382488373">4.18.0-147.5.1.6.h998.eulerosv2r9.x86_64</p>
<p id="cce_10_0059__p52321801171">4.18.0-147.5.1.6.h998.eulerosv2r9.x86_64</p>
</td>
</tr>
</tbody>
@ -55,7 +55,7 @@ spec:
- protocol: TCP
port: 6379</pre>
<p id="cce_10_0059__en-us_topic_0249851123_p88888434711">The following figure shows how podSelector works.</p>
<div class="fignone" id="cce_10_0059__en-us_topic_0249851123_fig139410543444"><span class="figcap"><b>Figure 1 </b>podSelector</span><br><span><img id="cce_10_0059__en-us_topic_0249851123_image185021946194414" src="en-us_image_0000001695896529.png"></span></div>
<div class="fignone" id="cce_10_0059__en-us_topic_0249851123_fig139410543444"><span class="figcap"><b>Figure 1 </b>podSelector</span><br><span><img id="cce_10_0059__en-us_topic_0249851123_image185021946194414" src="en-us_image_0000001750950232.png"></span></div>
</li></ul>
<ul id="cce_10_0059__en-us_topic_0249851123_ul68309714213"><li id="cce_10_0059__en-us_topic_0249851123_li1283027192120"><strong id="cce_10_0059__en-us_topic_0249851123_b184891164227">Using namespaceSelector to specify the access scope</strong><pre class="screen" id="cce_10_0059__en-us_topic_0249851123_screen18399134874818">apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
@ -74,11 +74,11 @@ spec:
- protocol: TCP
port: 6379</pre>
<p id="cce_10_0059__en-us_topic_0249851123_p3874718155019">The following figure shows how namespaceSelector works.</p>
<div class="fignone" id="cce_10_0059__en-us_topic_0249851123_fig127351855617"><span class="figcap"><b>Figure 2 </b>namespaceSelector</span><br><span><img id="cce_10_0059__en-us_topic_0249851123_image141441335560" src="en-us_image_0000001695737257.png"></span></div>
<div class="fignone" id="cce_10_0059__en-us_topic_0249851123_fig127351855617"><span class="figcap"><b>Figure 2 </b>namespaceSelector</span><br><span><img id="cce_10_0059__en-us_topic_0249851123_image141441335560" src="en-us_image_0000001750791324.png"></span></div>
</li></ul>
</div>
<div class="section" id="cce_10_0059__section20486817707"><h4 class="sectiontitle">Using Egress Rules</h4><p id="cce_10_0059__en-us_topic_0249851123_p1311606618">Egress supports not only podSelector and namespaceSelector, but also ipBlock.</p>
<div class="note" id="cce_10_0059__en-us_topic_0249851123_note16478276101"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0059__en-us_topic_0249851123_p1547814741018">Only clusters of version 1.23 or later support egress rules. Currently, nodes running EulerOS 2.5, EulerOS 2.9 are supported.</p>
<div class="note" id="cce_10_0059__en-us_topic_0249851123_note16478276101"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0059__en-us_topic_0249851123_p1547814741018">Only clusters of version 1.23 or later support Egress rules. Only nodes running EulerOS 2.5 or EulerOS 2.9 are supported.</p>
</div></div>
<pre class="screen" id="cce_10_0059__en-us_topic_0249851123_screen14581393131">apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
@ -98,7 +98,7 @@ spec:
except:
- 172.16.0.40/32 # This CIDR block cannot be accessed. This value must fall within the range specified by <strong id="cce_10_0059__b52842121410">cidr</strong>.</pre>
<p id="cce_10_0059__en-us_topic_0249851123_p3245846202818">The following figure shows how ipBlock works.</p>
<div class="fignone" id="cce_10_0059__en-us_topic_0249851123_fig15678132552812"><span class="figcap"><b>Figure 3 </b>ipBlock</span><br><span><img id="cce_10_0059__en-us_topic_0249851123_image6270134419182" src="en-us_image_0000001647576864.png"></span></div>
<div class="fignone" id="cce_10_0059__en-us_topic_0249851123_fig15678132552812"><span class="figcap"><b>Figure 3 </b>ipBlock</span><br><span><img id="cce_10_0059__en-us_topic_0249851123_image6270134419182" src="en-us_image_0000001797910037.png"></span></div>
<p id="cce_10_0059__en-us_topic_0249851123_p1260313810298">You can define ingress and egress in the same rule.</p>
<pre class="screen" id="cce_10_0059__en-us_topic_0249851123_screen235835922918">apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
@ -126,10 +126,10 @@ spec:
matchLabels:
role: web</pre>
<p id="cce_10_0059__en-us_topic_0249851123_p17239137193116">The following figure shows how to use ingress and egress together.</p>
<div class="fignone" id="cce_10_0059__en-us_topic_0249851123_fig14112102353618"><span class="figcap"><b>Figure 4 </b>Using both ingress and egress</span><br><span><img id="cce_10_0059__en-us_topic_0249851123_image103563915919" src="en-us_image_0000001695896533.png"></span></div>
<div class="fignone" id="cce_10_0059__en-us_topic_0249851123_fig14112102353618"><span class="figcap"><b>Figure 4 </b>Using both ingress and egress</span><br><span><img id="cce_10_0059__en-us_topic_0249851123_image103563915919" src="en-us_image_0000001797871009.png"></span></div>
</div>
<div class="section" id="cce_10_0059__section349662212313"><h4 class="sectiontitle">Creating a Network Policy on the Console</h4><ol id="cce_10_0059__ol10753729162012"><li id="cce_10_0059__li67621546123813"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0059__li275310297205"><span>Choose <strong id="cce_10_0059__b1684093473514">Networking</strong> in the navigation pane, click the <span class="uicontrol" id="cce_10_0059__uicontrol8840143418354"><b>Network Policies</b></span> tab, and click <strong id="cce_10_0059__b1684043412358">Create Network Policy</strong> in the upper right corner.</span><p><ul id="cce_10_0059__ul1275420367216"><li id="cce_10_0059__li207540368218"><strong id="cce_10_0059__b5858127617589">Policy Name</strong>: Specify a network policy name.</li><li id="cce_10_0059__li86551950162110"><strong id="cce_10_0059__b2485142065319">Namespace</strong>: Select a namespace in which the network policy is applied.</li><li id="cce_10_0059__li1811145118419"><strong id="cce_10_0059__b1082493183618">Selector</strong>: Enter a label, select the pod to be associated, and click <strong id="cce_10_0059__b39962039143613">Confirm</strong>. You can also click <span class="uicontrol" id="cce_10_0059__uicontrol127315410439"><b>Reference Workload Label</b></span> to reference the label of an existing workload.</li><li id="cce_10_0059__li20288331248"><strong id="cce_10_0059__b288315258371">Inbound Rule</strong>: Click <span><img id="cce_10_0059__image297081312440" src="en-us_image_0000001647417596.png"></span> to add an inbound rule. For details about parameter settings, see <a href="#cce_10_0059__table166419994515">Table 1</a>.<p id="cce_10_0059__p13464141094517"></p>
<p id="cce_10_0059__p1251071818275"><span><img id="cce_10_0059__image3789195442716" src="en-us_image_0000001647417588.png"></span></p>
<div class="section" id="cce_10_0059__section349662212313"><h4 class="sectiontitle">Creating a Network Policy on the Console</h4><ol id="cce_10_0059__ol10753729162012"><li id="cce_10_0059__li67621546123813"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0059__li275310297205"><span>Choose <strong id="cce_10_0059__b1684093473514"><span id="cce_10_0059__text144061727132711">Policies</span></strong> in the navigation pane, click the <span class="uicontrol" id="cce_10_0059__uicontrol8840143418354"><b>Network Policies</b></span> tab, and click <strong id="cce_10_0059__b1684043412358">Create Network Policy</strong> in the upper right corner.</span><p><ul id="cce_10_0059__ul1275420367216"><li id="cce_10_0059__li207540368218"><strong id="cce_10_0059__b5858127617589">Policy Name</strong>: Specify a network policy name.</li><li id="cce_10_0059__li86551950162110"><strong id="cce_10_0059__b2485142065319">Namespace</strong>: Select a namespace in which the network policy is applied.</li><li id="cce_10_0059__li1811145118419"><strong id="cce_10_0059__b1082493183618">Selector</strong>: Enter a label, select the pod to be associated, and click <strong id="cce_10_0059__b39962039143613">Add</strong>. You can also click <span class="uicontrol" id="cce_10_0059__uicontrol127315410439"><b>Reference Workload Label</b></span> to reference the label of an existing workload.</li><li id="cce_10_0059__li20288331248"><strong id="cce_10_0059__b288315258371">Inbound Rule</strong>: Click <span><img id="cce_10_0059__image297081312440" src="en-us_image_0000001750950236.png"></span> to add an inbound rule. For details about parameter settings, see <a href="#cce_10_0059__table166419994515">Table 1</a>.<p id="cce_10_0059__p13464141094517"></p>
<p id="cce_10_0059__p1251071818275"><span><img id="cce_10_0059__image3789195442716" src="en-us_image_0000001750791308.png"></span></p>
<div class="p" id="cce_10_0059__p16644759445">
<div class="tablenoborder"><a name="cce_10_0059__table166419994515"></a><a name="table166419994515"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0059__table166419994515" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Adding an inbound rule</caption><thead align="left"><tr id="cce_10_0059__row186401397458"><th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.8.2.2.2.1.4.6.1.2.3.1.1"><p id="cce_10_0059__p163919913452">Parameter</p>
</th>
@ -149,14 +149,14 @@ spec:
</tr>
<tr id="cce_10_0059__row1564115912452"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.8.2.2.2.1.4.6.1.2.3.1.1 "><p id="cce_10_0059__p8640792450">Source Pod Label</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.8.2.2.2.1.4.6.1.2.3.1.2 "><p id="cce_10_0059__p590912241576">Allow accessing the pods with this label. If this parameter is not specified, all pods in the namespace can be accessed.</p>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.8.2.2.2.1.4.6.1.2.3.1.2 "><p id="cce_10_0059__p590912241576">Allow accesses from the pods with this label. If this parameter is not specified, all pods in the namespace can access the port.</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</li><li id="cce_10_0059__li208969565264"><strong id="cce_10_0059__b13933104315451">Outbound Rule</strong>: Click <span><img id="cce_10_0059__image190375162714" src="en-us_image_0000001695737253.png"></span> to add an outbound rule. For details about parameter settings, see <a href="#cce_10_0059__table166419994515">Table 1</a>.<p id="cce_10_0059__p475815292283"><span><img id="cce_10_0059__image10587182118298" src="en-us_image_0000001647417600.png"></span></p>
</li><li id="cce_10_0059__li208969565264"><strong id="cce_10_0059__b13933104315451">Outbound Rule</strong>: Click <span><img id="cce_10_0059__image190375162714" src="en-us_image_0000001797871005.png"></span> to add an outbound rule. For details about parameter settings, see <a href="#cce_10_0059__table166419994515">Table 1</a>.<p id="cce_10_0059__p475815292283"><span><img id="cce_10_0059__image10587182118298" src="en-us_image_0000001797871017.png"></span></p>
<div class="p" id="cce_10_0059__p1052121812515">
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0059__table940510264284" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Adding an outbound rule</caption><thead align="left"><tr id="cce_10_0059__row15405182632814"><th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.8.2.2.2.1.5.5.1.2.3.1.1"><p id="cce_10_0059__p34051926152811">Parameter</p>
</th>

13
docs/cce/umn/cce_10_0063.html
View File

@ -4,18 +4,15 @@
<div id="body8662426"><div class="section" id="cce_10_0063__section127666327248"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0063__p192873216229">After a node scaling policy is created, you can delete, edit, disable, enable, or clone the policy.</p>
</div>
<div class="section" id="cce_10_0063__section102878407207"><h4 class="sectiontitle">Viewing a Node Scaling Policy</h4><p id="cce_10_0063__p713741135215">You can view the associated node pool, rules, and scaling history of a node scaling policy and rectify faults according to the error information displayed.</p>
<ol id="cce_10_0063__ol17409123885219"><li id="cce_10_0063__li148293318248"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0063__li3967519744"><span>Choose <strong id="cce_10_0063__b75474128512">Node Scaling</strong> in the navigation pane and click <span><img id="cce_10_0063__image1254712122518" src="en-us_image_0000001695896485.png"></span> in front of the policy to be viewed.</span></li><li id="cce_10_0063__li641003813527"><span>In the expanded area, the <span class="uicontrol" id="cce_10_0063__uicontrol864413924614"><b>Associated Node Pools</b></span>, <span class="uicontrol" id="cce_10_0063__uicontrol1164419910465"><b>Rules</b></span>, and <span class="uicontrol" id="cce_10_0063__uicontrol1964516974613"><b>Scaling History</b></span> tab pages are displayed. If the policy is abnormal, locate and rectify the fault based on the error information.</span><p><div class="note" id="cce_10_0063__note13404926203311"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0063__p268214718213">You can also disable or enable auto scaling on the <strong id="cce_10_0063__b57750163232">Node Pools</strong> page.</p>
<ol type="a" id="cce_10_0063__ol15169162582120"><li id="cce_10_0063__li13169425162117">Log in to the CCE console and click the cluster name to access the cluster console.</li><li id="cce_10_0063__li716942518219">In the navigation pane, choose <strong id="cce_10_0063__b189612560310">Nodes</strong> and switch to the <strong id="cce_10_0063__b19818721244">Node Pools</strong> tab.</li><li id="cce_10_0063__li498811231504">Locate the row containing the target node pool and click <span class="uicontrol" id="cce_10_0063__uicontrol95019393011"><b>Update</b></span> in the <strong id="cce_10_0063__b1496428185012">Operation</strong> column. In the window that slides out from the right, enable <strong id="cce_10_0063__b66112515390">Auto Scaling</strong>, and configure <strong id="cce_10_0063__b754915540391">Max. Nodes</strong>, <strong id="cce_10_0063__b1444816563399">Min. Nodes</strong>, and <strong id="cce_10_0063__b1724785813397">Cooldown Period</strong>.</li></ol>
</div></div>
</p></li></ol>
<ol id="cce_10_0063__ol17409123885219"><li id="cce_10_0063__li148293318248"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0063__li757116188514"><span>In the navigation pane, choose <span class="uicontrol" id="cce_10_0063__uicontrol885043603616"><b>Nodes</b></span>.On the page displayed, click the <strong id="cce_10_0063__b1785019363361">Node Pools</strong> tab and then the name of the node pool for which an auto scaling policy has been created to view the node pool details.</span></li><li id="cce_10_0063__li391162210375"><span>On the node pool details page, click the <strong id="cce_10_0063__b182822310377">Auto Scaling</strong> tab to view the auto scaling configuration and scaling records.</span></li></ol>
</div>
<div class="section" id="cce_10_0063__section128584032017"><h4 class="sectiontitle">Deleting a Node Scaling Policy</h4><ol id="cce_10_0063__ol14644105712488"><li id="cce_10_0063__li41181041153517"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0063__li21181041113517"><span>Choose <strong id="cce_10_0063__b12846115045411">Node Scaling</strong> in the navigation pane and choose <strong id="cce_10_0063__b1011425314546">More</strong> &gt; <strong id="cce_10_0063__b264025517541">Delete</strong> next to the policy to be deleted.</span></li><li id="cce_10_0063__li19809141991015"><span>In the <span class="wintitle" id="cce_10_0063__wintitle195460432178"><b>Delete Node Scaling Policy</b></span> dialog box displayed, confirm whether to delete the policy.</span></li><li id="cce_10_0063__li1340513385528"><span>Click <span class="uicontrol" id="cce_10_0063__uicontrol12723105481711"><b>Yes</b></span> to delete the policy.</span></li></ol>
<div class="section" id="cce_10_0063__section128584032017"><h4 class="sectiontitle">Deleting a Node Scaling Policy</h4><ol id="cce_10_0063__ol14644105712488"><li id="cce_10_0063__li41181041153517"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0063__li21181041113517"><span>In the navigation pane, choose <strong id="cce_10_0063__b1214315541372"><span id="cce_10_0063__text82292962415">Policies</span></strong>. On the page displayed, click the <strong id="cce_10_0063__b6742397389">Node Scaling</strong> tab, locate the row containing the target policy and choose <strong id="cce_10_0063__b1770171519392">More</strong> &gt; <strong id="cce_10_0063__b88264165396">Delete</strong> in the <strong id="cce_10_0063__b7342193564112">Operation</strong> column.</span></li><li id="cce_10_0063__li19809141991015"><span>In the <span class="wintitle" id="cce_10_0063__wintitle195460432178"><b>Delete Node Scaling Policy</b></span> dialog box displayed, confirm whether to delete the policy.</span></li><li id="cce_10_0063__li1340513385528"><span>Click <span class="uicontrol" id="cce_10_0063__uicontrol12723105481711"><b>Yes</b></span> to delete the policy.</span></li></ol>
</div>
<div class="section" id="cce_10_0063__section5652756162214"><h4 class="sectiontitle">Editing a Node Scaling Policy</h4><ol id="cce_10_0063__ol067875612225"><li id="cce_10_0063__li1148617913919"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0063__li19486498394"><span>Choose <strong id="cce_10_0063__b154762701819">Node Scaling</strong> in the navigation pane and click <span class="uicontrol" id="cce_10_0063__uicontrol14476675189"><b>Edit</b></span> in the <strong id="cce_10_0063__b647707161811">Operation</strong> column of the policy to be edited.</span></li><li id="cce_10_0063__li56781856152211"><span>On the <span class="uicontrol" id="cce_10_0063__uicontrol7933134119486"><b>Edit Node Scaling Policy</b></span> page displayed, modify policy parameter values listed in <a href="cce_10_0209.html#cce_10_0209__table18763092201">Table 1</a>.</span></li><li id="cce_10_0063__li86781756112220"><span>After the configuration is complete, click <span class="uicontrol" id="cce_10_0063__uicontrol07463587480"><b>OK</b></span>.</span></li></ol>
<div class="section" id="cce_10_0063__section5652756162214"><h4 class="sectiontitle">Editing a Node Scaling Policy</h4><ol id="cce_10_0063__ol067875612225"><li id="cce_10_0063__li1148617913919"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0063__li19486498394"><span>In the navigation pane, choose <strong id="cce_10_0063__b19317105710390"><span id="cce_10_0063__text105014172246">Policies</span></strong>. On the page displayed, click the <strong id="cce_10_0063__b5317185793910">Node Scaling</strong> tab, locate the row containing the target policy and click <strong id="cce_10_0063__b822154212401">Edit</strong> in the <strong id="cce_10_0063__b152854419415">Operation</strong> column.</span></li><li id="cce_10_0063__li56781856152211"><span>On the <span class="uicontrol" id="cce_10_0063__uicontrol7933134119486"><b>Edit Node Scaling Policy</b></span> page displayed, configure policy parameters listed in <a href="cce_10_0209.html#cce_10_0209__table18763092201">Table 2</a>.</span></li><li id="cce_10_0063__li86781756112220"><span>After the configuration is complete, click <span class="uicontrol" id="cce_10_0063__uicontrol07463587480"><b>OK</b></span>.</span></li></ol>
</div>
<div class="section" id="cce_10_0063__section367810565223"><h4 class="sectiontitle">Cloning a Node Scaling Policy</h4><ol id="cce_10_0063__ol1283103252519"><li id="cce_10_0063__li20680159143911"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0063__li1068085914390"><span>Choose <strong id="cce_10_0063__b889784805914">Node Scaling</strong> in the navigation pane and choose <strong id="cce_10_0063__b889764816594">More</strong> &gt; <strong id="cce_10_0063__b1589719489596">Clone</strong> next to the policy to be cloned.</span></li><li id="cce_10_0063__li128363212514"><span>On the <span class="uicontrol" id="cce_10_0063__uicontrol162071440144911"><b>Clone Node Scaling Policy</b></span> page displayed, certain parameters have been cloned. Add or modify other policy parameters based on service requirements.</span></li><li id="cce_10_0063__li383732172512"><span>Click <strong id="cce_10_0063__b76092016183">OK</strong>.</span></li></ol>
<div class="section" id="cce_10_0063__section367810565223"><h4 class="sectiontitle">Cloning a Node Scaling Policy</h4><ol id="cce_10_0063__ol1283103252519"><li id="cce_10_0063__li20680159143911"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0063__li1068085914390"><span>In the navigation pane, choose <strong id="cce_10_0063__b182079494212"><span id="cce_10_0063__text15369102114247">Policies</span></strong>. On the page displayed, click the <strong id="cce_10_0063__b1620711418426">Node Scaling</strong> tab, locate the row containing the target policy and choose <strong id="cce_10_0063__b1020734124213">More</strong> &gt; <strong id="cce_10_0063__b620724164218">Clone</strong> in the <strong id="cce_10_0063__b82081045425">Operation</strong> column.</span></li><li id="cce_10_0063__li128363212514"><span>On the <span class="uicontrol" id="cce_10_0063__uicontrol162071440144911"><b>Clone Node Scaling Policy</b></span> page displayed, certain parameters have been cloned. Add or modify other policy parameters based on service requirements.</span></li><li id="cce_10_0063__li383732172512"><span>Click <strong id="cce_10_0063__b76092016183">OK</strong>.</span></li></ol>
</div>
<div class="section" id="cce_10_0063__section4771832152513"><h4 class="sectiontitle">Enabling or Disabling a Node Scaling Policy</h4><ol id="cce_10_0063__ol0843321258"><li id="cce_10_0063__li1221435414019"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0063__li4214105494011"><span>Choose <strong id="cce_10_0063__b13778122416181">Node Scaling</strong> in the navigation pane and click <strong id="cce_10_0063__b0778424161820">Disable</strong> in the <strong id="cce_10_0063__b1977852441812">Operation</strong> column of the policy to be disabled. If the policy is in the disabled state, click <span class="uicontrol" id="cce_10_0063__uicontrol177902431813"><b>Enable</b></span> in the <strong id="cce_10_0063__b47795246181">Operation</strong> column of the policy.</span></li><li id="cce_10_0063__li78473252510"><span>In the dialog box displayed, confirm whether to disable or enable the node policy.</span></li></ol>
<div class="section" id="cce_10_0063__section4771832152513"><h4 class="sectiontitle">Enabling or Disabling a Node Scaling Policy</h4><ol id="cce_10_0063__ol0843321258"><li id="cce_10_0063__li1221435414019"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0063__li4214105494011"><span>In the navigation pane, choose <strong id="cce_10_0063__b4140849438"><span id="cce_10_0063__text1726717273247">Policies</span></strong>. On the page displayed, click the <strong id="cce_10_0063__b1814110454317">Node Scaling</strong> tab, locate the row containing the target policy click <strong id="cce_10_0063__b0778424161820">Disable</strong> in the <strong id="cce_10_0063__b1977852441812">Operation</strong> column. If the policy is in the disabled state, click <span class="uicontrol" id="cce_10_0063__uicontrol177902431813"><b>Enable</b></span> in the <strong id="cce_10_0063__b47795246181">Operation</strong> column.</span></li><li id="cce_10_0063__li78473252510"><span>In the dialog box displayed, confirm whether to disable or enable the node policy.</span></li></ol>
</div>
</div>
<div>

4
docs/cce/umn/cce_10_0064.html
View File

@ -16,11 +16,13 @@
</li>
<li class="ulchildlink"><strong><a href="cce_10_0205.html">Kubernetes Metrics Server</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0240.html">CCE Advanced HPA</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0141.html">CCE AI Suite (NVIDIA GPU)</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0193.html">Volcano Scheduler</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0127.html">CCE Container Storage (FlexVolume)</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0127.html">CCE Container Storage (FlexVolume, Discarded)</a></strong><br>
</li>
</ul>
</div>

201
docs/cce/umn/cce_10_0066.html
View File

File diff suppressed because it is too large Load Diff

2
docs/cce/umn/cce_10_0068.html
View File

@ -12,7 +12,7 @@
</li>
<li class="ulchildlink"><strong><a href="cce_bulletin_0026.html">Kubernetes 1.21 Release Notes</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_whsnew_0010.html">Kubernetes 1.19 EOM Release Notes</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_whsnew_0010.html">Kubernetes 1.19 (EOM) Release Notes</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_whsnew_0007.html">Kubernetes 1.17 (EOM) Release Notes</a></strong><br>
</li>

10
docs/cce/umn/cce_10_0081.html
View File

@ -8,13 +8,13 @@
<p id="cce_10_0081__p19802113820588">This section describes how node pools work in CCE and how to create and manage node pools.</p>
</div>
<div class="section" id="cce_10_0081__section1486732122217"><h4 class="sectiontitle">Node Pool Architecture</h4><p id="cce_10_0081__p2480134412214">Generally, all nodes in a node pool have the following same attributes:</p>
<ul id="cce_10_0081__ul134808449226"><li id="cce_10_0081__li1848004422220">Node OS</li><li id="cce_10_0081__li890631614331">Node specifications</li><li id="cce_10_0081__li730814322334">Node login mode</li><li id="cce_10_0081__li3978937183319">Node container runtime</li><li id="cce_10_0081__li20480184419225">Startup parameters of Kubernetes components on a node</li><li id="cce_10_0081__li17480104411227">User-defined startup script of a node</li><li id="cce_10_0081__li84806446229"><strong id="cce_10_0081__b452816349419">Kubernetes Labels</strong> and <strong id="cce_10_0081__b65284345410">Taints</strong></li></ul>
<ul id="cce_10_0081__ul134808449226"><li id="cce_10_0081__li1848004422220">Node OS</li><li id="cce_10_0081__li890631614331">Node flavor</li><li id="cce_10_0081__li730814322334">Node login mode</li><li id="cce_10_0081__li3978937183319">Node container runtime</li><li id="cce_10_0081__li20480184419225">Startup parameters of Kubernetes components on a node</li><li id="cce_10_0081__li17480104411227">User-defined startup script of a node</li><li id="cce_10_0081__li84806446229"><strong id="cce_10_0081__b452816349419">Kubernetes Labels</strong> and <strong id="cce_10_0081__b65284345410">Taints</strong></li></ul>
<p id="cce_10_0081__p1048019444223">CCE provides the following extended attributes for node pools:</p>
<ul id="cce_10_0081__ul84801544162219"><li id="cce_10_0081__li1480184410229">Node pool OS</li><li id="cce_10_0081__li114801944112213">Maximum number of pods on each node in a node pool</li></ul>
</div>
<div class="section" id="cce_10_0081__section16928123042115"><a name="cce_10_0081__section16928123042115"></a><a name="section16928123042115"></a><h4 class="sectiontitle">Description of <span class="keyword" id="cce_10_0081__keyword729863519811">DefaultPool</span></h4><p id="cce_10_0081__p5444184415215"><span class="keyword" id="cce_10_0081__keyword799943811813">DefaultPool</span> is not a real node pool. It only <strong id="cce_10_0081__b1896884414412">classifies</strong> nodes that are not in the user-created node pools. These nodes are directly created on the console or by calling APIs. DefaultPool does not support any user-created node pool functions, including scaling and parameter configuration. DefaultPool cannot be edited, deleted, expanded, or auto scaled, and nodes in it cannot be migrated.</p>
</div>
<div class="section" id="cce_10_0081__section32131316256"><h4 class="sectiontitle">Application Scenarios</h4><p id="cce_10_0081__p1945803011253">When a large-scale cluster is required, you are advised to use node pools to manage nodes.</p>
<div class="section" id="cce_10_0081__section32131316256"><h4 class="sectiontitle">Applicable Scenarios</h4><p id="cce_10_0081__p1945803011253">When a large-scale cluster is required, you are advised to use node pools to manage nodes.</p>
<p id="cce_10_0081__p1491578182512">The following table describes multiple scenarios of large-scale cluster management and the functions of node pools in each scenario.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0081__table1736317479258" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Using node pools for different management scenarios</caption><thead align="left"><tr id="cce_10_0081__row336414719256"><th align="left" class="cellrowborder" valign="top" width="39.32%" id="mcps1.3.4.4.2.3.1.1"><p id="cce_10_0081__p5364134792518">Scenario</p>
@ -69,7 +69,7 @@
</td>
<td class="cellrowborder" valign="top" width="39.603960396039604%" headers="mcps1.3.5.2.1.4.1.2 "><p id="cce_10_0081__p11579152892711">After auto scaling is enabled, nodes will be automatically created or deleted in the node pool based on the cluster loads.</p>
</td>
<td class="cellrowborder" valign="top" width="38.453845384538454%" headers="mcps1.3.5.2.1.4.1.3 "><p id="cce_10_0081__p105796284275">You are advised not to store important data on nodes in a node pool because after auto scaling, data cannot be restored as nodes may be deleted.</p>
<td class="cellrowborder" valign="top" width="38.453845384538454%" headers="mcps1.3.5.2.1.4.1.3 "><p id="cce_10_0081__p105796284275">Do not store important data on nodes in a node pool because the nodes may be deleted after scale-in. Data on the deleted nodes cannot be restored.</p>
</td>
</tr>
<tr id="cce_10_0081__row5843131718272"><td class="cellrowborder" valign="top" width="21.942194219421943%" headers="mcps1.3.5.2.1.4.1.1 "><p id="cce_10_0081__p18579132802720">Enabling auto scaling for a node pool</p>
@ -119,12 +119,12 @@
</div>
</div>
<div class="section" id="cce_10_0081__section12603142443319"><h4 class="sectiontitle"><span class="keyword" id="cce_10_0081__keyword134411635193118">Deploying a Workload in a Specified Node Pool</span></h4><p id="cce_10_0081__p153911712353">When creating a workload, you can constrain pods to run in a specified node pool.</p>
<p id="cce_10_0081__p554031713358">For example, on the CCE console, you can set the affinity between the workload and the node on the <strong id="cce_10_0081__b65991804713">Scheduling Policies</strong> tab page on the workload details page to forcibly deploy the workload to a specific node pool. In this way, the workload runs only on nodes in the node pool. To better control where the workload is to be scheduled, you can use affinity or anti-affinity policies between workloads and nodes described in <a href="cce_10_0232.html">Scheduling Policy (Affinity/Anti-affinity)</a>.</p>
<p id="cce_10_0081__p554031713358">For example, on the CCE console, you can set the affinity between the workload and the node on the <strong id="cce_10_0081__b65991804713">Scheduling Policies</strong> tab page on the workload details page to forcibly deploy the workload to a specific node pool. In this way, the workload runs only on nodes in the node pool. To better control where the workload is to be scheduled, you can use affinity or anti-affinity policies between workloads and nodes described in <a href="cce_10_0232.html">Scheduling Policies (Affinity/Anti-affinity)</a>.</p>
<p id="cce_10_0081__p614655184910">For example, you can use container's resource request as a nodeSelector so that workloads will run only on the nodes that meet the resource request.</p>
<p id="cce_10_0081__p1854041717353">If the workload definition file defines a container that requires four CPUs, the scheduler will not choose the nodes with two CPUs to run workloads.</p>
</div>
<div class="section" id="cce_10_0081__section17716744163316"><h4 class="sectiontitle">Related Operations</h4><p id="cce_10_0081__p12284195854916">You can log in to the CCE console and refer to the following sections to perform operations on node pools:</p>
<ul id="cce_10_0081__ul713912219920"><li id="cce_10_0081__li168801331326"><a href="cce_10_0012.html">Creating a Node Pool</a></li><li id="cce_10_0081__li1688010311326"><a href="cce_10_0222.html">Managing a Node Pool</a></li><li id="cce_10_0081__li1720114577918"><a href="cce_10_0047.html">Creating a Deployment</a></li><li id="cce_10_0081__li1849316127104"><a href="cce_10_0232.html">Scheduling Policy (Affinity/Anti-affinity)</a></li></ul>
<ul id="cce_10_0081__ul713912219920"><li id="cce_10_0081__li168801331326"><a href="cce_10_0012.html">Creating a Node Pool</a></li><li id="cce_10_0081__li1688010311326"><a href="cce_10_0222.html">Managing a Node Pool</a></li><li id="cce_10_0081__li1720114577918"><a href="cce_10_0047.html">Creating a Deployment</a></li><li id="cce_10_0081__li1849316127104"><a href="cce_10_0232.html">Scheduling Policies (Affinity/Anti-affinity)</a></li></ul>
</div>
</div>
<div>

12
docs/cce/umn/cce_10_0083.html
View File

@ -4,8 +4,8 @@
<div id="body1508729244098"><div class="section" id="cce_10_0083__section11873141710246"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0083__p799618243249">After an HPA policy is created, you can update, clone, edit, and delete the policy, as well as edit the YAML file.</p>
</div>
<div class="section" id="cce_10_0083__section14993443181414"><h4 class="sectiontitle">Checking an HPA Policy</h4><p id="cce_10_0083__p713741135215">You can view the rules, status, and events of an HPA policy and handle exceptions based on the error information displayed.</p>
<ol id="cce_10_0083__ol17409123885219"><li id="cce_10_0083__li754610559213"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li4409153817525"><span>In the navigation pane, choose <strong id="cce_10_0083__b9595121512611">Workload Scaling</strong>. On the <span class="uicontrol" id="cce_10_0083__uicontrol124101738135219"><b>HPA Policies</b></span> tab, click <span><img id="cce_10_0083__image1569143785619" src="en-us_image_0000001695737185.png"></span> next to the target HPA policy.</span></li><li id="cce_10_0083__li641003813527"><span>In the expanded area, view the <strong id="cce_10_0083__b3109121911720">Rule</strong> and <strong id="cce_10_0083__b1952313227174">Status</strong> tabs. Click <span class="uicontrol" id="cce_10_0083__uicontrol4974153615019"><b>View Events</b></span> in the <strong id="cce_10_0083__b1620814781718">Operation</strong> column. If the policy malfunctions, locate and rectify the fault based on the error message displayed on the page.</span><p><div class="note" id="cce_10_0083__note13404926203311"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0083__p1793618441931">You can also view the created HPA policy on the workload details page.</p>
<ol type="a" id="cce_10_0083__ol1691347738"><li id="cce_10_0083__li5468556932">Log in to the CCE console and click the cluster name to access the cluster console.</li><li id="cce_10_0083__li87313521749">In the navigation pane, choose <strong id="cce_10_0083__b01748420311">Workloads</strong>. Click the workload name to view its details.</li><li id="cce_10_0083__li1769110474318">On the workload details page, click the <strong id="cce_10_0083__b3716156354">Auto Scaling</strong> tab to view the HPA policies. You can also view the scaling policies you configured in the <strong id="cce_10_0083__b81591132105417">Workload Scaling</strong> page.</li></ol>
<ol id="cce_10_0083__ol17409123885219"><li id="cce_10_0083__li754610559213"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li4409153817525"><span>In the navigation pane, choose <strong id="cce_10_0083__b9595121512611"><span id="cce_10_0083__text67571453104013">Policies</span></strong>. On the page displayed, click the <span class="uicontrol" id="cce_10_0083__uicontrol124101738135219"><b>HPA Policies</b></span> tab and then <span><img id="cce_10_0083__image1569143785619" src="en-us_image_0000001797871061.png"></span> next to the target HPA policy.</span></li><li id="cce_10_0083__li641003813527"><span>In the expanded area, choose <strong id="cce_10_0083__b486014516522">View Events</strong> in the <strong id="cce_10_0083__b77159572522">Operation</strong> column. If the policy malfunctions, locate and rectify the fault based on the error message displayed on the page.</span><p><div class="note" id="cce_10_0083__note13404926203311"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0083__p1793618441931">You can also view the created HPA policy on the workload details page.</p>
<ol type="a" id="cce_10_0083__ol1691347738"><li id="cce_10_0083__li5468556932">Log in to the CCE console and click the cluster name to access the cluster console.</li><li id="cce_10_0083__li87313521749">In the navigation pane, choose <strong id="cce_10_0083__b01748420311">Workloads</strong>. Click the workload name to view its details.</li><li id="cce_10_0083__li1769110474318">On the workload details page, switch to the <strong id="cce_10_0083__b3716156354">Auto Scaling</strong> tab page to view the HPA policies. You can also view the scaling policies you configured on the <strong id="cce_10_0083__b1389131612229"><span id="cce_10_0083__text85771564218">Policies</span></strong> page.</li></ol>
</div></div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0083__table56931825193212" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Event types and names</caption><thead align="left"><tr id="cce_10_0083__row269117254324"><th align="left" class="cellrowborder" valign="top" width="17.531753175317533%" id="mcps1.3.2.3.3.2.2.2.4.1.1"><p id="cce_10_0083__p176911125153211">Event Type</p>
@ -90,12 +90,12 @@
</div>
</p></li></ol>
</div>
<div class="section" id="cce_10_0083__section119901143111420"><h4 class="sectiontitle">Updating an HPA Policy</h4><p id="cce_10_0083__p18160164715245">An HPA policy is used as an example.</p>
<ol id="cce_10_0083__ol14644105712488"><li id="cce_10_0083__li584173114516"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li2619151017014"><span>On the cluster console, choose <strong id="cce_10_0083__b147314501477">Workload Scaling</strong> in the navigation pane. Locate the row that contains the target policy and choose <strong id="cce_10_0083__b1859319500414">More</strong> &gt; <strong id="cce_10_0083__b043275516414">Edit</strong> in the <span class="uicontrol" id="cce_10_0083__uicontrol1275919157101"><b>Operation</b></span> column.</span></li><li id="cce_10_0083__li19809141991015"><span>On the <span class="uicontrol" id="cce_10_0083__uicontrol162451231134212"><b>Edit HPA Policy</b></span> page, configure the parameters as listed in <a href="cce_10_0208.html#cce_10_0208__table8638121213265">Table 1</a>.</span></li><li id="cce_10_0083__li1340513385528"><span>Click <strong id="cce_10_0083__b18186175524217">OK</strong>.</span></li></ol>
<div class="section" id="cce_10_0083__section119901143111420"><h4 class="sectiontitle">Editing an HPA Policy</h4><p id="cce_10_0083__p18160164715245">An HPA policy is used as an example.</p>
<ol id="cce_10_0083__ol14644105712488"><li id="cce_10_0083__li584173114516"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li2619151017014"><span>In the navigation pane, choose <strong id="cce_10_0083__b2313123642418"><span id="cce_10_0083__text15640203664218">Policies</span></strong>. On the page displayed, click the <strong id="cce_10_0083__b10327144132610">HPA Policies</strong> tab. Locate the row containing the target policy and choose <strong id="cce_10_0083__b143141736122411">More</strong> &gt; <strong id="cce_10_0083__b17314136172414">Edit</strong> in the <span class="uicontrol" id="cce_10_0083__uicontrol1231433652419"><b>Operation</b></span> column.</span></li><li id="cce_10_0083__li19809141991015"><span>On the <span class="uicontrol" id="cce_10_0083__uicontrol630212429422"><b>Edit HPA Policy</b></span> page, configure policy parameters listed in <a href="cce_10_0208.html#cce_10_0208__table8638121213265">Table 1</a>.</span></li><li id="cce_10_0083__li1340513385528"><span>Click <strong id="cce_10_0083__b084931111349">OK</strong>.</span></li></ol>
</div>
<div class="section" id="cce_10_0083__section14894314131710"><h4 class="sectiontitle">Editing the YAML File (HPA Policy)</h4><ol id="cce_10_0083__ol836024781710"><li id="cce_10_0083__li4747132218612"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li197478221868"><span>In the navigation pane, choose <strong id="cce_10_0083__b158614271186">Workload Scaling</strong>, locate the row containing the target policy, and click <span class="uicontrol" id="cce_10_0083__uicontrol173601547121714"><b>Edit YAML</b></span> in the <span class="uicontrol" id="cce_10_0083__uicontrol15862927288"><b>Operation</b></span> column.</span></li><li id="cce_10_0083__li3360104719175"><span>In the <span class="uicontrol" id="cce_10_0083__uicontrol19625193112511"><b>Edit YAML</b></span> dialog box displayed, edit or download the YAML file.</span></li></ol>
<div class="section" id="cce_10_0083__section14894314131710"><h4 class="sectiontitle">Editing the YAML File (HPA Policy)</h4><ol id="cce_10_0083__ol836024781710"><li id="cce_10_0083__li4747132218612"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li197478221868"><span>In the navigation pane, choose <strong id="cce_10_0083__b158614271186"><span id="cce_10_0083__text7289154554216">Policies</span></strong>. On the page displayed, click the <strong id="cce_10_0083__b5630485294">HPA Policies</strong> tab. Locate the row containing the target policy and click <span class="uicontrol" id="cce_10_0083__uicontrol173601547121714"><b>Edit YAML</b></span> in the <span class="uicontrol" id="cce_10_0083__uicontrol15862927288"><b>Operation</b></span> column.</span></li><li id="cce_10_0083__li3360104719175"><span>In the dialog box displayed, edit or download the YAML file.</span></li></ol>
</div>
<div class="section" id="cce_10_0083__section13361947161717"><h4 class="sectiontitle">Deleting an HPA Policy</h4><ol id="cce_10_0083__ol86853731815"><li id="cce_10_0083__li15254352473"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li1725419521973"><span>In the navigation pane, choose <strong id="cce_10_0083__b26191366917">Workload Scaling</strong>. Locate the row containing the target policy and choose <span class="uicontrol" id="cce_10_0083__uicontrol156193361795"><b>More</b></span> &gt; <strong id="cce_10_0083__b154116114551">Delete</strong> in the <span class="uicontrol" id="cce_10_0083__uicontrol1462014361391"><b>Operation</b></span> column.</span></li><li id="cce_10_0083__li96803718182"><span>In the dialog box displayed, click <strong id="cce_10_0083__b135291150994">Yes</strong>.</span></li></ol>
<div class="section" id="cce_10_0083__section13361947161717"><h4 class="sectiontitle">Deleting an HPA Policy</h4><ol id="cce_10_0083__ol86853731815"><li id="cce_10_0083__li15254352473"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0083__li1725419521973"><span>In the navigation pane, choose <strong id="cce_10_0083__b26191366917"><span id="cce_10_0083__text198981591435">Policies</span></strong>. Choose <strong id="cce_10_0083__b9845235103217">More</strong> &gt; <strong id="cce_10_0083__b154116114551">Delete</strong> in the <span class="uicontrol" id="cce_10_0083__uicontrol1462014361391"><b>Operation</b></span> column of the target policy.</span></li><li id="cce_10_0083__li96803718182"><span>In the dialog box displayed, click <strong id="cce_10_0083__b135291150994">Yes</strong>.</span></li></ol>
</div>
</div>
<div>

6
docs/cce/umn/cce_10_0094.html
View File

@ -3,14 +3,14 @@
<h1 class="topictitle1">Overview</h1>
<div id="body0000001159453456"><div class="section" id="cce_10_0094__section17868123416122"><h4 class="sectiontitle">Why We Need Ingresses</h4><p id="cce_10_0094__p19813582419">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 large number of HTTP/HTTPS access requests on the application layer, the Service cannot meet the forwarding requirements. Therefore, the Kubernetes cluster provides an HTTP-based access mode, ingress.</p>
<p id="cce_10_0094__p168757241679">An ingress is an independent resource in the Kubernetes cluster and defines rules for forwarding external access traffic. As shown in <a href="#cce_10_0094__fig18155819416">Figure 1</a>, you can customize forwarding rules based on domain names and URLs to implement fine-grained distribution of access traffic.</p>
<div class="fignone" id="cce_10_0094__fig18155819416"><a name="cce_10_0094__fig18155819416"></a><a name="fig18155819416"></a><span class="figcap"><b>Figure 1 </b>Ingress diagram</span><br><span><img class="eddx" id="cce_10_0094__image98185817414" src="en-us_image_0000001695896861.png"></span></div>
<div class="fignone" id="cce_10_0094__fig18155819416"><a name="cce_10_0094__fig18155819416"></a><a name="fig18155819416"></a><span class="figcap"><b>Figure 1 </b>Ingress diagram</span><br><span><img class="eddx" id="cce_10_0094__image98185817414" src="en-us_image_0000001750791624.png"></span></div>
<p id="cce_10_0094__p128258846">The following describes the ingress-related definitions:</p>
<ul id="cce_10_0094__ul2875811411"><li id="cce_10_0094__li78145815413">Ingress object: a set of access rules that forward requests to specified Services based on domain names or URLs. It can be added, deleted, modified, and queried by calling APIs.</li><li id="cce_10_0094__li148115817417">Ingress Controller: an executor for request forwarding. It monitors the changes of resource objects such as ingresses, Services, endpoints, secrets (mainly TLS certificates and keys), nodes, and ConfigMaps in real time, parses rules defined by ingresses, and forwards requests to the corresponding backend Services.</li></ul>
</div>
<div class="section" id="cce_10_0094__section162271821192312"><h4 class="sectiontitle">Working Principle of ELB Ingress Controller</h4><p id="cce_10_0094__p172542048121220">ELB Ingress Controller developed by CCE implements layer-7 network access for the internet and intranet (in the same VPC) based on ELB and distributes access traffic to the corresponding Services using different URLs.</p>
<p id="cce_10_0094__p4254124831218">ELB Ingress Controller is deployed on the master node and bound to the load balancer in the VPC where the cluster resides. Different domain names, ports, and forwarding policies can be configured for the same load balancer (with the same IP address). <a href="#cce_10_0094__fig122542486129">Figure 2</a> shows the working principle of ELB Ingress Controller.</p>
<ol id="cce_10_0094__ol525410483123"><li id="cce_10_0094__li8254184813127">A user creates an ingress object and configures a traffic access rule in the ingress, including the load balancer, URL, SSL, and backend service port.</li><li id="cce_10_0094__li1225474817126">When Ingress Controller detects that the ingress object changes, it reconfigures the listener and backend server route on the ELB side according to the traffic access rule.</li><li id="cce_10_0094__li115615167193">When a user accesses a workload, the traffic is forwarded to the corresponding backend service port based on the forwarding policy configured on ELB, and then forwarded to each associated workload through the Service.</li></ol>
<div class="fignone" id="cce_10_0094__fig122542486129"><a name="cce_10_0094__fig122542486129"></a><a name="fig122542486129"></a><span class="figcap"><b>Figure 2 </b>Working principle of ELB Ingress Controller</span><br><span><img class="eddx" id="cce_10_0094__image725424815120" src="en-us_image_0000001647577184.png"></span></div>
<div class="fignone" id="cce_10_0094__fig122542486129"><a name="cce_10_0094__fig122542486129"></a><a name="fig122542486129"></a><span class="figcap"><b>Figure 2 </b>Working principle of ELB Ingress Controller</span><br><span><img class="eddx" id="cce_10_0094__image725424815120" src="en-us_image_0000001750791628.png"></span></div>
</div>
<div class="section" id="cce_10_0094__section3565202819276"><a name="cce_10_0094__section3565202819276"></a><a name="section3565202819276"></a><h4 class="sectiontitle">Services Supported by Ingresses</h4><div class="p" id="cce_10_0094__p109298589133"><a href="#cce_10_0094__table143264518141">Table 1</a> lists the services supported by ELB Ingresses.
<div class="tablenoborder"><a name="cce_10_0094__table143264518141"></a><a name="table143264518141"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0094__table143264518141" width="100%" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Services supported by ELB Ingresses</caption><thead align="left"><tr id="cce_10_0094__row1132645112145"><th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.3.2.2.2.5.1.1"><p id="cce_10_0094__p33261518148">Cluster Type</p>
@ -23,7 +23,7 @@
</th>
</tr>
</thead>
<tbody><tr id="cce_10_0094__row1326185141413"><td class="cellrowborder" rowspan="2" valign="top" width="15%" headers="mcps1.3.3.2.2.2.5.1.1 "><p id="cce_10_0094__p132635111148">CCE cluster</p>
<tbody><tr id="cce_10_0094__row1326185141413"><td class="cellrowborder" rowspan="2" valign="top" width="15%" headers="mcps1.3.3.2.2.2.5.1.1 "><p id="cce_10_0094__p132635111148">CCE standard cluster</p>
</td>
<td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.3.2.2.2.5.1.2 "><p id="cce_10_0094__p10326351161414">Shared load balancer</p>
</td>

4
docs/cce/umn/cce_10_0105.html
View File

@ -1,6 +1,6 @@
<a name="cce_10_0105"></a><a name="cce_10_0105"></a>
<h1 class="topictitle1">Setting Container Lifecycle Parameters</h1>
<h1 class="topictitle1">Configuring Container Lifecycle Parameters</h1>
<div id="body1511833542433"><div class="section" id="cce_10_0105__section196471258364"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0105__p182561527714">CCE provides callback functions for the lifecycle management of containerized applications. For example, if you want a container to perform a certain operation before stopping, you can register a hook function. </p>
<p id="cce_10_0105__p152208151978">CCE provides the following lifecycle callback functions:</p>
<ul id="cce_10_0105__ul922021513717"><li id="cce_10_0105__li16220815773"><strong id="cce_10_0105__b8812154352715"><span class="keyword" id="cce_10_0105__keyword209119171317258">Startup Command</span></strong>: executed to start a container. For details, see <a href="#cce_10_0105__section54912655316">Startup Commands</a>.</li><li id="cce_10_0105__li14220201518713"><strong id="cce_10_0105__b150302499794538"><span class="keyword" id="cce_10_0105__keyword29571762817312">Post-Start</span></strong>: executed immediately after a container is started. For details, see <a href="#cce_10_0105__section15243544163715">Post-Start Processing</a>.</li><li id="cce_10_0105__li32206153712"><strong id="cce_10_0105__b162512053994533"><span class="keyword" id="cce_10_0105__keyword26075130317328">Pre-Stop</span></strong>: executed before a container is stopped. The pre-stop processing function helps you ensure that the services running on the pods can be completed in advance in the case of pod upgrade or deletion. For details, see <a href="#cce_10_0105__section2334114473712">Pre-Stop Processing</a>.</li></ul>
@ -132,7 +132,7 @@
</thead>
<tbody><tr id="cce_10_0105__row04201302279"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.2.2.1.2.3.1.1 "><p id="cce_10_0105__p6420110192718">CLI</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.2.2.1.2.3.1.2 "><p id="cce_10_0105__p94204010271">Set commands to be executed in the container for pre-stop processing. The command format is <strong id="cce_10_0105__b1784169779">Command Args[1] Args[2]...</strong>. <strong id="cce_10_0105__b1109858898">Command</strong> is a system command or a user-defined executable program. If no path is specified, an executable program in the default path will be selected. If multiple commands need to be executed, write the commands into a script for execution.</p>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.2.2.1.2.3.1.2 "><p id="cce_10_0105__p94204010271">Set commands to be executed in the container for pre-stop processing. The command format is <strong id="cce_10_0105__b992317765">Command Args[1] Args[2]...</strong>. <strong id="cce_10_0105__b1616752902">Command</strong> is a system command or a user-defined executable program. If no path is specified, an executable program in the default path will be selected. If multiple commands need to be executed, write the commands into a script for execution.</p>
<p id="cce_10_0105__p94203082712">Example command:</p>
<pre class="screen" id="cce_10_0105__screen6420190132712">exec:
command:

16
docs/cce/umn/cce_10_0107.html
View File

@ -1,13 +1,13 @@
<a name="cce_10_0107"></a><a name="cce_10_0107"></a>
<h1 class="topictitle1">Connecting to a Cluster Using kubectl</h1>
<div id="body1512462600292"><div class="section" id="cce_10_0107__section14234115144"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0107__p133539491408">This section uses a CCE cluster as an example to describe how to connect to a CCE cluster using <span class="keyword" id="cce_10_0107__keyword19467121518447">kubectl</span>.</p>
<div id="body1512462600292"><div class="section" id="cce_10_0107__section14234115144"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0107__p133539491408">This section uses a CCE standard cluster as an example to describe how to connect to a CCE cluster using <span class="keyword" id="cce_10_0107__keyword19467121518447">kubectl</span>.</p>
</div>
<div class="section" id="cce_10_0107__section17352373317"><h4 class="sectiontitle">Permissions</h4><p id="cce_10_0107__p51211251156">When you access a cluster using kubectl, CCE uses <strong id="cce_10_0107__b9161182320391"><span class="keyword" id="cce_10_0107__keyword1354319447418">kubeconfig</span>.json</strong> generated on the cluster for authentication. This file contains user information, based on which CCE determines which Kubernetes resources can be accessed by kubectl. The permissions recorded in a <strong id="cce_10_0107__b16295666413">kubeconfig.json</strong> file vary from user to user.</p>
<p id="cce_10_0107__p142391810113">For details about user permissions, see <a href="cce_10_0187.html#cce_10_0187__section1464135853519">Cluster Permissions (IAM-based) and Namespace Permissions (Kubernetes RBAC-based)</a>.</p>
</div>
<div class="section" id="cce_10_0107__section37321625113110"><a name="cce_10_0107__section37321625113110"></a><a name="section37321625113110"></a><h4 class="sectiontitle">Using kubectl</h4><p id="cce_10_0107__p764905418355">To connect to a Kubernetes cluster from a PC, you can use kubectl, a Kubernetes command line tool. You can log in to the CCE console, click the name of the cluster to be connected, and view the access address and kubectl connection procedure on the cluster details page.</p>
<div class="p" id="cce_10_0107__p7805114919351">CCE allows you to access a cluster through a private network or a public network.<ul id="cce_10_0107__ul126071124175518"><li id="cce_10_0107__li144192116548"><span class="keyword" id="cce_10_0107__keyword13441034142917">Intranet access</span>: The client that accesses the cluster must be in the same VPC as the cluster.</li><li id="cce_10_0107__li1460752419555">Public access: The client that accesses the cluster must be able to access public networks and the cluster has been bound with a public network IP.<div class="notice" id="cce_10_0107__note2967194410365"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cce_10_0107__p19671244103610">To bind a public IP (EIP) to the cluster, go to the cluster details page and click <strong id="cce_10_0107__b021910485396">Bind</strong> next to <strong id="cce_10_0107__b132197480394">EIP</strong> in the <strong id="cce_10_0107__b14219164815396">Connection Information</strong> pane. In a cluster with an EIP bound, kube-apiserver will be exposed to public networks and may be attacked. You are advised to configure Advanced Anti-DDoS (AAD) for the EIP of the node where kube-apiserver resides.</p>
<div class="section" id="cce_10_0107__section37321625113110"><a name="cce_10_0107__section37321625113110"></a><a name="section37321625113110"></a><h4 class="sectiontitle">Using kubectl</h4><p id="cce_10_0107__p764905418355">To connect to a Kubernetes cluster from a PC, you can use kubectl, a Kubernetes command line tool. You can log in to the CCE console and click the name of the target cluster to access the cluster console. On the <strong id="cce_10_0107__b127302345555">Overview</strong> page, view the access address and kubectl connection procedure.</p>
<div class="p" id="cce_10_0107__p7805114919351">CCE allows you to access a cluster through a private network or a public network.<ul id="cce_10_0107__ul126071124175518"><li id="cce_10_0107__li144192116548"><span class="keyword" id="cce_10_0107__keyword13441034142917">Intranet access</span>: The client that accesses the cluster must be in the same VPC as the cluster.</li><li id="cce_10_0107__li1460752419555">Public access: The client that accesses the cluster must be able to access public networks and the cluster has been bound with a public network IP.<div class="notice" id="cce_10_0107__note2967194410365"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cce_10_0107__p19671244103610">To bind an EIP to the cluster, go to the <strong id="cce_10_0107__b1061217302"><span id="cce_10_0107__text6807412192418">Overview</span></strong> page and click <strong id="cce_10_0107__b021910485396">Bind</strong> next to <strong id="cce_10_0107__b132197480394">EIP</strong> in the <strong id="cce_10_0107__b14219164815396">Connection Information</strong> area. In a cluster with an EIP bound, kube-apiserver will be exposed to the Internet and may be attacked. To solve this problem, you can configure Advanced Anti-DDoS for the EIP of the node on which kube-apiserver runs.</p>
</div></div>
</li></ul>
</div>
@ -16,12 +16,12 @@
<p id="cce_10_0107__p125851851153510">This section uses the Linux environment as an example to describe how to install and configure kubectl. For details, see <a href="https://kubernetes.io/docs/tasks/tools/#kubectl" target="_blank" rel="noopener noreferrer">Installing kubectl</a>.</p>
<ol type="a" id="cce_10_0107__ol735517018289"><li id="cce_10_0107__li551132463520">Log in to your client and download kubectl.<pre class="screen" id="cce_10_0107__screen8511142418352">cd /home
curl -LO https://dl.k8s.io/release/<em id="cce_10_0107__i13511182443516">{v1.25.0}</em>/bin/linux/amd64/kubectl</pre>
<p id="cce_10_0107__p6511924173518"><em id="cce_10_0107__i719013311241">{v1.25.0}</em> specifies the version number. Replace it as required.</p>
<p id="cce_10_0107__p6511924173518"><em id="cce_10_0107__i719013311241"><strong id="cce_10_0107__b16190153182415">{v1.25.0}</strong></em> specifies the version number. Replace it as required.</p>
</li><li id="cce_10_0107__li1216814211286">Install kubectl.<pre class="screen" id="cce_10_0107__screen16892115815271">chmod +x kubectl
mv -f kubectl /usr/local/bin</pre>
</li></ol>
</p></li><li id="cce_10_0107__li34691156151712"><a name="cce_10_0107__li34691156151712"></a><a name="li34691156151712"></a><span><strong id="cce_10_0107__b196211619192411">Obtain the kubectl configuration file (kubeconfig).</strong></span><p><p id="cce_10_0107__p1295818109256">In the <strong id="cce_10_0107__b450013549611">Connection Information</strong> pane on the cluster details page, click <strong id="cce_10_0107__b136512181078">Configure</strong> next to <strong id="cce_10_0107__b177317221173">kubectl</strong>. On the window displayed, download the configuration file.</p>
<div class="note" id="cce_10_0107__note191638104210"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0107__ul795610485546"><li id="cce_10_0107__li495634817549">The kubectl configuration file <strong id="cce_10_0107__b11741123981418">kubeconfig.json</strong> is used for cluster authentication. If the file is leaked, your clusters may be attacked.</li><li id="cce_10_0107__li62692399615">By default, two-way authentication is disabled for domain names in the current cluster. You can run the <strong id="cce_10_0107__b76312129249">kubectl config use-context externalTLSVerify</strong> command to enable two-way authentication. For details, see <a href="#cce_10_0107__section1559919152711">Two-Way Authentication for Domain Names</a>. For a cluster that has been bound to an EIP, if the authentication fails (x509: certificate is valid) when two-way authentication is used, bind the EIP again and download <strong id="cce_10_0107__b940713611819">kubeconfig.json</strong> again.</li><li id="cce_10_0107__li16956194817544">The Kubernetes permissions assigned by the configuration file downloaded by IAM users are the same as those assigned to the IAM users on the CCE console.</li><li id="cce_10_0107__li1537643019239">If the KUBECONFIG environment variable is configured in the Linux OS, kubectl preferentially loads the KUBECONFIG environment variable instead of <strong id="cce_10_0107__b5859154717398">$home/.kube/config</strong>.</li></ul>
</p></li><li id="cce_10_0107__li34691156151712"><a name="cce_10_0107__li34691156151712"></a><a name="li34691156151712"></a><span><strong id="cce_10_0107__b196211619192411">Obtain the kubectl configuration file (kubeconfig).</strong></span><p><p id="cce_10_0107__p1295818109256">On the <strong id="cce_10_0107__b124401123203115">Overview</strong> page, locate the <strong id="cce_10_0107__b450013549611">Connection Info</strong> area, click <strong id="cce_10_0107__b136512181078">Configure</strong> next to <strong id="cce_10_0107__b177317221173">kubectl</strong>. On the window displayed, download the configuration file.</p>
<div class="note" id="cce_10_0107__note191638104210"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0107__ul795610485546"><li id="cce_10_0107__li495634817549">The kubectl configuration file <strong id="cce_10_0107__b11741123981418">kubeconfig.json</strong> is used for cluster authentication. If the file is leaked, your clusters may be attacked.</li><li id="cce_10_0107__li16956194817544">The Kubernetes permissions assigned by the configuration file downloaded by IAM users are the same as those assigned to the IAM users on the CCE console.</li><li id="cce_10_0107__li1537643019239">If the KUBECONFIG environment variable is configured in the Linux OS, kubectl preferentially loads the KUBECONFIG environment variable instead of <strong id="cce_10_0107__b5859154717398">$home/.kube/config</strong>.</li></ul>
</div></div>
</p></li><li id="cce_10_0107__li25451059122317"><a name="cce_10_0107__li25451059122317"></a><a name="li25451059122317"></a><span>Configure kubectl.</span><p><div class="p" id="cce_10_0107__p109826082413">Configure kubectl (A Linux OS is used).<ol type="a" id="cce_10_0107__ol2291154772010"><li id="cce_10_0107__li102911547102012">Log in to your client and copy the kubeconfig.json configuration file downloaded in <a href="#cce_10_0107__li34691156151712">2</a> to the <strong id="cce_10_0107__b175828331240">/home</strong> directory on your client.</li><li id="cce_10_0107__li114766383477">Configure the kubectl authentication file.<pre class="screen" id="cce_10_0107__screen849155210477">cd /home
mkdir -p $HOME/.kube
@ -36,10 +36,10 @@ mv -f kubeconfig.json $HOME/.kube/config</pre>
</p></li></ol>
</div>
<div class="section" id="cce_10_0107__section1559919152711"><a name="cce_10_0107__section1559919152711"></a><a name="section1559919152711"></a><h4 class="sectiontitle"><span class="keyword" id="cce_10_0107__keyword311020376452">Two-Way Authentication for Domain Names</span></h4><p id="cce_10_0107__p138948491274">CCE supports two-way authentication for domain names.</p>
<ul id="cce_10_0107__ul88981331482"><li id="cce_10_0107__li1705116151915">Two-way authentication is disabled for domain names by default. You can run the <strong id="cce_10_0107__b198732542582">kubectl config use-context externalTLSVerify</strong> command to switch to the externalTLSVerify context to enable it.</li><li id="cce_10_0107__li1807459174818">When an EIP is bound to or unbound from a cluster, or a custom domain name is configured or updated, the cluster server certificate will be added the latest cluster access address (including the EIP bound to the cluster and all custom domain names configured for the cluster).</li><li id="cce_10_0107__li17898153310483">Asynchronous cluster synchronization takes about 5 to 10 minutes. You can view the synchronization result in <strong id="cce_10_0107__b196404619200">Synchronize Certificate</strong> in <strong id="cce_10_0107__b364620682012">Operation Records</strong>.</li><li id="cce_10_0107__li614337712">For a cluster that has been bound to an EIP, if the authentication fails (x509: certificate is valid) when two-way authentication is used, bind the EIP again and download <strong id="cce_10_0107__b121611451417">kubeconfig.json</strong> again.</li><li id="cce_10_0107__li5950658165414">If the domain name two-way authentication is not supported, <strong id="cce_10_0107__b56091346184712">kubeconfig.json</strong> contains the <strong id="cce_10_0107__b1961534614476">"insecure-skip-tls-verify": true</strong> field, as shown in <a href="#cce_10_0107__fig1941342411">Figure 1</a>. To use two-way authentication, you can download the <strong id="cce_10_0107__b549311585216">kubeconfig.json</strong> file again and enable two-way authentication for the domain names.<div class="fignone" id="cce_10_0107__fig1941342411"><a name="cce_10_0107__fig1941342411"></a><a name="fig1941342411"></a><span class="figcap"><b>Figure 1 </b>Two-way authentication disabled for domain names</span><br><span><img id="cce_10_0107__image13288203455018" src="en-us_image_0000001726718109.png"></span></div>
<ul id="cce_10_0107__ul88981331482"><li id="cce_10_0107__li1705116151915">After an EIP is bound to an API Server, two-way domain name authentication will be disabled by default if kubectl is used to connect to the cluster. You can run <strong id="cce_10_0107__b198732542582">kubectl config use-context externalTLSVerify</strong> to switch to the externalTLSVerify context to enable the two-way domain name authentication.</li><li id="cce_10_0107__li1807459174818">When an EIP is bound to or unbound from a cluster, or a custom domain name is configured or updated, the cluster server certificate will be added the latest cluster access address (including the EIP bound to the cluster and all custom domain names configured for the cluster).</li><li id="cce_10_0107__li17898153310483">Asynchronous cluster synchronization takes about 5 to 10 minutes. You can view the synchronization result in <strong id="cce_10_0107__b196404619200">Synchronize Certificate</strong> in <strong id="cce_10_0107__b364620682012">Operation Records</strong>.</li><li id="cce_10_0107__li614337712">For a cluster that has been bound to an EIP, if the authentication fails (x509: certificate is valid) when two-way authentication is used, bind the EIP again and download <strong id="cce_10_0107__b121611451417">kubeconfig.json</strong> again.</li><li id="cce_10_0107__li5950658165414">If the domain name two-way authentication is not supported, <strong id="cce_10_0107__b56091346184712">kubeconfig.json</strong> contains the <strong id="cce_10_0107__b1961534614476">"insecure-skip-tls-verify": true</strong> field, as shown in <a href="#cce_10_0107__fig1941342411">Figure 1</a>. To use two-way authentication, you can download the <strong id="cce_10_0107__b549311585216">kubeconfig.json</strong> file again and enable two-way authentication for the domain names.<div class="fignone" id="cce_10_0107__fig1941342411"><a name="cce_10_0107__fig1941342411"></a><a name="fig1941342411"></a><span class="figcap"><b>Figure 1 </b>Two-way authentication disabled for domain names</span><br><span><img id="cce_10_0107__image3414621613" src="en-us_image_0000001750791664.png"></span></div>
</li></ul>
</div>
<div class="section" id="cce_10_0107__section1628510591883"><h4 class="sectiontitle">Common Issues</h4><ul id="cce_10_0107__ul1374831051115"><li id="cce_10_0107__li4748810121112"><strong id="cce_10_0107__b456677171119"><span class="keyword" id="cce_10_0107__keyword0702458114510">Error from server Forbidden</span></strong><p id="cce_10_0107__p75241832114916">When you use kubectl to create or query Kubernetes resources, the following output is returned:</p>
<div class="section" id="cce_10_0107__section1628510591883"><h4 class="sectiontitle">FAQs</h4><ul id="cce_10_0107__ul1374831051115"><li id="cce_10_0107__li4748810121112"><strong id="cce_10_0107__b456677171119"><span class="keyword" id="cce_10_0107__keyword0702458114510">Error from server Forbidden</span></strong><p id="cce_10_0107__p75241832114916">When you use kubectl to create or query Kubernetes resources, the following output is returned:</p>
<pre class="screen" id="cce_10_0107__screen5530165114117"># kubectl get deploy Error from server (Forbidden): deployments.apps is forbidden: User "0c97ac3cb280f4d91fa7c0096739e1f8" cannot list resource "deployments" in API group "apps" in the namespace "default"</pre>
<p id="cce_10_0107__p1418636115119">The cause is that the user does not have the permissions to operate the Kubernetes resources. For details about how to assign permissions, see <a href="cce_10_0189.html">Namespace Permissions (Kubernetes RBAC-based)</a>.</p>
</li><li id="cce_10_0107__li0365152110"><strong id="cce_10_0107__b1829619716131"><span class="keyword" id="cce_10_0107__keyword159213536451">The connection to the server localhost:8080 was refused</span></strong><p id="cce_10_0107__p1776396131212">When you use kubectl to create or query Kubernetes resources, the following output is returned:</p>

2
docs/cce/umn/cce_10_0111.html
View File

@ -1,6 +1,6 @@
<a name="cce_10_0111"></a><a name="cce_10_0111"></a>
<h1 class="topictitle1">Scalable File Service (SFS)</h1>
<h1 class="topictitle1">Scalable File Service</h1>
<div id="body0000001487121868"><p id="cce_10_0111__p8060118"></p>
</div>
<div>

26
docs/cce/umn/cce_10_0112.html
View File

@ -1,6 +1,6 @@
<a name="cce_10_0112"></a><a name="cce_10_0112"></a>
<h1 class="topictitle1">Setting Health Check for a Container</h1>
<h1 class="topictitle1">Configuring Container Health Check</h1>
<div id="body1512535109871"><div class="section" id="cce_10_0112__section1731112174912"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0112__p8242924192"><span class="keyword" id="cce_10_0112__keyword22817116429">Health check</span> regularly checks the health status of containers during container running. If the health check function is not configured, a pod cannot detect application exceptions or automatically restart the application to restore it. This will result in a situation where the pod status is normal but the application in the pod is abnormal.</p>
<p id="cce_10_0112__a77e71e69afde4757ab0ef6087b2e30de">Kubernetes provides the following health check probes:</p>
<ul id="cce_10_0112__ul1867812287915"><li id="cce_10_0112__li574951765020"><strong id="cce_10_0112__b1644144411235">Liveness probe</strong> (livenessProbe): checks whether a container is still alive. It is similar to the <strong id="cce_10_0112__b5645134422313">ps</strong> command that checks whether a process exists. If the liveness check of a container fails, the cluster restarts the container. If the liveness check is successful, no operation is executed.</li><li id="cce_10_0112__li36781028792"><strong id="cce_10_0112__b1729242134220">Readiness probe</strong> (readinessProbe): checks whether a container is ready to process user requests. Upon that the container is detected unready, service traffic will not be directed to the container. It may take a long time for some applications to start up before they can provide services. This is because that they need to load disk data or rely on startup of an external module. In this case, the application process is running, but the application cannot provide services. To address this issue, this health check probe is used. If the container readiness check fails, the cluster masks all requests sent to the container. If the container readiness check is successful, the container can be accessed. </li><li id="cce_10_0112__li142001552181016"><strong id="cce_10_0112__b86001053354">Startup probe</strong> (startupProbe): checks when a containerized application has started. If such a probe is configured, it disables liveness and readiness checks until it succeeds, ensuring that those probes do not interfere with the application startup. This can be used to adopt liveness checks on slow starting containers, avoiding them getting terminated by the kubelet before they are started.</li></ul>
@ -22,40 +22,40 @@
</li></ul>
</div>
<div class="section" id="cce_10_0112__section2050653544516"><h4 class="sectiontitle">Common Parameters</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0112__t045a8ee10cb946eaa4c01da4319b7206" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Common parameter description</caption><thead align="left"><tr id="cce_10_0112__re3891f83a0b242b1bf3f178042398166"><th align="left" class="cellrowborder" valign="top" width="27%" id="mcps1.3.3.2.2.3.1.1"><p id="cce_10_0112__afec93a787dcb46788032cfc70a14a22e">Parameter</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0112__t045a8ee10cb946eaa4c01da4319b7206" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Common parameter description</caption><thead align="left"><tr id="cce_10_0112__re3891f83a0b242b1bf3f178042398166"><th align="left" class="cellrowborder" valign="top" width="19%" id="mcps1.3.3.2.2.3.1.1"><p id="cce_10_0112__afec93a787dcb46788032cfc70a14a22e">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="73%" id="mcps1.3.3.2.2.3.1.2"><p id="cce_10_0112__en-us_topic_0052519475_p74835383351">Description</p>
<th align="left" class="cellrowborder" valign="top" width="81%" id="mcps1.3.3.2.2.3.1.2"><p id="cce_10_0112__en-us_topic_0052519475_p74835383351">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="cce_10_0112__row20530143512017"><td class="cellrowborder" valign="top" width="27%" headers="mcps1.3.3.2.2.3.1.1 "><p id="cce_10_0112__p65301359204"><strong id="cce_10_0112__b1180312425104">Period</strong> (periodSeconds)</p>
<tbody><tr id="cce_10_0112__row20530143512017"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.2.3.1.1 "><p id="cce_10_0112__p65301359204">Period (periodSeconds)</p>
</td>
<td class="cellrowborder" valign="top" width="73%" headers="mcps1.3.3.2.2.3.1.2 "><p id="cce_10_0112__p5530935122014">Indicates the probe detection period, in seconds.</p>
<td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.2.3.1.2 "><p id="cce_10_0112__p5530935122014">Indicates the probe detection period, in seconds.</p>
<p id="cce_10_0112__p14542201010239">For example, if this parameter is set to <strong id="cce_10_0112__b113661844155919">30</strong>, the detection is performed every 30 seconds.</p>
</td>
</tr>
<tr id="cce_10_0112__r82f45c7641534b8d80da858ce9ce9be7"><td class="cellrowborder" valign="top" width="27%" headers="mcps1.3.3.2.2.3.1.1 "><p id="cce_10_0112__p183641821163711"><strong id="cce_10_0112__b42116252116">Delay</strong> (initialDelaySeconds)</p>
<tr id="cce_10_0112__r82f45c7641534b8d80da858ce9ce9be7"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.2.3.1.1 "><p id="cce_10_0112__p183641821163711">Delay (initialDelaySeconds)</p>
</td>
<td class="cellrowborder" valign="top" width="73%" headers="mcps1.3.3.2.2.3.1.2 "><p id="cce_10_0112__p173941610161614">Check delay time in seconds. Set this parameter according to the normal startup time of services.</p>
<td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.2.3.1.2 "><p id="cce_10_0112__p173941610161614">Check delay time in seconds. Set this parameter according to the normal startup time of services.</p>
<p id="cce_10_0112__en-us_topic_0052519475_p05855219373">For example, if this parameter is set to <strong id="cce_10_0112__b58566420014">30</strong>, the health check will be started 30 seconds after the container is started. The time is reserved for containerized services to start.</p>
</td>
</tr>
<tr id="cce_10_0112__rf8dd0b9b29af4b96bcf3efaecb0c4bb2"><td class="cellrowborder" valign="top" width="27%" headers="mcps1.3.3.2.2.3.1.1 "><p id="cce_10_0112__p36325348374"><strong id="cce_10_0112__b1575383111118">Timeout</strong> (timeoutSeconds)</p>
<tr id="cce_10_0112__rf8dd0b9b29af4b96bcf3efaecb0c4bb2"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.2.3.1.1 "><p id="cce_10_0112__p36325348374">Timeout (timeoutSeconds)</p>
</td>
<td class="cellrowborder" valign="top" width="73%" headers="mcps1.3.3.2.2.3.1.2 "><p id="cce_10_0112__p052822120161">Number of seconds after which the probe times out. Unit: second. </p>
<td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.2.3.1.2 "><p id="cce_10_0112__p052822120161">Number of seconds after which the probe times out. Unit: second. </p>
<p id="cce_10_0112__a376926047bc64e0a9304d6c9828fc5a2">For example, if this parameter is set to <strong id="cce_10_0112__b84235270617502">10</strong>, the timeout wait time for performing a health check is 10s. If the wait time elapses, the health check is regarded as a failure. If the parameter is left blank or set to <strong id="cce_10_0112__b84235270617523">0</strong>, the default timeout time is 1s. </p>
</td>
</tr>
<tr id="cce_10_0112__row122252672114"><td class="cellrowborder" valign="top" width="27%" headers="mcps1.3.3.2.2.3.1.1 "><p id="cce_10_0112__p22251962213"><strong id="cce_10_0112__b10473150161116">Success Threshold</strong> (successThreshold)</p>
<tr id="cce_10_0112__row122252672114"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.2.3.1.1 "><p id="cce_10_0112__p22251962213">Success Threshold (successThreshold)</p>
</td>
<td class="cellrowborder" valign="top" width="73%" headers="mcps1.3.3.2.2.3.1.2 "><p id="cce_10_0112__p68862519317">Minimum consecutive successes for the probe to be considered successful after having failed. For example, if this parameter is set to <strong id="cce_10_0112__b539251217254">1</strong>, the workload status is normal only when the health check is successful for one consecutive time after the health check fails.</p>
<td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.2.3.1.2 "><p id="cce_10_0112__p68862519317">Minimum consecutive successes for the probe to be considered successful after having failed. For example, if this parameter is set to <strong id="cce_10_0112__b539251217254">1</strong>, the workload status is normal only when the health check is successful for one consecutive time after the health check fails.</p>
<p id="cce_10_0112__p4789856113112">The default value is <strong id="cce_10_0112__b1813915471751">1</strong>, which is also the minimum value.</p>
<p id="cce_10_0112__p922520614215">The value of this parameter is fixed to <strong id="cce_10_0112__b699525419516">1</strong> in <strong id="cce_10_0112__b599610546519">Liveness Probe</strong> and <strong id="cce_10_0112__b69965541558">Startup Probe</strong>.</p>
</td>
</tr>
<tr id="cce_10_0112__row104681621102117"><td class="cellrowborder" valign="top" width="27%" headers="mcps1.3.3.2.2.3.1.1 "><p id="cce_10_0112__p1468121152113"><strong id="cce_10_0112__b88831329181512">Failure Threshold</strong> (failureThreshold)</p>
<tr id="cce_10_0112__row104681621102117"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.2.2.3.1.1 "><p id="cce_10_0112__p1468121152113">Failure Threshold (failureThreshold)</p>
</td>
<td class="cellrowborder" valign="top" width="73%" headers="mcps1.3.3.2.2.3.1.2 "><p id="cce_10_0112__p9644133173213">Number of retry times when the detection fails.</p>
<td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.3.2.2.3.1.2 "><p id="cce_10_0112__p9644133173213">Number of retry times when the detection fails.</p>
<p id="cce_10_0112__p111011316163216">Giving up in case of liveness probe means to restart the container. In case of readiness probe the pod will be marked Unready.</p>
<p id="cce_10_0112__p446822117214">The default value is <strong id="cce_10_0112__b18801222192519">3</strong>. The minimum value is <strong id="cce_10_0112__b9698122717253">1</strong>.</p>
</td>

6
docs/cce/umn/cce_10_0113.html
View File

@ -1,15 +1,15 @@
<a name="cce_10_0113"></a><a name="cce_10_0113"></a>
<h1 class="topictitle1">Setting an Environment Variable</h1>
<h1 class="topictitle1">Configuring Environment Variables</h1>
<div id="body1526008508696"><div class="section" id="cce_10_0113__section91908379912"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0113__p1566654220910">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 deployed, increasing flexibility in workload configuration.</p>
<p id="cce_10_0113__p33421347172917">The function of setting environment variables on CCE is the same as that of specifying <span class="parmname" id="cce_10_0113__parmname1630339175319"><b>ENV</b></span> in a Dockerfile.</p>
<div class="notice" id="cce_10_0113__note1262611218201"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cce_10_0113__p103084565278">After a container is started, do not modify configurations in the container. If configurations in the container are modified (for example, passwords, certificates, and environment variables of a containerized application are added to the container), the configurations will be lost after the container restarts and container services will become abnormal. An example scenario of container restart is pod rescheduling due to node anomalies.</p>
<p id="cce_10_0113__p26271321192016">Configurations must be imported to a container as arguments. Otherwise, configurations will be lost after the container restarts.</p>
</div></div>
<p id="cce_10_0113__p78261119155911">Environment variables can be set in the following modes:</p>
<ul id="cce_10_0113__ul1669104610598"><li id="cce_10_0113__li266913468594"><strong id="cce_10_0113__b4564141914250">Custom</strong>: Enter the environment variable name and parameter value.</li><li id="cce_10_0113__li13148164912599"><strong id="cce_10_0113__b31161818143614">Added from ConfigMap key</strong>: Import all keys in a ConfigMap as environment variables.</li><li id="cce_10_0113__li1855315291026"><strong id="cce_10_0113__b5398577535">Added from ConfigMap</strong>: Import a key in a ConfigMap as the value of an environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import <strong id="cce_10_0113__b20936188125511">configmap_value</strong> of <strong id="cce_10_0113__b12936684553">configmap_key</strong> in a ConfigMap as the value of environment variable <strong id="cce_10_0113__b593614805511">key1</strong>, an environment variable named <strong id="cce_10_0113__b893617815559">key1</strong> whose value is <strong id="cce_10_0113__b1293619819551">configmap_value</strong> exists in the container.</li><li id="cce_10_0113__li1727795616592"><strong id="cce_10_0113__b675162614437">Added from secret</strong>: Import all keys in a secret as environment variables.</li><li id="cce_10_0113__li93353201773"><strong id="cce_10_0113__b0483141614480">Added from secret key</strong>: Import the value of a key in a secret as the value of an environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import <strong id="cce_10_0113__b2840352135512">secret_value</strong> of <strong id="cce_10_0113__b12840145235515">secret_key</strong> in secret <strong id="cce_10_0113__b2084020521557">secret-example</strong> as the value of environment variable <strong id="cce_10_0113__b198401752195514">key2</strong>, an environment variable named <strong id="cce_10_0113__b2840145212556">key2</strong> whose value is <strong id="cce_10_0113__b1484165212556">secret_value</strong> exists in the container.</li><li id="cce_10_0113__li1749760535"><strong id="cce_10_0113__b19931701407">Variable value/reference</strong>: Use the field defined by a pod as the value of the environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if the pod name is imported as the value of environment variable <strong id="cce_10_0113__b10262145911552">key3</strong>, an environment variable named <strong id="cce_10_0113__b1226215914556">key3</strong> exists in the container and its value is the pod name.</li><li id="cce_10_0113__li16129071317"><strong id="cce_10_0113__b1625513417292">Resource Reference</strong>: The value of <strong id="cce_10_0113__b176281198307">Request</strong> or <strong id="cce_10_0113__b186221022193017">Limit</strong> defined by the container is used as the value of the environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import the CPU limit of <strong id="cce_10_0113__b1112012595611">container-1</strong> as the value of environment variable <strong id="cce_10_0113__b1120153563">key4</strong>, an environment variable named <strong id="cce_10_0113__b5120154565">key4</strong> exists in the container and its value is the CPU limit of <strong id="cce_10_0113__b131219518562">container-1</strong>.</li></ul>
<ul id="cce_10_0113__ul1669104610598"><li id="cce_10_0113__li266913468594"><strong id="cce_10_0113__b4564141914250">Custom</strong>: Enter the environment variable name and parameter value.</li><li id="cce_10_0113__li13148164912599"><strong id="cce_10_0113__b31161818143614">Added from ConfigMap key</strong>: Import all keys in a ConfigMap as environment variables.</li><li id="cce_10_0113__li1855315291026"><strong id="cce_10_0113__b5398577535">Added from ConfigMap</strong>: Import a key in a ConfigMap as the value of an environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import <strong id="cce_10_0113__b17273203011542">configmap_value</strong> of <strong id="cce_10_0113__b11273163035411">configmap_key</strong> in a ConfigMap as the value of environment variable <strong id="cce_10_0113__b327363011547">key1</strong>, an environment variable named <strong id="cce_10_0113__b17273123015548">key1</strong> whose value is <strong id="cce_10_0113__b72741430195420">configmap_value</strong> exists in the container.</li><li id="cce_10_0113__li1727795616592"><strong id="cce_10_0113__b675162614437">Added from secret</strong>: Import all keys in a secret as environment variables.</li><li id="cce_10_0113__li93353201773"><strong id="cce_10_0113__b0483141614480">Added from secret key</strong>: Import the value of a key in a secret as the value of an environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import <strong id="cce_10_0113__b21956593546">secret_value</strong> of <strong id="cce_10_0113__b1619505935419">secret_key</strong> in secret <strong id="cce_10_0113__b171951159145419">secret-example</strong> as the value of environment variable <strong id="cce_10_0113__b1819555965412">key2</strong>, an environment variable named <strong id="cce_10_0113__b17195859155410">key2</strong> whose value is <strong id="cce_10_0113__b1219510597545">secret_value</strong> exists in the container.</li><li id="cce_10_0113__li1749760535"><strong id="cce_10_0113__b19931701407">Variable value/reference</strong>: Use the field defined by a pod as the value of the environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if the pod name is imported as the value of environment variable <strong id="cce_10_0113__b1571429125511">key3</strong>, an environment variable named <strong id="cce_10_0113__b8571202914556">key3</strong> exists in the container and its value is the pod name.</li><li id="cce_10_0113__li16129071317"><strong id="cce_10_0113__b1625513417292">Resource Reference</strong>: The value of <strong id="cce_10_0113__b176281198307">Request</strong> or <strong id="cce_10_0113__b186221022193017">Limit</strong> defined by the container is used as the value of the environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import the CPU limit of <strong id="cce_10_0113__b1144418567">container-1</strong> as the value of environment variable <strong id="cce_10_0113__b1563165375511">key4</strong>, an environment variable named <strong id="cce_10_0113__b35638539558">key4</strong> exists in the container and its value is the CPU limit of <strong id="cce_10_0113__b1425871495610">container-1</strong>.</li></ul>
</div>
<div class="section" id="cce_10_0113__section13829152011595"><h4 class="sectiontitle">Adding Environment Variables</h4><ol id="cce_10_0113__ol4904646935"><li id="cce_10_0113__li330462393220"><span>Log in to the CCE console.</span></li><li id="cce_10_0113__li2075471341"><span>Click the cluster name to go to the cluster console, choose <strong id="cce_10_0113__b1794501219430">Workloads</strong> in the navigation pane, and click the <strong id="cce_10_0113__b11945131216432">Create Workload</strong> in the upper right corner.</span></li><li id="cce_10_0113__li190412461831"><span>When creating a workload, modify the container information in the <strong id="cce_10_0113__b101361766447">Container Settings</strong> area and click the <strong id="cce_10_0113__b8169124424315">Environment Variables</strong> tab.</span></li><li id="cce_10_0113__li468251942720"><span>Configure environment variables.</span><p><div class="fignone" id="cce_10_0113__fig164568529317"><a name="cce_10_0113__fig164568529317"></a><a name="fig164568529317"></a><span class="figcap"><b>Figure 1 </b>Configuring environment variables</span><br><span><img id="cce_10_0113__image486125516381" src="en-us_image_0000001695896581.png"></span></div>
<div class="section" id="cce_10_0113__section13829152011595"><h4 class="sectiontitle">Adding Environment Variables</h4><ol id="cce_10_0113__ol4904646935"><li id="cce_10_0113__li330462393220"><span>Log in to the CCE console.</span></li><li id="cce_10_0113__li2075471341"><span>Click the cluster name to go to the cluster console, choose <strong id="cce_10_0113__b1794501219430">Workloads</strong> in the navigation pane, and click the <strong id="cce_10_0113__b11945131216432">Create Workload</strong> in the upper right corner.</span></li><li id="cce_10_0113__li190412461831"><span>When creating a workload, modify the container information in <strong id="cce_10_0113__b101361766447">Container Settings</strong> and click the <strong id="cce_10_0113__b8169124424315">Environment Variables</strong> tab.</span></li><li id="cce_10_0113__li468251942720"><span>Configure environment variables.</span><p><div class="fignone" id="cce_10_0113__fig164568529317"><a name="cce_10_0113__fig164568529317"></a><a name="fig164568529317"></a><span class="figcap"><b>Figure 1 </b>Configuring environment variables</span><br><span><img id="cce_10_0113__image91271459162610" src="en-us_image_0000001750950284.png"></span></div>
</p></li></ol>
</div>
<div class="section" id="cce_10_0113__section19591158201313"><h4 class="sectiontitle">YAML Example</h4><pre class="screen" id="cce_10_0113__screen1034117614147">apiVersion: apps/v1

4
docs/cce/umn/cce_10_0125.html
View File

@ -1,6 +1,6 @@
<a name="cce_10_0125"></a><a name="cce_10_0125"></a>
<h1 class="topictitle1">SFS Turbo File Systems</h1>
<h1 class="topictitle1">SFS Turbo</h1>
<div id="body0000001538521545"><p id="cce_10_0125__p8060118"></p>
</div>
<div>
@ -11,7 +11,7 @@
</li>
<li class="ulchildlink"><strong><a href="cce_10_0626.html">Configuring SFS Turbo Mount Options</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_bestpractice_00253_0.html">Dynamically Creating and Mounting Subdirectories of an SFS Turbo File System</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_bestpractice_00253.html">Dynamically Creating and Mounting Subdirectories of an SFS Turbo File System</a></strong><br>
</li>
</ul>

10
docs/cce/umn/cce_10_0127.html
View File

@ -1,16 +1,16 @@
<a name="cce_10_0127"></a><a name="cce_10_0127"></a>
<h1 class="topictitle1">CCE Container Storage (FlexVolume)</h1>
<div id="body1541037494110"><div class="section" id="cce_10_0127__section25311744154917"><h4 class="sectiontitle">Introduction</h4><p id="cce_10_0127__p1574910495496">storage-driver functions as a standard Kubernetes FlexVolume plug-in to allow containers to use EVS, SFS, OBS, and SFS Turbo storage resources. By installing and upgrading storage-driver, you can quickly install and update cloud storage capabilities.</p>
<p id="cce_10_0127__p5414123111414"><strong id="cce_10_0127__b2471165511315">storage-driver is a system resource add-on. It is installed by default when a cluster of Kubernetes v1.13 or earlier is created.</strong></p>
<h1 class="topictitle1">CCE Container Storage (FlexVolume, Discarded)</h1>
<div id="body1541037494110"><div class="section" id="cce_10_0127__section25311744154917"><h4 class="sectiontitle">Introduction</h4><p id="cce_10_0127__p1574910495496">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 Turbo storage resources. By installing and upgrading storage-driver, you can quickly install and update cloud storage capabilities.</p>
<p id="cce_10_0127__p5414123111414"><strong id="cce_10_0127__b2471165511315">FlexVolume is a system resource add-on. It is installed by default when a cluster of Kubernetes v1.13 or earlier is created.</strong></p>
</div>
<div class="section" id="cce_10_0127__section3993231122718"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0127__ul113072911510"><li id="cce_10_0127__li10330171552010">For clusters created in CCE, Kubernetes v1.15.11 is a transitional version in which the FlexVolume add-on (storage-driver) is compatible with the CSI add-on (<a href="cce_10_0066.html">everest</a>). Clusters of v1.17 and later versions do not support FlexVolume anymore. Use the everest add-on.</li><li id="cce_10_0127__li25582642815">The FlexVolume add-on will be maintained by Kubernetes developers, but new functionality will only be added to <a href="cce_10_0066.html">CCE Container Storage (Everest)</a>. Do not create CCE storage that connects to the FlexVolume add-on (storage-driver) anymore. Otherwise, storage may malfunction.</li><li id="cce_10_0127__li51302291158">This add-on can be installed only in <strong id="cce_10_0127__b363773505113">clusters of v1.13 or earlier</strong>. By default, the <a href="cce_10_0066.html">everest</a> add-on is installed when clusters of v1.15 or later are created.<div class="note" id="cce_10_0127__note1531776113"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0127__p8532474112"><strong id="cce_10_0127__b411425325110">In a cluster of v1.13 or earlier</strong>, when an upgrade or bug fix is available for storage functionalities, you only need to install or upgrade the storage-driver add-on. Upgrading the cluster or creating a cluster is not required.</p>
<div class="section" id="cce_10_0127__section3993231122718"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0127__ul113072911510"><li id="cce_10_0127__li10330171552010">For clusters created in CCE, Kubernetes v1.15.11 is a transitional version in which the FlexVolume add-on is compatible with the CSI add-on (<a href="cce_10_0066.html">Everest</a>). Clusters of v1.17 and later versions do not support FlexVolume anymore. Use the Everest add-on.</li><li id="cce_10_0127__li25582642815">The FlexVolume add-on will be maintained by Kubernetes developers, but new functionality will only be added to <a href="cce_10_0066.html">Everest</a>. Do not create CCE storage that uses the FlexVolume add-on (storage-driver) anymore. Otherwise, storage may malfunction.</li><li id="cce_10_0127__li51302291158">This add-on can be installed only in <strong id="cce_10_0127__b363773505113">clusters of v1.13 or earlier</strong>. By default, the <a href="cce_10_0066.html">Everest</a> add-on is installed when clusters of v1.15 or later are created.<div class="note" id="cce_10_0127__note1531776113"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0127__p8532474112"><strong id="cce_10_0127__b411425325110">In a cluster of v1.13 or earlier</strong>, when an upgrade or bug fix is available for storage functionalities, you only need to install or upgrade the storage-driver add-on. Upgrading the cluster or creating a cluster is not required.</p>
</div></div>
</li></ul>
</div>
<div class="section" id="cce_10_0127__section776571919194"><h4 class="sectiontitle">Installing the Add-on</h4><p id="cce_10_0127__p11975102684817">This add-on has been installed by default. If it is uninstalled due to some reasons, you can reinstall it by performing the following steps:</p>
<p id="cce_10_0127__p21112429503">If storage-driver is not installed in a cluster, perform the following steps to install it:</p>
<ol id="cce_10_0127__ol9183433182510"><li id="cce_10_0127__li13183153352515"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0127__uicontrol91686151812"><b>Add-ons</b></span> in the navigation pane, locate <strong id="cce_10_0127__b1854013381808">storage-driver</strong><strong id="cce_10_0127__b876017407010"></strong> on the right, and click <strong id="cce_10_0127__b31752151083">Install</strong>.</span></li><li id="cce_10_0127__li9455819152615"><span>Click <strong id="cce_10_0127__b227242216554">Install</strong> to install the add-on. Note that the storage-driver has no configurable parameters and can be directly installed.</span></li></ol>
<ol id="cce_10_0127__ol9183433182510"><li id="cce_10_0127__li13183153352515"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0127__b636391011166"><span id="cce_10_0127__text77103384818">Add-ons</span></strong> in the navigation pane, locate <strong id="cce_10_0127__b8174151516816">CCE Container Storage (FlexVolume)</strong> on the right, and click <strong id="cce_10_0127__b31752151083">Install</strong>.</span></li><li id="cce_10_0127__li9455819152615"><span>Click <strong id="cce_10_0127__b227242216554">Install</strong> to install the add-on. Note that the storage-driver has no configurable parameters and can be directly installed.</span></li></ol>
</div>
</div>
<div>

223
docs/cce/umn/cce_10_0129.html
View File

File diff suppressed because it is too large Load Diff

12
docs/cce/umn/cce_10_0130.html
View File

@ -10,17 +10,17 @@
</li>
<li class="ulchildlink"><strong><a href="cce_10_0009.html">Using Third-Party Images</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0163.html">Setting Container Specifications</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0163.html">Configuring Container Specifications</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0105.html">Setting Container Lifecycle Parameters</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0105.html">Configuring Container Lifecycle Parameters</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0112.html">Setting Health Check for a Container</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0112.html">Configuring Container Health Check</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0113.html">Setting an Environment Variable</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0113.html">Configuring Environment Variables</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0397.html">Configuring the Workload Upgrade Policy</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0397.html">Workload Upgrade Policies</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0232.html">Scheduling Policy (Affinity/Anti-affinity)</a></strong><br>
<li class="ulchildlink"><strong><a href="cce_10_0232.html">Scheduling Policies (Affinity/Anti-affinity)</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0728.html">Taints and Tolerations</a></strong><br>
</li>

176
docs/cce/umn/cce_10_0132.html
View File

File diff suppressed because it is too large Load Diff

49
docs/cce/umn/cce_10_0141.html
View File

@ -1,37 +1,16 @@
<a name="cce_10_0141"></a><a name="cce_10_0141"></a>
<h1 class="topictitle1">CCE AI Suite (NVIDIA GPU)</h1>
<div id="body1552976392137"><div class="section" id="cce_10_0141__section26181722164712"><h4 class="sectiontitle">Introduction</h4><p id="cce_10_0141__p12273103844718">The CCE AI Suite (NVIDIA GPU) add-on is a device management add-on that supports GPUs in containers. If GPU nodes are used in the cluster, this add-on must be installed.</p>
<div id="body1552976392137"><div class="section" id="cce_10_0141__section26181722164712"><h4 class="sectiontitle">Introduction</h4><p id="cce_10_0141__p12273103844718">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.</p>
</div>
<div class="section" id="cce_10_0141__section3200193614201"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0141__ul1815672612156"><li id="cce_10_0141__li1715622613151">The driver to be downloaded must be a <span class="uicontrol" id="cce_10_0141__uicontrol113611965581"><b>.run</b></span> file.</li><li id="cce_10_0141__li8619191610138">Only NVIDIA Tesla drivers are supported, not GRID drivers.</li><li id="cce_10_0141__li94891186187">When installing or reinstalling the add-on, ensure that the driver download address is correct and accessible. CCE does not verify the address validity.</li><li id="cce_10_0141__li1843718111247">The gpu-beta add-on only enables you to download the driver and execute the installation script. The add-on status only indicates that how the add-on is running, not whether the driver is successfully installed.</li><li id="cce_10_0141__li39662291701">CCE does not guarantee the compatibility between the GPU driver version and the CDUA library version of your application. You need to check the compatibility by yourself.</li><li id="cce_10_0141__li938214018284">If a GPU driver has been added to a custom OS image, CCE cannot ensure that the GPU driver is compatible with other GPU components such as the monitoring components used in CCE.</li></ul>
<div class="section" id="cce_10_0141__section3200193614201"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0141__ul1815672612156"><li id="cce_10_0141__li1715622613151">The driver to be downloaded must be a <span class="uicontrol" id="cce_10_0141__uicontrol113611965581"><b>.run</b></span> file.</li><li id="cce_10_0141__li8619191610138">Only NVIDIA Tesla drivers are supported, not GRID drivers.</li><li id="cce_10_0141__li94891186187">When installing or reinstalling the add-on, ensure that the driver download address is correct and accessible. CCE does not verify the address validity.</li><li id="cce_10_0141__li1843718111247">The gpu-beta add-on only enables you to download the driver and execute the installation script. The add-on status only indicates that how the add-on is running, not whether the driver is successfully installed.</li><li id="cce_10_0141__li39662291701">CCE does not guarantee the compatibility between the GPU driver version and the CDUA library version of your application. You need to check the compatibility by yourself.</li><li id="cce_10_0141__li938214018284">If a custom OS image has had a a GPU driver installed, CCE cannot ensure that the GPU driver is compatible with other GPU components such as the monitoring components used in CCE.</li></ul>
</div>
<div class="section" id="cce_10_0141__section14115341020"><h4 class="sectiontitle">Installing the Add-on</h4><ol id="cce_10_0141__ol2011434603"><li id="cce_10_0141__li6116341702"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0141__uicontrol06719319429"><b>Add-ons</b></span> in the navigation pane, locate <strong id="cce_10_0141__b46461289382"></strong><strong id="cce_10_0141__b7674112917382"></strong><strong id="cce_10_0141__b1812733117389">CCE AI Suite (NVIDIA GPU)</strong> on the right, and click <strong id="cce_10_0141__b15691331164219">Install</strong>.</span></li><li id="cce_10_0141__li178033014157"><span>On the <strong id="cce_10_0141__b1186715186499">Install Add-on</strong> page, configure the specifications.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0141__table924319911495" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Add-on configuration</caption><thead align="left"><tr id="cce_10_0141__row42442974913"><th align="left" class="cellrowborder" valign="top" width="24%" id="mcps1.3.3.2.2.2.1.2.3.1.1"><p id="cce_10_0141__p17244793496">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="76%" id="mcps1.3.3.2.2.2.1.2.3.1.2"><p id="cce_10_0141__p42441596495">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="cce_10_0141__row1137014404511"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.3.2.2.2.1.2.3.1.1 "><p id="cce_10_0141__p11370134095120">Add-on Specifications</p>
</td>
<td class="cellrowborder" valign="top" width="76%" headers="mcps1.3.3.2.2.2.1.2.3.1.2 "><p id="cce_10_0141__p95819241166">Select <span class="uicontrol" id="cce_10_0141__uicontrol432385334213"><b>Default</b></span> or <strong id="cce_10_0141__b2323165314218">Custom</strong>.</p>
</td>
</tr>
<tr id="cce_10_0141__row4370840165119"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.3.2.2.2.1.2.3.1.1 "><p id="cce_10_0141__p937054045117">Containers</p>
</td>
<td class="cellrowborder" valign="top" width="76%" headers="mcps1.3.3.2.2.2.1.2.3.1.2 "><p id="cce_10_0141__p17860202182012">CPU and memory quotas of the container allowed for the selected add-on specifications.</p>
<p id="cce_10_0141__p1437014065110">If you select <strong id="cce_10_0141__b72306249010416">Custom</strong>, you can adjust the container specifications as required.</p>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="cce_10_0141__li6911527161717"><span>Configure the add-on parameters.</span><p><ul id="cce_10_0141__en-us_topic_0000001504601234_ul1129963191314"><li id="cce_10_0141__en-us_topic_0000001504601234_li1554416474556"><strong id="cce_10_0141__b1374472644917">NVIDIA Driver</strong>: Enter the link for downloading the NVIDIA driver. All GPU nodes in the cluster will use this driver.<div class="notice" id="cce_10_0141__en-us_topic_0000001504601234_note16659111785119"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="cce_10_0141__en-us_topic_0000001504601234_ul1765951765114"><li id="cce_10_0141__en-us_topic_0000001504601234_li1865921713514">If the download link is a public network address, for example, <strong id="cce_10_0141__b1680185713186">https://us.download.nvidia.com/tesla/470.103.01/NVIDIA-Linux-x86_64-470.103.01.run</strong>, bind an EIP to each GPU node. For details about how to obtain the driver link, see <a href="cce_10_0141.html#cce_10_0141__section95451728192112">Obtaining the Driver Link from Public Network</a>.</li><li id="cce_10_0141__en-us_topic_0000001504601234_li665981712519">If the download link is an OBS URL, you do not need to bind an EIP to GPU nodes. For details about how to obtain the driver link, see <a href="cce_10_0141.html#cce_10_0141__section14922133914508">Obtaining the Driver Link from OBS</a>.</li><li id="cce_10_0141__en-us_topic_0000001504601234_li17659317165114">Ensure that the NVIDIA driver version matches the GPU node.</li><li id="cce_10_0141__en-us_topic_0000001504601234_li76591517175120">After the driver version is changed, restart the node for the change to take effect.</li></ul>
<div class="section" id="cce_10_0141__section14115341020"><h4 class="sectiontitle">Installing the Add-on</h4><ol id="cce_10_0141__ol2011434603"><li id="cce_10_0141__li6116341702"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0141__b1277955205319"><span id="cce_10_0141__text77103384818">Add-ons</span></strong> in the navigation pane, locate <strong id="cce_10_0141__b182778556536">CCE AI Suite (NVIDIA GPU)</strong> on the right, and click <strong id="cce_10_0141__b52776553537">Install</strong>.</span></li><li id="cce_10_0141__li6911527161717"><span>Configure the add-on parameters.</span><p><ul id="cce_10_0141__en-us_topic_0000001504601234_ul1129963191314"><li id="cce_10_0141__en-us_topic_0000001504601234_li1554416474556"><strong id="cce_10_0141__b1374472644917">NVIDIA Driver</strong>: Enter the link for downloading the NVIDIA driver. All GPU nodes in the cluster will use this driver.<div class="notice" id="cce_10_0141__en-us_topic_0000001504601234_note16659111785119"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="cce_10_0141__en-us_topic_0000001504601234_ul1765951765114"><li id="cce_10_0141__en-us_topic_0000001504601234_li1865921713514">If the download link is a public network address, for example, <strong id="cce_10_0141__b1680185713186">https://us.download.nvidia.com/tesla/470.103.01/NVIDIA-Linux-x86_64-470.103.01.run</strong>, bind an EIP to each GPU node. For details about how to obtain the driver link, see <a href="cce_10_0141.html#cce_10_0141__section95451728192112">Obtaining the Driver Link from Public Network</a>.</li><li id="cce_10_0141__en-us_topic_0000001504601234_li665981712519">If the download link is an OBS URL, you do not need to bind an EIP to GPU nodes. For details about how to obtain the driver link, see <a href="cce_10_0141.html#cce_10_0141__section14922133914508">Obtaining the Driver Link from OBS</a>.</li><li id="cce_10_0141__en-us_topic_0000001504601234_li17659317165114">Ensure that the NVIDIA driver version matches the GPU node. </li><li id="cce_10_0141__en-us_topic_0000001504601234_li76591517175120">After the driver version is changed, restart the node for the change to take effect.</li></ul>
</div></div>
</li><li id="cce_10_0141__en-us_topic_0000001504601234_li073402311310"><strong id="cce_10_0141__b1660772412307">Driver Selection</strong>: If you do not want all GPU nodes in a cluster to use the same driver, CCE allows you to install a different GPU driver for each node pool.<div class="note" id="cce_10_0141__en-us_topic_0000001504601234_note6635813585"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0141__en-us_topic_0000001504601234_ul1883717714586"><li id="cce_10_0141__en-us_topic_0000001504601234_li14837117155815">The add-on installs the driver with the version specified by the node pool. The driver takes effect only for new pool nodes.</li><li id="cce_10_0141__en-us_topic_0000001504601234_li48389715582">After the driver version of new nodes is updated, restart the nodes for the update to take effect. The driver version cannot be updated for non-new nodes.</li></ul>
</li><li id="cce_10_0141__en-us_topic_0000001504601234_li073402311310"><strong id="cce_10_0141__b1660772412307">Driver Selection</strong>: If you do not want all GPU nodes in a cluster to use the same driver, CCE allows you to install a different GPU driver for each node pool.<div class="note" id="cce_10_0141__en-us_topic_0000001504601234_note6635813585"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0141__en-us_topic_0000001504601234_ul1883717714586"><li id="cce_10_0141__en-us_topic_0000001504601234_li14837117155815">The add-on installs the driver with the version specified by the node pool. The driver takes effect only for new pool nodes.</li><li id="cce_10_0141__en-us_topic_0000001504601234_li48389715582">After the driver version is updated, it takes effect on the nodes newly added to the node pool. Existing nodes must restart to apply the changes.</li></ul>
</div></div>
</li></ul>
</p></li><li id="cce_10_0141__li151113411011"><span>Click <strong id="cce_10_0141__b1543017210355">Install</strong>.</span><p><div class="note" id="cce_10_0141__note17799123474219"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0141__p107362261984">Uninstalling the add-on will clear the GPU driver on the nodes. As a result, GPU pods newly scheduled to the nodes cannot run properly, but running GPU pods are not affected.</p>
</p></li><li id="cce_10_0141__li151113411011"><span>Click <strong id="cce_10_0141__b1543017210355">Install</strong>.</span><p><div class="note" id="cce_10_0141__note17799123474219"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0141__p107362261984">If the add-on is uninstalled, GPU pods newly scheduled to the nodes cannot run properly, but GPU pods already running on the nodes will not be affected.</p>
</div></div>
</p></li></ol>
</div>
@ -44,11 +23,11 @@ cd /usr/local/nvidia/bin &amp;&amp; ./nvidia-smi</pre>
</li><li id="cce_10_0141__li186276437397">Container:<pre class="screen" id="cce_10_0141__screen11900202601214">cd /usr/local/nvidia/bin &amp;&amp; ./nvidia-smi</pre>
</li></ul>
<p id="cce_10_0141__p7254950101912">If GPU information is returned, the device is available and the add-on has been installed.</p>
<p id="cce_10_0141__p78452015208"><span><img id="cce_10_0141__image5372171217135" src="en-us_image_0000001647417812.png"></span></p>
<p id="cce_10_0141__p78452015208"><span><img id="cce_10_0141__image5372171217135" src="en-us_image_0000001750791684.png"></span></p>
</div>
<div class="section" id="cce_10_0141__section95451728192112"><a name="cce_10_0141__section95451728192112"></a><a name="section95451728192112"></a><h4 class="sectiontitle">Obtaining the Driver Link from Public Network</h4><ol id="cce_10_0141__ol1138125974915"><li id="cce_10_0141__li19138125912498"><span>Log in to the CCE console.</span></li><li id="cce_10_0141__li111387599493"><span>Click <strong id="cce_10_0141__b7473141016405">Create Node</strong> and select the GPU node to be created in the <strong id="cce_10_0141__b13473161014016">Specifications</strong> area. The GPU card model of the node is displayed in the lower part of the page.</span></li></ol><ol start="3" id="cce_10_0141__ol195031456154814"><li id="cce_10_0141__li165032056184815"><span>Visit <em id="cce_10_0141__i2070996145418"><a href="https://www.nvidia.com/Download/Find.aspx?lang=en" target="_blank" rel="noopener noreferrer">https://www.nvidia.com/Download/Find.aspx?lang=en</a></em>.</span></li><li id="cce_10_0141__li16232124410505"><span>Select the driver information on the <span class="uicontrol" id="cce_10_0141__uicontrol1291212498541"><b>NVIDIA Driver Downloads</b></span> page, as shown in <a href="#cce_10_0141__fig11696366517">Figure 1</a>. <span class="uicontrol" id="cce_10_0141__uicontrol1650164444518"><b>Operating System</b></span> must be <strong id="cce_10_0141__b10981947121910">Linux 64-bit</strong>.</span><p><div class="fignone" id="cce_10_0141__fig11696366517"><a name="cce_10_0141__fig11696366517"></a><a name="fig11696366517"></a><span class="figcap"><b>Figure 1 </b>Setting parameters</span><br><span><img id="cce_10_0141__image18514163918398" src="en-us_image_0000001695896741.png"></span></div>
</p></li><li id="cce_10_0141__li1682301014493"><span>After confirming the driver information, click <span class="uicontrol" id="cce_10_0141__uicontrol1411775314551"><b>SEARCH</b></span>. A page is displayed, showing the driver information, as shown in <a href="#cce_10_0141__fig7873421145213">Figure 2</a>. Click <span class="uicontrol" id="cce_10_0141__uicontrol163131533185618"><b>DOWNLOAD</b></span>.</span><p><div class="fignone" id="cce_10_0141__fig7873421145213"><a name="cce_10_0141__fig7873421145213"></a><a name="fig7873421145213"></a><span class="figcap"><b>Figure 2 </b>Driver information</span><br><span><img id="cce_10_0141__image6928629163818" src="en-us_image_0000001647577072.png"></span></div>
</p></li><li id="cce_10_0141__li624514474513"><span>Obtain the driver link in either of the following ways:</span><p><ul id="cce_10_0141__ul18225815213"><li id="cce_10_0141__li68351817115313">Method 1: As shown in <a href="#cce_10_0141__fig5901194614534">Figure 3</a>, find <em id="cce_10_0141__i1537731713469">url=/tesla/470.103.01/NVIDIA-Linux-x86_64-470.103.01.run</em> in the browser address box. Then, supplement it to obtain the driver link <a href="https://us.download.nvidia.com/tesla/470.103.01/NVIDIA-Linux-x86_64-470.103.01.run" target="_blank" rel="noopener noreferrer">https://us.download.nvidia.com/tesla/470.103.01/NVIDIA-Linux-x86_64-470.103.01.run</a>. By using this method, you must bind an EIP to each GPU node.</li><li id="cce_10_0141__li193423205231">Method 2: As shown in <a href="#cce_10_0141__fig5901194614534">Figure 3</a>, click <span class="uicontrol" id="cce_10_0141__uicontrol1435254915542"><b>AGREE &amp; DOWNLOAD</b></span> to download the driver. Then, upload the driver to OBS and record the OBS URL. By using this method, you do not need to bind an EIP to GPU nodes.<div class="fignone" id="cce_10_0141__fig5901194614534"><a name="cce_10_0141__fig5901194614534"></a><a name="fig5901194614534"></a><span class="figcap"><b>Figure 3 </b>Obtaining the link</span><br><span><img id="cce_10_0141__image293362819366" src="en-us_image_0000001647577080.png"></span></div>
<div class="section" id="cce_10_0141__section95451728192112"><a name="cce_10_0141__section95451728192112"></a><a name="section95451728192112"></a><h4 class="sectiontitle">Obtaining the Driver Link from Public Network</h4><ol id="cce_10_0141__ol1138125974915"><li id="cce_10_0141__li19138125912498"><span>Log in to the CCE console.</span></li><li id="cce_10_0141__li111387599493"><span>Click <strong id="cce_10_0141__b7473141016405">Create Node</strong> and select the GPU node to be created in the <strong id="cce_10_0141__b13473161014016">Specifications</strong> area. The GPU card model of the node is displayed in the lower part of the page.</span></li></ol><ol start="3" id="cce_10_0141__ol195031456154814"><li id="cce_10_0141__li165032056184815"><span>Visit <em id="cce_10_0141__i2070996145418"><a href="https://www.nvidia.com/Download/Find.aspx?lang=en" target="_blank" rel="noopener noreferrer">https://www.nvidia.com/Download/Find.aspx?lang=en</a></em>.</span></li><li id="cce_10_0141__li16232124410505"><span>Select the driver information on the <span class="uicontrol" id="cce_10_0141__uicontrol1291212498541"><b>NVIDIA Driver Downloads</b></span> page, as shown in <a href="#cce_10_0141__fig11696366517">Figure 1</a>. <span class="uicontrol" id="cce_10_0141__uicontrol1650164444518"><b>Operating System</b></span> must be <strong id="cce_10_0141__b10981947121910">Linux 64-bit</strong>.</span><p><div class="fignone" id="cce_10_0141__fig11696366517"><a name="cce_10_0141__fig11696366517"></a><a name="fig11696366517"></a><span class="figcap"><b>Figure 1 </b>Setting parameters</span><br><span><img id="cce_10_0141__image18514163918398" src="en-us_image_0000001750950592.png"></span></div>
</p></li><li id="cce_10_0141__li1682301014493"><span>After confirming the driver information, click <span class="uicontrol" id="cce_10_0141__uicontrol1411775314551"><b>SEARCH</b></span>. A page is displayed, showing the driver information, as shown in <a href="#cce_10_0141__fig7873421145213">Figure 2</a>. Click <span class="uicontrol" id="cce_10_0141__uicontrol163131533185618"><b>DOWNLOAD</b></span>.</span><p><div class="fignone" id="cce_10_0141__fig7873421145213"><a name="cce_10_0141__fig7873421145213"></a><a name="fig7873421145213"></a><span class="figcap"><b>Figure 2 </b>Driver information</span><br><span><img id="cce_10_0141__image6928629163818" src="en-us_image_0000001797871377.png"></span></div>
</p></li><li id="cce_10_0141__li624514474513"><span>Obtain the driver link in either of the following ways:</span><p><ul id="cce_10_0141__ul18225815213"><li id="cce_10_0141__li68351817115313">Method 1: As shown in <a href="#cce_10_0141__fig5901194614534">Figure 3</a>, find <em id="cce_10_0141__i1537731713469">url=/tesla/470.103.01/NVIDIA-Linux-x86_64-470.103.01.run</em> in the browser address box. Then, supplement it to obtain the driver link <a href="https://us.download.nvidia.com/tesla/470.103.01/NVIDIA-Linux-x86_64-470.103.01.run" target="_blank" rel="noopener noreferrer">https://us.download.nvidia.com/tesla/470.103.01/NVIDIA-Linux-x86_64-470.103.01.run</a>. By using this method, you must bind an EIP to each GPU node.</li><li id="cce_10_0141__li193423205231">Method 2: As shown in <a href="#cce_10_0141__fig5901194614534">Figure 3</a>, click <span class="uicontrol" id="cce_10_0141__uicontrol1435254915542"><b>AGREE &amp; DOWNLOAD</b></span> to download the driver. Then, upload the driver to OBS and record the OBS URL. By using this method, you do not need to bind an EIP to GPU nodes.<div class="fignone" id="cce_10_0141__fig5901194614534"><a name="cce_10_0141__fig5901194614534"></a><a name="fig5901194614534"></a><span class="figcap"><b>Figure 3 </b>Obtaining the link</span><br><span><img id="cce_10_0141__image293362819366" src="en-us_image_0000001750950604.png"></span></div>
</li></ul>
</p></li></ol>
</div>
@ -57,19 +36,19 @@ cd /usr/local/nvidia/bin &amp;&amp; ./nvidia-smi</pre>
</p></li><li id="cce_10_0141__li32141341144910"><span>In the bucket list, click a bucket name, and then the <strong id="cce_10_0141__b162847101346">Overview</strong> page of the bucket is displayed.</span></li><li id="cce_10_0141__li644534394917"><span>In the navigation pane, choose <strong id="cce_10_0141__b1431216143510">Objects</strong>.</span></li><li id="cce_10_0141__li3518125314429"><span>Select the name of the target object and copy the driver link on the object details page.</span></li></ol>
</div>
<div class="section" id="cce_10_0141__section0377457163618"><h4 class="sectiontitle">Components</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0141__table1965341035819" frame="border" border="1" rules="all"><caption><b>Table 2 </b>GPU component</caption><thead align="left"><tr id="cce_10_0141__row1565319102582"><th align="left" class="cellrowborder" valign="top" width="19%" id="mcps1.3.7.2.2.4.1.1"><p id="cce_10_0141__p14653141018584">Container Component</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0141__table1965341035819" frame="border" border="1" rules="all"><caption><b>Table 1 </b>GPU component</caption><thead align="left"><tr id="cce_10_0141__row1565319102582"><th align="left" class="cellrowborder" valign="top" width="19%" id="mcps1.3.7.2.2.4.1.1"><p id="cce_10_0141__p14653141018584">Component</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="63%" id="mcps1.3.7.2.2.4.1.2"><p id="cce_10_0141__p065391025820">Description</p>
<th align="left" class="cellrowborder" valign="top" width="60%" id="mcps1.3.7.2.2.4.1.2"><p id="cce_10_0141__p065391025820">Description</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="18%" id="mcps1.3.7.2.2.4.1.3"><p id="cce_10_0141__p5653111015587">Resource Type</p>
<th align="left" class="cellrowborder" valign="top" width="21%" id="mcps1.3.7.2.2.4.1.3"><p id="cce_10_0141__p5653111015587">Resource Type</p>
</th>
</tr>
</thead>
<tbody><tr id="cce_10_0141__row872889165919"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.7.2.2.4.1.1 "><p id="cce_10_0141__p1319715501426">nvidia-driver-installer</p>
</td>
<td class="cellrowborder" valign="top" width="63%" headers="mcps1.3.7.2.2.4.1.2 "><p id="cce_10_0141__p1455113183920">Used for installing an NVIDIA driver on GPU nodes.</p>
<td class="cellrowborder" valign="top" width="60%" headers="mcps1.3.7.2.2.4.1.2 "><p id="cce_10_0141__p1455113183920">Used for installing an NVIDIA driver on GPU nodes.</p>
</td>
<td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.7.2.2.4.1.3 "><p id="cce_10_0141__p772869115917">DaemonSet</p>
<td class="cellrowborder" valign="top" width="21%" headers="mcps1.3.7.2.2.4.1.3 "><p id="cce_10_0141__p772869115917">DaemonSet</p>
</td>
</tr>
</tbody>

6
docs/cce/umn/cce_10_0142.html
View File

@ -2,12 +2,12 @@
<h1 class="topictitle1">NodePort</h1>
<div id="body1553224785332"><div class="section" id="cce_10_0142__section13654155944916"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0142__p028915126124">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 (ClusterIP) of the cluster. When clients outside the cluster access &lt;NodeIP&gt;:&lt;NodePort&gt;, the traffic will be forwarded to the target pod through the ClusterIP of the NodePort Service.</p>
<div class="fignone" id="cce_10_0142__fig6819133414131"><span class="figcap"><b>Figure 1 </b>NodePort access</span><br><span><img id="cce_10_0142__image10510139711" src="en-us_image_0000001647417292.png"></span></div>
<div class="fignone" id="cce_10_0142__fig6819133414131"><span class="figcap"><b>Figure 1 </b>NodePort access</span><br><span><img id="cce_10_0142__image10510139711" src="en-us_image_0000001797870765.png"></span></div>
</div>
<div class="section" id="cce_10_0142__section8501151104219"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0142__ul1685519569431"><li id="cce_10_0142__li1585575616436">By default, a NodePort Service is accessed within a VPC. To use an EIP to access a NodePort Service through public networks, bind an EIP to the node in the cluster in advance.</li><li id="cce_10_0142__li128551156114310">After a Service is created, if the affinity setting is switched from the cluster level to the node level, the connection tracing table will not be cleared. Do not modify the Service affinity setting after the Service is created. To modify it, create a Service again.</li><li id="cce_10_0142__li62831358182017">CCE Turbo clusters support only cluster-level service affinity.</li><li id="cce_10_0142__li217783916207">In VPC network mode, when container A is published through a NodePort service and the service affinity is set to the node level (that is, <strong id="cce_10_0142__b1291203218520">externalTrafficPolicy</strong> is set to <strong id="cce_10_0142__b11911632135217">local</strong>), container B deployed on the same node cannot access container A through the node IP address and NodePort service.</li><li id="cce_10_0142__li14613571073">When a NodePort service is created in a cluster of v1.21.7 or later, the port on the node is not displayed using <strong id="cce_10_0142__b13256143512525">netstat</strong> by default. If the cluster forwarding mode is <strong id="cce_10_0142__b42563350522">iptables</strong>, run the <strong id="cce_10_0142__b62561135115212">iptables -t nat -L</strong> command to view the port. If the cluster forwarding mode is <strong id="cce_10_0142__b925763515218">IPVS</strong>, run the <strong id="cce_10_0142__b23917223106">ipvsadm -Ln</strong> command to view the port.</li></ul>
</div>
<div class="section" id="cce_10_0142__section1325012312139"><h4 class="sectiontitle">Creating a NodePort Service</h4><ol id="cce_10_0142__ol751935681319"><li id="cce_10_0142__li41731123658"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0142__li1651955651312"><span>Choose <strong id="cce_10_0142__b59268208277">Networking</strong> in the navigation pane and click <strong id="cce_10_0142__b59321820182716">Create Service</strong> in the upper right corner.</span></li><li id="cce_10_0142__li185190567138"><span>Set intra-cluster access parameters.</span><p><ul id="cce_10_0142__ul4446314017144"><li id="cce_10_0142__li6462394317144"><strong id="cce_10_0142__b845613814287">Service Name</strong>: Specify a Service name, which can be the same as the workload name.</li><li id="cce_10_0142__li89543531070"><strong id="cce_10_0142__b106597277362">Service Type</strong>: Select <span class="uicontrol" id="cce_10_0142__uicontrol5666142710366"><b>NodePort</b></span>.</li><li id="cce_10_0142__li4800017144"><strong id="cce_10_0142__b1263193014367">Namespace</strong>: Namespace to which the workload belongs.</li><li id="cce_10_0142__li1758110116149"><strong id="cce_10_0142__b38118349367">Service Affinity</strong>: For details, see <a href="cce_10_0249.html#cce_10_0249__section18134208069">externalTrafficPolicy (Service Affinity)</a>.<ul id="cce_10_0142__ul158101161412"><li id="cce_10_0142__li105815113141"><strong id="cce_10_0142__b2674164185210">Cluster level</strong>: The IP addresses and access ports of all nodes in a cluster can access the workload associated with the Service. Service access will cause performance loss due to route redirection, and the source IP address of the client cannot be obtained.</li><li id="cce_10_0142__li185817117145"><strong id="cce_10_0142__b465617445525">Node level</strong>: Only the IP address and access port of the node where the workload is located can access the workload associated with the Service. Service access will not cause performance loss due to route redirection, and the source IP address of the client can be obtained.</li></ul>
</li><li id="cce_10_0142__li43200017144"><strong id="cce_10_0142__b519871474713">Selector</strong>: Add a label and click <strong id="cce_10_0142__b0198191416479">Confirm</strong>. A Service selects a pod based on the added label. You can also click <strong id="cce_10_0142__b354965233619">Reference Workload Label</strong> to reference the label of an existing workload. In the dialog box that is displayed, select a workload and click <strong id="cce_10_0142__b16550125293615">OK</strong>.</li><li id="cce_10_0142__li388800117144"><strong id="cce_10_0142__b38881739133512">Port</strong><ul id="cce_10_0142__ul3499201217144"><li id="cce_10_0142__li4649265917144"><strong id="cce_10_0142__b28899114374">Protocol</strong>: protocol used by the Service.</li><li id="cce_10_0142__li353122153610"><strong id="cce_10_0142__b1852318551688">Service Port</strong>: port used by the Service. The port number ranges from 1 to 65535.</li><li id="cce_10_0142__li1578074917144"><strong id="cce_10_0142__b19416443712">Container Port</strong>: port on which the workload listens. For example, Nginx uses port 80 by default.</li><li id="cce_10_0142__li780902117144"><strong id="cce_10_0142__b11763931199">Node Port</strong>: You are advised to select <strong id="cce_10_0142__b1198741292">Auto</strong>. You can also specify a port. The default port ranges from 30000 to 32767.</li></ul>
<div class="section" id="cce_10_0142__section1325012312139"><h4 class="sectiontitle">Creating a NodePort Service</h4><ol id="cce_10_0142__ol751935681319"><li id="cce_10_0142__li41731123658"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0142__li1651955651312"><span>In the navigation pane, choose <strong id="cce_10_0142__b169702128151"><span id="cce_10_0142__text9765124722315">Services &amp; Ingresses</span></strong>. In the upper right corner, click <span class="uicontrol" id="cce_10_0142__uicontrol69701128153"><b>Create Service</b></span>.</span></li><li id="cce_10_0142__li185190567138"><span>Set intra-cluster access parameters.</span><p><ul id="cce_10_0142__ul4446314017144"><li id="cce_10_0142__li6462394317144"><strong id="cce_10_0142__b845613814287">Service Name</strong>: Specify a Service name, which can be the same as the workload name.</li><li id="cce_10_0142__li89543531070"><strong id="cce_10_0142__b106597277362">Service Type</strong>: Select <span class="uicontrol" id="cce_10_0142__uicontrol5666142710366"><b>NodePort</b></span>.</li><li id="cce_10_0142__li4800017144"><strong id="cce_10_0142__b1263193014367">Namespace</strong>: Namespace to which the workload belongs.</li><li id="cce_10_0142__li1758110116149"><strong id="cce_10_0142__b38118349367">Service Affinity</strong>: For details, see <a href="cce_10_0249.html#cce_10_0249__section18134208069">externalTrafficPolicy (Service Affinity)</a>.<ul id="cce_10_0142__ul158101161412"><li id="cce_10_0142__li105815113141"><strong id="cce_10_0142__b2674164185210">Cluster level</strong>: The IP addresses and access ports of all nodes in a cluster can access the workload associated with the Service. Service access will cause performance loss due to route redirection, and the source IP address of the client cannot be obtained.</li><li id="cce_10_0142__li185817117145"><strong id="cce_10_0142__b465617445525">Node level</strong>: Only the IP address and access port of the node where the workload is located can access the workload associated with the Service. Service access will not cause performance loss due to route redirection, and the source IP address of the client can be obtained.</li></ul>
</li><li id="cce_10_0142__li43200017144"><strong id="cce_10_0142__b2600143835813">Selector</strong>: Add a label and click <strong id="cce_10_0142__b260020382582">Confirm</strong>. A Service selects a pod based on the added label. You can also click <strong id="cce_10_0142__b354965233619">Reference Workload Label</strong> to reference the label of an existing workload. In the dialog box that is displayed, select a workload and click <strong id="cce_10_0142__b16550125293615">OK</strong>.</li><li id="cce_10_0142__li388800117144"><strong id="cce_10_0142__b451552415715">Port Settings</strong><ul id="cce_10_0142__ul3499201217144"><li id="cce_10_0142__li4649265917144"><strong id="cce_10_0142__b28899114374">Protocol</strong>: protocol used by the Service.</li><li id="cce_10_0142__li353122153610"><strong id="cce_10_0142__b1852318551688">Service Port</strong>: port used by the Service. The port number ranges from 1 to 65535.</li><li id="cce_10_0142__li1578074917144"><strong id="cce_10_0142__b19416443712">Container Port</strong>: port on which the workload listens. For example, Nginx uses port 80 by default.</li><li id="cce_10_0142__li780902117144"><strong id="cce_10_0142__b11763931199">Node Port</strong>: You are advised to select <strong id="cce_10_0142__b1198741292">Auto</strong>. You can also specify a port. The default port ranges from 30000 to 32767.</li></ul>
</li></ul>
</p></li><li id="cce_10_0142__li552017569135"><span>Click <strong id="cce_10_0142__b1012031216378">OK</strong>.</span></li></ol>
</div>

2
docs/cce/umn/cce_10_0144.html
View File

@ -42,7 +42,7 @@ to do port forwarding: socat not found.
Error: cannot connect to Tiller</pre>
<p id="cce_10_0144__en-us_topic_0226102212_en-us_topic_0179003017_p13666115403">The preceding information is displayed because the socat is not installed. Run the following command to install the socat:</p>
<pre class="screen" id="cce_10_0144__screen16761841183811">yum install socat -y</pre>
</li><li id="cce_10_0144__li188055156179">When you run the <strong id="cce_10_0144__b1884492273316">yum install socat –y</strong> command on a node running EulerOS 2.9 , if the following error message is displayed:<pre class="screen" id="cce_10_0144__screen13913115313819">No match for argument: socat
</li><li id="cce_10_0144__li188055156179">When you run the <strong id="cce_10_0144__b648116915353">yum install socat –y</strong> command on a node running EulerOS 2.9, the following error message is displayed:<pre class="screen" id="cce_10_0144__screen13913115313819">No match for argument: socat
Error: Unable to find a match: socat</pre>
<p id="cce_10_0144__p15706616131711">The node image does not contain socat. In this case, manually download the RPM chart and run the following command to install it (replace the RPM chart name with the actual one):</p>
<pre class="screen" id="cce_10_0144__screen20151457123819">rpm -i socat-1.7.3.2-8.oe1.x86_64.rpm</pre>

12
docs/cce/umn/cce_10_0146.html
View File

@ -33,7 +33,7 @@
</td>
<td class="cellrowborder" valign="top" width="78%" headers="mcps1.3.3.3.2.4.2.2.3.1.2 "><p id="cce_10_0146__p1678472115013">Describes configuration parameters required by templates.</p>
<div class="notice" id="cce_10_0146__note11415171194911"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><p id="cce_10_0146__p394216481648">Make sure that the image address set in the <strong id="cce_10_0146__b169837156417">values.yaml</strong> file is the same as the image address in the container image repository. Otherwise, an exception occurs when you create a workload, and the system displays a message indicating that the image fails to be pulled.</p>
<p id="cce_10_0146__p04177113498">To obtain the image address, perform the following operations: Log in to the CCE console. In the navigation pane, choose <strong id="cce_10_0146__b860412174116">Image Repository</strong> to access the SWR console. Choose <strong id="cce_10_0146__b10171926114117">My Images</strong> &gt; <strong id="cce_10_0146__b12372684119">Private Images</strong> and click the name of the uploaded image. On the <strong id="cce_10_0146__b223726104111">Image Tags</strong> tab page, obtain the image address from the pull command. You can click <span><img id="cce_10_0146__image292113414153" src="en-us_image_0000001647576684.png"></span> to copy the command in the <strong id="cce_10_0146__b723192619418">Image Pull Command</strong> column.</p>
<p id="cce_10_0146__p04177113498">To obtain the image address, perform the following operations: Log in to the CCE console. In the navigation pane, choose <strong id="cce_10_0146__b860412174116">Image Repository</strong> to access the SWR console. Choose <strong id="cce_10_0146__b10171926114117">My Images</strong> &gt; <strong id="cce_10_0146__b12372684119">Private Images</strong> and click the name of the uploaded image. On the <strong id="cce_10_0146__b223726104111">Image Tags</strong> tab page, obtain the image address from the pull command. You can click <span><img id="cce_10_0146__image292113414153" src="en-us_image_0000001797909977.png"></span> to copy the command in the <strong id="cce_10_0146__b723192619418">Image Pull Command</strong> column.</p>
</div></div>
</td>
</tr>
@ -60,11 +60,11 @@
</div>
</li></ul>
</div>
<div class="section" id="cce_10_0146__section62601733171011"><h4 class="sectiontitle">Uploading a Chart</h4><ol id="cce_10_0146__o0ec219910b544b1a8ea6cd99545eb9c9"><li id="cce_10_0146__li6330203615298"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0146__b95961354471">Charts</strong> in the navigation pane and click <strong id="cce_10_0146__b65968354474">Upload Chart</strong> in the upper right corner.</span></li><li id="cce_10_0146__l7d71632d3d0d46778da8db6da0c2d8be"><span>Click <strong id="cce_10_0146__b18533171414416">Select File</strong>, select the chart to be uploaded, and click <strong id="cce_10_0146__b453910145442">Upload</strong>.</span><p><div class="note" id="cce_10_0146__note1332512361214"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0146__p1132510366215">When you upload a chart, the naming rule of the OBS bucket is changed from cce-charts-{<em id="cce_10_0146__i91991329164411">region</em>}-{<strong id="cce_10_0146__b1220582915443">domain_name</strong>} to cce-charts-{<em id="cce_10_0146__i1520502912441">region</em>}-{<strong id="cce_10_0146__b62052297443">domain_id</strong>}. In the old naming rule, the system converts the <strong id="cce_10_0146__b9205132924411">domain_name</strong> value into a Base64 string and uses the first 63 characters. If you cannot find the chart in the OBS bucket with the new name, search for the bucket with the old name.</p>
<div class="section" id="cce_10_0146__section62601733171011"><h4 class="sectiontitle">Uploading a Chart</h4><ol id="cce_10_0146__o0ec219910b544b1a8ea6cd99545eb9c9"><li id="cce_10_0146__li6330203615298"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0146__b95961354471"><span id="cce_10_0146__text144134194612">App Templates</span></strong> in the navigation pane and click <strong id="cce_10_0146__b65968354474">Upload Chart</strong> in the upper right corner.</span></li><li id="cce_10_0146__l7d71632d3d0d46778da8db6da0c2d8be"><span>Click <strong id="cce_10_0146__b18533171414416">Select File</strong>, select the chart to be uploaded, and click <strong id="cce_10_0146__b453910145442">Upload</strong>.</span><p><div class="note" id="cce_10_0146__note1332512361214"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0146__p1132510366215">When you upload a chart, the naming rule of the OBS bucket is changed from cce-charts-{<em id="cce_10_0146__i91991329164411">region</em>}-{<strong id="cce_10_0146__b1220582915443">domain_name</strong>} to cce-charts-{<em id="cce_10_0146__i1520502912441">region</em>}-{<strong id="cce_10_0146__b62052297443">domain_id</strong>}. In the old naming rule, the system converts the <strong id="cce_10_0146__b9205132924411">domain_name</strong> value into a Base64 string and uses the first 63 characters. If you cannot find the chart in the OBS bucket with the new name, search for the bucket with the old name.</p>
</div></div>
</p></li></ol>
</div>
<div class="section" id="cce_10_0146__s94388d41fe234fba81844802bc682fb8"><h4 class="sectiontitle">Creating a Release</h4><ol id="cce_10_0146__o20585630b6dd4d15a7973999bed51640"><li id="cce_10_0146__li135815513542"><span>Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0146__b1383735115449">Charts</strong>.</span></li><li id="cce_10_0146__li1164182203613"><span>On the <span class="uicontrol" id="cce_10_0146__uicontrol1821864161814"><b>My Charts</b></span> tab page, click <span class="uicontrol" id="cce_10_0146__uicontrol1577535931912"><b>Install</b></span> of the target chart.</span></li><li id="cce_10_0146__l90a823bbc7b647b998ce344161a168f4"><span>Set workload installation parameters by referring to <a href="#cce_10_0146__t26bc1c499f114b5185e5edcf61e44d95">Table 2</a>.</span><p>
<div class="section" id="cce_10_0146__s94388d41fe234fba81844802bc682fb8"><h4 class="sectiontitle">Creating a Release</h4><ol id="cce_10_0146__o20585630b6dd4d15a7973999bed51640"><li id="cce_10_0146__li135815513542"><span>Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0146__b1383735115449"><span id="cce_10_0146__text1167002264619">App Templates</span></strong>.</span></li><li id="cce_10_0146__li1164182203613"><span>On the <span class="uicontrol" id="cce_10_0146__uicontrol1821864161814"><b>My Charts</b></span> tab page, click <span class="uicontrol" id="cce_10_0146__uicontrol1577535931912"><b>Install</b></span> of the target chart.</span></li><li id="cce_10_0146__l90a823bbc7b647b998ce344161a168f4"><span>Set workload installation parameters by referring to <a href="#cce_10_0146__t26bc1c499f114b5185e5edcf61e44d95">Table 2</a>.</span><p>
<div class="tablenoborder"><a name="cce_10_0146__t26bc1c499f114b5185e5edcf61e44d95"></a><a name="t26bc1c499f114b5185e5edcf61e44d95"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0146__t26bc1c499f114b5185e5edcf61e44d95" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Installation parameters</caption><thead align="left"><tr id="cce_10_0146__rbf609a3fcf2445d2b6d59cbcca7f75b3"><th align="left" class="cellrowborder" valign="top" width="23%" id="mcps1.3.5.2.3.2.1.2.3.1.1"><p id="cce_10_0146__a24b59ed54e3e49a7abefd7528912fb26">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="77%" id="mcps1.3.5.2.3.2.1.2.3.1.2"><p id="cce_10_0146__a48e24994d5e7491782edce936fd59c1a">Description</p>
@ -101,12 +101,12 @@
</p></li><li id="cce_10_0146__le625c1f421df4758b99f9184828926a9"><span>Click <span class="uicontrol" id="cce_10_0146__uicontrol67604016460"><b>Install</b></span>.</span><p><p id="cce_10_0146__p128679414295">On the <strong id="cce_10_0146__b377004011358">Releases</strong> tab page, you can view the installation status of the release.</p>
</p></li></ol>
</div>
<div class="section" id="cce_10_0146__section5324101171010"><h4 class="sectiontitle">Upgrading a Chart-based Workload</h4><ol id="cce_10_0146__ol1541655017447"><li id="cce_10_0146__li1869015203020"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0146__b1332619365361">Charts</strong> in the navigation pane and click the <strong id="cce_10_0146__b15333103663618">Releases</strong> tab.</span></li><li id="cce_10_0146__li9260155614447"><span>Click <strong id="cce_10_0146__b624761044718">Upgrade</strong> in the row where the desired workload resides and set the parameters for the workload.</span></li><li id="cce_10_0146__li1126255674414"><span>Select a chart version for <strong id="cce_10_0146__b420264371153445">Chart Version</strong>.</span></li><li id="cce_10_0146__li1126615644417"><span>Follow the prompts to modify the chart parameters. Click <strong id="cce_10_0146__b1224624192812">Upgrade</strong>, and then click <strong id="cce_10_0146__b2090164210284">Submit</strong>.</span></li><li id="cce_10_0146__li1327935644412"><span>Click <strong id="cce_10_0146__b824513662153516">Back to Release List</strong>. If the chart status changes to <strong id="cce_10_0146__b15735371333">Upgrade successful</strong>, the workload is successfully upgraded.</span></li></ol>
<div class="section" id="cce_10_0146__section5324101171010"><h4 class="sectiontitle">Upgrading a Chart-based Workload</h4><ol id="cce_10_0146__ol1541655017447"><li id="cce_10_0146__li1869015203020"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0146__b1332619365361"><span id="cce_10_0146__text1020012374467">App Templates</span></strong> in the navigation pane and click the <strong id="cce_10_0146__b15333103663618">Releases</strong> tab.</span></li><li id="cce_10_0146__li9260155614447"><span>Click <strong id="cce_10_0146__b624761044718">Upgrade</strong> in the row where the desired workload resides and set the parameters for the workload.</span></li><li id="cce_10_0146__li1126255674414"><span>Select a chart version for <strong id="cce_10_0146__b420264371153445">Chart Version</strong>.</span></li><li id="cce_10_0146__li1126615644417"><span>Follow the prompts to modify the chart parameters. Click <strong id="cce_10_0146__b1224624192812">Upgrade</strong>, and then click <strong id="cce_10_0146__b2090164210284">Submit</strong>.</span></li><li id="cce_10_0146__li1327935644412"><span>Click <strong id="cce_10_0146__b824513662153516">Back to Release List</strong>. If the chart status changes to <strong id="cce_10_0146__b15735371333">Upgrade successful</strong>, the workload is successfully upgraded.</span></li></ol>
</div>
<div class="section" id="cce_10_0146__section13251511191012"><h4 class="sectiontitle">Rolling Back a Chart-based Workload</h4><ol id="cce_10_0146__ol675012341451"><li id="cce_10_0146__li855613303328"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0146__b5287330381">Charts</strong> in the navigation pane and click the <strong id="cce_10_0146__b192885313382">Releases</strong> tab.</span></li><li id="cce_10_0146__li15170194294515"><span>Click <strong id="cce_10_0146__b42851336162919">More</strong> &gt; <strong id="cce_10_0146__b528583611291">Roll Back</strong> for the workload to be rolled back, select the workload version, and click <strong id="cce_10_0146__b14293173618298">Roll back</strong> <strong id="cce_10_0146__b4293436172920">to this version</strong>.</span><p><p id="cce_10_0146__p1917254212454">In the workload list, if the status is <strong id="cce_10_0146__b250435233917">Rollback successful</strong>, the workload is rolled back successfully.</p>
<div class="section" id="cce_10_0146__section13251511191012"><h4 class="sectiontitle">Rolling Back a Chart-based Workload</h4><ol id="cce_10_0146__ol675012341451"><li id="cce_10_0146__li855613303328"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0146__b5287330381"><span id="cce_10_0146__text733717447461">App Templates</span></strong> in the navigation pane and click the <strong id="cce_10_0146__b192885313382">Releases</strong> tab.</span></li><li id="cce_10_0146__li15170194294515"><span>Click <strong id="cce_10_0146__b42851336162919">More</strong> &gt; <strong id="cce_10_0146__b528583611291">Roll Back</strong> for the workload to be rolled back, select the workload version, and click <strong id="cce_10_0146__b14293173618298">Roll back</strong> <strong id="cce_10_0146__b4293436172920">to this version</strong>.</span><p><p id="cce_10_0146__p1917254212454">In the workload list, if the status is <strong id="cce_10_0146__b250435233917">Rollback successful</strong>, the workload is rolled back successfully.</p>
</p></li></ol>
</div>
<div class="section" id="cce_10_0146__section15325151161011"><h4 class="sectiontitle">Uninstalling a Chart-based Workload</h4><ol id="cce_10_0146__ol14516921124612"><li id="cce_10_0146__li1824033814320"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0146__b1272811919383">Charts</strong> in the navigation pane and click the <strong id="cce_10_0146__b27281918386">Releases</strong> tab.</span></li><li id="cce_10_0146__li33382293172417"><span>Click <strong id="cce_10_0146__b842352706172523">More</strong> &gt; <strong id="cce_10_0146__b842352706172527">Uninstall</strong> next to the release to be uninstalled, and click <strong id="cce_10_0146__b842352706172547">Yes</strong>. Exercise caution when performing this operation because releases cannot be restored after being uninstalled.</span></li></ol>
<div class="section" id="cce_10_0146__section15325151161011"><h4 class="sectiontitle">Uninstalling a Chart-based Workload</h4><ol id="cce_10_0146__ol14516921124612"><li id="cce_10_0146__li1824033814320"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0146__b1272811919383"><span id="cce_10_0146__text14894473461">App Templates</span></strong> in the navigation pane and click the <strong id="cce_10_0146__b27281918386">Releases</strong> tab.</span></li><li id="cce_10_0146__li33382293172417"><span>Click <strong id="cce_10_0146__b842352706172523">More</strong> &gt; <strong id="cce_10_0146__b842352706172527">Uninstall</strong> next to the release to be uninstalled, and click <strong id="cce_10_0146__b842352706172547">Yes</strong>. Exercise caution when performing this operation because releases cannot be restored after being uninstalled.</span></li></ol>
</div>
</div>
<div>

134
docs/cce/umn/cce_10_0150.html
View File

File diff suppressed because it is too large Load Diff

78
docs/cce/umn/cce_10_0151.html
View File

File diff suppressed because it is too large Load Diff

Some files were not shown because too many files have changed in this diff Show More