forked from docs/doc-exports
CCE UMN update 20250912 version
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com> Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com> Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
This commit is contained in:
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -47,7 +47,7 @@
|
||||
</li></ol>
|
||||
</div>
|
||||
<div class="section" id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_section0651319327"><h4 class="sectiontitle">Solution</h4><p id="CVE-2025-23266__en-us_topic_0000002394138741_p104132591912">Do not run an untrusted container image in the cluster before the vulnerabilities are fixed.</p>
|
||||
<p id="CVE-2025-23266__en-us_topic_0000002394138741_p93366712281">CCE will release a new version of the add-on to fix these vulnerabilities. For details, see <a href="cce_10_0141.html">CCE AI Suite (NVIDIA GPU) Release History</a>.</p>
|
||||
<p id="CVE-2025-23266__en-us_topic_0000002394138741_p93366712281">CCE has released a new version of the CCE AI Suite (NVIDIA GPU) add-on to fix these vulnerabilities. Upgrade the add-on to the fixed version. For details, see <a href="cce_10_0141.html">CCE AI Suite (NVIDIA GPU) Release History</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="CVE-2025-23266__en-us_topic_0000002394138741_en-us_topic_0000001159663171_section183061740102419"><h4 class="sectiontitle">Helpful Links</h4><p id="CVE-2025-23266__en-us_topic_0000002394138741_p174671921175419">NVIDIA Container Toolkit Security Bulletin: <a href="https://nvidia.custhelp.com/app/answers/detail/a_id/5659" target="_blank" rel="noopener noreferrer">https://nvidia.custhelp.com/app/answers/detail/a_id/5659</a></p>
|
||||
</div>
|
||||
|
||||
@ -8,7 +8,16 @@
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_01_0300__row153271013089"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p93277135815">2025-07-25</p>
|
||||
<tbody><tr id="cce_01_0300__row1055918131549"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p165591013125418">2025-09-12</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p8808123612548">Add:</p>
|
||||
<ul id="cce_01_0300__ul6808113614540"><li id="cce_01_0300__li1180893615416">Added <a href="cce_bulletin_0104.html">Kubernetes 1.32 Release Notes</a>.</li><li id="cce_01_0300__li14475257175413">Added <a href="cce_10_0961.html">Cluster Access Overview</a>.</li><li id="cce_01_0300__li1057882518561">Added <a href="cce_10_0962.html">Cluster Management Overview</a>.</li><li id="cce_01_0300__li23891526145617">Added <a href="cce_10_1006.html">Using AppArmor to Confine Container Access to Resources</a>.</li><li id="cce_01_0300__li1058418519163">Added <a href="cce_10_0845.html">GPU Driver Version</a>.</li><li id="cce_01_0300__li2145182713568">Added <a href="cce_10_0643.html">GPU Virtualization</a>.</li><li id="cce_01_0300__li6978102710567">Added <a href="cce_10_1016.html">GPU Monitoring</a> , <a href="cce_10_0741.html">Comprehensive Monitoring of GPU, Virtualization, and Pod Resource Metrics</a>.</li><li id="cce_01_0300__li12195183213567">Added <a href="cce_10_1017.html">GPU Auto Scaling</a>, <a href="cce_10_0844.html">Configuring Workload Scaling Based on GPU Monitoring Metrics</a>.</li><li id="cce_01_0300__li5448105217338">Added <a href="cce_10_0779.html">GPU Fault Handling</a>.</li><li id="cce_01_0300__li103001722173511">Added <a href="cce_10_1077.html">Configuring a Security Group for a Workload in a CCE Turbo Cluster</a>, <a href="cce_10_1078.html">Comparison of Workload Security Group Configuration Methods</a>, <a href="cce_10_1079.html">Using Node Pool Settings to Bind the Default Security Group to Pods in the Node Pool</a>.</li><li id="cce_01_0300__li06903525610">Added <a href="cce_10_0857.html">Nginx Ingress Usage Suggestions</a>.</li><li id="cce_01_0300__li1691213352563">Supported the <strong id="cce_01_0300__b477112161114">NodeLocal DNSCache</strong> add-on. Added <a href="cce_10_0404.html">NodeLocal DNSCache</a>, <a href="cce_10_0362.html">Using NodeLocal DNSCache to Improve DNS Performance</a>,<p id="cce_01_0300__p129961300614"><a href="cce_10_0959.html">Changing the Default NodeLocal DNSCache Port</a>, <a href="cce_bestpractice_0351.html">Using NodeLocal DNSCache</a>.</p>
|
||||
</li><li id="cce_01_0300__li147024365565">Supported the <strong id="cce_01_0300__b628419176114">Grafana</strong> add-on. Added <a href="cce_10_0828.html">Grafana</a>, <a href="cce_10_0960.html">Migrating Custom Views of Grafana</a>.</li><li id="cce_01_0300__li757218329817">Added <a href="cce_10_1012.html">Configuring EVS Mount Options</a>.</li><li id="cce_01_0300__li7139664102">Added <a href="cce_10_0966.html">Automatically Applying Updated Access Keys (AK/SK) for an OBS Volume</a>.</li><li id="cce_01_0300__li1498611691015">Added <a href="cce_10_0997.html">Using Dex for OIDC Authentication on CCE</a>.</li><li id="cce_01_0300__li176431871109">Added <a href="cce_faq_00493.html">What Should I Do If the LoadBalancer Ingress Configuration Is Inconsistent with the Load Balancer Configuration During a CCE Cluster Upgrade?</a>.</li><li id="cce_01_0300__li10586158131011">Added <a href="cce_faq_00501.html">What Can I Do If a GPU Card Is Unavailable on a GPU Node?</a>.</li><li id="cce_01_0300__li1754379111017">Added <a href="cce_faq_00277.html">How Do I Delete a Namespace in the Terminating State?</a>.</li><li id="cce_01_0300__li011015118186">Added <a href="cce_faq_00130.html">What Should I Do If Residual Process Resources Exist Due to an Earlier CCE Node Problem Detector Add-on Version?</a>.</li><li id="cce_01_0300__li1951811111813">Added <a href="cce_faq_00488.html">How Can I Drain a GPU Node After Upgrading or Rolling Back the CCE AI Suite (NVIDIA GPU) Add-on?</a></li></ul>
|
||||
<p id="cce_01_0300__p61852539547">Update:</p>
|
||||
<ul id="cce_01_0300__ul4185155375410"><li id="cce_01_0300__li654263972717">Updated <a href="cce_10_0028.html">Creating a CCE Standard/Turbo Cluster</a>.</li><li id="cce_01_0300__li8185753105418">Updated <a href="cce_10_0405.html">Patch Version Release Notes</a>.</li><li id="cce_01_0300__li15539124312584">Supported <strong id="cce_01_0300__b1017817111412">OIDC</strong>, Updated <a href="cce_10_0213.html">Modifying Cluster Configurations</a> and <a href="cce_10_0783.html">Cluster Access</a>.</li><li id="cce_01_0300__li19185155385410">Updated <a href="cce_10_0215.html">Upgrading a Cluster</a>.</li><li id="cce_01_0300__li84191114205816">Updated <a href="cce_10_0476.html">Node OSs</a>.</li><li id="cce_01_0300__li55011146285">Updated <a href="cce_10_0363.html">Creating a Node</a>, <a href="cce_10_0198.html">Accepting Nodes for Management</a>, <a href="cce_10_0003.html">Resetting a Node</a>.</li><li id="cce_01_0300__li14286114425814">Updated <a href="cce_10_0012.html">Creating a Node Pool</a>, <a href="cce_10_0653.html">Updating a Node Pool</a>.</li><li id="cce_01_0300__li16106134511581">Updated <a href="cce_10_0702.html">Scheduling Overview</a>.</li><li id="cce_01_0300__li2996545165818">Updated <a href="cce_10_0059.html">Configuring Network Policies to Restrict Pod Access</a>, <a href="cce_10_0945.html">DataPlane V2 Network Acceleration</a>.</li><li id="cce_01_0300__li241064194412">Updated <a href="cce_bestpractice_10006.html">CoreDNS Configuration Optimization</a>.</li><li id="cce_01_0300__li16514251185617">Updated the change history of all add-ons.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_01_0300__row153271013089"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p93277135815">2025-07-25</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p1832717138814">Added <a href="CVE-2025-23266.html">Notice of the NVIDIA Container Toolkit Container Escape Vulnerabilities (CVE-2025-23266 and CVE-2025-23267)</a>.</p>
|
||||
</td>
|
||||
@ -48,7 +57,7 @@
|
||||
<tr id="cce_01_0300__row19988104361114"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p1098910431118">2025-03-31</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p84969551112">Update:</p>
|
||||
<ul id="cce_01_0300__ul1074915179422"><li id="cce_01_0300__li1274951704212">Updated <a href="cce_faq_00020.html">How Do I Rectify Failures When the NVIDIA Driver Is Used to Start Containers on GPU Nodes?</a></li><li id="cce_01_0300__li7682171934212">Updated <a href="cce_10_0555.html">Collecting Container Logs Using Cloud Native Log Collection</a>.</li><li id="cce_01_0300__li17158133213818">Updated <a href="cce_10_0940.html">Configuring Advanced Forwarding Rules for a LoadBalancer Ingress</a>.</li></ul>
|
||||
<ul id="cce_01_0300__ul1074915179422"><li id="cce_01_0300__li1274951704212">Updated <a href="cce_faq_00020.html">How Do I Rectify Failures When the NVIDIA Driver Is Used to Start Containers on GPU Nodes?</a></li><li id="cce_01_0300__li7682171934212">Updated <a href="cce_10_0555.html">Collecting Container Logs Using Cloud Native Log Collection</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_01_0300__row176951955145713"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p2695135595716">2025-03-10</p>
|
||||
|
||||
@ -4,11 +4,11 @@
|
||||
<div id="body1522736306717"><div class="section" id="cce_10_0003__section87051629113714"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0003__p13461109175017">You can <span class="keyword" id="cce_10_0003__keyword217225485612">reset a node</span> to modify the node configuration, such as the node OS and login mode.</p>
|
||||
<p id="cce_10_0003__p341155285120">Resetting a node will reinstall the node OS and the Kubernetes software on the node. If a node is unavailable because you modify the node configuration, you can reset the node to rectify the fault.</p>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0003__section0339185914138"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="cce_10_0003__ul975585510397"><li id="cce_10_0003__li15755125513910">To enable node resetting in CCE standard clusters or CCE Turbo clusters, the version must be v1.13 or later.</li></ul>
|
||||
<div class="section" id="cce_10_0003__section0339185914138"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="cce_10_0003__ul975585510397"><li id="cce_10_0003__li15755125513910">Node resetting in CCE standard clusters or CCE Turbo clusters is supported for cluster versions v1.13 and later.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0003__section83421713122615"><h4 class="sectiontitle">Precautions</h4><ul id="cce_10_0003__ul189321612123615"><li id="cce_10_0003__li139331412133615">Only worker nodes can be reset. If the node is still unavailable after the resetting, delete the node and create a new one.</li><li id="cce_10_0003__li133748101461"><strong id="cce_10_0003__b161591159125218">After a node is reset, the node OS will be reinstalled. Before resetting a node, <a href="cce_10_0605.html">drain</a> the node to gracefully evict the pods running on the node to other available nodes. Perform this operation during off-peak hours.</strong></li><li id="cce_10_0003__li11336171744612"><strong id="cce_10_0003__b3113619509">After a node is reset, its system disk and data disks will be cleared. Back up important data before resetting a node.</strong></li><li id="cce_10_0003__li159325122367"><strong id="cce_10_0003__b18976436631">If you reset a worker node that has an additional data disk attached on the ECS console, the attachment will be removed. To keep the data, you need to reattach the disk.</strong></li><li id="cce_10_0003__li18904821103817">The IP addresses of the workload pods on the node will change, but the container network access is not affected.</li><li id="cce_10_0003__li33901348389">There is remaining EVS disk quota.</li><li id="cce_10_0003__li893261218365">When a node is reset, the backend will make it unschedulable.</li><li id="cce_10_0003__li49618284552">Resetting a node will clear the Kubernetes labels and taints you added (those added by editing a node pool will not be lost). As a result, node-specific resources (such as local storage and workloads scheduled to this node) may be unavailable.</li><li id="cce_10_0003__li551825451813">Resetting a node will cause PVC/PV data loss for the <a href="cce_10_0391.html">local PV</a> associated with the node. These PVCs and PVs cannot be restored or used again. In this scenario, the pod that uses the local PV is evicted from the node. A new pod is created and stays in the pending state. This is because the PVC used by the pod has a node label, due to which the pod cannot be scheduled. After the node is reset, the pod may be scheduled to the reset node. In this case, the pod remains in the creating state because the underlying logical volume corresponding to the PVC does not exist.</li></ul>
|
||||
<div class="section" id="cce_10_0003__section83421713122615"><h4 class="sectiontitle">Precautions</h4><ul id="cce_10_0003__ul189321612123615"><li id="cce_10_0003__li139331412133615">Only worker nodes can be reset. If the node is still unavailable after the resetting, delete the node and create a new one.</li><li id="cce_10_0003__li133748101461"><strong id="cce_10_0003__b25291016163214">After a node is reset, its OS will be reinstalled. Before resetting a node, <a href="cce_10_0605.html">drain</a> it to gracefully evict the pods running on the node to other available nodes. Perform this operation during off-peak hours.</strong> If pods remain when the node is reset, CCE will evict them. If a <a href="https://kubernetes.io/docs/tasks/run-application/configure-pdb/" target="_blank" rel="noopener noreferrer">Pod Disruption Budget</a> (PDB) policy is configured for your pods, they may fail to be evicted. In this case, the node will be forcibly reset after a period of time.</li><li id="cce_10_0003__li11336171744612"><strong id="cce_10_0003__b3113619509">After a node is reset, its system disk and data disks will be cleared. Back up important data before resetting a node.</strong></li><li id="cce_10_0003__li159325122367"><strong id="cce_10_0003__b1535212018418">If an ECS node has a raw data disk attached (not using LVM), detach it before resetting the node. After resetting, the original attachment information will be cleared. Re-attach the disk to the ECS node to retain the data.</strong></li><li id="cce_10_0003__li18904821103817">The IP addresses of the workload pods on the node will change, but the container network access is not affected.</li><li id="cce_10_0003__li33901348389">There is remaining EVS disk quota.</li><li id="cce_10_0003__li893261218365">When a node is reset, the backend will make it unschedulable.</li><li id="cce_10_0003__li49618284552">Resetting a node will clear the Kubernetes labels and taints you added (those added by editing a node pool will not be lost). As a result, node-specific resources (such as local storage and workloads scheduled to this node) may be unavailable.</li><li id="cce_10_0003__li551825451813">Resetting a node will cause PVC/PV data loss for the <a href="cce_10_0391.html">local PV</a> associated with the node. These PVCs and PVs cannot be restored or used again. In this scenario, the pod that uses the local PV is evicted from the node. A new pod is created and stays in the pending state. This is because the PVC used by the pod has a node label, due to which the pod cannot be scheduled. After the node is reset, the pod may be scheduled to the reset node. In this case, the pod remains in the creating state because the underlying logical volume corresponding to the PVC does not exist.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0003__section13505122310576"><h4 class="sectiontitle">Resetting Nodes in the Default Pool</h4><ol id="cce_10_0003__ol19107956331"><li id="cce_10_0003__li12107195613316"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0003__li314420611592"><span>In the navigation pane, choose <span class="uicontrol" id="cce_10_0003__uicontrol226720045103631"><b>Nodes</b></span>. On the displayed page, click the <strong id="cce_10_0003__b200115353103631">Nodes</strong> tab.</span></li><li id="cce_10_0003__li36690501449"><span>In the node list of the default pool, select one or more nodes to be reset and choose <strong id="cce_10_0003__b75704965116">More</strong> > <strong id="cce_10_0003__b4241551145119">Reset Node</strong> in the <strong id="cce_10_0003__b9468195465310">Operation</strong> column.</span></li><li id="cce_10_0003__li2062015811615"><span>In the displayed dialog box, click <strong id="cce_10_0003__b143401521627">Next</strong>.</span></li><li id="cce_10_0003__li1646785611239"><span>Specify node parameters.</span><p><div class="p" id="cce_10_0003__en-us_topic_0000001244141037_p67901445163816"><strong id="cce_10_0003__b31796610207">Compute Settings</strong>
|
||||
<div class="section" id="cce_10_0003__section13505122310576"><h4 class="sectiontitle">Resetting Nodes in the Default Pool</h4><ol id="cce_10_0003__ol19107956331"><li id="cce_10_0003__li12107195613316"><span>Log in to the <span id="cce_10_0003__ph2018515511788">CCE console</span> and click the cluster name to access the cluster console.</span></li><li id="cce_10_0003__li314420611592"><span>In the navigation pane, choose <span class="uicontrol" id="cce_10_0003__uicontrol226720045103631"><b>Nodes</b></span>. On the displayed page, click the <strong id="cce_10_0003__b200115353103631">Nodes</strong> tab.</span></li><li id="cce_10_0003__li36690501449"><span>In the node list of the default pool, select one or more nodes to be reset and choose <strong id="cce_10_0003__b75704965116">More</strong> > <strong id="cce_10_0003__b4241551145119">Reset Node</strong> in the <strong id="cce_10_0003__b9468195465310">Operation</strong> column.</span></li><li id="cce_10_0003__li2062015811615"><span>In the displayed dialog box, click <strong id="cce_10_0003__b143401521627">Next</strong>.</span></li><li id="cce_10_0003__li1646785611239"><span>Specify node parameters.</span><p><div class="p" id="cce_10_0003__en-us_topic_0000001244141037_p67901445163816"><strong id="cce_10_0003__b31796610207">Compute Settings</strong>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0003__en-us_topic_0000001244141037_table0668137185810" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Configuration parameters</caption><thead align="left"><tr id="cce_10_0003__en-us_topic_0000001244141037_row46680715812"><th align="left" class="cellrowborder" valign="top" width="20.02%" id="mcps1.3.4.2.5.2.1.2.2.3.1.1"><p id="cce_10_0003__en-us_topic_0000001244141037_p186688710581">Parameter</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="79.97999999999999%" id="mcps1.3.4.2.5.2.1.2.2.3.1.2"><p id="cce_10_0003__en-us_topic_0000001244141037_p16681570588">Description</p>
|
||||
@ -67,9 +67,9 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0003__cce_10_0198_row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.4.2.5.2.3.1.2.3.1.1 "><p id="cce_10_0003__cce_10_0198_p0669147185817">Data Disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.2.5.2.3.1.2.3.1.2 "><ul id="cce_10_0003__cce_10_0198_ul184351126605"><li id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_li103472126407"><strong id="cce_10_0003__cce_10_0198_b13284145912236">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol2284135972312"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol1284135952313"><b>Data Disk</b></span>. <strong id="cce_10_0003__cce_10_0198_b1828495914238">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.</li><li id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_li18830161664015">If <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol16275444867446"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol5641816837446"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.2.5.2.3.1.2.3.1.2 "><ul id="cce_10_0003__cce_10_0198_ul184351126605"><li id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_li103472126407"><strong id="cce_10_0003__cce_10_0198_b6314038347415">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_uicontrol79783262393"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_uicontrol179781326143914"><b>Data Disk</b></span>. <strong id="cce_10_0003__cce_10_0198_b7501571957415">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> </li><li id="cce_10_0003__cce_10_0198_en-us_topic_0000001199021246_li18830161664015">If <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol16275444867446"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol5641816837446"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.</li></ul>
|
||||
<p id="cce_10_0003__cce_10_0198_p3752312011">Click <strong id="cce_10_0003__cce_10_0198_b513813367555">Expand</strong> to configure <strong id="cce_10_0003__cce_10_0198_b13265825195416">Data Disk Space Allocation</strong>. This allocates space for container engines, images, and ephemeral storage to ensure their proper running. For details about how to allocate data disk space, see <a href="cce_10_0341.html">Space Allocation of a Data Disk</a>.</p>
|
||||
<p id="cce_10_0003__cce_10_0198_p1391618153118">For other data disks, a raw disk is created without any processing by default. You can also click <strong id="cce_10_0003__cce_10_0198_b16127101911540">Expand</strong> and select <strong id="cce_10_0003__cce_10_0198_b21351519135417">Mount Disk</strong> to mount the data disk to a specified directory. Data disks can also be used as <a href="cce_10_0391.html">local PVs</a> or <a href="cce_10_0726.html">local EVs</a>.</p>
|
||||
<p id="cce_10_0003__cce_10_0198_p1391618153118">For other data disks, a raw disk is created without any processing by default. You can also click <strong id="cce_10_0003__cce_10_0198_b16127101911540">Expand</strong> and select <strong id="cce_10_0003__cce_10_0198_b21351519135417">Mount Disk</strong> to mount the data disk to a specified directory. </p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@ -112,14 +112,16 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0003__en-us_topic_0000001244141037_row23431056203915"><td class="cellrowborder" valign="top" width="23.66%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.1 "><p id="cce_10_0003__en-us_topic_0000001244141037_p534319566391">Pre-installation Command</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.34%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.2 "><p id="cce_10_0003__en-us_topic_0000001244141037_p1644103463319">Installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.</p>
|
||||
<td class="cellrowborder" valign="top" width="76.34%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.2 "><p id="cce_10_0003__en-us_topic_0000001244141037_p1644103463319">Installation script command. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.</p>
|
||||
<p id="cce_10_0003__en-us_topic_0000001244141037_p03368579295">The script will be executed before Kubernetes software is installed. Note that if the script is incorrect, Kubernetes software may fail to be installed.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0003__en-us_topic_0000001244141037_row1167794673912"><td class="cellrowborder" valign="top" width="23.66%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.1 "><p id="cce_10_0003__en-us_topic_0000001244141037_p18677104643916">Post-installation Command</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.34%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.2 "><p id="cce_10_0003__en-us_topic_0000001244141037_p14193381618">Installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.</p>
|
||||
<p id="cce_10_0003__en-us_topic_0000001244141037_p13471136154110">The script will be executed after Kubernetes software is installed, which does not affect the installation.</p>
|
||||
<td class="cellrowborder" valign="top" width="76.34%" headers="mcps1.3.4.2.5.2.4.2.2.3.1.2 "><p id="cce_10_0003__en-us_topic_0000001244141037_p14193381618">Installation script command. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.</p>
|
||||
<div class="p" id="cce_10_0003__en-us_topic_0000001244141037_p13471136154110">The script will be executed after Kubernetes software is installed, which does not affect the installation. <span id="cce_10_0003__cce_10_0363_ph8900135164311">During post-installation script execution, pods can be scheduled normally. However, if the script execution times out, node installation will fail. To prevent pods from being scheduled to nodes with incomplete script execution, enable the option to schedule pods only after the post-installation script execution completes.</span><div class="caution" id="cce_10_0003__cce_10_0363_note14983019515"><span class="cautiontitle"> CAUTION: </span><div class="cautionbody"><p id="cce_10_0003__cce_10_0363_p792373105115">Do not use the <strong id="cce_10_0003__cce_10_0363_b4852104401">reboot</strong> command in the post-installation script to restart the system immediately. Instead, use the <strong id="cce_10_0003__cce_10_0363_b78527414018">shutdown -r 1</strong> command to restart the system with a one-minute delay.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@ -130,7 +132,7 @@
|
||||
</div>
|
||||
<div class="section" id="cce_10_0003__section132111259428"><h4 class="sectiontitle">Resetting Nodes in a Node Pool</h4><div class="note" id="cce_10_0003__note7766174418107"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0003__ul1097235481214"><li id="cce_10_0003__li8972185411125">When resetting a node in a node pool, you can only change its storage configuration. All other configurations will follow the settings of the node pool.</li><li id="cce_10_0003__li5972135411215">Resetting a node will execute the pre- and post-installation scripts in the current node pool and update the security group configurations to those of the node pool.</li></ul>
|
||||
</div></div>
|
||||
<ol id="cce_10_0003__ol2394422183712"><li id="cce_10_0003__li153942022183712"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0003__li1039462243718"><span>In the navigation pane, choose <span class="uicontrol" id="cce_10_0003__uicontrol1489635134313"><b>Nodes</b></span>. On the displayed page, click the <strong id="cce_10_0003__b11891935154313">Nodes</strong> tab.</span></li><li id="cce_10_0003__li1394112293711"><span>In the node list of the target node pool, select a node to be reset and choose <strong id="cce_10_0003__b12407405435">More</strong> > <strong id="cce_10_0003__b1640640194315">Reset Node</strong> in the <strong id="cce_10_0003__b13401140204312">Operation</strong> column.</span></li><li id="cce_10_0003__li2039492216377"><span>Modify the node storage parameters.</span><p>
|
||||
<ol id="cce_10_0003__ol2394422183712"><li id="cce_10_0003__li153942022183712"><span>Log in to the <span id="cce_10_0003__ph1196616543818">CCE console</span> and click the cluster name to access the cluster console.</span></li><li id="cce_10_0003__li1039462243718"><span>In the navigation pane, choose <span class="uicontrol" id="cce_10_0003__uicontrol1489635134313"><b>Nodes</b></span>. On the displayed page, click the <strong id="cce_10_0003__b11891935154313">Nodes</strong> tab.</span></li><li id="cce_10_0003__li1394112293711"><span>In the node list of the target node pool, select a node to be reset and choose <strong id="cce_10_0003__b12407405435">More</strong> > <strong id="cce_10_0003__b1640640194315">Reset Node</strong> in the <strong id="cce_10_0003__b13401140204312">Operation</strong> column.</span></li><li id="cce_10_0003__li2039492216377"><span>Modify the node storage parameters.</span><p>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0003__table8731630145913" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Configuration parameters</caption><thead align="left"><tr id="cce_10_0003__row1173103016596"><th align="left" class="cellrowborder" valign="top" width="20.02%" id="mcps1.3.5.3.4.2.1.2.3.1.1"><p id="cce_10_0003__p1873133015915">Parameter</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="79.97999999999999%" id="mcps1.3.5.3.4.2.1.2.3.1.2"><p id="cce_10_0003__p107353045914">Description</p>
|
||||
|
||||
@ -29,7 +29,7 @@
|
||||
<tr id="cce_10_0004__row186452248235"><td class="cellrowborder" valign="top" width="45%" headers="mcps1.4.2.4.2.3.1.1 "><p id="cce_10_0004__p935922465512">New: node.kubernetes.io/baremetal</p>
|
||||
<p id="cce_10_0004__p1664611247230">Old: failure-domain.beta.kubernetes.io/is-baremetal</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.4.2.4.2.3.1.2 "><p id="cce_10_0004__p10646132416235">Whether the node is a bare metal node</p>
|
||||
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.4.2.4.2.3.1.2 "><p id="cce_10_0004__p10646132416235">Whether it is a bare metal node</p>
|
||||
<p id="cce_10_0004__p878819218284"><strong id="cce_10_0004__b137781937201815">false</strong> indicates that the node is not a bare metal node.</p>
|
||||
</td>
|
||||
</tr>
|
||||
@ -94,7 +94,7 @@
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0004__section33951611481"><a name="cce_10_0004__section33951611481"></a><a name="section33951611481"></a><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 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"><a name="cce_10_0004__section33951611481"></a><a name="section33951611481"></a><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 <span id="cce_10_0004__ph18314322182">CCE console</span> 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 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>
|
||||
<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>
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
<a name="cce_10_0006"></a><a name="cce_10_0006"></a>
|
||||
|
||||
<h1 class="topictitle1">Overview</h1>
|
||||
<h1 class="topictitle1">Workload Overview</h1>
|
||||
<div id="body1522665832344"><p id="cce_10_0006__p1031812215459">A workload is an application running on Kubernetes. No matter how many components are there in your workload, you can run it in a group of Kubernetes pods. A workload is an abstract model of a group of pods in Kubernetes. Workloads in Kubernetes are classified as <span class="keyword" id="cce_10_0006__keyword1293375712468">Deployments</span>, <span class="keyword" id="cce_10_0006__keyword1541920224714">StatefulSets</span>, <span class="keyword" id="cce_10_0006__keyword1273972479">DaemonSets</span>, <span class="keyword" id="cce_10_0006__keyword21491010164711">jobs</span>, and <span class="keyword" id="cce_10_0006__keyword19556171584711">cron jobs</span>.</p>
|
||||
<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">Overview of Pods</h4><p id="cce_10_0006__en-us_topic_0254767870_p356108173515">Pods are the smallest unit that you can create or deploy in Kubernetes. Each pod comprises one or more containers, shared storage (volumes), a unique IP address, and container runtime policies.</p>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<a name="cce_10_0007"></a><a name="cce_10_0007"></a>
|
||||
|
||||
<h1 class="topictitle1">Managing Workloads</h1>
|
||||
<div id="body8662426"><div class="section" id="cce_10_0007__en-us_topic_0107283638_section430113764416"><h4 class="sectiontitle">Scenario</h4><div class="p" id="cce_10_0007__en-us_topic_0107283638_p723817425449">After a workload is created, you can upgrade, log, monitor, roll back, or delete the workload, as well as edit its YAML file.
|
||||
<div id="body8662426"><div class="section" id="cce_10_0007__en-us_topic_0107283638_section430113764416"><h4 class="sectiontitle">Scenario</h4><div class="p" id="cce_10_0007__en-us_topic_0107283638_p723817425449">After a workload is created, you can upgrade it, edit its YAML file, view logs and monitoring data, roll it back, and delete it.
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0007__en-us_topic_0107283638_table156143911815" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Workload/Job management</caption><thead align="left"><tr id="cce_10_0007__en-us_topic_0107283638_row856143916184"><th align="left" class="cellrowborder" valign="top" width="24.610000000000003%" id="mcps1.3.1.2.1.2.3.1.1"><p id="cce_10_0007__en-us_topic_0107283638_p1571039111814">Operation</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="75.39%" id="mcps1.3.1.2.1.2.3.1.2"><p id="cce_10_0007__en-us_topic_0107283638_p175703931816">Description</p>
|
||||
@ -10,7 +10,7 @@
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0007__row125441054163414"><td class="cellrowborder" valign="top" width="24.610000000000003%" headers="mcps1.3.1.2.1.2.3.1.1 "><p id="cce_10_0007__p452412553342"><a href="#cce_10_0007__section7200124254011">Monitor</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__p852495515348">You can view the CPU and memory usage of workloads and pods on the CCE console.</p>
|
||||
<td class="cellrowborder" valign="top" width="75.39%" headers="mcps1.3.1.2.1.2.3.1.2 "><p id="cce_10_0007__p852495515348">You can view the CPU and memory usage of workloads and pods on the CCE console to determine the resource specifications you may need.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0007__en-us_topic_0107283638_row75714395185"><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_p1557739101816"><a href="#cce_10_0007__en-us_topic_0107283638_section51511928173817">View Log</a></p>
|
||||
@ -71,52 +71,52 @@
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0007__section7200124254011"><a name="cce_10_0007__section7200124254011"></a><a name="section7200124254011"></a><h4 class="sectiontitle">Monitoring a Workload</h4><p id="cce_10_0007__en-us_topic_0107283638_p785625243110">You can view the CPU and memory usage of Deployments and pods on the CCE console to determine the resource specifications you may need. This section uses a Deployment as an example to describe how to monitor a workload.</p>
|
||||
<ol id="cce_10_0007__en-us_topic_0107283638_ol121998089396"><li id="cce_10_0007__en-us_topic_0107283638_li9879311402"><span>Log in to the CCE console, go to an existing cluster, and choose <strong id="cce_10_0007__b163134191278">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li2774856895942"><span>Click the <strong id="cce_10_0007__b1414121112713">Deployments</strong> tab and click <span class="uicontrol" id="cce_10_0007__uicontrol0414821162719"><b>Monitor</b></span> of the target workload. On the page that is displayed, you can view CPU usage and memory usage of the workload.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li08455571501"><span>Click the workload name. On the <strong id="cce_10_0007__b1170422772711">Pods</strong> tab page, click the <span class="uicontrol" id="cce_10_0007__uicontrol9704112716273"><b>Monitor</b></span> of the target pod to view its CPU and memory usage.</span></li></ol>
|
||||
<ol id="cce_10_0007__en-us_topic_0107283638_ol121998089396"><li id="cce_10_0007__en-us_topic_0107283638_li9879311402"><span>Log in to the <span id="cce_10_0007__ph1519791153812">CCE console</span>, go to the console of an existing cluster, and choose <strong id="cce_10_0007__b163134191278">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li2774856895942"><span>Click the <strong id="cce_10_0007__b1414121112713">Deployments</strong> tab and click <span class="uicontrol" id="cce_10_0007__uicontrol0414821162719"><b>Monitor</b></span> of the target workload. On the page that is displayed, you can view CPU usage and memory usage of the workload.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li08455571501"><span>Click the workload name. On the <strong id="cce_10_0007__b1170422772711">Pods</strong> tab page, click the <span class="uicontrol" id="cce_10_0007__uicontrol9704112716273"><b>Monitor</b></span> of the target pod to view its CPU and memory usage.</span></li></ol>
|
||||
</div>
|
||||
<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 <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>
|
||||
<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 <span id="cce_10_0007__ph15521523153013">CCE console</span>, go to the console of 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 <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&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">Collecting Container Logs Using ICAgent</a>.</p>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0007__en-us_topic_0107283638_section17604174417381"><a name="cce_10_0007__en-us_topic_0107283638_section17604174417381"></a><a name="en-us_topic_0107283638_section17604174417381"></a><h4 class="sectiontitle">Upgrading a Workload</h4><p id="cce_10_0007__en-us_topic_0107283638_p96551832133014">You quickly upgrade Deployments, StatefulSets, and DaemonSets on the CCE console.</p>
|
||||
<p id="cce_10_0007__en-us_topic_0107283638_p1243174462216">This section uses a Deployment as an example to describe how to upgrade a workload.</p>
|
||||
<p id="cce_10_0007__en-us_topic_0107283638_p15663124812311">Before replacing an image or image version, upload the new image to the SWR service.</p>
|
||||
<ol id="cce_10_0007__en-us_topic_0107283638_ol583013911434"><li id="cce_10_0007__li112420494810"><span>Log in to the CCE console, go to an existing cluster, and choose <strong id="cce_10_0007__b1068713277289">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li148303911437"><span>Click the <strong id="cce_10_0007__b1023143010284">Deployments</strong> tab and click <span class="uicontrol" id="cce_10_0007__uicontrol162343062817"><b>Upgrade</b></span> of the target workload.</span><p><div class="note" id="cce_10_0007__en-us_topic_0107283638_note104981317262"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0007__en-us_topic_0107283638_ul6585203411317"><li id="cce_10_0007__en-us_topic_0107283638_li658513412313">Workloads cannot be upgraded in batches.</li><li id="cce_10_0007__en-us_topic_0107283638_li175851834193120">Before performing an in-place StatefulSet upgrade, you must manually delete old pods. Otherwise, the upgrade status is always displayed as <strong id="cce_10_0007__en-us_topic_0107283638_b340512519164">Processing</strong>.</li></ul>
|
||||
<p id="cce_10_0007__en-us_topic_0107283638_p15663124812311">Before replacing an image or image tag, upload the new image to the SWR service.</p>
|
||||
<ol id="cce_10_0007__en-us_topic_0107283638_ol583013911434"><li id="cce_10_0007__li112420494810"><span>Log in to the <span id="cce_10_0007__ph15265526173019">CCE console</span>,go to the console of an existing cluster, and choose <strong id="cce_10_0007__b1068713277289">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li148303911437"><span>Click the <strong id="cce_10_0007__b1023143010284">Deployments</strong> tab and click <span class="uicontrol" id="cce_10_0007__uicontrol162343062817"><b>Upgrade</b></span> of the target workload.</span><p><div class="note" id="cce_10_0007__en-us_topic_0107283638_note104981317262"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0007__en-us_topic_0107283638_ul6585203411317"><li id="cce_10_0007__en-us_topic_0107283638_li658513412313">Workloads cannot be upgraded in batches.</li><li id="cce_10_0007__en-us_topic_0107283638_li175851834193120">Before performing an in-place StatefulSet upgrade, you must manually delete old pods. Otherwise, the upgrade status is always displayed as <strong id="cce_10_0007__en-us_topic_0107283638_b340512519164">Processing</strong>.</li></ul>
|
||||
</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 YAML files of Deployments, StatefulSets, DaemonSets, CronJobs, and pods 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> > <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>
|
||||
<ol id="cce_10_0007__en-us_topic_0107283638_ol1879112311361"><li id="cce_10_0007__li635115103505"><span>Log in to the <span id="cce_10_0007__ph1148883014303">CCE console</span>, go to the console of 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> > <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 and choose <span class="uicontrol" id="cce_10_0007__uicontrol1195354418284"><b>More > 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>
|
||||
<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 <span id="cce_10_0007__ph99183813013">CCE console</span>, go to the console of 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 and choose <span class="uicontrol" id="cce_10_0007__uicontrol1195354418284"><b>More > 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> > <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>
|
||||
<ol id="cce_10_0007__ol0529114105916"><li id="cce_10_0007__li152911415912"><span>Log in to the <span id="cce_10_0007__ph1291412418308">CCE console</span>, go to the console of 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> > <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>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0007__en-us_topic_0107283638_section12087915401"><a name="cce_10_0007__en-us_topic_0107283638_section12087915401"></a><a name="en-us_topic_0107283638_section12087915401"></a><h4 class="sectiontitle">Disabling/Enabling Upgrade (Available Only for Deployments)</h4><p id="cce_10_0007__p209311112155710">Only Deployments support this operation.</p>
|
||||
<ul id="cce_10_0007__ul978411517574"><li id="cce_10_0007__li177841115105714">After the upgrade is disabled, the upgrade command can be delivered but will not be applied to the pods.<p id="cce_10_0007__p28775173578"><a name="cce_10_0007__li177841115105714"></a><a name="li177841115105714"></a>If you are performing a rolling upgrade, the rolling upgrade stops after the disabling upgrade command is delivered. In this case, the new and old pods co-exist.</p>
|
||||
</li><li id="cce_10_0007__li14784141565720">After the upgrade is enabled, a Deployment can be upgraded or rolled back. Its pods will inherit the latest updates of the Deployment. If they are inconsistent, the pods will be upgraded automatically according to the latest information of the Deployment.</li></ul>
|
||||
<div class="notice" id="cce_10_0007__en-us_topic_0107283638_note10276839151110"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cce_10_0007__en-us_topic_0107283638_p17277163941114">Deployments in the disable upgrade state cannot be rolled back.</p>
|
||||
</div></div>
|
||||
<ol id="cce_10_0007__en-us_topic_0107283638_ol1188315418332"><li id="cce_10_0007__en-us_topic_0107283638_li1388334119335"><span>Log in to the CCE console, go to an existing cluster, and choose <strong id="cce_10_0007__b11769141672918">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li1588424111338"><span>Click the <strong id="cce_10_0007__b199921814299">Deployments</strong> tab and choose <strong id="cce_10_0007__b1799951820293">More</strong> > <strong id="cce_10_0007__b17031913299">Disable/Enable Upgrade</strong> in the <strong id="cce_10_0007__b180719162911">Operation</strong> column of the workload.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li1288404118334"><span>In the dialog box that is displayed, click <strong id="cce_10_0007__b1688621162914">Yes</strong>.</span></li></ol>
|
||||
<ol id="cce_10_0007__en-us_topic_0107283638_ol1188315418332"><li id="cce_10_0007__en-us_topic_0107283638_li1388334119335"><span>Log in to the <span id="cce_10_0007__ph181175457307">CCE console</span>, go to the console of an existing cluster, and choose <strong id="cce_10_0007__b11769141672918">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li1588424111338"><span>Click the <strong id="cce_10_0007__b199921814299">Deployments</strong> tab and choose <strong id="cce_10_0007__b1799951820293">More</strong> > <strong id="cce_10_0007__b17031913299">Disable/Enable Upgrade</strong> in the <strong id="cce_10_0007__b180719162911">Operation</strong> column of the workload.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li1288404118334"><span>In the dialog box that is displayed, click <strong id="cce_10_0007__b1688621162914">Yes</strong>.</span></li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0007__en-us_topic_0107283638_section5931193015488"><a name="cce_10_0007__en-us_topic_0107283638_section5931193015488"></a><a name="en-us_topic_0107283638_section5931193015488"></a><h4 class="sectiontitle">Managing Labels</h4><p id="cce_10_0007__en-us_topic_0107283638_p13735621112611">Labels are key-value pairs and can be attached to workloads. You can manage and select workloads by labels. You can add labels to multiple workloads or a specified workload.</p>
|
||||
<ol id="cce_10_0007__en-us_topic_0107283638_ol6251112511220"><li id="cce_10_0007__en-us_topic_0107283638_li53548551606"><span>Log in to the CCE console, go to an existing cluster, and choose <strong id="cce_10_0007__b1335702382915">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li22871259152611"><span>Click the <strong id="cce_10_0007__b1838219256291">Deployments</strong> tab and choose <strong id="cce_10_0007__b4383162552919">More</strong> > <strong id="cce_10_0007__b2383225142917">Manage Label</strong> in the <strong id="cce_10_0007__b18383182512912">Operation</strong> column of the target workload.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li47616189277"><span>Click <span><img id="cce_10_0007__image3143153919236" src="en-us_image_0000002253620001.png"></span>, enter a key and a value, and click <span class="uicontrol" id="cce_10_0007__uicontrol1277618274294"><b>OK</b></span>.</span><p><div class="note" id="cce_10_0007__en-us_topic_0107283638_note163751811133416"><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_p03751011133411">A key-value pair must contain 1 to 63 characters starting and ending with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.</p>
|
||||
<div class="section" id="cce_10_0007__en-us_topic_0107283638_section5931193015488"><a name="cce_10_0007__en-us_topic_0107283638_section5931193015488"></a><a name="en-us_topic_0107283638_section5931193015488"></a><h4 class="sectiontitle"><span class="keyword" id="cce_10_0007__en-us_topic_0107283638_keyword141731324132418">Managing Labels</span></h4><p id="cce_10_0007__en-us_topic_0107283638_p13735621112611">Labels are key-value pairs and can be attached to workloads. You can manage and select workloads by labels. You can add labels to multiple workloads or a specified workload.</p>
|
||||
<ol id="cce_10_0007__en-us_topic_0107283638_ol6251112511220"><li id="cce_10_0007__en-us_topic_0107283638_li53548551606"><span>Log in to the <span id="cce_10_0007__ph3930134823011">CCE console</span>, go to the console of an existing cluster, and choose <strong id="cce_10_0007__b1335702382915">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li22871259152611"><span>Click the <strong id="cce_10_0007__b1838219256291">Deployments</strong> tab and choose <strong id="cce_10_0007__b4383162552919">More</strong> > <strong id="cce_10_0007__b2383225142917">Manage Label</strong> in the <strong id="cce_10_0007__b18383182512912">Operation</strong> column of the target workload.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li47616189277"><span>Click <span><img id="cce_10_0007__image3143153919236" src="en-us_image_0000002434239840.png"></span>, enter a key and a value, and click <span class="uicontrol" id="cce_10_0007__uicontrol1277618274294"><b>OK</b></span>.</span><p><div class="note" id="cce_10_0007__en-us_topic_0107283638_note163751811133416"><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_p03751011133411">A key-value pair must contain 1 to 63 characters starting and ending with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.</p>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0007__en-us_topic_0107283638_section14423721191418"><a name="cce_10_0007__en-us_topic_0107283638_section14423721191418"></a><a name="en-us_topic_0107283638_section14423721191418"></a><h4 class="sectiontitle">Deleting a Workload/Job</h4><p id="cce_10_0007__en-us_topic_0107283638_p44461328132920">You can delete a workload or job that is no longer needed. Deleted workloads or jobs cannot be recovered. This section uses a Deployment as an example to describe how to delete a workload.</p>
|
||||
<ol id="cce_10_0007__en-us_topic_0107283638_ol16301162312555"><li id="cce_10_0007__li1824612582414"><span>Log in to the CCE console, go to an existing cluster, and choose <strong id="cce_10_0007__b4293132919298">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li23014231555"><span>In the same row as the workload you will delete, choose <strong id="cce_10_0007__en-us_topic_0107283638_b2032918125613">Operation</strong> > <strong id="cce_10_0007__en-us_topic_0107283638_b0329141219611">More</strong> > <strong id="cce_10_0007__en-us_topic_0107283638_b23291912765">Delete</strong>.</span><p><p id="cce_10_0007__en-us_topic_0107283638_p11245223162515">Read the system prompts carefully. A workload cannot be recovered after it is deleted. Exercise caution when performing this operation.</p>
|
||||
<ol id="cce_10_0007__en-us_topic_0107283638_ol16301162312555"><li id="cce_10_0007__li1824612582414"><span>Log in to the <span id="cce_10_0007__ph696345119306">CCE console</span>, go to the console of an existing cluster, and choose <strong id="cce_10_0007__b4293132919298">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__en-us_topic_0107283638_li23014231555"><span>In the same row as the workload you will delete, choose <strong id="cce_10_0007__en-us_topic_0107283638_b2032918125613">Operation</strong> > <strong id="cce_10_0007__en-us_topic_0107283638_b0329141219611">More</strong> > <strong id="cce_10_0007__en-us_topic_0107283638_b23291912765">Delete</strong>.</span><p><p id="cce_10_0007__en-us_topic_0107283638_p11245223162515">Read the system prompts carefully. A workload cannot be recovered after it is deleted. Exercise caution when performing this operation.</p>
|
||||
</p></li><li id="cce_10_0007__en-us_topic_0107283638_li1566102365617"><span>Click <strong id="cce_10_0007__en-us_topic_0107283638_b2297164413617">Yes</strong>.</span><p><div class="note" id="cce_10_0007__en-us_topic_0107283638_note1933510551189"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0007__en-us_topic_0107283638_ul204031813191914"><li id="cce_10_0007__en-us_topic_0107283638_li7404151371913">If the node where the pod is located is unavailable or shut down and the workload cannot be deleted, you can forcibly delete the pod from the pod list on the workload details page.</li><li id="cce_10_0007__en-us_topic_0107283638_li10404113191914">Ensure that the storage volumes to be deleted are not used by other workloads. If these volumes are imported or have snapshots, you can only unbind them.</li></ul>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0007__en-us_topic_0107283638_section1947616516301"><a name="cce_10_0007__en-us_topic_0107283638_section1947616516301"></a><a name="en-us_topic_0107283638_section1947616516301"></a><h4 class="sectiontitle">Events</h4><p id="cce_10_0007__p16951182315188">This section uses a Deployment as an example to describe how to view events of a workload. To view the event of a job or CronJob, click <span class="uicontrol" id="cce_10_0007__uicontrol5141163802911"><b>View Event</b></span> in the <strong id="cce_10_0007__b5141193842916">Operation</strong> column of the target workload.</p>
|
||||
<ol id="cce_10_0007__ol114609411810"><li id="cce_10_0007__li146044118811"><span>Log in to the CCE console, go to an existing cluster, and choose <strong id="cce_10_0007__b1144092910">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__li14460104111813"><span>On the <strong id="cce_10_0007__b10635642182913">Deployments</strong> tab page, click the target workload. In the <strong id="cce_10_0007__b1463504252913">Pods</strong> tab page, click the <span class="uicontrol" id="cce_10_0007__uicontrol96354422296"><b>View Events</b></span> to view the event name, event type, number of occurrences, Kubernetes event, first occurrence time, and last occurrence time.</span><p><div class="note" id="cce_10_0007__en-us_topic_0107283638_note645916250256"><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_p2459102542512">Event data will be retained for one hour and then automatically deleted.</p>
|
||||
<ol id="cce_10_0007__ol114609411810"><li id="cce_10_0007__li146044118811"><span>Log in to the <span id="cce_10_0007__ph17740135714307">CCE console</span>, go to the console of an existing cluster, and choose <strong id="cce_10_0007__b1144092910">Workloads</strong> in the navigation pane.</span></li><li id="cce_10_0007__li14460104111813"><span>On the <strong id="cce_10_0007__b10635642182913">Deployments</strong> tab page, click the target workload. In the <strong id="cce_10_0007__b1463504252913">Pods</strong> tab page, click the <span class="uicontrol" id="cce_10_0007__uicontrol96354422296"><b>View Events</b></span> to view the event name, event type, number of occurrences, Kubernetes event, first occurrence time, and last occurrence time.</span><p><div class="note" id="cce_10_0007__en-us_topic_0107283638_note645916250256"><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_p2459102542512">Event data will be retained for one hour and then automatically deleted.</p>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,38 +1,41 @@
|
||||
<a name="cce_10_0010"></a><a name="cce_10_0010"></a>
|
||||
|
||||
<h1 class="topictitle1">Overview</h1>
|
||||
<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_0000002218819838.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 number 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 pods 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 model seamlessly combines VPC routing with the underlying network, making it ideal for high-performance scenarios. However, the maximum number of nodes allowed in a cluster is determined by the VPC route quota. Each node is assigned a CIDR block of a fixed size. The VPC network model outperforms the container tunnel network model in terms of performance because it does not have tunnel encapsulation overhead. 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 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>
|
||||
<h1 class="topictitle1">Networking Overview</h1>
|
||||
<div id="body1522665832344"><p id="cce_10_0010__p1975632219432">The CCE cluster network architecture is based on the Kubernetes native network model. Combined with the cloud infrastructure capabilities, the architecture builds a three-layer communication system covering nodes, containers, and services. It is built to efficiently forward intra-cluster and inter-cluster traffic, discover services, and isolate networks. It meets the requirements of all scenarios that cover small- and medium-sized applications and large-scale microservice architectures.</p>
|
||||
<p id="cce_10_0010__p13310145119810">You can learn about the cluster network from the following aspects:</p>
|
||||
<ul id="cce_10_0010__ul65247121891"><li id="cce_10_0010__li14524161214917">Cluster network structure (<strong id="cce_10_0010__b1593645719381"><a href="#cce_10_0010__section1131733719195">Cluster Network Structure</a></strong>): A cluster consists of multiple nodes, and each node runs multiple pods (containers). To ensure the communications between nodes, between nodes and pods, and between pods, a cluster requires:<ul id="cce_10_0010__ul4887053103815"><li id="cce_10_0010__li2887853183810"><strong id="cce_10_0010__b2088745343815">A node network</strong>: enables all nodes in a cluster to communicate with each other.</li><li id="cce_10_0010__li289312539384"><strong id="cce_10_0010__b0887155318385">A container network</strong>: enables all pods in a cluster to communicate with each other using IP addresses without NAT.</li><li id="cce_10_0010__li2887205333818"><strong id="cce_10_0010__b688755323810">A Service network</strong>: ensures Services in a cluster can be accessed by other pods or Services in that cluster through stable virtual IP addresses.</li></ul>
|
||||
</li><li id="cce_10_0010__li55241612391"><strong id="cce_10_0010__b1433181819395">Pod access in a cluster</strong>: Kubernetes provides Services (<a href="#cce_10_0010__section1860619221134">Service</a>) and ingresses (<a href="#cce_10_0010__section1248852094313">Ingress</a>) for pod access. This section summarizes common network access scenarios. You can select the appropriate 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__p1299218814417">Cluster networks are the core of Kubernetes. They ensure that containers in a cluster can communicate with each other and with external systems. There are:</p>
|
||||
<ul id="cce_10_0010__ul71285348441"><li id="cce_10_0010__li9128173413440"><strong id="cce_10_0010__b766151614472">Node network</strong>: CCE uses VPC subnets as the node network of a cluster. The available IP addresses of a subnet limit the maximum number of nodes that can be created in a cluster. For example, a subnet with a mask of /24 can allocate a maximum of 254 node IP addresses. The number of nodes that can be created in a cluster is also affected by the container network. For details, see container network models.</li><li id="cce_10_0010__li36181922104819"><strong id="cce_10_0010__b890355844712">Container network</strong>: Pods in a cluster are allocated independent IP addresses. All pods in a cluster are on a flat network and can be accessed using their IP addresses without NAT. Kubernetes uses <a href="https://github.com/containernetworking/cni" target="_blank" rel="noopener noreferrer">Container Network Interface (CNI)</a> to standardize the network between containers. Network model plugins are used to allocate independent IP addresses to pods for flat network communications in a cluster. Different network models have different allocation principles.<div class="fignone" id="cce_10_0010__fig3527185315566"><span class="figcap"><b>Figure 1 </b>Container network</span><br><span><img class="eddx" id="cce_10_0010__image7527145315613" src="en-us_image_0000002467719141.png"></span></div>
|
||||
<p id="cce_10_0010__p17931122014208">Currently, CCE supports the following container network models:</p>
|
||||
<ul id="cce_10_0010__ul10464211245"><li id="cce_10_0010__li124613292414"><a href="cce_10_0282.html">Container tunnel network</a>: This network model is constructed based on the node network through tunnel encapsulation, but it is independent of the node network. It 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__li11464220244"><a href="cce_10_0283.html">VPC network</a>: This network model seamlessly combines VPC routing with the underlying network, making it ideal for high-performance scenarios. However, the maximum number of nodes allowed in a cluster is determined by the VPC route quota. Each node in a cluster that uses a VPC network is running in a subnet with a fixed number of IP addresses. The VPC network model outperforms the container tunnel network model in terms of performance because it does not have tunnel encapsulation overhead. In addition, as the routes destined for nodes and containers are added to a VPC route table, containers can be directly accessed from outside the cluster.</li><li id="cce_10_0010__li174612102411"><a href="cce_10_0284.html">Cloud Native Network 2.0</a> is a next-generation model developed by CCE and combines the network interfaces and supplementary network interfaces of VPC. Pod IP addresses are allocated from the VPC CIDR block. ELB passthrough networking is supported to forward requests to containers. Security groups and EIPs are associated to deliver high performance.</li></ul>
|
||||
<p id="cce_10_0010__p14408316536">The performance, networking scale, and application scenarios of a container network vary depending on 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__li1112813415448"><strong id="cce_10_0010__b18219104465218">Service network</strong>: Services are a kind of Kubernetes resource object. Each Service has a fixed IP address. Kubernetes provides stable access entries for pods through Services. When creating a cluster on CCE, you can specify the Service CIDR block. Service CIDR blocks cannot overlap with the node CIDR blocks or container CIDR blocks. They can be used only in a cluster.</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_0258889981.png"></span></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">In Kubernetes, pods are considered ephemeral and can be replaced at any time. When a pod is destroyed or replaced, its network resources also change. You need to provide a stable access method for pods. Kubernetes uses a Service to provide a fixed access entry for a group of pods with the same functions and balances the load among these pods.</p>
|
||||
<p id="cce_10_0010__p10450183103711">As shown in the following figure, a Service is associated with a group of pods through a selector. When the IP address and port of the Service are accessed, traffic is distributed to these pods. When pods change, the Service automatically updates the backend forwarding rules to ensure that the latest pods can be accessed through the Service.</p>
|
||||
<div class="fignone" id="cce_10_0010__en-us_topic_0249851121_fig163156154816"><span class="figcap"><b>Figure 2 </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>
|
||||
<p id="cce_10_0010__p1677717174140">For details about the Service, see <a href="cce_10_0249.html">Service 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 TCP and UDP at Layer 4. Ingresses forward requests using HTTP and HTTPS at Layer 7. Domain names and paths can be used for access of finer granularities.</p>
|
||||
<div class="fignone" id="cce_10_0010__fig816719454212"><span class="figcap"><b>Figure 2 </b>An ingress and associated Services</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 class="fignone" id="cce_10_0010__fig816719454212"><span class="figcap"><b>Figure 3 </b>An ingress and associated Services</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">Ingress Overview</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0010__section19359105124011"><h4 class="sectiontitle">DNS</h4><p id="cce_10_0010__p783620210412">CCE uses CoreDNS to implement service discovery in a cluster. For example, a client can access backend pods through a ClusterIP Service whose name is mapped to a cluster-scoped virtual IP address. This approach decouples the invoking between applications in a cluster from specific IP addresses and deployment environments. For details about the cluster DNS settings, see <a href="cce_10_0360.html">DNS Overview</a>.</p>
|
||||
<div class="fignone" id="cce_10_0010__fig56221517187"><span class="figcap"><b>Figure 4 </b>Example of domain name resolution in a cluster</span><br><span><img id="cce_10_0010__cce_10_0360_image13391194511278" src="en-us_image_0000002467679373.png"></span></div>
|
||||
</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 a VPC network or tunnel network is used), bind an EIP to the pod IP address (when Cloud Native Network 2.0 is used), or configure SNAT rules through the NAT gateway. For details, see <a href="cce_10_0400.html">Accessing the Internet 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 a private network: The workload accesses the private network address, but the implementation method varies depending on container network models. Ensure that the peer security group allows access 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 a VPC network or tunnel network is used), bind an EIP to the pod IP address (when Cloud Native Network 2.0 is used), or configure an SNAT rule on the NAT gateway. For details, see <a href="cce_10_0400.html">Accessing the Internet 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_0000002253619737.png"></span></div>
|
||||
<div class="fignone" id="cce_10_0010__fig13795829151515"><span class="figcap"><b>Figure 5 </b>Network access diagram</span><br><span><img id="cce_10_0010__image445972519529" src="en-us_image_0000002434080684.png"></span></div>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0020.html">Network</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0020.html">Networking</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
@ -1,16 +1,57 @@
|
||||
<a name="cce_10_0011"></a><a name="cce_10_0011"></a>
|
||||
|
||||
<h1 class="topictitle1">ClusterIP</h1>
|
||||
<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"><Service name></em>.<em id="cce_10_0011__i14179133519374"><Namespace of the workload></em><strong id="cce_10_0011__b164892813716">.svc.cluster.local:</strong><em id="cce_10_0011__i19337102815712"><Port></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_0000002253620361.png"></span></div>
|
||||
<div id="body1522736584192"><p id="cce_10_0011__p03821416270"><span class="keyword" id="cce_10_0011__keyword1546144019373">ClusterIP</span> is the default Service type of Kubernetes and provides stable intra-cluster access. Kubernetes assigns a virtual IP address (cluster-scoped IP address) that can only be accessed within the cluster from the Service CIDR block of the cluster. CoreDNS maps the <span class="uicontrol" id="cce_10_0011__uicontrol789033512616"><b>cluster-internal domain name</b></span> to the assigned cluster IP address. The domain name format is <em id="cce_10_0011__i111021242407"><Service-name></em>.<em id="cce_10_0011__i210234114014"><namespace-of-the-workload></em><strong id="cce_10_0011__b16102844404">.svc.cluster.local:</strong><em id="cce_10_0011__i91029414016"><port></em>, for example, <strong id="cce_10_0011__b610215434010">nginx.default.svc.cluster.local:80</strong>.</p>
|
||||
<p id="cce_10_0011__p326011246819">If pods need to communicate with each other within a cluster, you can create a ClusterIP Service. For example, if a frontend pod in a cluster needs to access a backend database in the same cluster, you can create a ClusterIP Service.</p>
|
||||
<p id="cce_10_0011__p1778412445517"><a href="#cce_10_0011__fig192245420557">Figure 1</a> shows how ClusterIP works. You can learn about the access channel, container port, and access port mapping rules of this type of Service.</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_0000002434081104.png"></span></div>
|
||||
<div class="section" id="cce_10_0011__section51925078171335"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0011__ol1321170617144"><li id="cce_10_0011__li64402531616"><span>Log in to the <span id="cce_10_0011__cce_10_0004_ph18314322182">CCE console</span> 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 & 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>Configure intra-cluster access parameters.</span><p>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0011__table23887196361" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0011__row33881619203617"><th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.5.2.3.2.1.1.3.1.1"><p id="cce_10_0011__p17388131914369">Parameter</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="75%" id="mcps1.3.5.2.3.2.1.1.3.1.2"><p id="cce_10_0011__p1388619183611">Description</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0011__row1038821923616"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.2.3.2.1.1.3.1.1 "><p id="cce_10_0011__p103881619143614">Service Name</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.5.2.3.2.1.1.3.1.2 "><p id="cce_10_0011__p338971913618">Enter a name, which can be the same as the workload name.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0011__row133899198363"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.2.3.2.1.1.3.1.1 "><p id="cce_10_0011__p738971923615">Service Type</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.5.2.3.2.1.1.3.1.2 "><p id="cce_10_0011__p5389131915363">Select <span class="uicontrol" id="cce_10_0011__uicontrol58292271528"><b>ClusterIP</b></span>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0011__row12389101933613"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.2.3.2.1.1.3.1.1 "><p id="cce_10_0011__p15389111920369">Namespace</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.5.2.3.2.1.1.3.1.2 "><p id="cce_10_0011__p193891119133610">Select the namespace that the workload belongs to.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0011__row167989113395"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.2.3.2.1.1.3.1.1 "><p id="cce_10_0011__p1979819119393">Selector</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.5.2.3.2.1.1.3.1.2 "><p id="cce_10_0011__p1419965253918">The Service will be associated with the workload pods based on the label and direct traffic to the pods with this label.</p>
|
||||
<p id="cce_10_0011__p4970919123814">You can add a key and value for the pod label and click <span class="uicontrol" id="cce_10_0011__uicontrol297916287394"><b>Confirm</b></span>.</p>
|
||||
<p id="cce_10_0011__p379816111392">You can also click <strong id="cce_10_0011__b15870155912238">Reference Workload Label</strong> to use the label of an existing workload. In the dialog box displayed, select a workload and click <strong id="cce_10_0011__b7870359182315">OK</strong>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0011__row9611112183918"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.2.3.2.1.1.3.1.1 "><p id="cce_10_0011__p361262163911">Protocol Version</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.5.2.3.2.1.1.3.1.2 "><p id="cce_10_0011__p1777572316397">Select the IP address of different versions based on service requirements. <strong id="cce_10_0011__b484914882410">This function is displayed only when IPv6 is enabled during the creation of clusters of v1.15 or later.</strong></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0011__row1961420125396"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.5.2.3.2.1.1.3.1.1 "><p id="cce_10_0011__p14614141216391">Port</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.5.2.3.2.1.1.3.1.2 "><ul id="cce_10_0011__ul6289131916397"><li id="cce_10_0011__li2289619143917"><strong id="cce_10_0011__b914900566">Protocol</strong>: the protocol supported by the Service.</li><li id="cce_10_0011__li628915191395"><strong id="cce_10_0011__b569396568">Container Port</strong>: the listening port of the service containers. The port ranges from 1 to 65535. You need to determine the port based on the container image. For example, the default port of Nginx is 80, and the default port of MySQL is 3306.</li><li id="cce_10_0011__li86391810174111"><strong id="cce_10_0011__b1066262561">Service Port</strong>: the port used to access the ClusterIP Service. You can customize the port as required. The port ranges from 1 to 65535.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</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>In the navigation pane, choose <strong id="cce_10_0011__b18658321171411"><span id="cce_10_0011__text9765124722315">Services & 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>Configure 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>: Specify a 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 that the workload belongs to.</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>. The Service will use this label to select pods. You can also click <strong id="cce_10_0011__b796831114161">Reference Workload Label</strong> to use 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__li142435567390"><strong id="cce_10_0011__b1917147174010">Protocol Version</strong>: Select the IP address of different versions based on service requirements. <strong id="cce_10_0011__b11322182810261">This parameter is available only in clusters of v1.15 or later with IPv6 enabled (set during cluster creation).</strong></li><li id="cce_10_0011__li388800117144"><strong id="cce_10_0011__b150413392315954">Ports</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>: listener port of the workload. 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>
|
||||
</p></li><li id="cce_10_0011__li5563226917144"><span>Click <strong id="cce_10_0011__b15590122052614">OK</strong>. Then, access the Service through <em id="cce_10_0011__i19315181994710"><ClusterIP></em>:<em id="cce_10_0011__i193154192477"><Service-port></em>.</span><p><p id="cce_10_0011__p7371754194518"></p>
|
||||
<p id="cce_10_0011__p364262418463"></p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0011__section9813121512319"><h4 class="sectiontitle">Setting the Access Type Using kubectl</h4><p id="cce_10_0011__p1626583075113">You can configure Service access using kubectl. This section uses an Nginx workload as an example to describe how to implement intra-cluster access using kubectl.</p>
|
||||
<div class="section" id="cce_10_0011__section9813121512319"><h4 class="sectiontitle">Using kubectl</h4><p id="cce_10_0011__p1626583075113">You can configure Service access using kubectl. This section uses an Nginx workload as an example to describe how to implement intra-cluster access using kubectl.</p>
|
||||
<ol id="cce_10_0011__ol19191171513118"><li id="cce_10_0011__li713365518486"><span>Use kubectl to access the cluster. For details, see <a href="cce_10_0107.html">Accessing a Cluster Using kubectl</a>.</span></li><li id="cce_10_0011__li15368125914444"><span>Create and edit the <strong id="cce_10_0011__b387556133418">nginx-deployment.yaml</strong> file to configure the sample workload. For details, see <a href="cce_10_0047.html">Creating a Deployment</a>. <strong id="cce_10_0011__b24072513352">nginx-deployment.yaml</strong> is an example file name. You can rename it as needed.</span><p><pre class="screen" id="cce_10_0011__screen4630145371716">vi nginx-deployment.yaml</pre>
|
||||
<div class="p" id="cce_10_0011__p76301953161719">File content:<pre class="screen" id="cce_10_0011__screen3630145361716">apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
@ -63,13 +104,12 @@ spec:
|
||||
<p id="cce_10_0011__p69744311435">Check the created Service.</p>
|
||||
<pre class="screen" id="cce_10_0011__screen14974113184316">kubectl get svc</pre>
|
||||
<p id="cce_10_0011__p6551651193219">If information similar to the following is displayed, the Service has been created, and a cluster-internal IP address has been assigned to the Service.</p>
|
||||
<pre class="screen" id="cce_10_0011__screen123716238321"># kubectl get svc
|
||||
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
||||
<pre class="screen" id="cce_10_0011__screen123716238321">NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
||||
kubernetes ClusterIP 10.247.0.1 <none> 443/TCP 4d6h
|
||||
nginx-clusterip ClusterIP 10.247.74.52 <none> 8080/TCP 14m</pre>
|
||||
</p></li><li id="cce_10_0011__li1847854017180"><span>Access the Service from a container or node in the cluster.</span><p><ol type="a" id="cce_10_0011__ol53271971591"><li id="cce_10_0011__li43271773592">Create a pod and access its container.<pre class="screen" id="cce_10_0011__screen149689934413">kubectl run -i --tty --image nginx:alpine test --rm /bin/sh</pre>
|
||||
</li><li id="cce_10_0011__li5722325185911">Run the <strong id="cce_10_0011__b5767171619395">curl</strong> command to access the Service.<ul id="cce_10_0011__ul1986311014474"><li id="cce_10_0011__li6863150114712">Access through <i><span class="varname" id="cce_10_0011__varname9966471907">IP:Port</span></i>:<pre class="screen" id="cce_10_0011__screen4464184664411">curl 10.247.74.52:8080</pre>
|
||||
</li><li id="cce_10_0011__li108638011473">Access through <i><span class="varname" id="cce_10_0011__varname1778718304394">Domain-name:Port</span></i>:<pre class="screen" id="cce_10_0011__screen1814544374612">curl nginx-clusterip.default.svc.cluster.local:8080</pre>
|
||||
</li><li id="cce_10_0011__li108638011473">Access using <i><span class="varname" id="cce_10_0011__varname697071110013">Domain name:Port</span></i> (not supported on nodes):<pre class="screen" id="cce_10_0011__screen1814544374612">curl nginx-clusterip.default.svc.cluster.local:8080</pre>
|
||||
<p id="cce_10_0011__p1946826135119"><i><span class="varname" id="cce_10_0011__varname225171385413">nginx-clusterip</span></i> is the Service name, <i><span class="varname" id="cce_10_0011__varname7682116175416">default</span></i> is the namespace where the Service is located, and <i><span class="varname" id="cce_10_0011__varname12918620105414">svc.cluster.local</span></i> is the DNS domain for the ClusterIP Service.</p>
|
||||
<p id="cce_10_0011__p1664427184818">You can simplify the domain name based on your requirements. For example, if the Service and the accessing pod are in the same namespace, you can use <strong id="cce_10_0011__b12461199115317">nginx-clusterip:8080</strong> to access it. If they are in different namespaces, you can use <strong id="cce_10_0011__b12537115419534">nginx-clusterip.default:8080</strong> to access it.</p>
|
||||
</li></ul>
|
||||
@ -105,7 +145,7 @@ Commercial support is available at
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0247.html">Service</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0247.html">Services</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
<h1 class="topictitle1">Creating a Node Pool</h1>
|
||||
<div id="body1564122277019"><div class="section" id="cce_10_0012__section14878105383915"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0012__p8060118">This section describes how to create a node pool and perform operations on the node pool. For details about how a node pool works, see <a href="cce_10_0081.html">Node Pool Overview</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0012__section953835110714"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0012__ol20304182312323"><li id="cce_10_0012__li7626452063"><span>Log in to the CCE console.</span></li><li id="cce_10_0012__li2075471341"><span>Click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0012__uicontrol1687204583717"><b>Nodes</b></span> in the navigation pane. In the right pane, click the <strong id="cce_10_0012__b1624616332153">Node Pools</strong> tab.</span></li><li id="cce_10_0012__li3387652384"><span>In the upper right corner of the page, click <strong id="cce_10_0012__b11543594158">Create Node Pool</strong>.</span><p><p id="cce_10_0012__p118166389258"><strong id="cce_10_0012__b861915213014">Basic Settings</strong></p>
|
||||
<div class="section" id="cce_10_0012__section953835110714"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0012__ol20304182312323"><li id="cce_10_0012__li9293104917265"><span>Log in to the <span id="cce_10_0012__ph15317134919712">CCE console</span>.</span></li><li id="cce_10_0012__li2075471341"><span>Click the cluster name to access the cluster console. Choose <span class="uicontrol" id="cce_10_0012__uicontrol1687204583717"><b>Nodes</b></span> in the navigation pane. In the right pane, click the <strong id="cce_10_0012__b1624616332153">Node Pools</strong> tab.</span></li><li id="cce_10_0012__li3387652384"><span>In the upper right corner of the page, click <strong id="cce_10_0012__b11543594158">Create Node Pool</strong>.</span><p><p id="cce_10_0012__p118166389258"><strong id="cce_10_0012__b861915213014">Basic Settings</strong></p>
|
||||
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0012__table11944089267" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Basic settings</caption><thead align="left"><tr id="cce_10_0012__row149446811263"><th align="left" class="cellrowborder" valign="top" width="24.529999999999998%" id="mcps1.3.2.2.3.2.2.2.3.1.1"><p id="cce_10_0012__p461429192615">Parameter</p>
|
||||
</th>
|
||||
@ -30,15 +30,15 @@
|
||||
<tbody><tr id="cce_10_0012__row1979195915497"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.2.2.3.2.4.1.2.3.1.1 "><p id="cce_10_0012__p18005944914">Node Type</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.4.1.2.3.1.2 "><p id="cce_10_0012__p4545161883316">Select a node type based on service requirements. Then, you can select a proper flavor from the node flavor list.</p>
|
||||
<div class="p" id="cce_10_0012__p17807592491">CCE standard clusters support the following node types:<ul id="cce_10_0012__en-us_topic_0000001199021246_ul203199555124"><li id="cce_10_0012__en-us_topic_0000001199021246_li931925518124">ECS (VM): A virtualized ECS is used as a cluster node.</li></ul>
|
||||
<div class="p" id="cce_10_0012__p17807592491">CCE standard clusters support the following node types:<ul id="cce_10_0012__en-us_topic_0000001199021246_ul203199555124"><li id="cce_10_0012__en-us_topic_0000001199021246_li931925518124">ECS (VM): A VM ECS is used as a cluster node.</li></ul>
|
||||
</div>
|
||||
<div class="p" id="cce_10_0012__p96493611512">CCE Turbo clusters support the following node types:<ul id="cce_10_0012__en-us_topic_0000001199021246_ul8196430101511"><li id="cce_10_0012__en-us_topic_0000001199021246_li31961830141515">ECS (VM): A VM ECS is used as a cluster node. A CCE Turbo cluster supports only the cloud servers that allow multiple ENIs. Select a server type displayed on the CCE console.</li></ul>
|
||||
<div class="p" id="cce_10_0012__p96493611512">CCE Turbo clusters support the following node types:<ul id="cce_10_0012__en-us_topic_0000001199021246_ul8196430101511"><li id="cce_10_0012__en-us_topic_0000001199021246_li31961830141515">ECS (VM): A VM ECS is used as a cluster node. A CCE Turbo cluster supports only the cloud servers that allow multiple network interfaces. Select a server type displayed on the CCE console.</li></ul>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0012__row156691178589"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.2.2.3.2.4.1.2.3.1.1 "><p id="cce_10_0012__p1669177185817">Specifications</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.4.1.2.3.1.2 "><div class="p" id="cce_10_0012__p156695715814">Select a node flavor based on service requirements. The available node flavors vary depending on regions. For details, see the CCE console. For the supported node flavors, see <a href="https://docs.otc.t-systems.com/en-us/api2/cce/cce_02_0368.html" target="_blank" rel="noopener noreferrer">Node Flavor Description</a>.<div class="note" id="cce_10_0012__note11800133115339"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0012__ul58111778349"><li id="cce_10_0012__li646111116412">If a node pool is configured with multiple node flavors, only the flavors (which can be located in different AZs) of the same node type are supported. For example, a node pool consisting of general computing-plus nodes supports only general computing-plus node flavors, but not the flavors of general computing nodes.</li><li id="cce_10_0012__li371317328359">A maximum of 10 node flavors can be added to a node pool (the flavors in different AZs are counted separately). When adding a node flavor, you can choose multiple AZs, but you need to specify them.</li><li id="cce_10_0012__li170272454517">Nodes in a newly created node pool are created using the default flavor. If the resources for the default flavor are insufficient, node creation will fail.</li><li id="cce_10_0012__li1755415220815">After a node pool is created, the flavors of existing nodes cannot be deleted.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.4.1.2.3.1.2 "><div class="p" id="cce_10_0012__p156695715814">Select a node flavor based on service requirements. The available node flavors vary depending on regions. For details, see the CCE console. For the supported node flavors, see <a href="https://docs.otc.t-systems.com/en-us/api2/cce/cce_02_0368.html" target="_blank" rel="noopener noreferrer">Node Flavor Description</a>.<div class="note" id="cce_10_0012__note11800133115339"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0012__ul58111778349"><li id="cce_10_0012__li646111116412">If a node pool is configured with multiple node flavors, only the flavors (which can be located in different AZs) of the same node type are supported. For example, a node pool consisting of general computing-plus nodes supports only general computing-plus node flavors, but not the flavors of general computing nodes.</li><li id="cce_10_0012__li3558258124416">Nodes added to a single node pool must have the same GPU type. For example, if you select the nvidia-v100 flavor, you are not allowed to select the nvidia-t4 flavor.</li><li id="cce_10_0012__li371317328359">A maximum of 10 node flavors can be added to a node pool (the flavors in different AZs are counted separately). When adding a node flavor, you can choose multiple AZs, but you need to specify them.</li><li id="cce_10_0012__li170272454517">Nodes in a newly created node pool are created using the default flavor. If the resources for the default flavor are insufficient, node creation will fail.</li><li id="cce_10_0012__li1755415220815">After a node pool is created, the flavors of existing nodes cannot be deleted.</li></ul>
|
||||
</div></div>
|
||||
</div>
|
||||
</td>
|
||||
@ -78,7 +78,7 @@
|
||||
<tbody><tr id="cce_10_0012__cce_10_0363_row5669170585"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.1 "><p id="cce_10_0012__cce_10_0363_p666916719588">System Disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.2 "><p id="cce_10_0012__cce_10_0363_p590942616323">System disk used by the node OS. The value ranges from 40 GiB to 1024 GiB. The default value is 50 GiB.</p>
|
||||
<div class="p" id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_p196385417139"><strong id="cce_10_0012__cce_10_0363_b11690144943516">System Disk Encryption</strong>: System disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. <strong id="cce_10_0012__cce_10_0363_b682192012018">Only the nodes of the </strong><strong id="cce_10_0012__cce_10_0363_b61621149008">Elastic Cloud Server (VM)</strong><strong id="cce_10_0012__cce_10_0363_b58218206019"> type in certain regions support system disk encryption. For details, see the console.</strong><ul id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_ul6195114261211"><li id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_li5195194211127"><strong id="cce_10_0012__cce_10_0363_b3414281726">Not encrypted</strong> is selected by default.</li><li id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_li5195184201217">If you select <strong id="cce_10_0012__cce_10_0363_b1914143518545">Enabled (key)</strong> for <strong id="cce_10_0012__cce_10_0363_b116539323544">System Disk Encryption</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0012__cce_10_0363_b1741811243462">View Key List</strong> and create a key. After the key is created, click the refresh icon next to the text box.</li><li id="cce_10_0012__cce_10_0363_li143358157216">If you select <strong id="cce_10_0012__cce_10_0363_b1034961319913">Enabled (KMS key ID)</strong> for <strong id="cce_10_0012__cce_10_0363_b6349513895">System Disk Encryption</strong>, enter a KMS key (which can be shared by others) in the current region.</li></ul>
|
||||
<div class="p" id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_p196385417139"><strong id="cce_10_0012__cce_10_0363_b11690144943516">System Disk Encryption</strong>: System disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. <strong id="cce_10_0012__cce_10_0363_b682192012018">Only the nodes of the Elastic Cloud Server (VM) type in certain regions support system disk encryption. For details, see the console.</strong><ul id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_ul6195114261211"><li id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_li5195194211127"><strong id="cce_10_0012__cce_10_0363_b3414281726">Not encrypted</strong> is selected by default.</li><li id="cce_10_0012__cce_10_0363_en-us_topic_0107283640_li5195184201217">If you select <strong id="cce_10_0012__cce_10_0363_b1914143518545">Enabled (key)</strong> for <strong id="cce_10_0012__cce_10_0363_b116539323544">System Disk Encryption</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0012__cce_10_0363_b1741811243462">View Key List</strong> and create a key. After the key is created, click the refresh icon next to the text box.</li><li id="cce_10_0012__cce_10_0363_li143358157216">If you select <strong id="cce_10_0012__cce_10_0363_b1034961319913">Enabled (KMS key ID)</strong> for <strong id="cce_10_0012__cce_10_0363_b6349513895">System Disk Encryption</strong>, enter a KMS key (which can be shared by others) in the current region.</li></ul>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
@ -92,7 +92,7 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0012__cce_10_0363_row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.1 "><p id="cce_10_0012__cce_10_0363_p0669147185817">Data Disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.2 "><ul id="cce_10_0012__cce_10_0363_ul13347201216402"><li id="cce_10_0012__cce_10_0363_li103472126407"><strong id="cce_10_0012__cce_10_0363_b87711342223">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol1378123452217"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol107853413227"><b>Data Disk</b></span>. <strong id="cce_10_0012__cce_10_0363_b187815343221">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.<ul id="cce_10_0012__cce_10_0363_ul324262033711"><li id="cce_10_0012__cce_10_0363_li1124252010378">Default data disk: used for container runtime and kubelet components. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.</li><li id="cce_10_0012__cce_10_0363_li6177165413374">Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.2 "><ul id="cce_10_0012__cce_10_0363_ul13347201216402"><li id="cce_10_0012__cce_10_0363_li103472126407"><strong id="cce_10_0012__cce_10_0363_b14356162274112">At least one default data disk must be added</strong> for storing container runtime and kubelet components if <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol1570817562482"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol179781326143914"><b>Data Disk</b></span>. <strong id="cce_10_0012__cce_10_0363_b5708195624814">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong> This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.<ul id="cce_10_0012__cce_10_0363_ul324262033711"><li id="cce_10_0012__cce_10_0363_li1124252010378">Default data disk: used for container runtime and kubelet components. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.</li><li id="cce_10_0012__cce_10_0363_li6177165413374">Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.</li></ul>
|
||||
</li><li id="cce_10_0012__cce_10_0363_li18830161664015">If <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol2621173512497"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0012__cce_10_0363_uicontrol19561032184918"><b>System Disk</b></span>, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.</li></ul>
|
||||
<div class="note" id="cce_10_0012__cce_10_0363_note95411755120"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0012__cce_10_0363_ul1388875765811"><li id="cce_10_0012__cce_10_0363_li9888165712586">If the node flavor is disk-intensive or ultra-high I/O, one data disk can be a local disk.</li><li id="cce_10_0012__cce_10_0363_li7888757125811">Local disks may break down and do not ensure data reliability. Store your service data in EVS disks, which are more reliable than local disks.</li></ul>
|
||||
</div></div>
|
||||
@ -162,7 +162,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.32%" headers="mcps1.3.2.2.3.2.10.1.2.3.1.2 "><p id="cce_10_0012__en-us_topic_0000001199021246_p14909254174019">You can add resource tags to classify resources.</p>
|
||||
<p id="cce_10_0012__en-us_topic_0000001199021246_p10327184710426">You can create <span class="uicontrol" id="cce_10_0012__en-us_topic_0000001199021246_uicontrol922854293212"><b>predefined tags</b></span> on the TMS console. These tags are available to all resources that support tags. You can use these tags to improve the tag creation and resource migration efficiency. </p>
|
||||
<p id="cce_10_0012__en-us_topic_0000001199021246_p1738110524401">CCE will automatically create the "CCE-Dynamic-Provisioning-Node=<em id="cce_10_0012__i1144553117262">Node ID</em>" tag.</p>
|
||||
<p id="cce_10_0012__en-us_topic_0000001199021246_p1738110524401">CCE will automatically create the <strong id="cce_10_0012__b1029719881312">CCE-Dynamic-Provisioning-Node=</strong><em id="cce_10_0012__i1144553117262">Node ID</em> tag.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0012__row978161211384"><td class="cellrowborder" valign="top" width="23.68%" headers="mcps1.3.2.2.3.2.10.1.2.3.1.1 "><p id="cce_10_0012__p98221312193817">Kubernetes Label</p>
|
||||
@ -210,22 +210,22 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0012__en-us_topic_0000001199021246_row23431056203915"><td class="cellrowborder" valign="top" width="23.68%" headers="mcps1.3.2.2.3.2.10.1.2.3.1.1 "><p id="cce_10_0012__en-us_topic_0000001199021246_p534319566391">Pre-installation Command</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.32%" headers="mcps1.3.2.2.3.2.10.1.2.3.1.2 "><p id="cce_10_0012__p1644103463319">Installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.</p>
|
||||
<td class="cellrowborder" valign="top" width="76.32%" headers="mcps1.3.2.2.3.2.10.1.2.3.1.2 "><p id="cce_10_0012__p1644103463319">Installation script command. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.</p>
|
||||
<p id="cce_10_0012__en-us_topic_0000001199021246_p03368579295">The script will be executed before Kubernetes software is installed. Note that if the script is incorrect, Kubernetes software may fail to be installed.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0012__en-us_topic_0000001199021246_row1167794673912"><td class="cellrowborder" valign="top" width="23.68%" headers="mcps1.3.2.2.3.2.10.1.2.3.1.1 "><p id="cce_10_0012__en-us_topic_0000001199021246_p18677104643916">Post-installation Command</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.32%" headers="mcps1.3.2.2.3.2.10.1.2.3.1.2 "><p id="cce_10_0012__p1335511819219">Installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.</p>
|
||||
<p id="cce_10_0012__en-us_topic_0000001199021246_p13471136154110">The script will be executed after Kubernetes software is installed, which does not affect the installation.</p>
|
||||
<div class="note" id="cce_10_0012__en-us_topic_0000001199021246_note1590243818552"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0012__en-us_topic_0000001199021246_p1590273816552">Do not run the <strong id="cce_10_0012__b1251418157018">reboot</strong> command in the post-installation script to restart the system immediately. To restart the system, run the <strong id="cce_10_0012__b155141315508">shutdown -r 1</strong> command to restart with a delay of one minute.</p>
|
||||
<td class="cellrowborder" valign="top" width="76.32%" headers="mcps1.3.2.2.3.2.10.1.2.3.1.2 "><p id="cce_10_0012__p1335511819219">Installation script command. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.</p>
|
||||
<div class="p" id="cce_10_0012__en-us_topic_0000001244141037_p13471136154110">The script will be executed after Kubernetes software is installed, which does not affect the installation. <span id="cce_10_0012__cce_10_0363_ph8900135164311">During post-installation script execution, pods can be scheduled normally. However, if the script execution times out, node installation will fail. To prevent pods from being scheduled to nodes with incomplete script execution, enable the option to schedule pods only after the post-installation script execution completes.</span><div class="caution" id="cce_10_0012__cce_10_0363_note14983019515"><span class="cautiontitle"> CAUTION: </span><div class="cautionbody"><p id="cce_10_0012__cce_10_0363_p792373105115">Do not use the <strong id="cce_10_0012__cce_10_0363_b4852104401">reboot</strong> command in the post-installation script to restart the system immediately. Instead, use the <strong id="cce_10_0012__cce_10_0363_b78527414018">shutdown -r 1</strong> command to restart the system with a one-minute delay.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0012__en-us_topic_0000001199021246_row3366174093118"><td class="cellrowborder" valign="top" width="23.68%" headers="mcps1.3.2.2.3.2.10.1.2.3.1.1 "><p id="cce_10_0012__en-us_topic_0000001199021246_p123672040183119">Agency</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.32%" headers="mcps1.3.2.2.3.2.10.1.2.3.1.2 "><p id="cce_10_0012__en-us_topic_0000001199021246_p15869944123119">An agency is created by the tenant administrator on the IAM console. Using an agency, you can share your cloud server resources with another account, or entrust a more professional person or team to manage your resources.</p>
|
||||
<p id="cce_10_0012__en-us_topic_0000001199021246_p151464163220">If no agency is available, click <strong id="cce_10_0012__b1163363920016">Create Agency</strong> on the right to create one.</p>
|
||||
<td class="cellrowborder" valign="top" width="76.32%" headers="mcps1.3.2.2.3.2.10.1.2.3.1.2 "><p id="cce_10_0012__p15869944123119">If you need to share ECS resources with other accounts or delegate a more professional person or team to manage the resources, you can create an agency on IAM and grant the agency the permissions to manage ECS resources. The delegated account can log in to the cloud system and switch to your account to manage resources. You do not need to share security credentials (such as passwords) with other accounts, ensuring the security of your account.</p>
|
||||
<p id="cce_10_0012__p186991857115911">If you have created an agency, select the agency from the drop-down list. If no agency is available, click <span class="uicontrol" id="cce_10_0012__uicontrol857405513814"><b>Create Agency</b></span> on the right to create one.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0012__row4917181815431"><td class="cellrowborder" valign="top" width="23.68%" headers="mcps1.3.2.2.3.2.10.1.2.3.1.1 "><p id="cce_10_0012__p1891810188438">Custom Prefix and Suffix</p>
|
||||
|
||||
@ -6,7 +6,7 @@
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0681.html">Creating a LoadBalancer Service</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0385.html">Configuring LoadBalancer Services Using Annotations</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0385.html">Configuring Advanced Load Balancing Functions Using Annotations</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0683.html">Configuring HTTP/HTTPS for a LoadBalancer Service</a></strong><br>
|
||||
</li>
|
||||
@ -33,7 +33,7 @@
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0247.html">Service</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0247.html">Services</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ data:
|
||||
</li><li id="cce_10_0015__li18669525155017">When a ConfigMap is used as an environment variable, data is not automatically updated when the ConfigMap is updated. To update the data, restart the pod.</li></ul>
|
||||
</div></div>
|
||||
<div class="section" id="cce_10_0015__section1737733192813"><a name="cce_10_0015__section1737733192813"></a><a name="section1737733192813"></a><h4 class="sectiontitle">Configuring Environment Variables of a Workload</h4><p id="cce_10_0015__p1975419271338"><strong id="cce_10_0015__b861465944612">Using the CCE console</strong></p>
|
||||
<ol id="cce_10_0015__ol475442783311"><li id="cce_10_0015__li775432712335"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0015__li17754102763319"><span>In the navigation pane, choose <strong id="cce_10_0015__b363832612589">Workloads</strong>. In the dialog box displayed, click <strong id="cce_10_0015__b1463892615588">Create Workload</strong> in the upper right corner.</span><p><p id="cce_10_0015__p1875542733312">When creating a workload, click <strong id="cce_10_0015__b27246401479">Environment Variables</strong> in the <strong id="cce_10_0015__b77256402479">Container Settings</strong> area, and click <strong id="cce_10_0015__b5452468565">Add Variable</strong>.</p>
|
||||
<ol id="cce_10_0015__ol475442783311"><li id="cce_10_0015__li330462393220"><span>Log in to the <span id="cce_10_0015__cce_10_0004_ph18314322182">CCE console</span> and click the cluster name to access the cluster console.</span></li><li id="cce_10_0015__li17754102763319"><span>In the navigation pane, choose <strong id="cce_10_0015__b363832612589">Workloads</strong>. In the dialog box displayed, click <strong id="cce_10_0015__b1463892615588">Create Workload</strong> in the upper right corner.</span><p><p id="cce_10_0015__p1875542733312">When creating a workload, click <strong id="cce_10_0015__b27246401479">Environment Variables</strong> in the <strong id="cce_10_0015__b77256402479">Container Settings</strong> area, and click <strong id="cce_10_0015__b5452468565">Add Variable</strong>.</p>
|
||||
<ul id="cce_10_0015__ul259911812406"><li id="cce_10_0015__li1459919185403"><strong id="cce_10_0015__b1914814524820">Added from ConfigMap</strong>: Select a ConfigMap to import all of its keys as environment variables.</li><li id="cce_10_0015__li12862240165014"><strong id="cce_10_0015__b155102528529">Added from ConfigMap key</strong>: Import a key in a ConfigMap as the value of an environment variable.<ul id="cce_10_0015__ul15909447135011"><li id="cce_10_0015__li95213468509"><strong id="cce_10_0015__b596420211530">Variable Name</strong>: name of an environment variable in the workload. The name can be customized and is set to the key name selected in the ConfigMap by default.</li><li id="cce_10_0015__li591660145119"><strong id="cce_10_0015__b33151918155511">Variable Value/Reference</strong>: Select a ConfigMap and the key to be imported. The corresponding value is imported as a workload environment variable.</li></ul>
|
||||
<p id="cce_10_0015__p3488115325013">For example, after you import the value <span class="parmvalue" id="cce_10_0015__parmvalue1521846165010"><b>Hello</b></span> of <span class="parmname" id="cce_10_0015__parmname195219464500"><b>SPECIAL_LEVEL</b></span> in ConfigMap <strong id="cce_10_0015__b182132016115816">cce-configmap</strong> as the value of workload environment variable <span class="parmname" id="cce_10_0015__parmname105214467503"><b>SPECIAL_LEVEL</b></span>, an environment variable named <span class="parmname" id="cce_10_0015__parmname1552546115017"><b>SPECIAL_LEVEL</b></span> with its value <span class="parmvalue" id="cce_10_0015__parmvalue1352146195016"><b>Hello</b></span> exists in the container.</p>
|
||||
</li></ul>
|
||||
@ -94,9 +94,9 @@ CCE</pre>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0015__section17930105710189"><a name="cce_10_0015__section17930105710189"></a><a name="section17930105710189"></a><h4 class="sectiontitle">Configuring Command Line Parameters</h4><p id="cce_10_0015__p45411930102310">You can use a ConfigMap as an environment variable to set commands or parameter values for a container by using the environment variable substitution syntax $(VAR_NAME).</p>
|
||||
<p id="cce_10_0015__p5994114316458"><strong id="cce_10_0015__b114442425326">Using the CCE console</strong></p>
|
||||
<ol id="cce_10_0015__ol16994114312457"><li id="cce_10_0015__li6994843164519"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0015__li15994124354513"><span>In the navigation pane, choose <strong id="cce_10_0015__b89235174711">Workloads</strong>. In the dialog box displayed, click <strong id="cce_10_0015__b1487353414416">Create Workload</strong> in the upper right corner.</span><p><p id="cce_10_0015__p1999444310452">When creating a workload, click <strong id="cce_10_0015__b54131412335">Environment Variables</strong> in the <strong id="cce_10_0015__b144141719335">Container Settings</strong> area, and click <strong id="cce_10_0015__b854615035813">Add Variable</strong>. In this example, select <strong id="cce_10_0015__b1430221893413">Added from ConfigMap</strong>.</p>
|
||||
<ol id="cce_10_0015__ol16994114312457"><li id="cce_10_0015__li42631228253"><span>Log in to the <span id="cce_10_0015__cce_10_0004_ph18314322182_1">CCE console</span> and click the cluster name to access the cluster console.</span></li><li id="cce_10_0015__li15994124354513"><span>In the navigation pane, choose <strong id="cce_10_0015__b89235174711">Workloads</strong>. In the dialog box displayed, click <strong id="cce_10_0015__b1487353414416">Create Workload</strong> in the upper right corner.</span><p><p id="cce_10_0015__p1999444310452">When creating a workload, click <strong id="cce_10_0015__b54131412335">Environment Variables</strong> in the <strong id="cce_10_0015__b144141719335">Container Settings</strong> area, and click <strong id="cce_10_0015__b854615035813">Add Variable</strong>. In this example, select <strong id="cce_10_0015__b1430221893413">Added from ConfigMap</strong>.</p>
|
||||
<ul id="cce_10_0015__ul699410435458"><li id="cce_10_0015__li109941843144520"><strong id="cce_10_0015__cce_10_0015_b1914814524820">Added from ConfigMap</strong>: Select a ConfigMap to import all of its keys as environment variables.</li></ul>
|
||||
</p></li><li id="cce_10_0015__li109671539114618"><span>Click <strong id="cce_10_0015__b1137494243510">Lifecycle</strong> in the <strong id="cce_10_0015__b866373883517">Container Settings</strong> area, click the <strong id="cce_10_0015__b1655659113518">Post-Start</strong> tab on the right, and set the following parameters:</span><p><ul id="cce_10_0015__ul187452564918"><li id="cce_10_0015__li28741425174912"><strong id="cce_10_0015__b3211814163611">Processing Method</strong>: <strong id="cce_10_0015__b172321423619">CLI</strong></li><li id="cce_10_0015__li175584316502"><strong id="cce_10_0015__b092741516378">Command</strong>: Enter the following three command lines. <i><span class="varname" id="cce_10_0015__varname11232556182218">SPECIAL_LEVEL</span></i> and <i><span class="varname" id="cce_10_0015__varname7232175692212">SPECIAL_TYPE</span></i> are the environment variable names in the workload, which are key names in the <strong id="cce_10_0015__b1489856173716">cce-configmap</strong> ConfigMap.<pre class="screen" id="cce_10_0015__screen1276011131501">/bin/bash
|
||||
</p></li><li id="cce_10_0015__li109671539114618"><span>Click <strong id="cce_10_0015__b1137494243510">Lifecycle</strong> in the <strong id="cce_10_0015__b866373883517">Container Settings</strong> area, click the <strong id="cce_10_0015__b1655659113518">Post-Start</strong> tab on the right, and configure parameters.</span><p><ul id="cce_10_0015__ul187452564918"><li id="cce_10_0015__li28741425174912"><strong id="cce_10_0015__b3211814163611">Processing Method</strong>: <strong id="cce_10_0015__b172321423619">CLI</strong></li><li id="cce_10_0015__li175584316502"><strong id="cce_10_0015__b092741516378">Command</strong>: Enter the following three command lines. <i><span class="varname" id="cce_10_0015__varname11232556182218">SPECIAL_LEVEL</span></i> and <i><span class="varname" id="cce_10_0015__varname7232175692212">SPECIAL_TYPE</span></i> are the environment variable names in the workload, which are key names in the <strong id="cce_10_0015__b1489856173716">cce-configmap</strong> ConfigMap.<pre class="screen" id="cce_10_0015__screen1276011131501">/bin/bash
|
||||
-c
|
||||
echo $SPECIAL_LEVEL $SPECIAL_TYPE > /usr/share/nginx/html/index.html</pre>
|
||||
</li></ul>
|
||||
@ -146,7 +146,7 @@ spec:
|
||||
</div>
|
||||
<div class="section" id="cce_10_0015__section1490261161916"><a name="cce_10_0015__section1490261161916"></a><a name="section1490261161916"></a><h4 class="sectiontitle">Mounting a ConfigMap to a Workload Data Volume</h4><p id="cce_10_0015__p192196124125">The data stored in a ConfigMap can be referenced in a volume of type ConfigMap. You can mount such a volume to a specified container path. The platform supports the separation of workload codes and configuration files. ConfigMap volumes are used to store workload configuration parameters. Before that, create ConfigMaps in advance. For details, see <a href="cce_10_0152.html">Creating a ConfigMap</a>. </p>
|
||||
<p id="cce_10_0015__p1597512255182"><strong id="cce_10_0015__b38519476325">Using the CCE console</strong></p>
|
||||
<ol id="cce_10_0015__ol1964410161043"><li id="cce_10_0015__li1179513219432"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0015__li13692141222712"><span>In the navigation pane, choose <strong id="cce_10_0015__b102110358479">Workloads</strong>. In the dialog box displayed, click <strong id="cce_10_0015__b11957134319413">Create Workload</strong> in the upper right corner.</span><p><p id="cce_10_0015__p89743143278">When creating a workload, click <span class="uicontrol" id="cce_10_0015__uicontrol19397145984917"><b>Data Storage</b></span> in the <span class="uicontrol" id="cce_10_0015__uicontrol639895924919"><b>Container Settings</b></span> area. Click <span class="uicontrol" id="cce_10_0015__uicontrol13399165954917"><b>Add Volume</b></span> and select <strong id="cce_10_0015__b8400145915493">ConfigMap</strong> from the drop-down list.</p>
|
||||
<ol id="cce_10_0015__ol1964410161043"><li id="cce_10_0015__li1153310632519"><span>Log in to the <span id="cce_10_0015__cce_10_0004_ph18314322182_2">CCE console</span> and click the cluster name to access the cluster console.</span></li><li id="cce_10_0015__li13692141222712"><span>In the navigation pane, choose <strong id="cce_10_0015__b102110358479">Workloads</strong>. In the dialog box displayed, click <strong id="cce_10_0015__b11957134319413">Create Workload</strong> in the upper right corner.</span><p><p id="cce_10_0015__p89743143278">When creating a workload, click <span class="uicontrol" id="cce_10_0015__uicontrol19397145984917"><b>Data Storage</b></span> in the <span class="uicontrol" id="cce_10_0015__uicontrol639895924919"><b>Container Settings</b></span> area. Click <span class="uicontrol" id="cce_10_0015__uicontrol13399165954917"><b>Add Volume</b></span> and choose <strong id="cce_10_0015__b8400145915493">ConfigMap</strong> from the drop-down list.</p>
|
||||
</p></li><li id="cce_10_0015__li6644161617412"><span>Select parameters for mounting a ConfigMap volume, as shown in <a href="#cce_10_0015__table1776324831114">Table 1</a>.</span><p>
|
||||
<div class="tablenoborder"><a name="cce_10_0015__table1776324831114"></a><a name="table1776324831114"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0015__table1776324831114" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Mounting a ConfigMap volume</caption><thead align="left"><tr id="cce_10_0015__row177484871120"><th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.8.4.3.2.1.2.3.1.1"><p id="cce_10_0015__p977974818111">Parameter</p>
|
||||
</th>
|
||||
|
||||
@ -19,7 +19,7 @@ data:
|
||||
</li></ul>
|
||||
</div></div>
|
||||
<div class="section" id="cce_10_0016__section207271352141216"><a name="cce_10_0016__section207271352141216"></a><a name="section207271352141216"></a><h4 class="sectiontitle">Configuring Environment Variables of a Workload</h4><p id="cce_10_0016__p1975419271338"><strong id="cce_10_0016__b213354423733249">Using the CCE console</strong></p>
|
||||
<ol id="cce_10_0016__ol475442783311"><li id="cce_10_0016__li775432712335"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0016__li17754102763319"><span>In the navigation pane, choose <strong id="cce_10_0016__b48842638164736">Workloads</strong>. In the dialog box displayed, click <strong id="cce_10_0016__b109653168064736">Create Workload</strong> in the upper right corner.</span><p><p id="cce_10_0016__p1875542733312">When creating a workload, click <strong id="cce_10_0016__b1392016314276">Environment Variables</strong> in the <strong id="cce_10_0016__b8922143113278">Container Settings</strong> area, and click <strong id="cce_10_0016__b146165363112">Add Variable</strong>.</p>
|
||||
<ol id="cce_10_0016__ol475442783311"><li id="cce_10_0016__li330462393220"><span>Log in to the <span id="cce_10_0016__cce_10_0004_ph18314322182">CCE console</span> and click the cluster name to access the cluster console.</span></li><li id="cce_10_0016__li17754102763319"><span>In the navigation pane, choose <strong id="cce_10_0016__b48842638164736">Workloads</strong>. In the dialog box displayed, click <strong id="cce_10_0016__b109653168064736">Create Workload</strong> in the upper right corner.</span><p><p id="cce_10_0016__p1875542733312">When creating a workload, click <strong id="cce_10_0016__b1392016314276">Environment Variables</strong> in the <strong id="cce_10_0016__b8922143113278">Container Settings</strong> area, and click <strong id="cce_10_0016__b146165363112">Add Variable</strong>.</p>
|
||||
<ul id="cce_10_0016__ul259911812406"><li id="cce_10_0016__li1459919185403"><strong id="cce_10_0016__b16966165016278">Added from secret</strong>: Select a secret and import all keys in the secret as environment variables.</li><li id="cce_10_0016__li12862240165014"><strong id="cce_10_0016__b20968220132913">Added from secret key</strong>: Import the value of a key in a secret as the value of an environment variable.<ul id="cce_10_0016__ul15909447135011"><li id="cce_10_0016__li95213468509"><strong id="cce_10_0016__b199784317300">Variable Name</strong>: name of an environment variable in the workload. The name can be customized and is set to the key name selected in the secret by default.</li><li id="cce_10_0016__li591660145119"><strong id="cce_10_0016__b1268109153118">Variable Value/Reference</strong>: Select a secret and the key to be imported. The corresponding value is imported as a workload environment variable.</li></ul>
|
||||
<p id="cce_10_0016__p3488115325013">For example, after you import the value of <span class="parmname" id="cce_10_0016__parmname9630135816408"><b>username</b></span> in secret <strong id="cce_10_0016__b6631145811406">mysecret</strong> as the value of workload environment variable <span class="parmname" id="cce_10_0016__parmname863285812402"><b>username</b></span>, an environment variable named <span class="parmname" id="cce_10_0016__parmname0633185814019"><b>username</b></span> exists in the container.</p>
|
||||
</li></ul>
|
||||
@ -94,7 +94,7 @@ spec:
|
||||
</div>
|
||||
<div class="section" id="cce_10_0016__section472505211214"><a name="cce_10_0016__section472505211214"></a><a name="section472505211214"></a><h4 class="sectiontitle">Configuring the Data Volume of a Workload</h4><p id="cce_10_0016__p196047901010">You can mount a secret as a volume to the specified container path. Contents in a secret are user-defined. Before that, create a secret. For details, see <a href="cce_10_0153.html">Creating a Secret</a>.</p>
|
||||
<p id="cce_10_0016__p748195412417"><strong id="cce_10_0016__b201492784833249">Using the CCE console</strong></p>
|
||||
<ol id="cce_10_0016__ol668714114817"><li id="cce_10_0016__li1179513219432"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0016__li13692141222712"><span>Choose <strong id="cce_10_0016__b211914674314">Workloads</strong> in the navigation pane. In the right pane, click the <strong id="cce_10_0016__b812012614435">Deployments</strong> tab. Click <strong id="cce_10_0016__b25719165432">Create Workload</strong> in the upper right corner.</span><p><p id="cce_10_0016__p89743143278">When creating a workload, click <span class="uicontrol" id="cce_10_0016__uicontrol818333124318"><b>Data Storage</b></span> in the <span class="uicontrol" id="cce_10_0016__uicontrol151851931144318"><b>Container Settings</b></span> area. Click <span class="uicontrol" id="cce_10_0016__uicontrol1218616318436"><b>Add Volume</b></span> and select <strong id="cce_10_0016__b318973114434">Secret</strong> from the drop-down list.</p>
|
||||
<ol id="cce_10_0016__ol668714114817"><li id="cce_10_0016__li61302215256"><span>Log in to the <span id="cce_10_0016__cce_10_0004_ph18314322182_1">CCE console</span> and click the cluster name to access the cluster console.</span></li><li id="cce_10_0016__li13692141222712"><span>Choose <strong id="cce_10_0016__b211914674314">Workloads</strong> in the navigation pane. In the right pane, click the <strong id="cce_10_0016__b812012614435">Deployments</strong> tab. Click <strong id="cce_10_0016__b25719165432">Create Workload</strong> in the upper right corner.</span><p><p id="cce_10_0016__p89743143278">When creating a workload, click <span class="uicontrol" id="cce_10_0016__uicontrol818333124318"><b>Data Storage</b></span> in the <span class="uicontrol" id="cce_10_0016__uicontrol151851931144318"><b>Container Settings</b></span> area. Click <span class="uicontrol" id="cce_10_0016__uicontrol1218616318436"><b>Add Volume</b></span> and choose <strong id="cce_10_0016__b318973114434">Secret</strong> from the drop-down list.</p>
|
||||
</p></li><li id="cce_10_0016__li06877414482"><span>Select parameters for mounting a secret volume, as shown in <a href="#cce_10_0016__table861818920109">Table 1</a>.</span><p>
|
||||
<div class="tablenoborder"><a name="cce_10_0016__table861818920109"></a><a name="table861818920109"></a><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0016__table861818920109" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Mounting a secret volume</caption><thead align="left"><tr id="cce_10_0016__row1962619171020"><th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.8.4.3.2.1.2.3.1.1"><p id="cce_10_0016__p196285991018">Parameter</p>
|
||||
</th>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,10 +1,10 @@
|
||||
<a name="cce_10_0019"></a><a name="cce_10_0019"></a>
|
||||
|
||||
<h1 class="topictitle1">Helm Chart</h1>
|
||||
<h1 class="topictitle1">Helm Charts</h1>
|
||||
<div id="body1522665832345"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0191.html">Overview of a Chart</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0191.html">Chart Overview</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0146.html">Deploying an Application from a Chart</a></strong><br>
|
||||
</li>
|
||||
|
||||
@ -1,14 +1,14 @@
|
||||
<a name="cce_10_0020"></a><a name="cce_10_0020"></a>
|
||||
|
||||
<h1 class="topictitle1">Network</h1>
|
||||
<h1 class="topictitle1">Networking</h1>
|
||||
<div id="body1506570432072"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0010.html">Overview</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0010.html">Networking Overview</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0280.html">Container Network</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0280.html">Container Networks</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0247.html">Service</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0247.html">Services</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0248.html">Ingresses</a></strong><br>
|
||||
</li>
|
||||
|
||||
@ -4,7 +4,7 @@
|
||||
<div id="body1525226397666"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0025.html">CCE Operations Supported by Cloud Trace Service</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0025.html">CCE Operations Supported by CTS</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0026.html">Viewing CTS Traces in the Trace List</a></strong><br>
|
||||
</li>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,20 +1,68 @@
|
||||
<a name="cce_10_0026"></a><a name="cce_10_0026"></a>
|
||||
|
||||
<h1 class="topictitle1">Viewing CTS Traces in the Trace List</h1>
|
||||
<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 Cloud Trace Service (CTS) and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records (traces) generated in the last seven days.</p>
|
||||
<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_p5235541767">Cloud Trace Service (CTS) records operations performed on cloud service resources. A record contains information such as the user who performed the operation, IP address, operation content, and returned response message. These records facilitate security auditing, issue tracking, and resource locating. They also help you plan and use resources, and identify high-risk or non-compliant operations.</p>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section19271975203"><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_image2091881811436" src="en-us_image_0000001696838310.png"></span> in the upper left corner and choose <strong id="cce_10_0026__en-us_topic_0179639644_b785314592818">Management & Deployment</strong> > <strong id="cce_10_0026__en-us_topic_0179639644_b031292616283">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: Select <strong id="cce_10_0026__en-us_topic_0179639644_b1840823133614">Last 1 hour</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b6408123118362">Last 1 day</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b12408231123610">Last 1 week</strong>, or specify a custom time range within the last seven days.</li></ul>
|
||||
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section036851413573"><h4 class="sectiontitle">What Is a Trace?</h4><p id="cce_10_0026__en-us_topic_0179639644_p7344192412579">A trace is an operation log for a cloud service resource, tracked and stored by CTS. Traces record operations such as adding, modifying, or deleting cloud service resources. You can view them to identify who performed operations and when for detailed tracking.</p>
|
||||
</div>
|
||||
</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 5,000 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>
|
||||
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section19271975203"><h4 class="sectiontitle">Viewing Traces in the Trace List</h4><ol id="cce_10_0026__en-us_topic_0179639644_ol143115612115"><li id="cce_10_0026__en-us_topic_0179639644_li1629194722218"><span>Log in to the management console, click <span><img id="cce_10_0026__en-us_topic_0179639644_image1229124714224" src="en-us_image_0000002359774578.png"></span> in the upper left corner, and choose <strong id="cce_10_0026__en-us_topic_0179639644_b0101171161313">Management & Deployment</strong> > <strong id="cce_10_0026__en-us_topic_0179639644_b17101511131310">Cloud Trace Service</strong>.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li1443115692119"><span>In the navigation pane, choose <strong id="cce_10_0026__en-us_topic_0179639644_b5352121921314">Trace List</strong>.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li1468123811239"><span>In the upper right corner of the page, set a desired query time range: <strong id="cce_10_0026__en-us_topic_0179639644_b18885164252718">Last 1 hour</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b3885114232715">Last 1 day</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b1688574213277">Last 1 week</strong>. You can also click <strong id="cce_10_0026__en-us_topic_0179639644_b288519425275">Customize</strong> to specify a custom time range within the last seven days.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li243155612119"><span>Set filters to search for your desired traces, as shown in <a href="#cce_10_0026__en-us_topic_0179639644_fig139361441134311">Figure 1</a>.</span><p><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="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0026__en-us_topic_0179639644_table147746583014" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Trace filtering parameters</caption><thead align="left"><tr id="cce_10_0026__en-us_topic_0179639644_row1877510573019"><th align="left" class="cellrowborder" valign="top" width="18.95%" id="mcps1.3.3.2.4.2.2.2.3.1.1"><p id="cce_10_0026__en-us_topic_0179639644_p1877512593016">Parameter</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="81.05%" id="mcps1.3.3.2.4.2.2.2.3.1.2"><p id="cce_10_0026__en-us_topic_0179639644_p57751859302">Description</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0026__en-us_topic_0179639644_row1285411013373"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p28541510143716">Trace Type</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p08541510193711">Select <strong id="cce_10_0026__en-us_topic_0179639644_b14902228784">Management</strong> or <strong id="cce_10_0026__en-us_topic_0179639644_b129020281815">Data</strong>.</p>
|
||||
<ul id="cce_10_0026__en-us_topic_0179639644_ul1060181493817"><li id="cce_10_0026__en-us_topic_0179639644_li156071412384">Management traces record operations performed by users on cloud service resources, including creation, modification, and deletion.</li><li id="cce_10_0026__en-us_topic_0179639644_li1385816156388">Data traces are reported by OBS and record operations performed on data in OBS buckets, including uploads and downloads.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0026__en-us_topic_0179639644_row113186562383"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p157759523017">Trace Source</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p177757543019">Select the name of the cloud service that triggers a trace from the drop-down list.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0026__en-us_topic_0179639644_row531111429400"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p167757553018">Resource type</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p1677513515307">Select the type of the resource involved in a trace from the drop-down list.</p>
|
||||
<p id="cce_10_0026__en-us_topic_0179639644_p1077535173016">For details about the resource types of each cloud service, see section "Supported Services and Operations" in the <em id="cce_10_0026__en-us_topic_0179639644_i62441747131712">Cloud Trace Service User Guide</em>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0026__en-us_topic_0179639644_row17951953163817"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p17951145393815">Search By</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p1866016362423">Select one of the following options:</p>
|
||||
<ul id="cce_10_0026__en-us_topic_0179639644_ul8324201518432"><li id="cce_10_0026__en-us_topic_0179639644_li1332441519434"><strong id="cce_10_0026__en-us_topic_0179639644_b17755195192214">Resource ID</strong>: ID of the cloud resource involved in a trace.<p id="cce_10_0026__en-us_topic_0179639644_p927319140446">Leave this field empty if the resource has no resource ID or if resource creation failed.</p>
|
||||
</li><li id="cce_10_0026__en-us_topic_0179639644_li19324111594319"><strong id="cce_10_0026__en-us_topic_0179639644_b20740051162314">Trace name</strong>: name of a trace.<p id="cce_10_0026__en-us_topic_0179639644_p162131756164314">For details about the operations that can be audited for each cloud service, see section "Supported Services and Operations" in the <em id="cce_10_0026__en-us_topic_0179639644_i1219145055114">Cloud Trace Service User Guide</em>.</p>
|
||||
</li><li id="cce_10_0026__en-us_topic_0179639644_li53251315144311"><strong id="cce_10_0026__en-us_topic_0179639644_b113836152512">Resource name</strong>: name of the cloud resource involved in a trace.<p id="cce_10_0026__en-us_topic_0179639644_p546964974419">If the cloud resource involved in the trace does not have a resource name or the corresponding API operation does not involve the resource name parameter, leave this field empty.</p>
|
||||
</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0026__en-us_topic_0179639644_row10776105103014"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p47761954309">Operator</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p17761455309">User who triggers a trace.</p>
|
||||
<p id="cce_10_0026__en-us_topic_0179639644_p1577616513018">Select one or more operators from the drop-down list.</p>
|
||||
<p id="cce_10_0026__en-us_topic_0179639644_p47761952302">If the value of <strong id="cce_10_0026__en-us_topic_0179639644_b1470691118286">trace_type</strong> in a trace is <strong id="cce_10_0026__en-us_topic_0179639644_b18706191132818">SystemAction</strong>, the operation is triggered by the service and the trace's operator may be empty.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0026__en-us_topic_0179639644_row1377615153014"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p877615519306">Trace Status</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p10776115133014">Select one of the following options:</p>
|
||||
<ul id="cce_10_0026__en-us_topic_0179639644_ul177767517302"><li id="cce_10_0026__en-us_topic_0179639644_li177617583015"><strong id="cce_10_0026__en-us_topic_0179639644_b14380125823418">Normal</strong>: The operation succeeded.</li><li id="cce_10_0026__en-us_topic_0179639644_li1077665143015"><strong id="cce_10_0026__en-us_topic_0179639644_b128046471357">Warning</strong>: The operation failed.</li><li id="cce_10_0026__en-us_topic_0179639644_li19776135143018"><strong id="cce_10_0026__en-us_topic_0179639644_b134361033365">Incident</strong>: The operation caused a fault that is more serious than a normal failure, for example, causing other faults.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</p></li><li class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_li124311756172111"><span>Click <strong id="cce_10_0026__en-us_topic_0179639644_b158561654073256">Query</strong>.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li7432056192112"><span>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.</span><p><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 5,000 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>
|
||||
</p></li><li id="cce_10_0026__en-us_topic_0179639644_li15432145622119"><span>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.</span><p><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_image1767234653119" src="en-us_image_0000001942942816.png"></span></p>
|
||||
<p id="cce_10_0026__en-us_topic_0179639644_p145491156142711"></p>
|
||||
<p id="cce_10_0026__en-us_topic_0179639644_p1352018181294"></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 <a href="https://docs.otc.t-systems.com/cloud-trace-service/umn/user_guide/trace_references/trace_structure.html#cts-03-0010" target="_blank" rel="noopener noreferrer">Trace Structure</a> and <a href="https://docs.otc.t-systems.com/cloud-trace-service/umn/user_guide/trace_references/example_traces.html" target="_blank" rel="noopener noreferrer">Example Traces</a> in the <em id="cce_10_0026__en-us_topic_0179639644_i1765453563620">CTS User Guide</em>.</li></ol>
|
||||
</p></li><li id="cce_10_0026__en-us_topic_0179639644_li143245616217"><span>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.</span><p><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>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section18501734161612"><h4 class="sectiontitle">Helpful Links</h4><ul id="cce_10_0026__en-us_topic_0179639644_ul19442019172"><li id="cce_10_0026__en-us_topic_0179639644_li547715311275">For details about the key fields in the trace structure, see <a href="https://docs.otc.t-systems.com/cloud-trace-service/umn/user_guide/trace_references/trace_structure.html#cts-03-0010" target="_blank" rel="noopener noreferrer">Trace Structure</a> and <a href="https://docs.otc.t-systems.com/cloud-trace-service/umn/user_guide/trace_references/example_traces.html" target="_blank" rel="noopener noreferrer">Example Traces</a>.</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,9 +1,11 @@
|
||||
<a name="cce_10_0031"></a><a name="cce_10_0031"></a>
|
||||
|
||||
<h1 class="topictitle1">Managing a Cluster</h1>
|
||||
<h1 class="topictitle1">Managing Clusters</h1>
|
||||
<div id="body1506157580881"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0962.html">Cluster Management Overview</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0213.html">Modifying Cluster Configurations</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0602.html">Enabling Overload Control for a Cluster</a></strong><br>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -10,7 +10,7 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0658.html">Scaling a Node Pool</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0222.html">Managing a Node Pool</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0222.html">Managing Node Pools</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
@ -5,7 +5,7 @@
|
||||
</div>
|
||||
<div class="section" id="cce_10_0036__section1489437103610"><h4 class="sectiontitle">Precautions</h4><ul id="cce_10_0036__ul0917755162415"><li id="cce_10_0036__li1891719552246">Stopping a node will lead to pod migration, which may affect services. Perform this operation during off-peak hours.</li><li id="cce_10_0036__li791875552416">Unexpected risks may occur during the operation. Back up data beforehand.</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__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">OK</strong>.</span></li></ol>
|
||||
<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 <span id="cce_10_0036__ph149708409114">CCE console</span> 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">OK</strong>.</span></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
<a name="cce_10_0044"></a><a name="cce_10_0044"></a>
|
||||
|
||||
<h1 class="topictitle1">Elastic Volume Service</h1>
|
||||
<h1 class="topictitle1">EVS</h1>
|
||||
<div id="body0000001487281736"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0613.html">Overview</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0613.html">EVS Overview</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0614.html">Using an Existing EVS Disk Through a Static PV</a></strong><br>
|
||||
</li>
|
||||
@ -18,6 +18,8 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0381.html">Snapshots and Backups</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_1012.html">Configuring EVS Mount Options</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
|
||||
@ -4,7 +4,7 @@
|
||||
<div id="body1508729244098"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0006.html">Overview</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0006.html">Workload Overview</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0673.html">Creating a Workload</a></strong><br>
|
||||
</li>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -4,8 +4,8 @@
|
||||
<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__li757116188514"><span>In the navigation pane, choose <span class="uicontrol" id="cce_10_0063__uicontrol181311281374"><b>Nodes</b></span>. On the page displayed, click the <strong id="cce_10_0063__b1381322833713">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><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__p1793618441931">You can obtain created auto scaling policies on the <strong id="cce_10_0063__b514212331917"><span id="cce_10_0063__text67571453104013">Policies</span></strong> page.</p>
|
||||
<ol type="a" id="cce_10_0063__ol1691347738"><li id="cce_10_0063__li5468556932">Log in to the CCE console and click the cluster name to access the cluster console.</li><li id="cce_10_0063__li87313521749">In the navigation pane, choose <strong id="cce_10_0063__b576614533199"><span id="cce_10_0063__text1838374619210">Policies</span></strong>. On the page displayed, click the <strong id="cce_10_0063__b810014379203">Node Scaling Policies</strong> tab.</li><li id="cce_10_0063__li141394161742">Check the configuration of the auto scaling policies. Choose <strong id="cce_10_0063__b10717289212">More</strong> > <strong id="cce_10_0063__b817473111210">Scaling History</strong> for the target policy to check the scaling records of the policy.</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><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__p1793618441931">You can obtain created auto scaling policies on the <strong id="cce_10_0063__b514212331917"><span id="cce_10_0063__text67571453104013">Policies</span></strong> page.</p>
|
||||
<ol type="a" id="cce_10_0063__ol1691347738"><li id="cce_10_0063__li330462393220">Log in to the <span id="cce_10_0063__cce_10_0004_ph18314322182">CCE console</span> and click the cluster name to access the cluster console.</li><li id="cce_10_0063__li87313521749">In the navigation pane, choose <strong id="cce_10_0063__b576614533199"><span id="cce_10_0063__text1838374619210">Policies</span></strong>. On the page displayed, click the <strong id="cce_10_0063__b810014379203">Node Scaling Policies</strong> tab.</li><li id="cce_10_0063__li141394161742">Check the configuration of the auto scaling policies. Choose <strong id="cce_10_0063__b10717289212">More</strong> > <strong id="cce_10_0063__b817473111210">Scaling History</strong> for the target policy to check the scaling records of the policy.</li></ol>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
@ -20,7 +20,7 @@
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0291.html">Scaling a Node</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0291.html">Node Scaling</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0908.html">Cloud Native Observability Add-ons</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0909.html">Cloud Native Heterogeneous Computing Add-ons</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0909.html">Cloud Native AI Add-ons</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0910.html">Container Network Add-ons</a></strong><br>
|
||||
</li>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -4,6 +4,8 @@
|
||||
<div id="body8662426"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_bulletin_0104.html">Kubernetes 1.32 Release Notes</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_bulletin_0099.html">Kubernetes 1.31 Release Notes</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_bulletin_0095.html">Kubernetes 1.30 Release Notes</a></strong><br>
|
||||
@ -14,7 +16,7 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_bulletin_0059.html">Kubernetes 1.27 Release Notes</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_bulletin_0058.html">Kubernetes 1.25 (EOM) Release Notes</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_bulletin_0058.html">Kubernetes 1.25 Release Notes</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_bulletin_0027.html">Kubernetes 1.23 (EOM) Release Notes</a></strong><br>
|
||||
</li>
|
||||
|
||||
@ -14,7 +14,7 @@
|
||||
</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 custom 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">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>
|
||||
<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>
|
||||
<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>
|
||||
@ -122,8 +122,8 @@
|
||||
<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_0892.html">Configuring Node Affinity Scheduling (nodeAffinity)</a></li></ul>
|
||||
<div class="section" id="cce_10_0081__section17716744163316"><h4 class="sectiontitle">Helpful Links</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 Node Pools</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_0892.html">Configuring Node Affinity Scheduling (nodeAffinity)</a></li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
@ -4,24 +4,24 @@
|
||||
<div id="body1508729244098"><div class="section" id="cce_10_0083__section11873141710246"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0083__p799618243249">After a workload scaling policy is created, you can update and delete the policy, as well as edit the YAML file.</p>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0083__section14993443181414"><h4 class="sectiontitle">Procedure</h4><p id="cce_10_0083__p713741135215">You can view the rules, latest status, and events of a workload scaling 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__b19449409494"><span id="cce_10_0083__text67571453104013">Policies</span></strong>. On the <strong id="cce_10_0083__b1981255145015">Scaling Policies</strong> tab page, click the <strong id="cce_10_0083__b818535165015">HPA Policies</strong>/<strong id="cce_10_0083__b135618485506">CronHPA Policies</strong> tab based on the scaling policy type.</span></li><li id="cce_10_0083__li641003813527"><span>Check the latest status, rules, and associated workloads of a scaling policy.</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 check a created scaling 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 obtain the scaling policies. You can also obtain 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>
|
||||
<ol id="cce_10_0083__ol17409123885219"><li id="cce_10_0083__li330462393220"><span>Log in to the <span id="cce_10_0083__cce_10_0004_ph18314322182">CCE console</span> 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__b19449409494"><span id="cce_10_0083__text67571453104013">Policies</span></strong>. On the <strong id="cce_10_0083__b1981255145015">Scaling Policies</strong> tab, click the <strong id="cce_10_0083__b818535165015">HPA Policies</strong>/<strong id="cce_10_0083__b135618485506">CronHPA Policies</strong> tab based on the scaling policy type.</span></li><li id="cce_10_0083__li641003813527"><span>Check the latest status, rules, and associated workloads of a scaling policy.</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 check a created scaling policy on the workload details page.</p>
|
||||
<ol type="a" id="cce_10_0083__ol1691347738"><li id="cce_10_0083__li1425531691613">Log in to the <span id="cce_10_0083__cce_10_0004_ph18314322182_1">CCE console</span> 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 to obtain the scaling policies. You can also obtain 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>
|
||||
</p></li><li id="cce_10_0083__li11795124518345"><span>Manage scaling policies.</span><p>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0083__table11153172763517" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0083__row31541927143518"><th align="left" class="cellrowborder" valign="top" width="20.990000000000002%" id="mcps1.3.2.3.4.2.1.1.3.1.1"><p id="cce_10_0083__p151543274354">Scaling Policy Type</p>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0083__table11153172763517" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0083__row31541927143518"><th align="left" class="cellrowborder" valign="top" width="20.97%" id="mcps1.3.2.3.4.2.1.1.3.1.1"><p id="cce_10_0083__p151543274354">Scaling Policy Type</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="79.01%" id="mcps1.3.2.3.4.2.1.1.3.1.2"><p id="cce_10_0083__p015492710352">Operation</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="79.03%" id="mcps1.3.2.3.4.2.1.1.3.1.2"><p id="cce_10_0083__p015492710352">Operation</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0083__row181541727173512"><td class="cellrowborder" valign="top" width="20.990000000000002%" headers="mcps1.3.2.3.4.2.1.1.3.1.1 "><p id="cce_10_0083__p131541427143511">HPA</p>
|
||||
<tbody><tr id="cce_10_0083__row181541727173512"><td class="cellrowborder" valign="top" width="20.97%" headers="mcps1.3.2.3.4.2.1.1.3.1.1 "><p id="cce_10_0083__p131541427143511">HPA</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.01%" headers="mcps1.3.2.3.4.2.1.1.3.1.2 "><ul id="cce_10_0083__ul8951581506"><li id="cce_10_0083__li119614810010"><strong id="cce_10_0083__b14252035135114">View Events</strong>: Check HPA policy events. If an error occurred, locate and rectify the fault based on the error message displayed on the page.</li><li id="cce_10_0083__li096138700"><strong id="cce_10_0083__b156564025114">Edit YAML</strong>: In the dialog box displayed, edit, copy, or download the YAML file.</li><li id="cce_10_0083__li496198204"><strong id="cce_10_0083__b84431045155119">Edit</strong>: On the <span class="uicontrol" id="cce_10_0083__uicontrol2339657154818"><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>.</li><li id="cce_10_0083__li12962813011"><strong id="cce_10_0083__b1389574895110">Clone</strong>: Duplicate an existing auto scaling policy and modify the parameter settings as required.</li><li id="cce_10_0083__li209708604"><strong id="cce_10_0083__b148877517512">Delete</strong>: In the dialog box displayed, click <strong id="cce_10_0083__b1885312489522">Yes</strong>.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="79.03%" headers="mcps1.3.2.3.4.2.1.1.3.1.2 "><ul id="cce_10_0083__ul8951581506"><li id="cce_10_0083__li119614810010"><strong id="cce_10_0083__b14252035135114">View Events</strong>: Check HPA policy events. If an error occurred, locate and rectify the fault based on the error message displayed on the page.</li><li id="cce_10_0083__li096138700"><strong id="cce_10_0083__b156564025114">Edit YAML</strong>: In the dialog box displayed, edit, copy, or download the YAML file.</li><li id="cce_10_0083__li496198204"><strong id="cce_10_0083__b84431045155119">Edit</strong>: On the <span class="uicontrol" id="cce_10_0083__uicontrol2339657154818"><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>.</li><li id="cce_10_0083__li12962813011"><strong id="cce_10_0083__b1389574895110">Clone</strong>: Duplicate an existing auto scaling policy and modify the parameter settings as required.</li><li id="cce_10_0083__li209708604"><strong id="cce_10_0083__b148877517512">Delete</strong>: In the dialog box displayed, click <strong id="cce_10_0083__b1885312489522">Yes</strong>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0083__row7154427173517"><td class="cellrowborder" valign="top" width="20.990000000000002%" headers="mcps1.3.2.3.4.2.1.1.3.1.1 "><p id="cce_10_0083__p1215592720355">CronHPA</p>
|
||||
<tr id="cce_10_0083__row7154427173517"><td class="cellrowborder" valign="top" width="20.97%" headers="mcps1.3.2.3.4.2.1.1.3.1.1 "><p id="cce_10_0083__p1215592720355">CronHPA</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.01%" headers="mcps1.3.2.3.4.2.1.1.3.1.2 "><ul id="cce_10_0083__ul497118405"><li id="cce_10_0083__li19971816016"><strong id="cce_10_0083__b121481510185212">View YAML</strong>: In the dialog box displayed, copy or download the YAML file but you are not allowed to modify it.</li><li id="cce_10_0083__li13971817017"><strong id="cce_10_0083__b15919101315529">Delete</strong>: In the dialog box displayed, click <strong id="cce_10_0083__b164171213467">Yes</strong>.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="79.03%" headers="mcps1.3.2.3.4.2.1.1.3.1.2 "><ul id="cce_10_0083__ul497118405"><li id="cce_10_0083__li19971816016"><strong id="cce_10_0083__b121481510185212">View YAML</strong>: In the dialog box displayed, copy or download the YAML file but you are not allowed to modify it.</li><li id="cce_10_0083__li13971817017"><strong id="cce_10_0083__b15919101315529">Delete</strong>: In the dialog box displayed, click <strong id="cce_10_0083__b164171213467">Yes</strong>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@ -32,7 +32,7 @@
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0293.html">Scaling a Workload</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0293.html">Workload Scaling</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
<h1 class="topictitle1">Enabling ICMP Security Group Rules</h1>
|
||||
<div id="body1530866171131"><div class="section" id="cce_10_0084__section106079439418"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0084__p34679509418">If a workload uses UDP for both load balancing and health check, enable ICMP security group rules for the backend servers. </p>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0084__section865612352391"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0084__ol1999461164212"><li id="cce_10_0084__li2114123554110"><span>Log in to the CCE console and choose <span class="uicontrol" id="cce_10_0084__uicontrol8903205152316"><b>Networking</b></span> > <span class="uicontrol" id="cce_10_0084__uicontrol2903851102314"><b>Virtual Private Cloud</b></span> in the service list. In the navigation pane, choose <span class="uicontrol" id="cce_10_0084__uicontrol13903195119235"><b>Access Control</b></span> > <span class="uicontrol" id="cce_10_0084__uicontrol1903115192316"><b>Security Groups</b></span>.</span></li><li id="cce_10_0084__li1211191111308"><span>In the security group list, locate the security group of the cluster. Click the <strong id="cce_10_0084__b104332046247">Inbound Rules</strong> tab page and then <strong id="cce_10_0084__b104331541248">Add Rule</strong>. In the <strong id="cce_10_0084__b143384162410">Add Inbound Rule</strong> dialog box, configure inbound parameters.</span><p>
|
||||
<div class="section" id="cce_10_0084__section865612352391"><h4 class="sectiontitle">Procedure</h4><ol id="cce_10_0084__ol1999461164212"><li id="cce_10_0084__li2114123554110"><span>Log in to the <span id="cce_10_0084__ph174011314145011">VPC console</span> and choose <strong id="cce_10_0084__b877415542174">Access Control</strong> > <strong id="cce_10_0084__b137741454191720">Security Groups</strong>.</span></li><li id="cce_10_0084__li1211191111308"><span>In the security group list, locate the security group of the cluster. Click the <strong id="cce_10_0084__b104332046247">Inbound Rules</strong> tab page and then <strong id="cce_10_0084__b104331541248">Add Rule</strong>. In the <strong id="cce_10_0084__b143384162410">Add Inbound Rule</strong> dialog box, configure inbound parameters.</span><p>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0084__table14257503611" frame="border" border="1" rules="all"><thead align="left"><tr id="cce_10_0084__row02645133615"><th align="left" class="cellrowborder" valign="top" width="16.189999999999998%" id="mcps1.3.2.2.2.2.1.1.6.1.1"><p id="cce_10_0084__p84201847103620">Cluster Type</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="12.690000000000001%" id="mcps1.3.2.2.2.2.1.1.6.1.2"><p id="cce_10_0084__p152616516364">ELB Type</p>
|
||||
|
||||
@ -10,9 +10,9 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0298.html">Creating a Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0140.html">Connecting to a Cluster</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0140.html">Accessing a Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0031.html">Managing a Cluster</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0031.html">Managing Clusters</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0215.html">Upgrading a Cluster</a></strong><br>
|
||||
</li>
|
||||
|
||||
@ -1,9 +1,9 @@
|
||||
<a name="cce_10_0094"></a><a name="cce_10_0094"></a>
|
||||
|
||||
<h1 class="topictitle1">Overview</h1>
|
||||
<h1 class="topictitle1">Ingress 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_0000002218660810.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_0000002434240944.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0094__section195431917247"><h4 class="sectiontitle">Ingress Overview</h4><p id="cce_10_0094__p128258846">Kubernetes uses ingress resources to define how incoming traffic should be handled, while the Ingress Controller is responsible for processing the actual traffic.</p>
|
||||
<ul id="cce_10_0094__ul2875811411"><li id="cce_10_0094__li78145815413"><strong id="cce_10_0094__b1561012463389">Ingress object</strong>: a set of access rules that forward requests to specified Services based on domain names or paths. It can be added, deleted, modified, and queried by calling APIs.</li><li id="cce_10_0094__li148115817417"><strong id="cce_10_0094__b289514915381">Ingress Controller</strong>: an executor for forwarding requests. 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 target backend Services.<div class="p" id="cce_10_0094__p37234233412">The way of implementing Ingress Controllers varies depending on their vendors. CCE supports LoadBalancer Ingress Controllers and NGINX Ingress Controllers.<ul id="cce_10_0094__ul852429154112"><li id="cce_10_0094__li1274314520414">LoadBalancer Ingress Controllers are deployed on master nodes and forward traffic based on the ELB. All policy configurations and forwarding behaviors are managed on the ELB.</li><li id="cce_10_0094__li1218142764120">NGINX Ingress Controllers are deployed in clusters using charts and images maintained by the Kubernetes community. They provide external access through NodePort and forward external traffic to other services in the cluster through Nginx. All traffic forwarding behaviors and forwarding objects are within the cluster.</li></ul>
|
||||
@ -83,19 +83,19 @@
|
||||
<p id="cce_10_0094__p4254124831218">LoadBalancer Ingress Controllers are deployed on master nodes and bound to load balancers in the cluster's VPC. You can configure different domain names, ports, and forwarding policies for the same load balancer (with the same IP address). The working rules of LoadBalancer Ingress Controllers are as follows:</p>
|
||||
<ol id="cce_10_0094__ol525410483123"><li id="cce_10_0094__li8254184813127">A user creates an ingress and configures a traffic access rule in the ingress, including the load balancer, access path, SSL, and backend Service port.</li><li id="cce_10_0094__li1225474817126">When Ingress Controller detects that the ingress changes, it reconfigures the listener and backend server route on the ELB according to the traffic access rule.</li><li id="cce_10_0094__li115615167193">When a user attempts to access a workload, the ELB forwards the traffic to the target workload according to the configured forwarding rule.</li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0094__section192736230432"><h4 class="sectiontitle">CCE Standard Clusters</h4><div class="fignone" id="cce_10_0094__fig122542486129"><span class="figcap"><b>Figure 2 </b>Working flow of a LoadBalancer ingress in a CCE standard cluster</span><br><span><img class="eddx" id="cce_10_0094__image719893318176" src="en-us_image_0000002218820646.png"></span></div>
|
||||
<div class="section" id="cce_10_0094__section192736230432"><h4 class="sectiontitle">CCE Standard Clusters</h4><div class="fignone" id="cce_10_0094__fig122542486129"><span class="figcap"><b>Figure 2 </b>Working flow of a LoadBalancer ingress in a CCE standard cluster</span><br><span><img class="eddx" id="cce_10_0094__image719893318176" src="en-us_image_0000002434081112.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0094__section37915441111"><h4 class="sectiontitle">CCE Turbo Clusters Where a Shared Load Balancer Is Used</h4><div class="fignone" id="cce_10_0094__fig1775293011117"><span class="figcap"><b>Figure 3 </b>Working flow of a LoadBalancer ingress in a CCE Turbo cluster where a shared load balancer is used</span><br><span><img class="eddx" id="cce_10_0094__image82441664451" src="en-us_image_0000002218820650.png"></span></div>
|
||||
<div class="section" id="cce_10_0094__section37915441111"><h4 class="sectiontitle">CCE Turbo Clusters Where a Shared Load Balancer Is Used</h4><div class="fignone" id="cce_10_0094__fig1775293011117"><span class="figcap"><b>Figure 3 </b>Working flow of a LoadBalancer ingress in a CCE Turbo cluster where a shared load balancer is used</span><br><span><img class="eddx" id="cce_10_0094__image82441664451" src="en-us_image_0000002434081116.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0094__section1136916519430"><h4 class="sectiontitle">CCE Turbo Clusters Where a Dedicated Load Balancer Is Used</h4><p id="cce_10_0094__p3662933103112">When a <strong id="cce_10_0094__b91242035143310">CCE Turbo cluster</strong> is used, pod IP addresses are directly allocated from the VPC. <strong id="cce_10_0094__b1611815531919">Dedicated load balancers</strong> enable passthrough networking to pods. When creating an ingress for external cluster access, you can use ELB to access a ClusterIP Service and use pods as the backend server of the ELB listener. In this way, external traffic can directly access the pods in the cluster without being forwarded by node ports.</p>
|
||||
<div class="fignone" id="cce_10_0094__fig44531612193618"><span class="figcap"><b>Figure 4 </b>Working flow of a LoadBalancer ingress in a CCE Turbo cluster where a dedicated load balancer is used</span><br><span><img class="eddx" id="cce_10_0094__image6906154516408" src="en-us_image_0000002253620533.png"></span></div>
|
||||
<div class="fignone" id="cce_10_0094__fig44531612193618"><span class="figcap"><b>Figure 4 </b>Working flow of a LoadBalancer ingress in a CCE Turbo cluster where a dedicated load balancer is used</span><br><span><img class="eddx" id="cce_10_0094__image6906154516408" src="en-us_image_0000002434081124.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0094__section1973674703410"><h4 class="sectiontitle">Working Rules of NGINX Ingress Controller</h4><p id="cce_10_0094__p34261911121314">Nginx Ingress uses ELB as the traffic ingress. The <a href="cce_10_0034.html">NGINX Ingress Controller</a> add-on is deployed in a cluster to balance traffic and control access.</p>
|
||||
<div class="note" id="cce_10_0094__note342691161311"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0094__p1742714117138">NGINX Ingress Controller uses the charts and images provided by the <a href="https://github.com/kubernetes/ingress-nginx" target="_blank" rel="noopener noreferrer">open-source community</a>, and issues may occur during usage. CCE periodically synchronizes the community version to fix known vulnerabilities. Check whether your service requirements can be met.</p>
|
||||
</div></div>
|
||||
<p id="cce_10_0094__p94276112138">NGINX Ingress Controller is deployed on worker nodes through pods, which will result in O&M costs and Nginx component running overheads. <a href="#cce_10_0094__fig2042781115133">Figure 5</a> shows the working rules of NGINX Ingress Controller.</p>
|
||||
<ol id="cce_10_0094__ol8427111151315"><li id="cce_10_0094__li1942701121313">After you update ingress resources, NGINX Ingress Controller writes a forwarding rule defined in the ingress resources into the <strong id="cce_10_0094__b14941113124320">nginx.conf</strong> configuration file of Nginx.</li><li id="cce_10_0094__li13427101181313">The built-in Nginx component reloads the updated configuration file to modify and update the Nginx forwarding rule.</li><li id="cce_10_0094__li11427201113138">When traffic accesses a cluster, the traffic is first forwarded by the created load balancer to the Nginx component in the cluster. Then, the Nginx component forwards the traffic to each workload based on the forwarding rule.</li></ol>
|
||||
<div class="fignone" id="cce_10_0094__fig2042781115133"><a name="cce_10_0094__fig2042781115133"></a><a name="fig2042781115133"></a><span class="figcap"><b>Figure 5 </b>Working rules of NGINX Ingress Controller</span><br><span><img class="eddx" id="cce_10_0094__image45705134553" src="en-us_image_0000002253620541.png"></span></div>
|
||||
<div class="fignone" id="cce_10_0094__fig2042781115133"><a name="cce_10_0094__fig2042781115133"></a><a name="fig2042781115133"></a><span class="figcap"><b>Figure 5 </b>Working rules of NGINX Ingress Controller</span><br><span><img class="eddx" id="cce_10_0094__image45705134553" src="en-us_image_0000002434081132.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 LoadBalancer Ingresses</h4>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0094__table143264518141" width="100%" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Services supported by LoadBalancer ingresses</caption><thead align="left"><tr id="cce_10_0094__row1132645112145"><th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.9.2.2.5.1.1"><p id="cce_10_0094__p33261518148">Cluster Type</p>
|
||||
@ -137,9 +137,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.9.2.2.5.1.2 "><p id="cce_10_0094__p124061958154512">Supported</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.9.2.2.5.1.3 "><p id="cce_10_0094__p4406758154518">Not supported</p>
|
||||
<div class="note" id="cce_10_0094__note9898137193520"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0094__p1389833711356">ENIs are separately bound to pods in a CCE Turbo cluster, and ELB directly connects to pods. Therefore, NodePort access is not available.</p>
|
||||
</div></div>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.9.2.2.5.1.3 "><p id="cce_10_0094__p195145615814">Supported</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -1,11 +1,11 @@
|
||||
<a name="cce_10_0111"></a><a name="cce_10_0111"></a>
|
||||
|
||||
<h1 class="topictitle1">Scalable File Service</h1>
|
||||
<h1 class="topictitle1">SFS</h1>
|
||||
<div id="body0000001487121868"><p id="cce_10_0111__p8060118"></p>
|
||||
</div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0617.html">Overview</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0617.html">SFS Overview</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0619.html">Using an Existing SFS File System Through a Static PV</a></strong><br>
|
||||
</li>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -5,7 +5,7 @@
|
||||
</div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0624.html">Overview</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0624.html">SFS Turbo Overview</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0625.html">Using an Existing SFS Turbo File System Through a Static PV</a></strong><br>
|
||||
</li>
|
||||
@ -13,7 +13,7 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0839.html">(Recommended) Creating an SFS Turbo Subdirectory Using a Dynamic PV</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_bestpractice_00253.html">Dynamically Creating an SFS Turbo Subdirectory Using StorageClass</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_bestpractice_00253_0.html">Dynamically Creating an SFS Turbo Subdirectory Using StorageClass</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@
|
||||
</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>
|
||||
<p id="cce_10_0127__p21112429503">If storage-driver is not installed in a cluster, perform the following operations 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. In the navigation pane, choose <strong id="cce_10_0127__b9141193415148"><span id="cce_10_0127__text1114113345145">Add-ons</span></strong>, locate <strong id="cce_10_0127__b191416342144">CCE Container Storage (FlexVolume)</strong> on the right, and click <strong id="cce_10_0127__b141411534191416">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>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -14,13 +14,13 @@
|
||||
</li>
|
||||
<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">Configuring Container Lifecycle Parameters</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0105.html">Configuring the Container Lifecycle</a></strong><br>
|
||||
</li>
|
||||
<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">Configuring Environment Variables</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0397.html">Configuring Workload Upgrade Policies</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0397.html">Upgrading and Rolling Back a Workload</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0728.html">Configuring Tolerance Policies</a></strong><br>
|
||||
</li>
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user