forked from docs/doc-exports
CCE UMN update 20241130 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
@ -8,7 +8,39 @@
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_01_0300__row12382285577"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p6239182811572">2024-11-25</p>
|
||||
<tbody><tr id="cce_01_0300__row138537511817"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p6853195171815">2025-02-10</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p205161934133412">Add:</p>
|
||||
<ul id="cce_01_0300__ul25161034163419"><li id="cce_01_0300__li15161034173411">Added <a href="cce_10_0836.html">Monitoring</a>.</li><li id="cce_01_0300__li12059215016">Added <a href="cce_bestpractice_00222.html">Creating an IPv4/IPv6 Dual-Stack Cluster in CCE</a>.</li></ul>
|
||||
<p id="cce_01_0300__p1467154351912">Update:</p>
|
||||
<ul id="cce_01_0300__ul66711043141912"><li id="cce_01_0300__li1467113437198">Updated <a href="cce_10_0406.html">Cloud Native Cluster Monitoring</a>.</li><li id="cce_01_0300__li8307510211">Updated <a href="cce_10_0240.html">CCE Advanced HPA</a>.</li><li id="cce_01_0300__li115719137229">Updated <a href="cce_10_0197.html">Process and Method of Upgrading a Cluster</a>.</li><li id="cce_01_0300__li1913916152218">Updated <a href="cce_faq_00089.html">Can I Create a CCE Node Without Adding a Data Disk to the Node?</a>.</li><li id="cce_01_0300__li1831413182225">Updated <a href="cce_10_0783.html">Cluster Access</a>.</li><li id="cce_01_0300__li17561519132213">Updated <a href="cce_productdesc_0000.html">Service Overview</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_01_0300__row20846101110107"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p2084620118107">2024-12-20</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p192721921121010">Add:</p>
|
||||
<ul id="cce_01_0300__ul17913134010215"><li id="cce_01_0300__li19303826141118">Added <a href="cce_bulletin_0095.html">Kubernetes 1.30 Release Notes</a>.</li><li id="cce_01_0300__li11914154019214">Added <a href="cce_bulletin_0098.html">EOM of CentOS</a>.</li><li id="cce_01_0300__li16371103993217">Added <a href="cce_10_0744.html">Revoking a Credential to Access the Corresponding Cluster</a>, <a href="cce_10_0927.html">Preventing Cluster Deletion</a>.</li><li id="cce_01_0300__li16703013312">Added <a href="cce_10_0889.html">Scheduling a Workload</a>.</li><li id="cce_01_0300__li145106513332">Added <a href="cce_10_0916.html">Enabling a LoadBalancer Service to Obtain the Client IP Address</a>, <a href="cce_10_0924.html">Configuring a Custom EIP for a LoadBalancer Service</a>.</li><li id="cce_01_0300__li174261762330">Added <a href="cce_10_0944.html">Creating an HPA Policy with Custom Metrics</a>, <a href="cce_10_0934.html">Creating an AHPA Policy</a>.</li><li id="cce_01_0300__li109660172323">Added <a href="cce_10_0781.html">Settings</a>.</li><li id="cce_01_0300__li57551076338">Added <a href="cce_bestpractice_10047.html">Configuration Suggestions on CCE Container Image Security</a>.</li><li id="cce_01_0300__li106387810331">Added <a href="cce_faq_00445.html">What Are the Impacts of Changing the Flavor of a Node in a CCE Node Pool?</a>, <a href="cce_faq_00185.html">How Do I Obtain a TLS Key Certificate?</a>, <a href="cce_faq_00446.html">How Can I Check Whether an ENI Is Used by a Cluster?</a>, <a href="cce_faq_00447.html">How Can I Delete a Security Group Rule Associated with a Deleted Subnet?</a>, <a href="cce_faq_00460.html">How Can I Determine Which Ingress the Listener Settings Have Been Applied To?</a>.</li></ul>
|
||||
<p id="cce_01_0300__p9546114511102">Update:</p>
|
||||
<ul id="cce_01_0300__ul1548895761012"><li id="cce_01_0300__li186619511116">Updated <a href="cce_10_0405.html">Patch Version Release Notes</a>.</li><li id="cce_01_0300__li06015221333">Updated <a href="cce_bulletin_0033.html">Kubernetes Version Policy</a>.</li><li id="cce_01_0300__li1893312092314">Update <a href="cce_productdesc_0005.html">Notes and Constraints</a>.</li><li id="cce_01_0300__li366715119369">Updated <a href="cce_10_0550.html">Troubleshooting for Pre-upgrade Check Exceptions</a>.</li><li id="cce_01_0300__li648519410397">Updated <a href="cce_10_0476.html">Node OS</a>, <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>, <a href="cce_10_0605.html">Draining a Node</a>.</li><li id="cce_01_0300__li142324894314">Updated <a href="cce_10_0012.html">Creating a Node Pool</a>, <a href="cce_10_0653.html">Updating a Node Pool</a>, <a href="cce_10_0652.html">Modifying Node Pool Configurations</a>, <a href="cce_10_0886.html">Accepting Nodes in a Node Pool</a>, <a href="cce_10_0656.html">Migrating a Node</a>.</li><li id="cce_01_0300__li1876317325492">Updated <a href="cce_10_0673.html">Creating a Workload</a>.</li><li id="cce_01_0300__li1279632145720">Updated <a href="cce_10_0681.html">Configuring LoadBalancer Services Using Annotations</a>, <a href="cce_10_0831.html">Configuring a Blocklist/Trustlist Access Policy for a LoadBalancer Service</a>, <a href="cce_10_0935.html">Advanced Setting Examples of LoadBalancer Ingresses</a>, <a href="cce_10_0936.html">Advanced Setting Examples of Nginx Ingresses</a>.</li><li id="cce_01_0300__li179611212577">Updated <a href="cce_10_0615.html">Using an EVS Disk Through a Dynamic PV</a>, <a href="cce_10_0616.html">Dynamically Mounting an EVS Disk to a StatefulSet</a>, <a href="cce_10_0620.html">Using an SFS File System Through a Dynamic PV</a>, <a href="cce_10_0839.html">(Recommended) Creating an SFS Turbo Subdirectory Using a Dynamic PV</a>, <a href="cce_10_0630.html">Using an OBS Bucket Through a Dynamic PV</a>, <a href="cce_10_0634.html">Using a Local PV Through a Dynamic PV</a>, <a href="cce_10_0635.html">Dynamically Mounting a Local PV to a StatefulSet</a>, <a href="cce_10_0380.html">StorageClass</a>.</li><li id="cce_01_0300__li850116582361">Updated <a href="cce_10_0290.html">Workload Scaling Rules</a>.</li><li id="cce_01_0300__li1499064232117">Updated <a href="cce_10_0064.html">Add-ons</a>.</li></ul>
|
||||
<p id="cce_01_0300__p1655218110146">Delete:</p>
|
||||
<ul id="cce_01_0300__ul2028721331311"><li id="cce_01_0300__li68421328181312">Deleted "CCE Console Upgrade".</li><li id="cce_01_0300__li109481512526">Deleted "Scheduling Policies (Affinity/Anti-affinity)".</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_01_0300__row85903716311"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p11591176316">2024-12-19</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p1359116718312">Update:</p>
|
||||
<ul id="cce_01_0300__ul2035812552317"><li id="cce_01_0300__li19988135410">Update <a href="cce_10_0476.html">Node OS</a>.</li><li id="cce_01_0300__li4988536416">Update <a href="cce_productdesc_0005.html">Notes and Constraints</a>.</li><li id="cce_01_0300__li147891671848">Update <a href="cce_10_0059.html">Configuring Network Policies to Restrict Pod Access</a>.</li><li id="cce_01_0300__li1820210505517">Update <a href="cce_10_0614.html">Using an Existing EVS Disk Through a Static PV</a>.</li><li id="cce_01_0300__li82212420620">Update <a href="cce_10_0615.html">Using an EVS Disk Through a Dynamic PV</a>.</li><li id="cce_01_0300__li10860195668">Update <a href="cce_10_0616.html">Dynamically Mounting an EVS Disk to a StatefulSet</a>.</li><li id="cce_01_0300__li145755710611">Update <a href="cce_10_0380.html">StorageClass</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_01_0300__row26731218144011"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p1674131854018">2024-11-30</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p2067416188402">Add:</p>
|
||||
<p id="cce_01_0300__p6270131134011">Added <a href="cce_bestpractice_10046.html">Configuration Suggestions on CCE Container Runtime Security</a>.</p>
|
||||
<p id="cce_01_0300__p69918375406">Added <a href="cce_bestpractice_0333.html">Configuration Suggestions on CCE Workload Identity Security</a>.</p>
|
||||
<p id="cce_01_0300__p131981238114010">Added <a href="cce_bestpractice_0300.html">Performing Cluster Namespace RBAC</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_01_0300__row12382285577"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p6239182811572">2024-11-25</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p2023952875710">Update:</p>
|
||||
<p id="cce_01_0300__p740273811578">Updated the <strong id="cce_01_0300__b1132371515018">Specifications</strong> field in <a href="cce_10_0363.html">Creating a Node</a> and <a href="cce_10_0012.html">Creating a Node Pool</a>.</p>
|
||||
@ -21,7 +53,7 @@
|
||||
<p id="cce_01_0300__p20417102112418">Added <a href="cce_10_0692.html">Nginx Ingresses</a>.</p>
|
||||
<p id="cce_01_0300__p1606529121812">Added <a href="cce_10_0508.html">nginx-ingress Upgrade</a>.</p>
|
||||
<p id="cce_01_0300__p89468554106">Update:</p>
|
||||
<ul id="cce_01_0300__ul13617102410314"><li id="cce_01_0300__li18626356833">Supported the NGINX Ingress Controller add-on. Updated <a href="cce_10_0277.html">Overview</a>, <a href="cce_bulletin_0061.html">CCE Console Upgrade</a>.</li><li id="cce_01_0300__li12162133812224">Supported Nginx Ingress. Updated <a href="cce_10_0094.html">Overview</a>, <a href="cce_10_0251.html">Creating a LoadBalancer Ingress on the Console</a>, <a href="cce_10_0695.html">Configuring a LoadBalancer Ingress Using Annotations</a>.</li><li id="cce_01_0300__li146172024237">The EVS disk type supports <strong id="cce_01_0300__b1047922821711">General Purpose SSD</strong> and <strong id="cce_01_0300__b18374164641717">Extreme SSD</strong>. Updated <a href="cce_10_0613.html">Overview</a>, <a href="cce_10_0614.html">Using an Existing EVS Disk Through a Static PV</a>, <a href="cce_10_0615.html">Using an EVS Disk Through a Dynamic PV</a>, <a href="cce_10_0616.html">Dynamically Mounting an EVS Disk to a StatefulSet</a>.</li><li id="cce_01_0300__li22671214175220">Updated <a href="cce_10_0028.html">Creating a CCE Standard/Turbo Cluster</a>.</li><li id="cce_01_0300__li18397152611527">Updated <a href="cce_10_0012.html">Creating a Node Pool</a>.</li><li id="cce_01_0300__li147530281527">Updated <a href="cce_bestpractice_0320.html">Configuration Suggestions on CCE Secret Security</a>.</li></ul>
|
||||
<ul id="cce_01_0300__ul13617102410314"><li id="cce_01_0300__li18626356833">Supported the NGINX Ingress Controller add-on. Updated <a href="cce_10_0277.html">Overview</a>.</li><li id="cce_01_0300__li12162133812224">Supported Nginx Ingress. Updated <a href="cce_10_0094.html">Overview</a>, <a href="cce_10_0251.html">Creating a LoadBalancer Ingress on the Console</a>, <a href="cce_10_0695.html">Configuring a LoadBalancer Ingress Using Annotations</a>.</li><li id="cce_01_0300__li146172024237">The EVS disk type supports <strong id="cce_01_0300__b1047922821711">General Purpose SSD</strong> and <strong id="cce_01_0300__b18374164641717">Extreme SSD</strong>. Updated <a href="cce_10_0613.html">Overview</a>, <a href="cce_10_0614.html">Using an Existing EVS Disk Through a Static PV</a>, <a href="cce_10_0615.html">Using an EVS Disk Through a Dynamic PV</a>, <a href="cce_10_0616.html">Dynamically Mounting an EVS Disk to a StatefulSet</a>.</li><li id="cce_01_0300__li22671214175220">Updated <a href="cce_10_0028.html">Creating a CCE Standard/Turbo Cluster</a>.</li><li id="cce_01_0300__li18397152611527">Updated <a href="cce_10_0012.html">Creating a Node Pool</a>.</li><li id="cce_01_0300__li147530281527">Updated <a href="cce_bestpractice_0320.html">Configuration Suggestions on CCE Secret Security</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_01_0300__row196562925719"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p1565620945712">2024-08-30</p>
|
||||
@ -61,7 +93,7 @@
|
||||
</tr>
|
||||
<tr id="cce_01_0300__row125431763718"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p175401713377">2024-03-29</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><ul id="cce_01_0300__ul178522051143711"><li id="cce_01_0300__li157281413144019">Modified the console style.</li><li id="cce_01_0300__li11783163645218">Added <a href="cce_bulletin_0061.html">CCE Console Upgrade</a>.</li><li id="cce_01_0300__li1485265114379">HCE OS 2.0 is supported. </li><li id="cce_01_0300__li143973152818">Update <a href="cce_10_0405.html">Release Notes for CCE Cluster Versions</a>.</li><li id="cce_01_0300__li96317418918">Update <a href="cce_10_0423.html">Volcano Scheduling</a>.</li><li id="cce_01_0300__li12925155011536">Added the CCE Advanced HPA add-on.</li><li id="cce_01_0300__li19887214113914">Updated <a href="cce_bestpractice_0000.html">Best Practice</a>.</li><li id="cce_01_0300__li1963584304012">Updated <a href="cce_faq_0000.html">FAQs</a>.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><ul id="cce_01_0300__ul178522051143711"><li id="cce_01_0300__li157281413144019">Modified the console style.</li><li id="cce_01_0300__li1485265114379">HCE OS 2.0 is supported. </li><li id="cce_01_0300__li143973152818">Update <a href="cce_10_0405.html">Release Notes for CCE Cluster Versions</a>.</li><li id="cce_01_0300__li96317418918">Update <a href="cce_10_0423.html">Volcano Scheduling</a>.</li><li id="cce_01_0300__li12925155011536">Added the CCE Advanced HPA add-on.</li><li id="cce_01_0300__li19887214113914">Updated <a href="cce_bestpractice_0000.html">Best Practice</a>.</li><li id="cce_01_0300__li1963584304012">Updated <a href="cce_faq_0000.html">FAQs</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_01_0300__row15301133891"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p16301431995">2024-01-29</p>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,11 +1,10 @@
|
||||
<a name="cce_10_0004"></a><a name="cce_10_0004"></a>
|
||||
|
||||
<h1 class="topictitle1">Managing Node Labels</h1>
|
||||
<div id="body1523168310157"><p id="shortdesc139984301190">You can add different labels to nodes and define different attributes for labels. By using these <span class="keyword" id="keyword161492666714287">node labels</span>, you can quickly understand the characteristics of each node.</p>
|
||||
<div class="section" id="cce_10_0004__section825504204814"><h4 class="sectiontitle">Node Label Usage Scenario</h4><p id="cce_10_0004__p780125519482">Node labels are mainly used in the following scenarios:</p>
|
||||
<ul id="cce_10_0004__ul1269074720287"><li id="cce_10_0004__li1269054722816">Node management: Node labels are used to classify nodes.</li><li id="cce_10_0004__li13690184719287">Node affinity or anti-affinity for workloads: By adding labels to nodes, you can schedule pods to specific nodes through node affinity or prevent pods from being scheduled to specific nodes through node anti-affinity. For details, see <a href="cce_10_0232.html">Scheduling Policies (Affinity/Anti-affinity)</a>.</li></ul>
|
||||
<div id="body1523168310157"><div class="section" id="cce_10_0004__section825504204814"><h4 class="sectiontitle">Node Label Usage Scenario</h4><p id="cce_10_0004__p780125519482">Node labels are mainly used in the following scenarios:</p>
|
||||
<ul id="cce_10_0004__ul1269074720287"><li id="cce_10_0004__li1269054722816">Node management: Node labels are used to classify nodes.</li><li id="cce_10_0004__li13690184719287">Node affinity or anti-affinity for workloads: By adding labels to nodes, you can schedule pods to specific nodes through node affinity or prevent pods from being scheduled to specific nodes through node anti-affinity. For details, see <a href="cce_10_0892.html">Configuring Node Affinity Scheduling (nodeAffinity)</a>.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0004__section74111324152813"><h4 class="sectiontitle"><span class="keyword" id="cce_10_0004__keyword544709935144944">Inherent Label of a Node</span></h4><p id="cce_10_0004__p096179164111">After a node is created, some fixed labels exist and cannot be deleted. For details about these labels, see <a href="#cce_10_0004__table83962234533">Table 1</a>.</p>
|
||||
<div class="section" id="cce_10_0004__section74111324152813"><a name="cce_10_0004__section74111324152813"></a><a name="section74111324152813"></a><h4 class="sectiontitle"><span class="keyword" id="cce_10_0004__keyword544709935144944">Inherent Label of a Node</span></h4><p id="cce_10_0004__p096179164111">After a node is created, some fixed labels exist and cannot be deleted. For details about these labels, see <a href="#cce_10_0004__table83962234533">Table 1</a>.</p>
|
||||
<div class="note" id="cce_10_0004__note1531361014395"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0004__p16314181043913">Do not manually change the inherent labels that are automatically added to a node. If the manually changed value conflicts with the system value, the system value is used.</p>
|
||||
</div></div>
|
||||
|
||||
@ -62,7 +61,7 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0004__row85011821447"><td class="cellrowborder" valign="top" width="45%" headers="mcps1.4.2.4.2.3.1.1 "><p id="cce_10_0004__p950218211147">node.kubernetes.io/subnetid</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.4.2.4.2.3.1.2 "><p id="cce_10_0004__p950282110419">ID of the subnet where the node is located.</p>
|
||||
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.4.2.4.2.3.1.2 "><p id="cce_10_0004__p950282110419">ID of the subnet where the node is located</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0004__row15411523165312"><td class="cellrowborder" valign="top" width="45%" headers="mcps1.4.2.4.2.3.1.1 "><p id="cce_10_0004__p2411192310532">os.architecture</p>
|
||||
@ -83,19 +82,19 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0004__row157991762533"><td class="cellrowborder" valign="top" width="45%" headers="mcps1.4.2.4.2.3.1.1 "><p id="cce_10_0004__p1159194516538">accelerator</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.4.2.4.2.3.1.2 "><p id="cce_10_0004__p13799136175313">GPU node labels.</p>
|
||||
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.4.2.4.2.3.1.2 "><p id="cce_10_0004__p13799136175313">GPU node labels</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0004__row43521213544"><td class="cellrowborder" valign="top" width="45%" headers="mcps1.4.2.4.2.3.1.1 "><p id="cce_10_0004__p1859767185417">cce.cloud.com/cce-nodepool</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.4.2.4.2.3.1.2 "><p id="cce_10_0004__p8447111011543">The dedicated label of a node in a node pool.</p>
|
||||
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.4.2.4.2.3.1.2 "><p id="cce_10_0004__p8447111011543">The dedicated label of a node in a node pool</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0004__section33951611481"><h4 class="sectiontitle">Adding or Deleting a Node Label</h4><ol id="cce_10_0004__ol4618636938"><li id="cce_10_0004__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 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>
|
||||
<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,9 +1,9 @@
|
||||
<a name="cce_10_0006"></a><a name="cce_10_0006"></a>
|
||||
|
||||
<h1 class="topictitle1">Overview</h1>
|
||||
<div id="body1522665832344"><p id="shortdesc12779194282617">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="keyword1293375712468">Deployments</span>, <span class="keyword" id="keyword1541920224714">StatefulSets</span>, <span class="keyword" id="keyword1273972479">DaemonSets</span>, <span class="keyword" id="keyword21491010164711">jobs</span>, and <span class="keyword" id="keyword19556171584711">cron jobs</span>.</p>
|
||||
<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 Pod</h4><p id="cce_10_0006__en-us_topic_0254767870_p356108173515">A pod is the smallest and simplest unit in the Kubernetes object model that you create or deploy. A pod is a group of one or more containers, with shared storage and network resources, and a specification for how to run the containers. Each pod has a separate IP address.</p>
|
||||
<div class="section" id="cce_10_0006__section9645114684816"><h4 class="sectiontitle">Overview of Pod</h4><p id="cce_10_0006__en-us_topic_0254767870_p356108173515">A pod is the smallest, simplest unit in the Kubernetes object model that you create or deploy. A pod is a group of one or more containers, with shared storage and network resources, and a specification for how to run the containers. Each pod has a separate IP address.</p>
|
||||
<p id="cce_10_0006__en-us_topic_0254767870_p4629172611480">Pods can be used in either of the following ways:</p>
|
||||
<ul id="cce_10_0006__en-us_topic_0254767870_ul062982617481"><li id="cce_10_0006__en-us_topic_0254767870_li1629172611482">A pod runs only one container. This is the most common usage of pods in Kubernetes. You can consider a pod as a container, but Kubernetes directly manages pods instead of containers.</li><li id="cce_10_0006__en-us_topic_0254767870_li1962932615480">A pod runs multiple containers that need to be tightly coupled. In this scenario, a pod contains a main container and several sidecar containers, as shown in <a href="#cce_10_0006__en-us_topic_0254767870_fig347141918551">Figure 1</a>. For example, the main container is a web server that provides file services from a fixed directory, and sidecar containers periodically download files to this fixed directory.<div class="fignone" id="cce_10_0006__en-us_topic_0254767870_fig347141918551"><a name="cce_10_0006__en-us_topic_0254767870_fig347141918551"></a><a name="en-us_topic_0254767870_fig347141918551"></a><span class="figcap"><b>Figure 1 </b>Pod running multiple containers</span><br><span><img id="cce_10_0006__en-us_topic_0254767870_image1835215316361" src="en-us_image_0258392378.png"></span></div>
|
||||
</li></ul>
|
||||
@ -19,57 +19,57 @@
|
||||
<p id="cce_10_0006__en-us_topic_0249896621_p97277467269">Distributed stateful applications involve different roles for different responsibilities. For example, databases work in active/standby mode, and pods depend on each other. To deploy stateful applications in Kubernetes, ensure pods meet the following requirements:</p>
|
||||
<ul id="cce_10_0006__en-us_topic_0249896621_ul1181724132317"><li id="cce_10_0006__en-us_topic_0249896621_li10181102419231">Each pod must have a fixed identifier so that it can be recognized by other pods.</li><li id="cce_10_0006__en-us_topic_0249896621_li81819249237">Separate storage resources must be configured for each pod. In this way, the original data can be retrieved after a pod is deleted and restored. Otherwise, the pod status will be changed after the pod is rebuilt.</li></ul>
|
||||
<p id="cce_10_0006__en-us_topic_0249896621_p929315724313">To address the preceding requirements, Kubernetes provides StatefulSets.</p>
|
||||
<ol id="cce_10_0006__en-us_topic_0249896621_ol117020203559"><li id="cce_10_0006__en-us_topic_0249896621_li183871501692">StatefulSets provide a fixed name for each pod following a fixed number ranging from 0 to N. After a pod is rescheduled, the pod name and the hostname remain unchanged.</li><li id="cce_10_0006__en-us_topic_0249896621_li1789810518913">StatefulSets use a headless Service to allocate a fixed domain name for each pod.</li><li id="cce_10_0006__en-us_topic_0249896621_li43183204569">StatefulSets create PersistentVolumeClaims (PVCs) with fixed identifiers to ensure that pods can access the same persistent data after being rescheduled.<p id="cce_10_0006__en-us_topic_0249896621_p8536185392116"><a name="cce_10_0006__en-us_topic_0249896621_li43183204569"></a><a name="en-us_topic_0249896621_li43183204569"></a><span><img id="cce_10_0006__en-us_topic_0249896621_image9125145402111" src="en-us_image_0258203193.png"></span></p>
|
||||
<ol id="cce_10_0006__en-us_topic_0249896621_ol117020203559"><li id="cce_10_0006__en-us_topic_0249896621_li183871501692">StatefulSets provide a fixed name for each pod following a fixed number ranging from 0 to N. After a pod is rescheduled, the pod name and the hostname remain unchanged.</li><li id="cce_10_0006__en-us_topic_0249896621_li1789810518913">StatefulSets use a headless Service to allocate a fixed domain name for each pod.</li><li id="cce_10_0006__en-us_topic_0249896621_li43183204569">StatefulSets create PVCs with fixed identifiers to ensure that pods can access the same persistent data after being rescheduled.<div class="fignone" id="cce_10_0006__en-us_topic_0249896621_fig97542112114"><span class="figcap"><b>Figure 3 </b>StatefulSet</span><br><span><img id="cce_10_0006__en-us_topic_0249896621_image9125145402111" src="en-us_image_0258203193.png"></span></div>
|
||||
</li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0006__section7846281504"><h4 class="sectiontitle">Overview of DaemonSet</h4><p id="cce_10_0006__en-us_topic_0249851114_p441104813815">A DaemonSet runs a pod on each node in a cluster and ensures that there is only one pod. This works well for certain system-level applications such as log collection and resource monitoring since they must run on each node and need only a few pods. A good example is kube-proxy.</p>
|
||||
<p id="cce_10_0006__en-us_topic_0249851114_p5986375820">DaemonSets are closely related to nodes. If a node becomes faulty, the DaemonSet will not create the same pods on other nodes.</p>
|
||||
<div class="fignone" id="cce_10_0006__en-us_topic_0249851114_fig27588261914"><span class="figcap"><b>Figure 3 </b>DaemonSet</span><br><span><img id="cce_10_0006__en-us_topic_0249851114_image13336133243518" src="en-us_image_0258871213.png"></span></div>
|
||||
<div class="fignone" id="cce_10_0006__en-us_topic_0249851114_fig27588261914"><span class="figcap"><b>Figure 4 </b>DaemonSet</span><br><span><img id="cce_10_0006__en-us_topic_0249851114_image13336133243518" src="en-us_image_0258871213.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0006__section153173319578"><h4 class="sectiontitle">Overview of Job and CronJob</h4><p id="cce_10_0006__en-us_topic_0249851115_p10889736123218">Jobs and CronJobs allow you to run short lived, one-off tasks in batch. They ensure the task pods run to completion.</p>
|
||||
<ul id="cce_10_0006__en-us_topic_0249851115_ul197714911354"><li id="cce_10_0006__en-us_topic_0249851115_li47711097352">A job is a resource object used by Kubernetes to control batch tasks. Jobs are different from long-term servo tasks (such as Deployments and StatefulSets). The former is started and terminated at specific times, while the latter runs unceasingly unless being terminated. The pods managed by a job will be automatically removed after successfully completing tasks based on user configurations.</li><li id="cce_10_0006__en-us_topic_0249851115_li249061111353">A CronJob runs a job periodically on a specified schedule. A CronJob object is similar to a line of a crontab file in Linux.</li></ul>
|
||||
<p id="cce_10_0006__en-us_topic_0249851115_p166171774387">This run-to-completion feature of jobs is especially suitable for one-off tasks, such as continuous integration (CI).</p>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0006__section3891192610218"><h4 class="sectiontitle">Workload Lifecycle</h4>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0006__table488465253420" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Status description</caption><thead align="left"><tr id="cce_10_0006__row13888105212343"><th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.4.7.2.2.3.1.1"><p id="cce_10_0006__p1788975203415">Status</p>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0006__table488465253420" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Status description</caption><thead align="left"><tr id="cce_10_0006__row13888105212343"><th align="left" class="cellrowborder" valign="top" width="25%" id="mcps1.3.8.2.2.3.1.1"><p id="cce_10_0006__p1788975203415">Status</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="75%" id="mcps1.4.7.2.2.3.1.2"><p id="cce_10_0006__p788975211347">Description</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="75%" id="mcps1.3.8.2.2.3.1.2"><p id="cce_10_0006__p788975211347">Description</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0006__row14889152173415"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.4.7.2.2.3.1.1 "><p id="cce_10_0006__p1788905212343">Running</p>
|
||||
<tbody><tr id="cce_10_0006__row14889152173415"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.8.2.2.3.1.1 "><p id="cce_10_0006__p1788905212343">Running</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.4.7.2.2.3.1.2 "><p id="cce_10_0006__p188914522345">All pods are running or the number of pods is 0.</p>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.8.2.2.3.1.2 "><p id="cce_10_0006__p188914522345">All pods are running or the number of pods is 0.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0006__row12889195263417"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.4.7.2.2.3.1.1 "><p id="cce_10_0006__p1888915253412">Unready</p>
|
||||
<tr id="cce_10_0006__row12889195263417"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.8.2.2.3.1.1 "><p id="cce_10_0006__p1888915253412">Unready</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.4.7.2.2.3.1.2 "><p id="cce_10_0006__p12889152113418">The container malfunctions and the pod under the workload is not working.</p>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.8.2.2.3.1.2 "><p id="cce_10_0006__p12889152113418">The container malfunctions and the pod under the workload is not working.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0006__row1940155313521"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.4.7.2.2.3.1.1 "><p id="cce_10_0006__p9415165881719">Processing</p>
|
||||
<tr id="cce_10_0006__row1940155313521"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.8.2.2.3.1.1 "><p id="cce_10_0006__p9415165881719">Processing</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.4.7.2.2.3.1.2 "><p id="cce_10_0006__p1141511585170">The workload is not running but no error is reported.</p>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.8.2.2.3.1.2 "><p id="cce_10_0006__p1141511585170">The workload is not running but no error is reported.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0006__row6241718141019"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.4.7.2.2.3.1.1 "><p id="cce_10_0006__p132017221115">Available</p>
|
||||
<tr id="cce_10_0006__row6241718141019"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.8.2.2.3.1.1 "><p id="cce_10_0006__p132017221115">Available</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.4.7.2.2.3.1.2 "><p id="cce_10_0006__p16202132212113">For a multi-pod Deployment, some pods are abnormal but at least one pod is available.</p>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.8.2.2.3.1.2 "><p id="cce_10_0006__p16202132212113">For a multi-pod Deployment, some pods are abnormal but at least one pod is available.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0006__row13688115719"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.4.7.2.2.3.1.1 "><p id="cce_10_0006__p196891715814">Completed</p>
|
||||
<tr id="cce_10_0006__row13688115719"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.8.2.2.3.1.1 "><p id="cce_10_0006__p196891715814">Completed</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.4.7.2.2.3.1.2 "><p id="cce_10_0006__p19689181515119">The task is successfully executed. This status is available only for common tasks.</p>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.8.2.2.3.1.2 "><p id="cce_10_0006__p19689181515119">The task is successfully executed. This status is available only for common tasks.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0006__row2088975211346"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.4.7.2.2.3.1.1 "><p id="cce_10_0006__p788915203415">Stopped</p>
|
||||
<tr id="cce_10_0006__row2088975211346"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.8.2.2.3.1.1 "><p id="cce_10_0006__p788915203415">Stopped</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.4.7.2.2.3.1.2 "><p id="cce_10_0006__p15889152103417">The workload is stopped and the number of pods changes to 0. This status is available for workloads earlier than v1.13.</p>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.8.2.2.3.1.2 "><p id="cce_10_0006__p15889152103417">The workload is stopped and the number of pods changes to 0. This status is available for workloads earlier than v1.13.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0006__row172011222121114"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.4.7.2.2.3.1.1 "><p id="cce_10_0006__p198052054104811">Deleting</p>
|
||||
<tr id="cce_10_0006__row172011222121114"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.8.2.2.3.1.1 "><p id="cce_10_0006__p198052054104811">Deleting</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.4.7.2.2.3.1.2 "><p id="cce_10_0006__p8805854104812">The workload is being deleted.</p>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.8.2.2.3.1.2 "><p id="cce_10_0006__p8805854104812">The workload is being deleted.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
||||
@ -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, 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, log, monitor, roll back, or delete the workload, as well as edit its YAML file.
|
||||
<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>
|
||||
@ -99,13 +99,13 @@
|
||||
</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">If a Deployment is being upgraded, it can be upgraded or rolled back. Its pods will inherit the latest updates of the Deployment. If they are inconsistent, the pods are upgraded automatically according to the latest information of the Deployment.</li></ul>
|
||||
</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>
|
||||
</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 <strong id="cce_10_0007__b97761327172916">Add</strong>, 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>
|
||||
<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_0000002065638710.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>
|
||||
|
||||
@ -4,7 +4,7 @@
|
||||
<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_0000001981436297.png"></span></p>
|
||||
<p id="cce_10_0010__p452843519446"><span><img id="cce_10_0010__image94831936164418" src="en-us_image_0000002101597285.png"></span></p>
|
||||
<ul id="cce_10_0010__ul1916179122617"><li id="cce_10_0010__li13455145754315"><strong id="cce_10_0010__b19468105563811">Node Network</strong><p id="cce_10_0010__p17682193014812">A node network assigns IP addresses to hosts (nodes in the figure above) in a cluster. Select a VPC subnet as the node network of the CCE cluster. The number of available IP addresses in a subnet determines the maximum number of nodes (including master nodes and worker nodes) that can be created in a cluster. This quantity is also affected by the container network. For details, see the container network model.</p>
|
||||
</li><li id="cce_10_0010__li16131141644715"><strong id="cce_10_0010__b1975815172433">Container Network</strong><p id="cce_10_0010__p523322010499">A container network assigns IP addresses to 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>
|
||||
@ -27,7 +27,7 @@
|
||||
<ul id="cce_10_0010__ul125010117542"><li id="cce_10_0010__li1466355519018">Intra-cluster access: A ClusterIP Service is used for workloads in the same cluster to access each other.</li><li id="cce_10_0010__li1014011111110">Access from outside a cluster: A Service (NodePort or LoadBalancer type) or an ingress is recommended for a workload outside a cluster to access workloads in the cluster.<ul id="cce_10_0010__ul101426119117"><li id="cce_10_0010__li8904911447">Access through the public network: An EIP should be bound to the node or load balancer.</li><li id="cce_10_0010__li2501311125411">Access through the private network: The workload can be accessed through the internal IP address of the node or load balancer. If workloads are located in different VPCs, a peering connection is required to enable communication between different VPCs.</li></ul>
|
||||
</li><li id="cce_10_0010__li1066365520014">The workload can access the external network as follows:<ul id="cce_10_0010__ul17529512239"><li id="cce_10_0010__li26601017165619">Accessing an intranet: The workload accesses the intranet address, but the implementation method varies depending on container network models. Ensure that the peer security group allows the access requests from the container CIDR block.</li><li id="cce_10_0010__li8257105318237">Accessing a public network: Assign an EIP to the node where the workload runs (when the VPC network or tunnel network model is used), bind an EIP to the pod IP address (when the Cloud Native Network 2.0 model is used), or configure SNAT rules through the NAT gateway. For details, see <a href="cce_10_0400.html">Accessing 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_0000001981436301.png"></span></div>
|
||||
<div class="fignone" id="cce_10_0010__fig13795829151515"><span class="figcap"><b>Figure 3 </b>Network access diagram</span><br><span><img id="cce_10_0010__image445972519529" src="en-us_image_0000002101678773.png"></span></div>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
@ -4,9 +4,9 @@
|
||||
<div id="body1522736584192"><div class="section" id="cce_10_0011__section13559184110492"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0011__p32401248184910">ClusterIP Services allow workloads in the same cluster to use their cluster-internal domain names to access each other.</p>
|
||||
<p id="cce_10_0011__p653753053815">The cluster-internal domain name format is <em id="cce_10_0011__i8179113533712"><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_0000001981436829.png"></span></div>
|
||||
<div class="fignone" id="cce_10_0011__fig192245420557"><a name="cce_10_0011__fig192245420557"></a><a name="fig192245420557"></a><span class="figcap"><b>Figure 1 </b>Intra-cluster access (ClusterIP)</span><br><span><img id="cce_10_0011__image1942163010278" src="en-us_image_0000002101679261.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0011__section51925078171335"><h4 class="sectiontitle">Creating a ClusterIP Service</h4><ol id="cce_10_0011__ol1321170617144"><li id="cce_10_0011__li41731123658"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0011__li836916478329"><span>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__b2095128121518">IPv6</strong>: This function is disabled by default. After this function is enabled, the cluster IP address of the Service changes to an IPv6 address. <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>
|
||||
<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>
|
||||
</div>
|
||||
@ -56,7 +56,7 @@ spec:
|
||||
<pre class="screen" id="cce_10_0011__screen088610169318">NAME READY STATUS RESTARTS AGE
|
||||
<strong id="cce_10_0011__b859512281317">nginx-2601814895-znhbr 1/1 Running 0 15s</strong></pre>
|
||||
</p></li><li id="cce_10_0011__li72314917413"><span>Create a Service.</span><p><p id="cce_10_0011__p652151618484"><strong id="cce_10_0011__b125716411456">kubectl create -f nginx-clusterip-svc.yaml</strong></p>
|
||||
<p id="cce_10_0011__p7647437193211">If information similar to the following is displayed, the Service is being created.</p>
|
||||
<p id="cce_10_0011__p7647437193211">If information similar to the following is displayed, the Service is being created:</p>
|
||||
<pre class="screen" id="cce_10_0011__screen21756141325">service "nginx-clusterip" created</pre>
|
||||
<p id="cce_10_0011__p94411847104519"><strong id="cce_10_0011__b139414472452">kubectl get svc</strong></p>
|
||||
<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>
|
||||
|
||||
@ -45,7 +45,7 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0012__row1546565714210"><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__p45571547134211">Container Engine</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__en-us_topic_0000001244141037_p1015871915468">The container engines supported by CCE include Docker and containerd, which may vary depending on cluster types, cluster versions, and OSs. Select a container engine based on the information displayed on the CCE console. For details, see <a href="cce_10_0462.html#cce_10_0462__section159298451879">Mapping between Node OSs and Container Engines</a>.</p>
|
||||
<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__en-us_topic_0000001244141037_p1015871915468">The container engines supported by CCE include Docker and containerd, which may vary depending on cluster types, cluster versions, and OSs. Select a container engine based on the information displayed on the CCE console. For details, see <a href="cce_10_0462.html#cce_10_0462__section159298451879">Mapping Between Node OSs and Container Engines</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0012__row146695755817"><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__p176690785813">OS</p>
|
||||
@ -69,7 +69,7 @@
|
||||
</div>
|
||||
<p id="cce_10_0012__p136695718581"><strong id="cce_10_0012__b1636315301685">Storage Settings</strong></p>
|
||||
<div class="p" id="cce_10_0012__p866914735818">Configure storage resources on a node for the containers running on it. Select a disk type and configure its size based on service requirements.
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0012__table56691276581" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Storage configuration parameters</caption><thead align="left"><tr id="cce_10_0012__cce_10_0363_row186697710581"><th align="left" class="cellrowborder" valign="top" width="20.02%" id="mcps1.3.2.2.3.2.6.1.2.3.1.1"><p id="cce_10_0012__cce_10_0363_p9669576584">Parameter</p>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0012__table56691276581" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Configuration parameters</caption><thead align="left"><tr id="cce_10_0012__cce_10_0363_row186697710581"><th align="left" class="cellrowborder" valign="top" width="20.02%" id="mcps1.3.2.2.3.2.6.1.2.3.1.1"><p id="cce_10_0012__cce_10_0363_p9669576584">Parameter</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="79.97999999999999%" id="mcps1.3.2.2.3.2.6.1.2.3.1.2"><p id="cce_10_0012__cce_10_0363_p366912711589">Description</p>
|
||||
</th>
|
||||
@ -78,19 +78,28 @@
|
||||
<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">Encryption</strong>: System disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. Only the nodes of the <strong id="cce_10_0012__cce_10_0363_b61621149008">Elastic Cloud Server (VM)</strong> type in certain regions support system disk encryption. For details, see the console.<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. Only the nodes of the <strong id="cce_10_0012__cce_10_0363_b61621149008">Elastic Cloud Server (VM)</strong> type in certain regions support system disk encryption. For details, see the console.<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>
|
||||
<tr id="cce_10_0012__cce_10_0363_row913318122514"><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_p1413315892519">System Component Storage</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_p324785392516">Select a disk for storing system components.</p>
|
||||
<ul id="cce_10_0012__cce_10_0363_ul566328102615"><li id="cce_10_0012__cce_10_0363_li3931805278"><strong id="cce_10_0012__cce_10_0363_b354258318">Data Disk</strong>: added for storing container runtime and kubelet components by default. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</li><li id="cce_10_0012__cce_10_0363_li20663168152611"><strong id="cce_10_0012__cce_10_0363_b724291716512">System Disk</strong>: stores CCE resources such as downloaded images, ephemeral storage for containers, and container stdout logs. If the system disk is fully occupied, it will negatively affect the stability of the node.</li></ul>
|
||||
<div class="note" id="cce_10_0012__cce_10_0363_note6478170183416"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0012__cce_10_0363_p5437848286">In clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later, you can select a disk for storing system components. If <a href="cce_10_0132.html">CCE Node Problem Detector</a> is used, ensure that its version is 1.19.2 or later.</p>
|
||||
</div></div>
|
||||
</td>
|
||||
</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 "><p id="cce_10_0012__cce_10_0363_p246755017336"><strong id="cce_10_0012__cce_10_0363_b126825318466">At least one data disk is required</strong> for the container runtime and kubelet. <strong id="cce_10_0012__cce_10_0363_b1568213115463">The data disk cannot be deleted or uninstalled. Otherwise, the node will be unavailable.</strong></p>
|
||||
<ul id="cce_10_0012__cce_10_0363_ul324262033711"><li id="cce_10_0012__cce_10_0363_li1124252010378">First data disk: used for container runtime and kubelet components. The value ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.</li><li id="cce_10_0012__cce_10_0363_li6177165413374">Other 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 "><div class="p" id="cce_10_0012__cce_10_0363_p246755017336"><strong id="cce_10_0012__cce_10_0363_b178044816211">At least one data disk is required</strong> for the container runtime and kubelet components in 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. <strong id="cce_10_0012__cce_10_0363_b58051819219">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong><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>
|
||||
</div>
|
||||
<p id="cce_10_0012__cce_10_0363_p455973124316">In clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later, 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 have the option not to add the 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.</p>
|
||||
<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>
|
||||
<p id="cce_10_0012__cce_10_0363_p20408122884010"><strong id="cce_10_0012__cce_10_0363_b168590318488">Advanced Settings</strong></p>
|
||||
<p id="cce_10_0012__cce_10_0363_p3752312011">Expand the area and configure the following parameters:</p>
|
||||
<ul id="cce_10_0012__cce_10_0363_ul197721145155911"><li id="cce_10_0012__cce_10_0363_li12110343014"><strong id="cce_10_0012__cce_10_0363_b158191435122117">Data Disk Space Allocation</strong>: allocates space for container engines, images, and ephemeral storage for them to run properly. For details about how to allocate data disk space, see <a href="cce_10_0341.html">Data Disk Space Allocation</a>.</li><li id="cce_10_0012__cce_10_0363_li1095641711169"><strong id="cce_10_0012__cce_10_0363_b8672113734817">Data Disk Encryption</strong>: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. <ul id="cce_10_0012__cce_10_0363_ul1924511512168"><li id="cce_10_0012__cce_10_0363_li4245181561611"><strong id="cce_10_0012__cce_10_0363_b1573516333164">Not encrypted</strong> is selected by default.</li><li id="cce_10_0012__cce_10_0363_li172751284225">If you select <strong id="cce_10_0012__cce_10_0363_b16761923958">Enabled (key)</strong> for <strong id="cce_10_0012__cce_10_0363_b1267610231951">Data Disk Encryption</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0012__cce_10_0363_b76761231051">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_li22751687228">If you select <strong id="cce_10_0012__cce_10_0363_b79545611132">Enabled (KMS key ID)</strong> for <strong id="cce_10_0012__cce_10_0363_b129547621311">Data Disk Encryption</strong>, enter a KMS key (which can be shared by others) in the current region.</li></ul>
|
||||
<ul id="cce_10_0012__cce_10_0363_ul197721145155911"><li id="cce_10_0012__cce_10_0363_li12110343014"><strong id="cce_10_0012__cce_10_0363_b158191435122117">Data Disk Space Allocation</strong>: allocates space for container engines, images, and ephemeral storage for them to run properly. For details about how to allocate data disk space, see <a href="cce_10_0341.html">Space Allocation of a Data Disk</a>.</li><li id="cce_10_0012__cce_10_0363_li1095641711169"><strong id="cce_10_0012__cce_10_0363_b8672113734817">Data Disk Encryption</strong>: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. <ul id="cce_10_0012__cce_10_0363_ul1924511512168"><li id="cce_10_0012__cce_10_0363_li4245181561611"><strong id="cce_10_0012__cce_10_0363_b1573516333164">Not encrypted</strong> is selected by default.</li><li id="cce_10_0012__cce_10_0363_li172751284225">If you select <strong id="cce_10_0012__cce_10_0363_b16761923958">Enabled (key)</strong> for <strong id="cce_10_0012__cce_10_0363_b1267610231951">Data Disk Encryption</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0012__cce_10_0363_b76761231051">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_li22751687228">If you select <strong id="cce_10_0012__cce_10_0363_b79545611132">Enabled (KMS key ID)</strong> for <strong id="cce_10_0012__cce_10_0363_b129547621311">Data Disk Encryption</strong>, enter a KMS key (which can be shared by others) in the current region.</li></ul>
|
||||
</li></ul>
|
||||
<p id="cce_10_0012__cce_10_0363_p1391618153118"><strong id="cce_10_0012__cce_10_0363_b698132517473">Adding data disks</strong></p>
|
||||
<p id="cce_10_0012__cce_10_0363_p45741654112612">A maximum of 16 data disks can be attached to an ECS. By default, a raw disk is created without any processing. You can also click <strong id="cce_10_0012__cce_10_0363_b1353214375715">Expand</strong> and select any of the following options:</p>
|
||||
@ -153,14 +162,14 @@
|
||||
<tbody><tr id="cce_10_0012__en-us_topic_0000001199021246_row25394514014"><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_p25391859406">Resource Tag</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_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. The predefined tags are available to all resources that support tags. You can use predefined tags to improve the tag creation and resource migration efficiency. </p>
|
||||
<p id="cce_10_0012__en-us_topic_0000001199021246_p10327184710426">You can create <span class="uicontrol" id="cce_10_0012__uicontrol15396739571"><b>predefined tags</b></span> on the TMS console. The predefined 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>
|
||||
</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>
|
||||
</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__p1822181243818">A key-value pair added to a Kubernetes object (such as a pod). After specifying a label, click <strong id="cce_10_0012__b23241545145616">Add Label</strong> for more. A maximum of 20 labels can be added.</p>
|
||||
<p id="cce_10_0012__p198221812153813">Labels can be used to distinguish nodes. With workload affinity settings, pods can be scheduled to a specified node. For more information, see <a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/" target="_blank" rel="noopener noreferrer">Labels and Selectors</a>.</p>
|
||||
<p id="cce_10_0012__p198221812153813">Labels can be used to distinguish nodes. With workload affinity settings, container pods can be scheduled to a specified node. For more information, see <a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/" target="_blank" rel="noopener noreferrer">Labels and Selectors</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0012__en-us_topic_0000001199021246_row115391952402"><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_p55391457404">Taint</p>
|
||||
@ -202,13 +211,13 @@
|
||||
</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">Pre-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, 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_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">Pre-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__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>
|
||||
</div></div>
|
||||
@ -216,11 +225,11 @@
|
||||
</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 account 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>
|
||||
<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>
|
||||
</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">User-defined node name prefix and suffix</p>
|
||||
<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>
|
||||
</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__p9918181894313">Custom name prefix and suffix of a node in a node pool. After the configuration, the nodes in the node pool will be named with the configured prefix and suffix. For example, if the prefix is <strong id="cce_10_0012__b8946182075914">prefix-</strong> and the suffix is <strong id="cce_10_0012__b12175424145910">-suffix</strong>, the nodes in the node pool will be named in the format of "prefix-Node pool name with five-digit random characters-suffix".</p>
|
||||
<div class="notice" id="cce_10_0012__note197383116447"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><ul id="cce_10_0012__ul179183516441"><li id="cce_10_0012__li49163584414">A prefix and suffix can be customized only when a node pool is created, and they cannot be modified after the node pool is created.</li><li id="cce_10_0012__li591143524414">A prefix can end with a special character, and a suffix can start with a special character.</li><li id="cce_10_0012__li129218353445">A node name consists of a maximum of 56 characters in the format of "Prefix-Node pool name with five-digit random characters-Suffix".</li><li id="cce_10_0012__li5125114811812">A node name does not support the combination of a period (.) and special characters (such as .., .-, or -.).</li><li id="cce_10_0012__li153132417446">This function is available only in clusters of v1.28.1, v1.27.3, v1.25.6, v1.23.11, v1.21.12, or later.</li></ul>
|
||||
|
||||
@ -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">Using Annotations to Balance Load</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0385.html">Configuring LoadBalancer Services 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>
|
||||
@ -22,6 +22,10 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0355.html">Configuring Passthrough Networking for a LoadBalancer Service</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0916.html">Enabling a LoadBalancer Service to Obtain the Client IP Address</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0924.html">Configuring a Custom EIP for a LoadBalancer Service</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0685.html">Setting the Pod Ready Status Through the ELB Health Check</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0084.html">Enabling ICMP Security Group Rules</a></strong><br>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<a name="cce_10_0015"></a><a name="cce_10_0015"></a>
|
||||
|
||||
<h1 class="topictitle1">Using a ConfigMap</h1>
|
||||
<div id="body1523236302435"><p id="shortdesc15876143794213">After a ConfigMap is created, it can be used in three workload scenarios: <span class="keyword" id="keyword213237704511448">environment variables</span>, <span class="keyword" id="keyword1458163128114411">command line parameters</span>, and <span class="keyword" id="keyword538320223114413">data volumes</span>.</p>
|
||||
<div id="body1523236302435"><p id="cce_10_0015__p181359518">After a ConfigMap is created, it can be used in three workload scenarios: <span class="keyword" id="cce_10_0015__keyword213237704511448">environment variables</span>, <span class="keyword" id="cce_10_0015__keyword1458163128114411">command line parameters</span>, and <span class="keyword" id="cce_10_0015__keyword538320223114413">data volumes</span>.</p>
|
||||
<ul id="cce_10_0015__ul784252913353"><li id="cce_10_0015__li0842229163518"><a href="#cce_10_0015__section1737733192813">Configuring Environment Variables of a Workload</a></li><li id="cce_10_0015__li56474053519"><a href="#cce_10_0015__section17930105710189">Configuring Command Line Parameters</a></li><li id="cce_10_0015__li1855144412358"><a href="#cce_10_0015__section1490261161916">Mounting a ConfigMap to the Workload Data Volume</a></li></ul>
|
||||
<p id="cce_10_0015__p1119921953413">The following example shows how to use a ConfigMap.</p>
|
||||
<pre class="screen" id="cce_10_0015__screen1245419316221">apiVersion: v1
|
||||
@ -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__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>. Then, 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>
|
||||
@ -96,7 +96,7 @@ CCE</pre>
|
||||
<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>
|
||||
<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, that is, the 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 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
|
||||
-c
|
||||
echo $SPECIAL_LEVEL $SPECIAL_TYPE > /usr/share/nginx/html/index.html</pre>
|
||||
</li></ul>
|
||||
@ -107,7 +107,7 @@ echo $SPECIAL_LEVEL $SPECIAL_TYPE > /usr/share/nginx/html/index.html</pre>
|
||||
</p></li></ol>
|
||||
<p id="cce_10_0015__p4491185413187"><strong id="cce_10_0015__b4624652134016">Using kubectl</strong></p>
|
||||
<ol id="cce_10_0015__ol34911754131817"><li id="cce_10_0015__li1949135461810"><span>Use kubectl to access the cluster. For details, see <a href="cce_10_0107.html">Connecting to a Cluster Using kubectl</a>.</span></li><li id="cce_10_0015__li94910544186"><span>Create a file named <strong id="cce_10_0015__b1168565594">nginx-configmap.yaml</strong> and edit it.</span><p><p id="cce_10_0015__p1249155491817"><strong id="cce_10_0015__b749135421815">vi nginx-configmap.yaml</strong></p>
|
||||
<div class="p" id="cce_10_0015__p1265811921915">As shown in the following example, the <strong id="cce_10_0015__b66288220412">cce-configmap</strong> ConfigMap is imported to the workload. <i><span class="varname" id="cce_10_0015__varname040473852310">SPECIAL_LEVEL</span></i> and <i><span class="varname" id="cce_10_0015__varname1840483822318">SPECIAL_TYPE</span></i> are the environment variable names in the workload, that is, the key names in the <strong id="cce_10_0015__b3940185910414">cce-configmap</strong> ConfigMap.<pre class="screen" id="cce_10_0015__screen4422017182118">apiVersion: apps/v1
|
||||
<div class="p" id="cce_10_0015__p1265811921915">In the following example, the <strong id="cce_10_0015__b66288220412">cce-configmap</strong> ConfigMap is imported to the workload. <i><span class="varname" id="cce_10_0015__varname040473852310">SPECIAL_LEVEL</span></i> and <i><span class="varname" id="cce_10_0015__varname1840483822318">SPECIAL_TYPE</span></i> are the environment variable names in the workload, which are key names in the <strong id="cce_10_0015__b3940185910414">cce-configmap</strong> ConfigMap.<pre class="screen" id="cce_10_0015__screen4422017182118">apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
metadata:
|
||||
name: nginx-configmap
|
||||
@ -135,7 +135,7 @@ spec:
|
||||
- name: default-secret</pre>
|
||||
</div>
|
||||
</p></li><li id="cce_10_0015__li39421117570"><span>Create a workload.</span><p><p id="cce_10_0015__p119541114574"><strong id="cce_10_0015__b595191185711">kubectl apply -f nginx-configmap.yaml</strong></p>
|
||||
</p></li><li id="cce_10_0015__li06653419198"><span>After the workload runs properly, the following content is entered into the <strong id="cce_10_0015__b09065208465">/usr/share/nginx/html/index.html</strong> file in the container:</span><p><ol type="a" id="cce_10_0015__ol524017313238"><li id="cce_10_0015__li1524017319232">Run the following command to view the created pod:<pre class="screen" id="cce_10_0015__screen1324053120233">kubectl get pod | grep nginx-configmap</pre>
|
||||
</p></li><li id="cce_10_0015__li06653419198"><span>Wait until the workload runs properly. Then, data will be added the <strong id="cce_10_0015__b09065208465">/usr/share/nginx/html/index.html</strong> file in the container.</span><p><ol type="a" id="cce_10_0015__ol524017313238"><li id="cce_10_0015__li1524017319232">Run the following command to view the created pod:<pre class="screen" id="cce_10_0015__screen1324053120233">kubectl get pod | grep nginx-configmap</pre>
|
||||
<div class="p" id="cce_10_0015__p172401131112311">Expected output:<pre class="screen" id="cce_10_0015__screen1424083122310">nginx-configmap-*** 1/1 Running 0 2m18s</pre>
|
||||
</div>
|
||||
</li><li id="cce_10_0015__li1424023114232">Run the following command to view the environment variables in the pod:<pre class="screen" id="cce_10_0015__screen192401631152310">kubectl exec <i><span class="varname" id="cce_10_0015__varname162406316238">nginx-configmap-***</span></i> -- cat /usr/share/nginx/html/index.html</pre>
|
||||
@ -148,35 +148,35 @@ spec:
|
||||
<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>
|
||||
</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.4.7.4.3.2.1.2.3.1.1"><p id="cce_10_0015__p977974818111">Parameter</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>
|
||||
<th align="left" class="cellrowborder" valign="top" width="85%" id="mcps1.4.7.4.3.2.1.2.3.1.2"><p id="cce_10_0015__p978113488113">Description</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="85%" id="mcps1.3.8.4.3.2.1.2.3.1.2"><p id="cce_10_0015__p978113488113">Description</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0015__row342915156166"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.4.7.4.3.2.1.2.3.1.1 "><p id="cce_10_0015__p17429315151617">ConfigMap</p>
|
||||
<tbody><tr id="cce_10_0015__row342915156166"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.8.4.3.2.1.2.3.1.1 "><p id="cce_10_0015__p17429315151617">ConfigMap</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.4.7.4.3.2.1.2.3.1.2 "><p id="cce_10_0015__p3133142513414">Select the desired ConfigMap.</p>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.8.4.3.2.1.2.3.1.2 "><p id="cce_10_0015__p3133142513414">Select the desired ConfigMap.</p>
|
||||
<p id="cce_10_0015__p17741424142">A ConfigMap must be created beforehand. For details, see <a href="cce_10_0152.html">Creating a ConfigMap</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0015__row030921189"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.4.7.4.3.2.1.2.3.1.1 "><p id="cce_10_0015__p11311217185">Mount Path</p>
|
||||
<tr id="cce_10_0015__row030921189"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.8.4.3.2.1.2.3.1.1 "><p id="cce_10_0015__p11311217185">Mount Path</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.4.7.4.3.2.1.2.3.1.2 "><p id="cce_10_0015__p1548510541219">Enter a mount point. After the ConfigMap volume is mounted, a configuration file with the key as the file name and value as the file content is generated in the mount path of the container.</p>
|
||||
<div class="p" id="cce_10_0015__p53873531026">This parameter specifies a container path to which a data volume will be mounted. Do not mount the volume to a system directory such as <strong id="cce_10_0015__b172894059355716">/</strong> or <strong id="cce_10_0015__b207686195955716">/var/run</strong>. This may lead to container errors. Mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. Otherwise, the files will be replaced, which leads to a container startup failure or workload creation failure.<div class="notice" id="cce_10_0015__note1538785311211"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><p id="cce_10_0015__p16387105311220">If the container is mounted to a high-risk directory, use an account with minimum permissions to start the container. Otherwise, high-risk files on the host may be damaged.</p>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.8.4.3.2.1.2.3.1.2 "><p id="cce_10_0015__p1548510541219">Enter a mount path. After the ConfigMap volume is mounted, a configuration file with the key as the file name and value as the file content is generated in the mount path of the container.</p>
|
||||
<div class="p" id="cce_10_0015__p53873531026">This parameter specifies a container path to which a data volume will be mounted. Do not mount the volume to a system directory such as <strong id="cce_10_0015__b172894059355716">/</strong> or <strong id="cce_10_0015__b207686195955716">/var/run</strong>. This may lead to container errors. Mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. Otherwise, the files will be replaced, leading to container startup failures or workload creation failures.<div class="notice" id="cce_10_0015__note1538785311211"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><p id="cce_10_0015__p16387105311220">If the container is mounted to a high-risk directory, use an account with minimum permissions to start the container. Otherwise, high-risk files on the host may be damaged.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0015__row234422611211"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.4.7.4.3.2.1.2.3.1.1 "><p id="cce_10_0015__p2345192619215">Subpath</p>
|
||||
<tr id="cce_10_0015__row234422611211"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.8.4.3.2.1.2.3.1.1 "><p id="cce_10_0015__p2345192619215">Subpath</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.4.7.4.3.2.1.2.3.1.2 "><div class="p" id="cce_10_0015__p199608476216">Enter a subpath of the mount path.<ul id="cce_10_0015__ul92301146622"><li id="cce_10_0015__li823017469215">A subpath is used to mount a local volume so that the same data volume is used in a single pod. If this parameter is left blank, the root path is used by default.</li><li id="cce_10_0015__li102311346420">The subpath can be the key and value of a ConfigMap or secret. If the subpath is a key-value pair that does not exist, the data import does not take effect.</li><li id="cce_10_0015__li112312463217">The data imported by specifying a subpath will not be updated along with the ConfigMap/secret updates.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.8.4.3.2.1.2.3.1.2 "><div class="p" id="cce_10_0015__p199608476216">Enter a subpath of the mount path.<ul id="cce_10_0015__ul92301146622"><li id="cce_10_0015__li823017469215">A subpath is used to mount a local volume so that the same data volume is used in a single pod. If this parameter is left blank, the root path will be used by default.</li><li id="cce_10_0015__li102311346420">The subpath can be the key and value of a ConfigMap or secret. If the subpath is a key-value pair that does not exist, the data import does not take effect.</li><li id="cce_10_0015__li112312463217">The data imported by specifying a subpath will not be updated along with the ConfigMap/secret updates.</li></ul>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0015__row143321930728"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.4.7.4.3.2.1.2.3.1.1 "><p id="cce_10_0015__p1133273015218">Permission</p>
|
||||
<tr id="cce_10_0015__row143321930728"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.8.4.3.2.1.2.3.1.1 "><p id="cce_10_0015__p1133273015218">Permission</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.4.7.4.3.2.1.2.3.1.2 "><p id="cce_10_0015__p1794824114211">Read-only, indicating that data volume in the path is read-only.</p>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.8.4.3.2.1.2.3.1.2 "><p id="cce_10_0015__p1794824114211">Read-only, indicating that data volume in the path is read-only.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<a name="cce_10_0016"></a><a name="cce_10_0016"></a>
|
||||
|
||||
<h1 class="topictitle1">Using a Secret</h1>
|
||||
<div id="body1523236302435"><p id="shortdesc11673121711466">After secrets are created, they can be mounted as <span class="keyword" id="keyword37518294516">data volumes</span> or be exposed as <span class="keyword" id="keyword19590446124414">environment variables</span> to be used by a container in a pod.</p>
|
||||
<div id="body1523236302435"><p id="cce_10_0016__p4630123213510">After secrets are created, they can be mounted as <span class="keyword" id="cce_10_0016__keyword37518294516">data volumes</span> or be exposed as <span class="keyword" id="cce_10_0016__keyword19590446124414">environment variables</span> to be used by a container in a pod.</p>
|
||||
<div class="notice" id="cce_10_0016__note13556115019429"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cce_10_0016__p39918120437">Do not perform any operation on the following secrets. For details, see <a href="cce_10_0388.html">Cluster Secrets</a>.</p>
|
||||
<ul id="cce_10_0016__ul13678122414717"><li id="cce_10_0016__li19678132424718">Do not operate secrets under kube-system.</li><li id="cce_10_0016__li206781324204718">Do not operate default-secret and paas.elb in any of the namespaces. The default-secret is used to pull the private image of SWR, and the paas.elb is used to connect the service in the namespace to the ELB service.</li></ul>
|
||||
</div></div>
|
||||
@ -96,35 +96,35 @@ spec:
|
||||
<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>
|
||||
</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.4.7.4.3.2.1.2.3.1.1"><p id="cce_10_0016__p196285991018">Parameter</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>
|
||||
<th align="left" class="cellrowborder" valign="top" width="85%" id="mcps1.4.7.4.3.2.1.2.3.1.2"><p id="cce_10_0016__p126314951020">Description</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="85%" id="mcps1.3.8.4.3.2.1.2.3.1.2"><p id="cce_10_0016__p126314951020">Description</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0016__row563713981015"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.4.7.4.3.2.1.2.3.1.1 "><p id="cce_10_0016__p16638594102">Secret</p>
|
||||
<tbody><tr id="cce_10_0016__row563713981015"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.8.4.3.2.1.2.3.1.1 "><p id="cce_10_0016__p16638594102">Secret</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.4.7.4.3.2.1.2.3.1.2 "><p id="cce_10_0016__p790921317488">Select the desired secret.</p>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.8.4.3.2.1.2.3.1.2 "><p id="cce_10_0016__p790921317488">Select the desired secret.</p>
|
||||
<p id="cce_10_0016__p128541638181620">A secret must be created beforehand. For details, see <a href="cce_10_0153.html">Creating a Secret</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0016__row12511814162518"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.4.7.4.3.2.1.2.3.1.1 "><p id="cce_10_0016__p11311217185">Mount Path</p>
|
||||
<tr id="cce_10_0016__row12511814162518"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.8.4.3.2.1.2.3.1.1 "><p id="cce_10_0016__p11311217185">Mount Path</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.4.7.4.3.2.1.2.3.1.2 "><p id="cce_10_0016__p1548510541219">Enter a mount point. After the secret volume is mounted, a secret file with the key as the file name and value as the file content is generated in the mount path of the container.</p>
|
||||
<div class="p" id="cce_10_0016__p53873531026">This parameter specifies a container path to which a data volume will be mounted. Do not mount the volume to a system directory such as <strong id="cce_10_0016__b14073263005443">/</strong> or <strong id="cce_10_0016__b15813089835443">/var/run</strong>. This may cause container errors. Mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. Otherwise, the files will be replaced, which leads to a container startup failure or workload creation failure.<div class="notice" id="cce_10_0016__note1538785311211"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><p id="cce_10_0016__p16387105311220">If the container is mounted to a high-risk directory, use an account with minimum permissions to start the container. Otherwise, high-risk files on the host may be damaged.</p>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.8.4.3.2.1.2.3.1.2 "><p id="cce_10_0016__p1548510541219">Enter a mount path. After the secret volume is mounted, a secret file with the key as the file name and value as the file content is generated in the mount path of the container.</p>
|
||||
<div class="p" id="cce_10_0016__p53873531026">This parameter specifies a container path to which a data volume will be mounted. Do not mount the volume to a system directory such as <strong id="cce_10_0016__b14073263005443">/</strong> or <strong id="cce_10_0016__b15813089835443">/var/run</strong>. This may lead to container errors. Mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. Otherwise, the files will be replaced, leading to container startup failures or workload creation failures.<div class="notice" id="cce_10_0016__note1538785311211"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><p id="cce_10_0016__p16387105311220">If the container is mounted to a high-risk directory, use an account with minimum permissions to start the container. Otherwise, high-risk files on the host may be damaged.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0016__row1513114150251"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.4.7.4.3.2.1.2.3.1.1 "><p id="cce_10_0016__p2345192619215">Subpath</p>
|
||||
<tr id="cce_10_0016__row1513114150251"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.8.4.3.2.1.2.3.1.1 "><p id="cce_10_0016__p2345192619215">Subpath</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.4.7.4.3.2.1.2.3.1.2 "><p id="cce_10_0016__p199608476216">Enter a subpath of the mount path.</p>
|
||||
<ul id="cce_10_0016__ul92301146622"><li id="cce_10_0016__li823017469215">A subpath is used to mount a local volume so that the same data volume is used in a single pod. If this parameter is left blank, the root path is used by default.</li><li id="cce_10_0016__li102311346420">The subpath can be the key and value of a ConfigMap or secret. If the subpath is a key-value pair that does not exist, the data import does not take effect.</li><li id="cce_10_0016__li112312463217">The data imported by specifying a subpath will not be updated along with the ConfigMap/secret updates.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.8.4.3.2.1.2.3.1.2 "><p id="cce_10_0016__p199608476216">Enter a subpath of the mount path.</p>
|
||||
<ul id="cce_10_0016__ul92301146622"><li id="cce_10_0016__li823017469215">A subpath is used to mount a local volume so that the same data volume is used in a single pod. If this parameter is left blank, the root path will be used by default.</li><li id="cce_10_0016__li102311346420">The subpath can be the key and value of a ConfigMap or secret. If the subpath is a key-value pair that does not exist, the data import does not take effect.</li><li id="cce_10_0016__li112312463217">The data imported by specifying a subpath will not be updated along with the ConfigMap/secret updates.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0016__row561113158259"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.4.7.4.3.2.1.2.3.1.1 "><p id="cce_10_0016__p1133273015218">Permission</p>
|
||||
<tr id="cce_10_0016__row561113158259"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.8.4.3.2.1.2.3.1.1 "><p id="cce_10_0016__p1133273015218">Permission</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.4.7.4.3.2.1.2.3.1.2 "><p id="cce_10_0016__p1794824114211">Read-only, indicating that data volume in the path is read-only.</p>
|
||||
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.8.4.3.2.1.2.3.1.2 "><p id="cce_10_0016__p1794824114211">Read-only, indicating that data volume in the path is read-only.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
||||
@ -4,8 +4,7 @@
|
||||
<div id="body1522667123001"><p id="cce_10_0018__p78381781804">CCE works with AOM to collect workload logs. When a node is created, ICAgent (a DaemonSet named <strong id="cce_10_0018__b13829819578">icagent</strong> in the <strong id="cce_10_0018__b697274313582">kube-system</strong> namespace of a cluster) of AOM is installed by default. ICAgent collects workload logs and reports them to AOM. You can view workload logs on the CCE or AOM console.</p>
|
||||
<div class="section" id="cce_10_0018__section17884754413"><h4 class="sectiontitle">Constraints</h4><p id="cce_10_0018__p23831558355">ICAgent only collects text logs in .log, .trace, and .out formats.</p>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0018__section1951732710"><h4 class="sectiontitle">Using ICAgent to Collect Logs</h4><ol id="cce_10_0018__ol1253654833013"><li id="cce_10_0018__li19284854163014"><span>When <a href="cce_10_0047.html">creating a workload</a>, set logging for the container.</span></li><li id="cce_10_0018__li2427158104715"><span>Click <span><img id="cce_10_0018__image134281583473" src="en-us_image_0000001950317236.png"></span> to add a log policy.</span><p><div class="p" id="cce_10_0018__p9862125810472">The following uses Nginx as an example. Log policies vary depending on workloads.<div class="fignone" id="cce_10_0018__fig19856172153216"><span class="figcap"><b>Figure 1 </b>Adding a log policy</span><br><span><img id="cce_10_0018__image664110265156" src="en-us_image_0000001981276785.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0018__section1951732710"><h4 class="sectiontitle">Using ICAgent to Collect Logs</h4><ol id="cce_10_0018__ol1253654833013"><li id="cce_10_0018__li19284854163014"><span>When <a href="cce_10_0047.html">creating a workload</a>, set logging for the container.</span></li><li id="cce_10_0018__li2427158104715"><span>Click <span><img id="cce_10_0018__image134281583473" src="en-us_image_0000002065639042.png"></span> to add a log policy.</span><p><p id="cce_10_0018__p9862125810472">The following uses Nginx as an example. Log policies vary depending on workloads.</p>
|
||||
</p></li><li id="cce_10_0018__li1479392315150"><span>Set <strong id="cce_10_0018__b5461630195419">Volume Type</strong> to <span class="uicontrol" id="cce_10_0018__uicontrol105212302547"><b>hostPath</b></span> or <span class="uicontrol" id="cce_10_0018__uicontrol1752103095410"><b>emptyDir</b></span>.</span><p>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0018__table115901715550" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Configuring log policies</caption><thead align="left"><tr id="cce_10_0018__row45851074554"><th align="left" class="cellrowborder" valign="top" width="22.12%" id="mcps1.3.3.2.3.2.1.2.3.1.1"><p id="cce_10_0018__p115843785517">Parameter</p>
|
||||
</th>
|
||||
@ -98,7 +97,7 @@ spec:
|
||||
name: vol-log
|
||||
imagePullSecrets:
|
||||
- name: default-secret</pre>
|
||||
<p id="cce_10_0018__p878213715533">The following shows how to use a hostPath volume. Compared with emptyDir, the type of <strong id="cce_10_0018__b1818572291612">volume</strong><strong id="cce_10_0018__b16186132221614">s</strong> is changed to <strong id="cce_10_0018__b8437327171619">hostPath</strong>, and the path on the host needs to be configured for this hostPath volume. In the following example, <span class="uicontrol" id="cce_10_0018__uicontrol046012383406"><b>/tmp/log</b></span> on the host is mounted to <span class="uicontrol" id="cce_10_0018__uicontrol1546533819400"><b>/var/log/nginx</b></span>. In this way, the ICAgent can collects logs in <strong id="cce_10_0018__b1246512382409">/var/log/nginx</strong>, without deleting the logs from <strong id="cce_10_0018__b64661838144012">/tmp/log</strong>.</p>
|
||||
<p id="cce_10_0018__p878213715533">The following shows how to use a hostPath volume. Compared with emptyDir, the type of <strong id="cce_10_0018__b116061846152315">volumes</strong> is changed to <strong id="cce_10_0018__b19606134616237">hostPath</strong>, and the path on the host needs to be configured for this hostPath volume. In the following example, <span class="uicontrol" id="cce_10_0018__uicontrol046012383406"><b>/tmp/log</b></span> on the host is mounted to <span class="uicontrol" id="cce_10_0018__uicontrol1546533819400"><b>/var/log/nginx</b></span>. In this way, the ICAgent can collects logs in <strong id="cce_10_0018__b1246512382409">/var/log/nginx</strong>, without deleting the logs from <strong id="cce_10_0018__b64661838144012">/tmp/log</strong>.</p>
|
||||
<pre class="screen" id="cce_10_0018__screen1347245314534">apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
metadata:
|
||||
@ -155,8 +154,8 @@ spec:
|
||||
<td class="cellrowborder" valign="top" width="19.23%" headers="mcps1.3.4.7.2.4.1.2 "><p id="cce_10_0018__p6329709512">Extended host path</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="63.71%" headers="mcps1.3.4.7.2.4.1.3 "><p id="cce_10_0018__p32881805119">Extended host paths contain pod IDs or container names to distinguish different containers into which the host path is mounted.</p>
|
||||
<p id="cce_10_0018__p1728888115112">A level-3 directory is added to the original volume directory/subdirectory. You can easily obtain the files output by a single <span class="keyword" id="cce_10_0018__keyword794706769">Pod</span>.</p>
|
||||
<ul id="cce_10_0018__ul2028828105113"><li id="cce_10_0018__li428815865110"><strong id="cce_10_0018__b1402185631">None</strong>: No extended path is configured. </li><li id="cce_10_0018__li62889814517"><strong id="cce_10_0018__b1868207742">PodUID</strong>: ID of a pod.</li><li id="cce_10_0018__li528818135113"><strong id="cce_10_0018__b1874430595">PodName</strong>: name of a pod.</li><li id="cce_10_0018__li62882084517"><strong id="cce_10_0018__b1735619381">PodUID/ContainerName</strong>: ID of a pod or name of a container.</li><li id="cce_10_0018__li528898175110"><strong id="cce_10_0018__b8818125942116">PodName/ContainerName</strong>: name of a pod or container.</li></ul>
|
||||
<p id="cce_10_0018__p1728888115112">A level-3 directory is added to the original volume directory/subdirectory. You can easily obtain the files output by a single <span class="keyword" id="cce_10_0018__keyword1126675436">Pod</span>.</p>
|
||||
<ul id="cce_10_0018__ul2028828105113"><li id="cce_10_0018__li428815865110"><strong id="cce_10_0018__b157376074">None</strong>: No extended path is configured. </li><li id="cce_10_0018__li62889814517"><strong id="cce_10_0018__b1606015244">PodUID</strong>: ID of a pod.</li><li id="cce_10_0018__li528818135113"><strong id="cce_10_0018__b680447047">PodName</strong>: name of a pod.</li><li id="cce_10_0018__li62882084517"><strong id="cce_10_0018__b678547011">PodUID/ContainerName</strong>: ID of a pod or name of a container.</li><li id="cce_10_0018__li528898175110"><strong id="cce_10_0018__b8818125942116">PodName/ContainerName</strong>: name of a pod or container.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0018__row732915085118"><td class="cellrowborder" valign="top" width="17.06%" headers="mcps1.3.4.7.2.4.1.1 "><p id="cce_10_0018__p17329004514">policy.logs.rotate</p>
|
||||
@ -164,7 +163,7 @@ spec:
|
||||
<td class="cellrowborder" valign="top" width="19.23%" headers="mcps1.3.4.7.2.4.1.2 "><p id="cce_10_0018__p123292055113">Log dump</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="63.71%" headers="mcps1.3.4.7.2.4.1.3 "><p id="cce_10_0018__p1017113396539">Log dump refers to rotating log files on a local host.</p>
|
||||
<ul id="cce_10_0018__ul1617120398533"><li id="cce_10_0018__li71711639105316"><strong id="cce_10_0018__b4837638192520">Enabled</strong>: AOM scans log files every minute. When a log file exceeds 50 MB, it is dumped immediately. A new <strong id="cce_10_0018__b98429388254">.zip</strong> file is generated in the directory where the log file locates. For a log file, AOM stores only the latest 20 <strong id="cce_10_0018__b2216332192917">.zip</strong> files. When the number of <strong id="cce_10_0018__b1621653252914">.zip</strong> files exceeds 20, earlier <strong id="cce_10_0018__b1321623212917">.zip</strong> files will be deleted. After the dump is complete, the log file in AOM will be cleared.</li><li id="cce_10_0018__li817133985315"><strong id="cce_10_0018__b1701440828">Disabled</strong>: AOM does not dump log files.</li></ul>
|
||||
<ul id="cce_10_0018__ul1617120398533"><li id="cce_10_0018__li71711639105316"><strong id="cce_10_0018__b4837638192520">Enabled</strong>: AOM scans log files every minute. When a log file exceeds 50 MB, it is dumped immediately. A new <strong id="cce_10_0018__b98429388254">.zip</strong> file is generated in the directory where the log file locates. For a log file, AOM stores only the latest 20 <strong id="cce_10_0018__b2216332192917">.zip</strong> files. When the number of <strong id="cce_10_0018__b1621653252914">.zip</strong> files exceeds 20, earlier <strong id="cce_10_0018__b1321623212917">.zip</strong> files will be deleted. After the dump is complete, the log file in AOM will be cleared.</li><li id="cce_10_0018__li817133985315"><strong id="cce_10_0018__b642591027">Disabled</strong>: AOM does not dump log files.</li></ul>
|
||||
<div class="note" id="cce_10_0018__note121711639195319"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0018__ul817183918533"><li id="cce_10_0018__li9171183945310">AOM rotates log files using copytruncate. Before enabling log dumping, ensure that log files are written in the append mode. Otherwise, file holes may occur.</li><li id="cce_10_0018__li1117153914535">Currently, mainstream log components such as Log4j and Logback support log file rotation. If you have already set rotation for log files, skip the configuration. Otherwise, conflicts may occur.</li><li id="cce_10_0018__li317113915532">You are advised to configure log file rotation for your own services to flexibly control the size and number of rolled files.</li></ul>
|
||||
</div></div>
|
||||
</td>
|
||||
@ -174,7 +173,7 @@ spec:
|
||||
<td class="cellrowborder" valign="top" width="19.23%" headers="mcps1.3.4.7.2.4.1.2 "><p id="cce_10_0018__p14388112019519">Collection path</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="63.71%" headers="mcps1.3.4.7.2.4.1.3 "><p id="cce_10_0018__p63882201153">A collection path narrows down the scope of collection to specified logs.</p>
|
||||
<ul id="cce_10_0018__ul73883209510"><li id="cce_10_0018__li14388162011513">If no collection path is specified, log files in <strong id="cce_10_0018__b2074831367">.log</strong>, <strong id="cce_10_0018__b1268946909">.trace</strong>, and <strong id="cce_10_0018__b1916570637">.out</strong> formats will be collected from the specified path.</li><li id="cce_10_0018__li03886201854"><strong id="cce_10_0018__b1348669150">/Path/**/</strong> indicates that all log files in <strong id="cce_10_0018__b1576016562">.log</strong>, <strong id="cce_10_0018__b1678875580">.trace</strong>, and <strong id="cce_10_0018__b515549583">.out</strong> formats will be recursively collected from the specified path and all subdirectories at 5 levels deep.</li><li id="cce_10_0018__li1938811201058">* in log file names indicates a fuzzy match.</li></ul>
|
||||
<ul id="cce_10_0018__ul73883209510"><li id="cce_10_0018__li14388162011513">If no collection path is specified, log files in <strong id="cce_10_0018__b1129214307">.log</strong>, <strong id="cce_10_0018__b1581621110">.trace</strong>, and <strong id="cce_10_0018__b2037581547">.out</strong> formats will be collected from the specified path.</li><li id="cce_10_0018__li03886201854"><strong id="cce_10_0018__b45106373">/Path/**/</strong> indicates that all log files in <strong id="cce_10_0018__b2008565461">.log</strong>, <strong id="cce_10_0018__b2061915364">.trace</strong>, and <strong id="cce_10_0018__b2076841527">.out</strong> formats will be recursively collected from the specified path and all subdirectories at 5 levels deep.</li><li id="cce_10_0018__li1938811201058">* in log file names indicates a fuzzy match.</li></ul>
|
||||
<p id="cce_10_0018__p17388152013515">Example: The collection path <strong id="cce_10_0018__b19951612237">/tmp/**/test*.log</strong> indicates that all <strong id="cce_10_0018__b49571315239">.log</strong> files prefixed with <strong id="cce_10_0018__b4958101202315">test</strong> will be collected from <strong id="cce_10_0018__b695815172316">/tmp</strong> and subdirectories at 5 levels deep.</p>
|
||||
<div class="caution" id="cce_10_0018__note153881220751"><span class="cautiontitle"> CAUTION: </span><div class="cautionbody"><p id="cce_10_0018__p938810204516">Ensure that ICAgent is of v5.12.22 or later.</p>
|
||||
</div></div>
|
||||
@ -203,7 +202,7 @@ spec:
|
||||
<div class="section" id="cce_10_0018__section25851847232"><h4 class="sectiontitle">Viewing Logs</h4><p id="cce_10_0018__p209669599247">After a log collection path is configured and the workload is created, the ICAgent collects log files from the configured path. The collection takes about 1 minute.</p>
|
||||
<p id="cce_10_0018__p242194515304">After the log collection is complete, go to the workload details page and click <strong id="cce_10_0018__b13484541192818">Logs</strong> in the upper right corner to view logs.</p>
|
||||
<p id="cce_10_0018__p32989282515">You can also view logs on the AOM console.</p>
|
||||
<p id="cce_10_0018__p160613416815">You can also run the <strong id="cce_10_0018__b12443114301613">kubectl logs</strong> command to view the container stdout.</p>
|
||||
<p id="cce_10_0018__p160613416815">You can also run the <strong id="cce_10_0018__b9741144192912">kubectl logs</strong> command to view the container stdout.</p>
|
||||
<pre class="screen" id="cce_10_0018__screen1210248152712"># View logs of a specified pod.
|
||||
kubectl logs <pod_name>
|
||||
kubectl logs -f <pod_name> # Similar to <strong id="cce_10_0018__b34131514579">tail -f</strong>
|
||||
|
||||
@ -4,7 +4,7 @@
|
||||
<div id="body1522665832345"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0191.html">Overview</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0191.html">Overview of a Chart</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0146.html">Deploying an Application from a Chart</a></strong><br>
|
||||
</li>
|
||||
|
||||
@ -5,7 +5,7 @@
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0025.html">CCE Operations Supported by Cloud Trace Service</a></strong><br>
|
||||
Cloud Trace Service (CTS) records operations on cloud service resources, allowing users to query, audit, and backtrack the resource operation requests initiated from the management console or open APIs as well as responses to the requests.</li>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0026.html">Viewing CTS Traces in the Trace List</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -4,19 +4,10 @@
|
||||
<div id="body1525226397666"><div class="section" id="cce_10_0026__en-us_topic_0179639644_section5470822195238"><h4 class="sectiontitle">Scenarios</h4><p id="cce_10_0026__en-us_topic_0179639644_p333055219577">After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. Cloud Trace Service (CTS) stores operation records (traces) generated in the last seven days.</p>
|
||||
<div class="note" id="cce_10_0026__en-us_topic_0179639644_note1438715448188"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0026__en-us_topic_0179639644_p1138754410182">These operation records are retained for seven days on the CTS console and are automatically deleted upon expiration. Manual deletion is not supported.</p>
|
||||
</div></div>
|
||||
<p id="cce_10_0026__en-us_topic_0179639644_p3008599195238">This section describes how to query or export operation records of the last seven days on the CTS console.</p>
|
||||
<ul id="cce_10_0026__en-us_topic_0179639644_ul17577535194620"><li id="cce_10_0026__en-us_topic_0179639644_li195771235174613"><a href="#cce_10_0026__en-us_topic_0179639644_section6300091795238">Viewing Real-Time Traces in the Trace List of the New Edition</a></li><li id="cce_10_0026__en-us_topic_0179639644_li201409184718"><a href="#cce_10_0026__en-us_topic_0179639644_section19271975203">Viewing Real-Time Traces in the Trace List of the Old Edition</a></li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section17513919143614"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0026__en-us_topic_0179639644_ul10927192364611"><li id="cce_10_0026__en-us_topic_0179639644_li9927223134614">You can only query operation records of the last seven days on the CTS console. To store operation records for longer than seven days, you must configure transfer to OBS or Log Tank Service (LTS) so that you can view them in OBS buckets or LTS log groups.</li><li id="cce_10_0026__en-us_topic_0179639644_li8852101625020">After performing operations on the cloud, you can query management traces on the CTS console one minute later.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section6300091795238"><a name="cce_10_0026__en-us_topic_0179639644_section6300091795238"></a><a name="en-us_topic_0179639644_section6300091795238"></a><h4 class="sectiontitle">Viewing Real-Time Traces in the Trace List of the New Edition</h4><ol id="cce_10_0026__en-us_topic_0179639644_ol3001478295238"><li id="cce_10_0026__en-us_topic_0179639644_li3954991595238">Log in to the management console.</li><li id="cce_10_0026__en-us_topic_0179639644_li3694304795238">Click <span><img id="cce_10_0026__en-us_topic_0179639644_image18230310103219" src="en-us_image_0000001187249376.png"></span> in the upper left corner and choose <strong id="cce_10_0026__en-us_topic_0179639644_b1248293451010">Management & Deployment</strong> > <strong id="cce_10_0026__en-us_topic_0179639644_b176581110111019">Cloud Trace Service</strong>. The CTS console is displayed.</li><li id="cce_10_0026__en-us_topic_0179639644_li4560416895238">Choose <strong id="cce_10_0026__en-us_topic_0179639644_b1548161231117">Trace List</strong> in the navigation pane on the left.</li><li id="cce_10_0026__en-us_topic_0179639644_li877858395238">On the <strong id="cce_10_0026__en-us_topic_0179639644_b1537711461318">Trace List</strong> page, use advanced search to query traces. You can combine one or more filters.<ul class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_ul13105101342515"><li class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_li470415162610"><strong id="cce_10_0026__en-us_topic_0179639644_b121811341812">Trace Name</strong>: Enter a trace name.</li><li id="cce_10_0026__en-us_topic_0179639644_li5845153914283"><strong id="cce_10_0026__en-us_topic_0179639644_b1868642096">Trace ID</strong>: Enter a trace ID.</li><li class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_li121812712610"><strong id="cce_10_0026__en-us_topic_0179639644_b149256147919">Resource Name</strong>: Enter a resource name. 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.</li><li class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_li11791482268"><strong id="cce_10_0026__en-us_topic_0179639644_b08609468911">Resource ID</strong>: Enter a resource ID. Leave this field empty if the resource has no resource ID or if resource creation failed.</li><li class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_li619185017272"><strong id="cce_10_0026__en-us_topic_0179639644_b280617118104">Trace Source</strong>: Select a cloud service name from the drop-down list.</li><li id="cce_10_0026__en-us_topic_0179639644_li18193203903417"><strong id="cce_10_0026__en-us_topic_0179639644_b13863421131010">Resource Type</strong>: Select a resource type from the drop-down list.</li><li id="cce_10_0026__en-us_topic_0179639644_li14105141392513"><strong id="cce_10_0026__en-us_topic_0179639644_b179165641114">Operator</strong>: Select one or more operators from the drop-down list.</li><li id="cce_10_0026__en-us_topic_0179639644_li110591317255"><strong id="cce_10_0026__en-us_topic_0179639644_b377193202212">Trace Status</strong>: Select <strong id="cce_10_0026__en-us_topic_0179639644_b107818329223">normal</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b1378113272212">warning</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b2787327222">incident</strong>.<ul id="cce_10_0026__en-us_topic_0179639644_ul7141162215312"><li id="cce_10_0026__en-us_topic_0179639644_li145201024135111"><strong id="cce_10_0026__en-us_topic_0179639644_b143575532314">normal</strong>: The operation succeeded.</li><li id="cce_10_0026__en-us_topic_0179639644_li10846192555119"><strong id="cce_10_0026__en-us_topic_0179639644_b426712462235">warning</strong>: The operation failed.</li><li id="cce_10_0026__en-us_topic_0179639644_li19512310115116"><strong id="cce_10_0026__en-us_topic_0179639644_b1252219416241">incident</strong>: The operation caused a fault that is more serious than the operation failure, for example, causing other faults.</li></ul>
|
||||
</li><li id="cce_10_0026__en-us_topic_0179639644_li12161950321">Time range: Select <strong id="cce_10_0026__en-us_topic_0179639644_b1602115041017">Last 1 hour</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b46024507108">Last 1 day</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b2060235013102">Last 1 week</strong>, or specify a custom time range within the last seven days.</li></ul>
|
||||
</li><li id="cce_10_0026__en-us_topic_0179639644_li17684227175818">On the <strong id="cce_10_0026__en-us_topic_0179639644_b1922182591118">Trace List</strong> page, you can also export and refresh the trace list, and customize columns to display.<ul id="cce_10_0026__en-us_topic_0179639644_ul171014569599"><li id="cce_10_0026__en-us_topic_0179639644_li68555243511">Enter any keyword in the search box and press <strong id="cce_10_0026__en-us_topic_0179639644_b2365948135712">Enter</strong> to filter desired traces.</li><li id="cce_10_0026__en-us_topic_0179639644_li13101185685914">Click <strong id="cce_10_0026__en-us_topic_0179639644_b18601848191112">Export</strong> to export all traces in the query result as an .xlsx file. The file can contain up to 5,000 records.</li><li id="cce_10_0026__en-us_topic_0179639644_li86171118016">Click <span><img id="cce_10_0026__en-us_topic_0179639644_image1874712381601" src="en-us_image_0000001667734001.png"></span> to view the latest information about traces.</li><li id="cce_10_0026__en-us_topic_0179639644_li209831840119">Click <span><img id="cce_10_0026__en-us_topic_0179639644_image564420481812" src="en-us_image_0000001619094530.png"></span> to customize the information to be displayed in the trace list. If <strong id="cce_10_0026__en-us_topic_0179639644_b67271845111312">Auto wrapping</strong> is enabled (<span><img id="cce_10_0026__en-us_topic_0179639644_image12727174571318" src="en-us_image_0000001667694873.png"></span>), excess text will move down to the next line; otherwise, the text will be truncated. By default, this function is disabled.</li></ul>
|
||||
</li><li id="cce_10_0026__en-us_topic_0179639644_li1714145242219">For details about key fields in the trace structure, see and section "Trace References" > "Example Traces".</li><li id="cce_10_0026__en-us_topic_0179639644_li343919722319">(Optional) On the <strong id="cce_10_0026__en-us_topic_0179639644_b39126353206">Trace List</strong> page of the new edition, click <strong id="cce_10_0026__en-us_topic_0179639644_b573342114">Go to Old Edition</strong> in the upper right corner to switch to the <strong id="cce_10_0026__en-us_topic_0179639644_b4747415172118">Trace List</strong> page of the old edition.</li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section19271975203"><a name="cce_10_0026__en-us_topic_0179639644_section19271975203"></a><a name="en-us_topic_0179639644_section19271975203"></a><h4 class="sectiontitle">Viewing Real-Time Traces in the Trace List of the Old Edition</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_b12821731121516">Management & Deployment</strong> > <strong id="cce_10_0026__en-us_topic_0179639644_b178213191512">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_li20323199115315">Each time you log in to the CTS console, the new edition is displayed by default. Click <strong id="cce_10_0026__en-us_topic_0179639644_b72452318231">Go to Old Edition</strong> in the upper right corner to switch to the trace list of the old edition.</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="section" id="cce_10_0026__en-us_topic_0179639644_section19271975203"><h4 class="sectiontitle">Viewing Real-Time Traces</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_image3220189363" src="en-us_image_0000001696838310.png"></span> in the upper left corner and choose <strong id="cce_10_0026__en-us_topic_0179639644_b112111833612">Management & Deployment</strong> > <strong id="cce_10_0026__en-us_topic_0179639644_b172191811363">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_b107601514121615">Last 1 hour</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b1676021410164">Last 1 day</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b37601914121610">Last 1 week</strong>, or specify a custom time range within the last seven days.</li><li id="cce_10_0026__en-us_topic_0179639644_li8936104118436">Click <strong id="cce_10_0026__en-us_topic_0179639644_b861150123114">Export</strong> to export all traces in the query result as a CSV file. The file can contain up to 5,000 records.</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>
|
||||
</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>
|
||||
@ -25,7 +16,7 @@
|
||||
<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 section "Trace References" > "Trace Structure" and section "Trace References" > "Example Traces" in the <em id="cce_10_0026__en-us_topic_0179639644_i149551042114218">CTS User Guide</em>.</li><li id="cce_10_0026__en-us_topic_0179639644_li11635104116013">(Optional) On the <strong id="cce_10_0026__en-us_topic_0179639644_b128618229347">Trace List</strong> page of the old edition, click <strong id="cce_10_0026__en-us_topic_0179639644_b1186112216341">New Edition</strong> in the upper right corner to switch to the <strong id="cce_10_0026__en-us_topic_0179639644_b886118225346">Trace List</strong> page of the new edition.</li></ol>
|
||||
</li><li id="cce_10_0026__en-us_topic_0179639644_li129561719446">For details about key fields in the trace structure, see section "Trace References" > "Trace Structure" and section "Trace References" > "Example Traces" in the <em id="cce_10_0026__en-us_topic_0179639644_i327125153611">CTS User Guide</em>.</li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -14,6 +14,8 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0212.html">Deleting a Cluster</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0927.html">Preventing Cluster Deletion</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0214.html">Hibernating or Waking Up a Cluster</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -3,6 +3,8 @@
|
||||
<h1 class="topictitle1">Logging In to a Container</h1>
|
||||
<div id="body0000001151211236"><div class="section" id="cce_10_00356__section7379040716"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_00356__p1134114511811">If you encounter unexpected problems when using a container, you can log in to the container to debug it.</p>
|
||||
</div>
|
||||
<div class="section" id="cce_10_00356__section1536420242714"><h4 class="sectiontitle">Notes and Constraints</h4><p id="cce_10_00356__cce_10_0671_p1192104192713">When using CloudShell to access a CCE cluster or container, you can open a maximum of 15 instances simultaneously.</p>
|
||||
</div>
|
||||
<div class="section" id="cce_10_00356__section1293318163114"><h4 class="sectiontitle">Using kubectl</h4><ol id="cce_10_00356__ol1392823394416"><li id="cce_10_00356__li1681024195710"><span>Use kubectl to access the cluster. For details, see <a href="cce_10_0107.html">Connecting to a Cluster Using kubectl</a>.</span></li><li id="cce_10_00356__li1020013819415"><span>Run the following command to view the created pod:</span><p><pre class="screen" id="cce_10_00356__screen156898195914">kubectl get pod</pre>
|
||||
<div class="p" id="cce_10_00356__p18257204595920">The example output is as follows:<pre class="screen" id="cce_10_00356__screen7944553592">NAME READY STATUS RESTARTS AGE
|
||||
nginx-59d89cb66f-mhljr 1/1 Running 0 11m</pre>
|
||||
|
||||
@ -3,10 +3,9 @@
|
||||
<h1 class="topictitle1">Stopping a Node</h1>
|
||||
<div id="body1564130562761"><div class="section" id="cce_10_0036__section127213017388"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0036__p866311509249">When a node in the cluster is stopped, all services on that node will also be stopped, and the node will no longer be available for scheduling. Check if your services will be affected before stopping a node.</p>
|
||||
</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">Deleting 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 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">Yes</strong>.</span><p><div class="fignone" id="cce_10_0036__fig19269101385311"><span class="figcap"><b>Figure 1 </b>ECS details page</span><br><span><img id="cce_10_0036__image124001418192" src="en-us_image_0000001981276729.png"></span></div>
|
||||
</p></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 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>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
@ -7,11 +7,11 @@
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0152.html">Creating a ConfigMap</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0015.html">Using a ConfigMap</a></strong><br>
|
||||
After a ConfigMap is created, it can be used in three workload scenarios: <span class="keyword">environment variables</span>, <span class="keyword">command line parameters</span>, and <span class="keyword">data volumes</span>.</li>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0153.html">Creating a Secret</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0016.html">Using a Secret</a></strong><br>
|
||||
After secrets are created, they can be mounted as <span class="keyword">data volumes</span> or be exposed as <span class="keyword">environment variables</span> to be used by a container in a pod.</li>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0388.html">Cluster Secrets</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@ -5,11 +5,13 @@
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0006.html">Overview</a></strong><br>
|
||||
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">Deployments</span>, <span class="keyword">StatefulSets</span>, <span class="keyword">DaemonSets</span>, <span class="keyword">jobs</span>, and <span class="keyword">cron jobs</span>.</li>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0673.html">Creating a Workload</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0130.html">Configuring a Workload</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0889.html">Scheduling a Workload</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_00356.html">Logging In to a Container</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0007.html">Managing Workloads</a></strong><br>
|
||||
|
||||
@ -81,10 +81,10 @@
|
||||
<p id="cce_10_0047__p1447162741615"><strong id="cce_10_0047__b154561192487">(Optional) Service Settings</strong></p>
|
||||
<p id="cce_10_0047__p102354303348">A Service provides external access for pods. With a static IP address, a Service forwards access traffic to pods and automatically balances load for these pods.</p>
|
||||
<p id="cce_10_0047__p13343123113612">You can also create a Service after creating a workload. For details about Services of different types, see <a href="cce_10_0249.html">Overview</a>.</p>
|
||||
<div class="p" id="cce_10_0047__p310913521612"><strong id="cce_10_0047__b204881212144816">(Optional) Advanced Settings</strong><ul id="cce_10_0047__ul142811417"><li id="cce_10_0047__li0421513417"><strong id="cce_10_0047__b15415314859">Upgrade</strong>: Specify the upgrade mode and parameters of the workload. <strong id="cce_10_0047__b153151558165913">Rolling upgrade</strong> and <strong id="cce_10_0047__b1621251402">Replace upgrade</strong> are available. For details, see <a href="cce_10_0397.html">Configuring Workload Upgrade Policies</a>.</li><li id="cce_10_0047__li5292111713411"><strong id="cce_10_0047__b289714923012">Scheduling</strong>: Configure affinity and anti-affinity policies for flexible workload scheduling. Load affinity and node affinity are provided.<ul id="cce_10_0047__ul16976133413332"><li id="cce_10_0047__li7687143311331"><strong id="cce_10_0047__b1243811103214">Load Affinity</strong>: Common load affinity policies are offered for quick load affinity deployment.<ul id="cce_10_0047__ul1865517492338"><li id="cce_10_0047__li84431255153310"><strong id="cce_10_0047__b21119711352">Multi-AZ deployment is preferred</strong>: Workload pods are preferentially scheduled to nodes in different AZs through pod anti-affinity (<strong id="cce_10_0047__b156511824123612">podAntiAffinity</strong>). If all the nodes in the cluster are deployed in the same AZ, the pods will be scheduled to that AZ but onto different nodes for high availability. If there are fewer nodes than pods, the extra pods will fail to run.</li><li id="cce_10_0047__li10775194183413"><strong id="cce_10_0047__b1667575214119">Forcible multi-AZ deployment</strong>: Workload pods are forcibly scheduled to nodes in different AZs through pod anti-affinity (<strong id="cce_10_0047__b10853186174217">podAntiAffinity</strong>). If there are fewer AZs than pods, the extra pods will fail to run.</li><li id="cce_10_0047__li177960111349"><strong id="cce_10_0047__b18931103644418">Custom policies</strong>: Affinity and anti-affinity policies can be customized as needed. For details, see <a href="cce_10_0232.html">Scheduling Policies (Affinity/Anti-affinity)</a>.</li></ul>
|
||||
</li><li id="cce_10_0047__li136191442193318"><strong id="cce_10_0047__b540915914458">Node Affinity</strong>: Common load affinity policies are offered for quick load affinity deployment.<ul id="cce_10_0047__ul106562113415"><li id="cce_10_0047__li11588172453415"><strong id="cce_10_0047__b1354131044913">Node Affinity</strong>: Workload pods can be deployed on specified nodes through node affinity (<strong id="cce_10_0047__b17387313105016">nodeAffinity</strong>). If no node is specified, the pods will be randomly scheduled based on the default scheduling policy of the cluster.</li><li id="cce_10_0047__li12588142414347"><strong id="cce_10_0047__b1143642735217">Specified node pool scheduling</strong>: Workload pods can be deployed in a specified node pool through node affinity (<strong id="cce_10_0047__b1443715272523">nodeAffinity</strong>). If no node pool is specified, the pods will be randomly scheduled based on the default scheduling policy of the cluster.</li><li id="cce_10_0047__li14588192418347"><strong id="cce_10_0047__b145411819458">Custom policies</strong>: Affinity and anti-affinity policies can be customized as needed. For details, see <a href="cce_10_0232.html">Scheduling Policies (Affinity/Anti-affinity)</a>.</li></ul>
|
||||
<div class="p" id="cce_10_0047__p310913521612"><strong id="cce_10_0047__b204881212144816">(Optional) Advanced Settings</strong><ul id="cce_10_0047__ul142811417"><li id="cce_10_0047__li0421513417"><strong id="cce_10_0047__b15415314859">Upgrade</strong>: Specify the upgrade mode and parameters of the workload. <strong id="cce_10_0047__b153151558165913">Rolling upgrade</strong> and <strong id="cce_10_0047__b1621251402">Replace upgrade</strong> are available. For details, see <a href="cce_10_0397.html">Configuring Workload Upgrade Policies</a>.</li><li id="cce_10_0047__li5292111713411"><strong id="cce_10_0047__b289714923012">Scheduling</strong>: Configure affinity and anti-affinity policies for flexible workload scheduling. Load affinity and node affinity are provided.<ul id="cce_10_0047__ul16976133413332"><li id="cce_10_0047__li7687143311331"><strong id="cce_10_0047__b1243811103214">Load Affinity</strong>: Common load affinity policies are offered for quick load affinity deployment.<ul id="cce_10_0047__ul1865517492338"><li id="cce_10_0047__li7393234068"><strong id="cce_10_0047__b15439175514563">Not configured</strong>: No load affinity policy is configured.</li><li id="cce_10_0047__li84431255153310"><strong id="cce_10_0047__b1069211531709">Multi-AZ deployment preferred</strong>: Workload pods are <strong id="cce_10_0047__b126921353203">preferentially</strong> scheduled to nodes in different AZs through pod anti-affinity.</li><li id="cce_10_0047__li10775194183413"><strong id="cce_10_0047__b1667575214119">Forcible multi-AZ deployment</strong>: Workload pods are forcibly scheduled to nodes in different AZs through pod anti-affinity (<strong id="cce_10_0047__b10853186174217">podAntiAffinity</strong>). If there are fewer AZs than pods, the extra pods will fail to run.</li><li id="cce_10_0047__li177960111349"><strong id="cce_10_0047__b18931103644418">Custom policies</strong>: Affinity and anti-affinity policies can be customized. For details, see <a href="cce_10_0893.html">Configuring Workload Affinity or Anti-affinity Scheduling (podAffinity or podAntiAffinity)</a>.</li></ul>
|
||||
</li><li id="cce_10_0047__li136191442193318"><strong id="cce_10_0047__b540915914458">Node Affinity</strong>: Common load affinity policies are offered for quick load affinity deployment.<ul id="cce_10_0047__ul106562113415"><li id="cce_10_0047__li3815113910617"><strong id="cce_10_0047__b129361841585">Not configured</strong>: No node affinity policy is configured.</li><li id="cce_10_0047__li11588172453415"><strong id="cce_10_0047__b1354131044913">Node Affinity</strong>: Workload pods can be deployed on specified nodes through node affinity (<strong id="cce_10_0047__b17387313105016">nodeAffinity</strong>). If no node is specified, the pods will be randomly scheduled based on the default scheduling policy of the cluster.</li><li id="cce_10_0047__li12588142414347"><strong id="cce_10_0047__b1143642735217">Specified node pool scheduling</strong>: Workload pods can be deployed in a specified node pool through node affinity (<strong id="cce_10_0047__b1443715272523">nodeAffinity</strong>). If no node pool is specified, the pods will be randomly scheduled based on the default scheduling policy of the cluster.</li><li id="cce_10_0047__li14588192418347"><strong id="cce_10_0047__b145411819458">Custom policies</strong>: Affinity and anti-affinity policies can be customized. For details, see <a href="cce_10_0892.html">Configuring Node Affinity Scheduling (nodeAffinity)</a>.</li></ul>
|
||||
</li></ul>
|
||||
</li><li id="cce_10_0047__li13285132913414"><strong id="cce_10_0047__b15261142101217">Toleration</strong>: Using both taints and tolerations allows (not forcibly) the pod to be scheduled to a node with the matching taints, and controls the pod eviction policies after the node where the pod is located is tainted. For details, see <a href="cce_10_0728.html">Configuring Tolerance Policies</a>.</li><li id="cce_10_0047__li179714209414"><a name="cce_10_0047__li179714209414"></a><a name="li179714209414"></a><strong id="cce_10_0047__b562135212518">Labels and Annotations</strong>: Add labels or annotations for pods using key-value pairs. After entering the key and value, click <strong id="cce_10_0047__b1439805716617">Confirm</strong>. For details about how to use and configure labels and annotations, see <a href="cce_10_0386.html">Configuring Labels and Annotations</a>.</li><li id="cce_10_0047__li1917237124111"><strong id="cce_10_0047__b1428118321389">DNS</strong>: Configure a separate DNS policy for the workload. For details, see <a href="cce_10_0365.html">DNS Configuration</a>.</li><li id="cce_10_0047__li191696549535"><strong id="cce_10_0047__b563938103113">Network Configuration</strong><ul id="cce_10_0047__ul101792551538"><li id="cce_10_0047__li1985863319162">Pod ingress/egress bandwidth limitation: You can set ingress/egress bandwidth limitation for pods. For details, see <a href="cce_10_0382.html">Configuring QoS for a Pod</a>.</li><li id="cce_10_0047__li053620118549">IPv6 shared bandwidth: available only for clusters that support this function. After this function is enabled, you can configure a shared bandwidth for a pod with IPv6 dual-stack ENIs. For details, see <a href="cce_10_0604.html">Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack ENIs</a>.</li></ul>
|
||||
</li><li id="cce_10_0047__li13285132913414"><strong id="cce_10_0047__b15261142101217">Toleration</strong>: Using both taints and tolerations allows (not forcibly) the pod to be scheduled to a node with the matching taints, and controls the pod eviction policies after the node where the pod is located is tainted. For details, see <a href="cce_10_0728.html">Configuring Tolerance Policies</a>.</li><li id="cce_10_0047__li179714209414"><a name="cce_10_0047__li179714209414"></a><a name="li179714209414"></a><strong id="cce_10_0047__b562135212518">Labels and Annotations</strong>: Add labels or annotations for pods using key-value pairs. After entering the key and value, click <strong id="cce_10_0047__b1439805716617">Confirm</strong>. For details about how to use and configure labels and annotations, see <a href="cce_10_0386.html">Configuring Labels and Annotations</a>.</li><li id="cce_10_0047__li1917237124111"><strong id="cce_10_0047__b1428118321389">DNS</strong>: Configure a separate DNS policy for the workload. For details, see <a href="cce_10_0365.html">DNS Configuration</a>.</li><li id="cce_10_0047__li191696549535"><strong id="cce_10_0047__b563938103113">Network Configuration</strong><ul id="cce_10_0047__ul101792551538"><li id="cce_10_0047__li1985863319162">Pod ingress/egress bandwidth limitation: You can set ingress/egress bandwidth limitation for pods. For details, see <a href="cce_10_0382.html">Configuring QoS for a Pod</a>.</li><li id="cce_10_0047__li1898141443111">Whether to enable a specified container network configuration: available only for clusters that support this function. After you enable a specified container network configuration, the workload will be created using the container subnet and security group in the configuration. For details, see <a href="cce_10_0196.html">Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configuration</a>.</li><li id="cce_10_0047__li465673203314">Specify the container network configuration name: Only the custom container network configuration whose associated resource type is workload can be selected.</li><li id="cce_10_0047__li053620118549">IPv6 shared bandwidth: available only for clusters that support this function. After this function is enabled, you can configure a shared bandwidth for a pod with IPv6 dual-stack ENIs. For details, see <a href="cce_10_0604.html">Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack ENIs</a>.</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
</p></li><li id="cce_10_0047__li01417411620"><span>Click <strong id="cce_10_0047__b5824103317919">Create Workload</strong> in the lower right corner.</span></li></ol>
|
||||
@ -232,7 +232,7 @@ spec:
|
||||
<p id="cce_10_0047__p1046019326248">If the following information is displayed, the Deployment is running.</p>
|
||||
<pre class="screen" id="cce_10_0047__screen1353922112020">NAME READY UP-TO-DATE AVAILABLE AGE
|
||||
nginx 1/1 1 1 4m5s</pre>
|
||||
<p id="cce_10_0047__p194511348101611"><strong id="cce_10_0047__b1018145319612">Parameter description</strong></p>
|
||||
<p id="cce_10_0047__p194511348101611"><strong id="cce_10_0047__b1018145319612">Parameters</strong></p>
|
||||
<ul id="cce_10_0047__ul1964317513175"><li id="cce_10_0047__li1264312531719"><strong id="cce_10_0047__b11576432181319">NAME</strong>: Name of the application running in the pod.</li><li id="cce_10_0047__li864317513171"><strong id="cce_10_0047__b12611534101318">READY</strong>: indicates the number of available workloads. The value is displayed as "the number of available pods/the number of expected pods".</li><li id="cce_10_0047__li16643955172"><strong id="cce_10_0047__b185316367134">UP-TO-DATE</strong>: indicates the number of replicas that have been updated.</li><li id="cce_10_0047__li18643558176"><strong id="cce_10_0047__b483113811138">AVAILABLE</strong>: indicates the number of available pods.</li><li id="cce_10_0047__li964310512175"><strong id="cce_10_0047__b15727740161317">AGE</strong>: period the Deployment keeps running</li></ul>
|
||||
</p></li><li id="cce_10_0047__li128617541093"><span>If the Deployment will be accessed through a ClusterIP or NodePort Service, configure the access mode. For details, see <a href="cce_10_0020.html">Network</a>.</span></li></ol>
|
||||
</div>
|
||||
|
||||
@ -89,10 +89,10 @@
|
||||
<p id="cce_10_0048__p13343123113612">You can also create a Service after creating a workload. For details about Services of different types, see <a href="cce_10_0249.html">Overview</a>.</p>
|
||||
<div class="p" id="cce_10_0048__p310913521612"><strong id="cce_10_0048__b21631580735239">(Optional) Advanced Settings</strong><ul id="cce_10_0048__ul142811417"><li id="cce_10_0048__li0421513417"><strong id="cce_10_0048__cce_10_0047_b15415314859">Upgrade</strong>: Specify the upgrade mode and parameters of the workload. <strong id="cce_10_0048__cce_10_0047_b153151558165913">Rolling upgrade</strong> and <strong id="cce_10_0048__cce_10_0047_b1621251402">Replace upgrade</strong> are available. For details, see <a href="cce_10_0397.html">Configuring Workload Upgrade Policies</a>.</li><li id="cce_10_0048__li206428507436"><strong id="cce_10_0048__b1840219331836">Pod Management Policies</strong><p id="cce_10_0048__p151323251334">For some distributed systems, the StatefulSet sequence is unnecessary and/or should not occur. These systems require only uniqueness and identifiers.</p>
|
||||
<ul id="cce_10_0048__ul758812493316"><li id="cce_10_0048__li258832417338"><strong id="cce_10_0048__b13534251116">OrderedReady</strong>: The StatefulSet will deploy, delete, or scale pods in order and one by one. (The StatefulSet continues only after the previous pod is ready or deleted.) This is the default policy.</li><li id="cce_10_0048__li1558862416338"><strong id="cce_10_0048__b112293521039">Parallel</strong>: The StatefulSet will create pods in parallel to match the desired scale without waiting, and will delete all pods at once.</li></ul>
|
||||
</li><li id="cce_10_0048__li7127180594"><strong id="cce_10_0048__cce_10_0047_b289714923012">Scheduling</strong>: Configure affinity and anti-affinity policies for flexible workload scheduling. Load affinity and node affinity are provided.<ul id="cce_10_0048__cce_10_0047_ul16976133413332"><li id="cce_10_0048__cce_10_0047_li7687143311331"><strong id="cce_10_0048__cce_10_0047_b1243811103214">Load Affinity</strong>: Common load affinity policies are offered for quick load affinity deployment.<ul id="cce_10_0048__cce_10_0047_ul1865517492338"><li id="cce_10_0048__cce_10_0047_li84431255153310"><strong id="cce_10_0048__cce_10_0047_b21119711352">Multi-AZ deployment is preferred</strong>: Workload pods are preferentially scheduled to nodes in different AZs through pod anti-affinity (<strong id="cce_10_0048__cce_10_0047_b156511824123612">podAntiAffinity</strong>). If all the nodes in the cluster are deployed in the same AZ, the pods will be scheduled to that AZ but onto different nodes for high availability. If there are fewer nodes than pods, the extra pods will fail to run.</li><li id="cce_10_0048__cce_10_0047_li10775194183413"><strong id="cce_10_0048__cce_10_0047_b1667575214119">Forcible multi-AZ deployment</strong>: Workload pods are forcibly scheduled to nodes in different AZs through pod anti-affinity (<strong id="cce_10_0048__cce_10_0047_b10853186174217">podAntiAffinity</strong>). If there are fewer AZs than pods, the extra pods will fail to run.</li><li id="cce_10_0048__cce_10_0047_li177960111349"><strong id="cce_10_0048__cce_10_0047_b18931103644418">Custom policies</strong>: Affinity and anti-affinity policies can be customized as needed. For details, see <a href="cce_10_0232.html">Scheduling Policies (Affinity/Anti-affinity)</a>.</li></ul>
|
||||
</li><li id="cce_10_0048__cce_10_0047_li136191442193318"><strong id="cce_10_0048__cce_10_0047_b540915914458">Node Affinity</strong>: Common load affinity policies are offered for quick load affinity deployment.<ul id="cce_10_0048__cce_10_0047_ul106562113415"><li id="cce_10_0048__cce_10_0047_li11588172453415"><strong id="cce_10_0048__cce_10_0047_b1354131044913">Node Affinity</strong>: Workload pods can be deployed on specified nodes through node affinity (<strong id="cce_10_0048__cce_10_0047_b17387313105016">nodeAffinity</strong>). If no node is specified, the pods will be randomly scheduled based on the default scheduling policy of the cluster.</li><li id="cce_10_0048__cce_10_0047_li12588142414347"><strong id="cce_10_0048__cce_10_0047_b1143642735217">Specified node pool scheduling</strong>: Workload pods can be deployed in a specified node pool through node affinity (<strong id="cce_10_0048__cce_10_0047_b1443715272523">nodeAffinity</strong>). If no node pool is specified, the pods will be randomly scheduled based on the default scheduling policy of the cluster.</li><li id="cce_10_0048__cce_10_0047_li14588192418347"><strong id="cce_10_0048__cce_10_0047_b145411819458">Custom policies</strong>: Affinity and anti-affinity policies can be customized as needed. For details, see <a href="cce_10_0232.html">Scheduling Policies (Affinity/Anti-affinity)</a>.</li></ul>
|
||||
</li><li id="cce_10_0048__li7127180594"><strong id="cce_10_0048__cce_10_0047_b289714923012">Scheduling</strong>: Configure affinity and anti-affinity policies for flexible workload scheduling. Load affinity and node affinity are provided.<ul id="cce_10_0048__cce_10_0047_ul16976133413332"><li id="cce_10_0048__cce_10_0047_li7687143311331"><strong id="cce_10_0048__cce_10_0047_b1243811103214">Load Affinity</strong>: Common load affinity policies are offered for quick load affinity deployment.<ul id="cce_10_0048__cce_10_0047_ul1865517492338"><li id="cce_10_0048__cce_10_0047_li7393234068"><strong id="cce_10_0048__cce_10_0047_b15439175514563">Not configured</strong>: No load affinity policy is configured.</li><li id="cce_10_0048__cce_10_0047_li84431255153310"><strong id="cce_10_0048__cce_10_0047_b1069211531709">Multi-AZ deployment preferred</strong>: Workload pods are <strong id="cce_10_0048__cce_10_0047_b126921353203">preferentially</strong> scheduled to nodes in different AZs through pod anti-affinity.</li><li id="cce_10_0048__cce_10_0047_li10775194183413"><strong id="cce_10_0048__cce_10_0047_b1667575214119">Forcible multi-AZ deployment</strong>: Workload pods are forcibly scheduled to nodes in different AZs through pod anti-affinity (<strong id="cce_10_0048__cce_10_0047_b10853186174217">podAntiAffinity</strong>). If there are fewer AZs than pods, the extra pods will fail to run.</li><li id="cce_10_0048__cce_10_0047_li177960111349"><strong id="cce_10_0048__cce_10_0047_b18931103644418">Custom policies</strong>: Affinity and anti-affinity policies can be customized. For details, see <a href="cce_10_0893.html">Configuring Workload Affinity or Anti-affinity Scheduling (podAffinity or podAntiAffinity)</a>.</li></ul>
|
||||
</li><li id="cce_10_0048__cce_10_0047_li136191442193318"><strong id="cce_10_0048__cce_10_0047_b540915914458">Node Affinity</strong>: Common load affinity policies are offered for quick load affinity deployment.<ul id="cce_10_0048__cce_10_0047_ul106562113415"><li id="cce_10_0048__cce_10_0047_li3815113910617"><strong id="cce_10_0048__cce_10_0047_b129361841585">Not configured</strong>: No node affinity policy is configured.</li><li id="cce_10_0048__cce_10_0047_li11588172453415"><strong id="cce_10_0048__cce_10_0047_b1354131044913">Node Affinity</strong>: Workload pods can be deployed on specified nodes through node affinity (<strong id="cce_10_0048__cce_10_0047_b17387313105016">nodeAffinity</strong>). If no node is specified, the pods will be randomly scheduled based on the default scheduling policy of the cluster.</li><li id="cce_10_0048__cce_10_0047_li12588142414347"><strong id="cce_10_0048__cce_10_0047_b1143642735217">Specified node pool scheduling</strong>: Workload pods can be deployed in a specified node pool through node affinity (<strong id="cce_10_0048__cce_10_0047_b1443715272523">nodeAffinity</strong>). If no node pool is specified, the pods will be randomly scheduled based on the default scheduling policy of the cluster.</li><li id="cce_10_0048__cce_10_0047_li14588192418347"><strong id="cce_10_0048__cce_10_0047_b145411819458">Custom policies</strong>: Affinity and anti-affinity policies can be customized. For details, see <a href="cce_10_0892.html">Configuring Node Affinity Scheduling (nodeAffinity)</a>.</li></ul>
|
||||
</li></ul>
|
||||
</li><li id="cce_10_0048__li13285132913414"><strong id="cce_10_0048__cce_10_0047_b15261142101217">Toleration</strong>: Using both taints and tolerations allows (not forcibly) the pod to be scheduled to a node with the matching taints, and controls the pod eviction policies after the node where the pod is located is tainted. For details, see <a href="cce_10_0728.html">Configuring Tolerance Policies</a>.</li><li id="cce_10_0048__li179714209414"><strong id="cce_10_0048__cce_10_0047_b562135212518">Labels and Annotations</strong>: Add labels or annotations for pods using key-value pairs. After entering the key and value, click <strong id="cce_10_0048__cce_10_0047_b1439805716617">Confirm</strong>. For details about how to use and configure labels and annotations, see <a href="cce_10_0386.html">Configuring Labels and Annotations</a>.</li><li id="cce_10_0048__li1917237124111"><strong id="cce_10_0048__cce_10_0047_b1428118321389">DNS</strong>: Configure a separate DNS policy for the workload. For details, see <a href="cce_10_0365.html">DNS Configuration</a>.</li><li id="cce_10_0048__li1985863319162"><strong id="cce_10_0048__b157014128328">Network Configuration</strong><ul id="cce_10_0048__ul9870163414162"><li id="cce_10_0048__li8488616152">Pod ingress/egress bandwidth limitation: You can set ingress/egress bandwidth limitation for pods. For details, see <a href="cce_10_0382.html">Configuring QoS for a Pod</a>.</li><li id="cce_10_0048__li246062816567">Whether to enable the static IP address: available only for clusters that support this function. After this function is enabled, you can set the interval for reclaiming expired pod IP addresses. For details, see <a href="cce_10_0603.html">Configuring a Static IP Address for a Pod</a>.</li><li id="cce_10_0048__li6361894173">IPv6 shared bandwidth: available only for clusters that support this function. After this function is enabled, you can configure a shared bandwidth for a pod with IPv6 dual-stack ENIs. For details, see <a href="cce_10_0604.html">Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack ENIs</a>.</li></ul>
|
||||
</li><li id="cce_10_0048__li13285132913414"><strong id="cce_10_0048__cce_10_0047_b15261142101217">Toleration</strong>: Using both taints and tolerations allows (not forcibly) the pod to be scheduled to a node with the matching taints, and controls the pod eviction policies after the node where the pod is located is tainted. For details, see <a href="cce_10_0728.html">Configuring Tolerance Policies</a>.</li><li id="cce_10_0048__li179714209414"><strong id="cce_10_0048__cce_10_0047_b562135212518">Labels and Annotations</strong>: Add labels or annotations for pods using key-value pairs. After entering the key and value, click <strong id="cce_10_0048__cce_10_0047_b1439805716617">Confirm</strong>. For details about how to use and configure labels and annotations, see <a href="cce_10_0386.html">Configuring Labels and Annotations</a>.</li><li id="cce_10_0048__li1917237124111"><strong id="cce_10_0048__cce_10_0047_b1428118321389">DNS</strong>: Configure a separate DNS policy for the workload. For details, see <a href="cce_10_0365.html">DNS Configuration</a>.</li><li id="cce_10_0048__li1985863319162"><strong id="cce_10_0048__b157014128328">Network Configuration</strong><ul id="cce_10_0048__ul9870163414162"><li id="cce_10_0048__li8488616152">Pod ingress/egress bandwidth limitation: You can set ingress/egress bandwidth limitation for pods. For details, see <a href="cce_10_0382.html">Configuring QoS for a Pod</a>.</li><li id="cce_10_0048__li246062816567">Whether to enable the static IP address: available only for clusters that support this function. After this function is enabled, you can set the interval for reclaiming expired pod IP addresses. For details, see <a href="cce_10_0603.html">Configuring a Static IP Address for a Pod</a>.</li><li id="cce_10_0048__li1898141443111">Whether to enable a specified container network configuration: available only for clusters that support this function. After you enable a specified container network configuration, the workload will be created using the container subnet and security group in the configuration. For details, see <a href="cce_10_0196.html">Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configuration</a>.</li><li id="cce_10_0048__li465673203314">Specify the container network configuration name: Only the custom container network configuration whose associated resource type is workload can be selected.</li><li id="cce_10_0048__li6361894173">IPv6 shared bandwidth: available only for clusters that support this function. After this function is enabled, you can configure a shared bandwidth for a pod with IPv6 dual-stack ENIs. For details, see <a href="cce_10_0604.html">Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack ENIs</a>.</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
</p></li><li id="cce_10_0048__li01417411620"><span>Click <strong id="cce_10_0048__b2573105264313">Create Workload</strong> in the lower right corner.</span></li></ol>
|
||||
|
||||
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,6 +4,8 @@
|
||||
<div id="body8662426"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_bulletin_0095.html">Kubernetes 1.30 Release Notes</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_bulletin_0089.html">Kubernetes 1.29 Release Notes</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_bulletin_0068.html">Kubernetes 1.28 Release Notes</a></strong><br>
|
||||
|
||||
@ -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">Application Scenarios</h4><p id="cce_10_0081__p1945803011253">When a large-scale cluster is required, you are advised to use node pools to manage nodes.</p>
|
||||
<div class="section" id="cce_10_0081__section32131316256"><h4 class="sectiontitle">Applicable Scenarios</h4><p id="cce_10_0081__p1945803011253">When a large-scale cluster is required, you are advised to use node pools to manage nodes.</p>
|
||||
<p id="cce_10_0081__p1491578182512">The following table describes multiple scenarios of large-scale cluster management and the functions of node pools in each scenario.</p>
|
||||
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0081__table1736317479258" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Using node pools for different management scenarios</caption><thead align="left"><tr id="cce_10_0081__row336414719256"><th align="left" class="cellrowborder" valign="top" width="39.32%" id="mcps1.3.4.4.2.3.1.1"><p id="cce_10_0081__p5364134792518">Scenario</p>
|
||||
@ -119,12 +119,12 @@
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0081__section12603142443319"><h4 class="sectiontitle"><span class="keyword" id="cce_10_0081__keyword134411635193118">Deploying a Workload in a Specified Node Pool</span></h4><p id="cce_10_0081__p153911712353">When creating a workload, you can constrain pods to run in a specified node pool.</p>
|
||||
<p id="cce_10_0081__p554031713358">For example, on the CCE console, you can set the affinity between the workload and the node on the <strong id="cce_10_0081__b65991804713">Scheduling Policies</strong> tab page on the workload details page to forcibly deploy the workload to a specific node pool. In this way, the workload runs only on nodes in the node pool. To better control where the workload is to be scheduled, you can use affinity or anti-affinity policies between workloads and nodes described in <a href="cce_10_0232.html">Scheduling Policies (Affinity/Anti-affinity)</a>.</p>
|
||||
<p id="cce_10_0081__p554031713358">For example, on the CCE console, you can set the affinity between the workload and the node on the <strong id="cce_10_0081__b65991804713">Scheduling Policies</strong> tab page on the workload details page to forcibly deploy the workload to a specific node pool. In this way, the workload runs only on nodes in the node pool. To better control where the workload is to be scheduled, you can use affinity or anti-affinity policies between workloads and nodes described in <a href="cce_10_0892.html">Configuring Node Affinity Scheduling (nodeAffinity)</a>.</p>
|
||||
<p id="cce_10_0081__p614655184910">For example, you can use container's resource request as a nodeSelector so that workloads will run only on the nodes that meet the resource request.</p>
|
||||
<p id="cce_10_0081__p1854041717353">If the workload definition file defines a container that requires four CPUs, the scheduler will not choose the nodes with two CPUs to run workloads.</p>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0081__section17716744163316"><h4 class="sectiontitle">Related Operations</h4><p id="cce_10_0081__p12284195854916">You can log in to the CCE console and refer to the following sections to perform operations on node pools:</p>
|
||||
<ul id="cce_10_0081__ul713912219920"><li id="cce_10_0081__li168801331326"><a href="cce_10_0012.html">Creating a Node Pool</a></li><li id="cce_10_0081__li1688010311326"><a href="cce_10_0222.html">Managing a Node Pool</a></li><li id="cce_10_0081__li1720114577918"><a href="cce_10_0047.html">Creating a Deployment</a></li><li id="cce_10_0081__li1849316127104"><a href="cce_10_0232.html">Scheduling Policies (Affinity/Anti-affinity)</a></li></ul>
|
||||
<ul id="cce_10_0081__ul713912219920"><li id="cce_10_0081__li168801331326"><a href="cce_10_0012.html">Creating a Node Pool</a></li><li id="cce_10_0081__li1688010311326"><a href="cce_10_0222.html">Managing a Node Pool</a></li><li id="cce_10_0081__li1720114577918"><a href="cce_10_0047.html">Creating a Deployment</a></li><li id="cce_10_0081__li1849316127104"><a href="cce_10_0892.html">Configuring Node Affinity Scheduling (nodeAffinity)</a></li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
@ -3,8 +3,8 @@
|
||||
<h1 class="topictitle1">Managing Workload Scaling Policies</h1>
|
||||
<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, 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__b1393251134318"><span id="cce_10_0083__text67571453104013">Policies</span></strong>. On the displayed page, click the <strong id="cce_10_0083__b13971202411450">HPA</strong>/<strong id="cce_10_0083__b104027277451">CronHPA</strong> <strong id="cce_10_0083__b8283194012455">Policies</strong> tab page based on the scaling policy type.</span></li><li id="cce_10_0083__li641003813527"><span>Check the 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>
|
||||
<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>
|
||||
</div></div>
|
||||
</p></li><li id="cce_10_0083__li11795124518345"><span>Manage scaling policies.</span><p>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<a name="cce_10_0084"></a><a name="cce_10_0084"></a>
|
||||
|
||||
<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 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, choose <span class="uicontrol" id="cce_10_0084__uicontrol16903135110235"><b>Service List</b></span> > <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>, and 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> in the navigation pane.</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>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -5,7 +5,7 @@
|
||||
<p id="cce_10_0105__p152208151978">CCE provides the following lifecycle callback functions:</p>
|
||||
<ul id="cce_10_0105__ul922021513717"><li id="cce_10_0105__li16220815773"><strong id="cce_10_0105__b8812154352715"><span class="keyword" id="cce_10_0105__keyword209119171317258">Startup Command</span></strong>: executed to start a container. For details, see <a href="#cce_10_0105__section54912655316">Startup Commands</a>.</li><li id="cce_10_0105__li14220201518713"><strong id="cce_10_0105__b150302499794538"><span class="keyword" id="cce_10_0105__keyword29571762817312">Post-Start</span></strong>: executed immediately after a container is started. For details, see <a href="#cce_10_0105__section15243544163715">Post-Start Processing</a>.</li><li id="cce_10_0105__li32206153712"><strong id="cce_10_0105__b162512053994533"><span class="keyword" id="cce_10_0105__keyword26075130317328">Pre-Stop</span></strong>: executed before a container is stopped. The pre-stop processing function helps you ensure that the services running on the pods can be completed in advance in the case of pod upgrade or deletion. For details, see <a href="#cce_10_0105__section2334114473712">Pre-Stop Processing</a>.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0105__section54912655316"><a name="cce_10_0105__section54912655316"></a><a name="section54912655316"></a><h4 class="sectiontitle">Startup Commands</h4><p id="cce_10_0105__p198271342105918">By default, the default command during image start. To run a specific command or rewrite the default image value, you must perform specific settings:</p>
|
||||
<div class="section" id="cce_10_0105__section54912655316"><a name="cce_10_0105__section54912655316"></a><a name="section54912655316"></a><h4 class="sectiontitle">Startup Commands</h4><p id="cce_10_0105__p198271342105918">By default, the default command is executed during image start. To run a specific command or rewrite the default image setting, you must perform specific operations.</p>
|
||||
<p id="cce_10_0105__p1639559153012">A Docker image has metadata that stores image information. If lifecycle commands and arguments are not set, CCE runs the default commands and arguments, that is, Docker instructions <strong id="cce_10_0105__b18834121511325">ENTRYPOINT</strong> and <strong id="cce_10_0105__b4834215103216">CMD</strong>, provided during image creation. </p>
|
||||
<p id="cce_10_0105__p20395798303">If the commands and arguments used to run a container are set during application creation, the default commands <strong id="cce_10_0105__b125702255322">ENTRYPOINT</strong> and <strong id="cce_10_0105__b105781025143210">CMD</strong> are overwritten during image build. The rules are as follows:</p>
|
||||
|
||||
@ -132,13 +132,13 @@
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0105__row04201302279"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.2.2.1.2.3.1.1 "><p id="cce_10_0105__p6420110192718">CLI</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.2.2.1.2.3.1.2 "><p id="cce_10_0105__p94204010271">Set commands to be executed in the container for pre-stop processing. The command format is <strong id="cce_10_0105__b2000314378">Command Args[1] Args[2]...</strong>. <strong id="cce_10_0105__b2097726279">Command</strong> is a system command or a user-defined executable program. If no path is specified, an executable program in the default path will be selected. If multiple commands need to be executed, write the commands into a script for execution.</p>
|
||||
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.4.2.2.2.1.2.3.1.2 "><p id="cce_10_0105__p94204010271">Set commands to be executed in the container for pre-stop processing. The command format is <strong id="cce_10_0105__b795696493">Command Args[1] Args[2]...</strong>. <strong id="cce_10_0105__b85336488">Command</strong> is a system command or a user-defined executable program. If no path is specified, an executable program in the default path will be selected. If multiple commands need to be executed, write the commands into a script for execution.</p>
|
||||
<p id="cce_10_0105__p94203082712">Example command:</p>
|
||||
<pre class="screen" id="cce_10_0105__screen6420190132712">exec:
|
||||
command:
|
||||
- /uninstall.sh
|
||||
- uninstall_agent</pre>
|
||||
<p id="cce_10_0105__p742120182716">Enter <strong id="cce_10_0105__b103722545816">/uninstall uninstall_agent</strong> in the script. This command indicates that the <strong id="cce_10_0105__b19674026155910">uninstall.sh</strong> script will be executed before the container completes its execution and stops running.</p>
|
||||
<p id="cce_10_0105__p742120182716">Enter <strong id="cce_10_0105__b103722545816">/uninstall uninstall_agent</strong> in the script. This command indicates that <strong id="cce_10_0105__b19674026155910">uninstall.sh</strong> will be executed before the container completes its execution and stops running.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0105__row4421190152715"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.4.2.2.2.1.2.3.1.1 "><p id="cce_10_0105__p154216032719">HTTP request</p>
|
||||
|
||||
@ -36,7 +36,7 @@ mv -f <i><span class="varname" id="cce_10_0107__varname937302110334">kubeconfig.
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0107__section1559919152711"><a name="cce_10_0107__section1559919152711"></a><a name="section1559919152711"></a><h4 class="sectiontitle"><span class="keyword" id="cce_10_0107__keyword311020376452">Two-Way Authentication for Domain Names</span></h4><p id="cce_10_0107__p138948491274">CCE supports two-way authentication for domain names.</p>
|
||||
<ul id="cce_10_0107__ul88981331482"><li id="cce_10_0107__li1705116151915">After an EIP is bound to an API Server, two-way domain name authentication is disabled by default if kubectl is used to access the cluster. You can run <strong id="cce_10_0107__b198732542582">kubectl config use-context externalTLSVerify</strong> to enable the two-way domain name authentication.</li><li id="cce_10_0107__li1807459174818">When an EIP is bound to or unbound from a cluster, or a custom domain name is configured or updated, the cluster server certificate will be added the latest cluster access address (including the EIP bound to the cluster and all custom domain names configured for the cluster).</li><li id="cce_10_0107__li17898153310483">Asynchronous cluster synchronization takes about 5 to 10 minutes. You can view the synchronization result in <strong id="cce_10_0107__b196404619200">Synchronize Certificate</strong> in <strong id="cce_10_0107__b364620682012">Operation Records</strong>.</li><li id="cce_10_0107__li614337712">For a cluster that has been bound to an EIP, if the authentication fails (x509: certificate is valid) when two-way authentication is used, bind the EIP again and download <strong id="cce_10_0107__b121611451417">kubeconfig.yaml</strong> again.</li><li id="cce_10_0107__li5950658165414">If the two-way domain name authentication is not supported, <strong id="cce_10_0107__b56091346184712">kubeconfig.yaml</strong> contains the <strong id="cce_10_0107__b1961534614476">"insecure-skip-tls-verify": true</strong> field, as shown in <a href="#cce_10_0107__fig1941342411">Figure 1</a>. To use two-way authentication, download the <strong id="cce_10_0107__b549311585216">kubeconfig.yaml</strong> file again and enable two-way authentication for the domain names.<div class="fignone" id="cce_10_0107__fig1941342411"><a name="cce_10_0107__fig1941342411"></a><a name="fig1941342411"></a><span class="figcap"><b>Figure 1 </b>Two-way authentication disabled for domain names</span><br><span><img id="cce_10_0107__image3414621613" src="en-us_image_0000001981436769.png"></span></div>
|
||||
<ul id="cce_10_0107__ul88981331482"><li id="cce_10_0107__li1705116151915">After an EIP is bound to an API Server, two-way domain name authentication is disabled by default if kubectl is used to access the cluster. You can run <strong id="cce_10_0107__b198732542582">kubectl config use-context externalTLSVerify</strong> to enable the two-way domain name authentication.</li><li id="cce_10_0107__li1807459174818">When an EIP is bound to or unbound from a cluster, or a custom domain name is configured or updated, the cluster server certificate will be added the latest cluster access address (including the EIP bound to the cluster and all custom domain names configured for the cluster).</li><li id="cce_10_0107__li17898153310483">Asynchronous cluster synchronization takes about 5 to 10 minutes. You can view the synchronization result in <strong id="cce_10_0107__b196404619200">Synchronize Certificate</strong> in <strong id="cce_10_0107__b364620682012">Operation Records</strong>.</li><li id="cce_10_0107__li614337712">For a cluster that has been bound to an EIP, if the authentication fails (x509: certificate is valid) when two-way authentication is used, bind the EIP again and download <strong id="cce_10_0107__b121611451417">kubeconfig.yaml</strong> again.</li><li id="cce_10_0107__li5950658165414">If the two-way domain name authentication is not supported, <strong id="cce_10_0107__b56091346184712">kubeconfig.yaml</strong> contains the <strong id="cce_10_0107__b1961534614476">"insecure-skip-tls-verify": true</strong> field, as shown in <a href="#cce_10_0107__fig1941342411">Figure 1</a>. To use two-way authentication, download the <strong id="cce_10_0107__b549311585216">kubeconfig.yaml</strong> file again and enable two-way authentication for the domain names.<div class="fignone" id="cce_10_0107__fig1941342411"><a name="cce_10_0107__fig1941342411"></a><a name="fig1941342411"></a><span class="figcap"><b>Figure 1 </b>Two-way authentication disabled for domain names</span><br><span><img id="cce_10_0107__image3414621613" src="en-us_image_0000002101597765.png"></span></div>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0107__section1628510591883"><h4 class="sectiontitle">FAQs</h4><ul id="cce_10_0107__ul1374831051115"><li id="cce_10_0107__li4748810121112"><strong id="cce_10_0107__b456677171119"><span class="keyword" id="cce_10_0107__keyword0702458114510">Error from server Forbidden</span></strong><p id="cce_10_0107__p75241832114916">When you use kubectl to create or query Kubernetes resources, the following output is returned:</p>
|
||||
|
||||
@ -1,8 +1,7 @@
|
||||
<a name="cce_10_0111"></a><a name="cce_10_0111"></a>
|
||||
|
||||
<h1 class="topictitle1">Scalable File Service</h1>
|
||||
<div id="body0000001487121868"><p id="cce_10_0111__p8060118"></p>
|
||||
</div>
|
||||
<div id="body0000001487121868"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0617.html">Overview</a></strong><br>
|
||||
|
||||
@ -94,7 +94,7 @@ spec:
|
||||
periodSeconds: 5
|
||||
startupProbe: # Startup probe
|
||||
httpGet: # Checking an HTTP request is used as an example.
|
||||
path: /healthz # The HTTP check path is <strong id="cce_10_0112__b975836857">/healthz</strong>.
|
||||
path: /healthz # The HTTP check path is <strong id="cce_10_0112__b1188531819">/healthz</strong>.
|
||||
port: 80 # The check port number is <strong id="cce_10_0112__b561594217264">80</strong>.
|
||||
failureThreshold: 30
|
||||
periodSeconds: 10</pre>
|
||||
|
||||
@ -7,9 +7,10 @@
|
||||
<p id="cce_10_0113__p26271321192016">Configurations must be imported to a container as arguments. Otherwise, configurations will be lost after the container restarts.</p>
|
||||
</div></div>
|
||||
<p id="cce_10_0113__p78261119155911">Environment variables can be set in the following modes:</p>
|
||||
<ul id="cce_10_0113__ul1669104610598"><li id="cce_10_0113__li266913468594"><strong id="cce_10_0113__b4564141914250">Custom</strong>: Enter the environment variable name and parameter value.</li><li id="cce_10_0113__li13148164912599"><strong id="cce_10_0113__b31161818143614">Added from ConfigMap key</strong>: Import all keys in a ConfigMap as environment variables.</li><li id="cce_10_0113__li1855315291026"><strong id="cce_10_0113__b5398577535">Added from ConfigMap</strong>: Import a key in a ConfigMap as the value of an environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import <strong id="cce_10_0113__b67861335193619">configmap_value</strong> of <strong id="cce_10_0113__b478643513618">configmap_key</strong> in <strong id="cce_10_0113__b14610123945714">configmap-example</strong> as the value of environment variable <strong id="cce_10_0113__b7786133573616">key1</strong>, an environment variable named <strong id="cce_10_0113__b678683518364">key1</strong> whose value is <strong id="cce_10_0113__b1378615359362">configmap_value</strong> is available in the container.</li><li id="cce_10_0113__li1727795616592"><strong id="cce_10_0113__b675162614437">Added from secret</strong>: Import all keys in a secret as environment variables.</li><li id="cce_10_0113__li93353201773"><strong id="cce_10_0113__b0483141614480">Added from secret key</strong>: Import the value of a key in a secret as the value of an environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import <strong id="cce_10_0113__b12974122713812">secret_value</strong> of <strong id="cce_10_0113__b197472716385">secret_key</strong> in <strong id="cce_10_0113__b722441953910">secret-example</strong> as the value of environment variable <strong id="cce_10_0113__b8975627173810">key2</strong>, an environment variable named <strong id="cce_10_0113__b29756275384">key2</strong> whose value is <strong id="cce_10_0113__b097552703811">secret_value</strong> is available in the container.</li><li id="cce_10_0113__li1749760535"><strong id="cce_10_0113__b19931701407">Variable value/reference</strong>: Use the field defined by a pod as the value of the environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if the pod name is imported as the value of environment variable <strong id="cce_10_0113__b1939710417283">key3</strong>, an environment variable named <strong id="cce_10_0113__b11252186142914">key3</strong> whose value is the pod name is available in the container.</li><li id="cce_10_0113__li16129071317"><strong id="cce_10_0113__b1625513417292">Resource Reference</strong>: The value of <strong id="cce_10_0113__b176281198307">Request</strong> or <strong id="cce_10_0113__b186221022193017">Limit</strong> defined by the container is used as the value of the environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import the CPU limit of container-1 as the value of environment variable <strong id="cce_10_0113__b272674753017">key4</strong>, an environment variable named <strong id="cce_10_0113__b99015318423">key4</strong> whose value is the CPU limit of container-1 is available in the container.</li></ul>
|
||||
<ul id="cce_10_0113__ul1669104610598"><li id="cce_10_0113__li266913468594"><strong id="cce_10_0113__b4564141914250">Custom</strong>: Enter the environment variable name and parameter value.</li><li id="cce_10_0113__li13148164912599"><strong id="cce_10_0113__b31161818143614">Added from ConfigMap</strong>: Import all key values in a ConfigMap as environment variables.</li><li id="cce_10_0113__li1855315291026"><strong id="cce_10_0113__b5398577535">Added from ConfigMap key</strong>: Import the value of a key in a ConfigMap as the value of an environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import <strong id="cce_10_0113__b67861335193619">configmap_value</strong> of <strong id="cce_10_0113__b478643513618">configmap_key</strong> in <strong id="cce_10_0113__b14610123945714">configmap-example</strong> as the value of environment variable <strong id="cce_10_0113__b7786133573616">key1</strong>, an environment variable named <strong id="cce_10_0113__b678683518364">key1</strong> whose value is <strong id="cce_10_0113__b1378615359362">configmap_value</strong> is available in the container.</li><li id="cce_10_0113__li1727795616592"><strong id="cce_10_0113__b675162614437">Added from secret</strong>: Import all key values in a secret as environment variables.</li><li id="cce_10_0113__li93353201773"><strong id="cce_10_0113__b0483141614480">Added from secret key</strong>: Import the value of a key in a secret as the value of an environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import <strong id="cce_10_0113__b12974122713812">secret_value</strong> of <strong id="cce_10_0113__b197472716385">secret_key</strong> in <strong id="cce_10_0113__b722441953910">secret-example</strong> as the value of environment variable <strong id="cce_10_0113__b8975627173810">key2</strong>, an environment variable named <strong id="cce_10_0113__b29756275384">key2</strong> whose value is <strong id="cce_10_0113__b097552703811">secret_value</strong> is available in the container.</li><li id="cce_10_0113__li1749760535"><strong id="cce_10_0113__b19931701407">Variable Value/Reference</strong>: Use the field defined by a pod as the value of the environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if the pod name is imported as the value of environment variable <strong id="cce_10_0113__b1939710417283">key3</strong>, an environment variable named <strong id="cce_10_0113__b11252186142914">key3</strong> whose value is the pod name is available in the container.</li><li id="cce_10_0113__li16129071317"><strong id="cce_10_0113__b1625513417292">Resource Reference</strong>: The value of <strong id="cce_10_0113__b176281198307">Request</strong> or <strong id="cce_10_0113__b186221022193017">Limit</strong> defined by the container is used as the value of the environment variable. As shown in <a href="#cce_10_0113__fig164568529317">Figure 1</a>, if you import the CPU limit of container-1 as the value of environment variable <strong id="cce_10_0113__b272674753017">key4</strong>, an environment variable named <strong id="cce_10_0113__b99015318423">key4</strong> whose value is the CPU limit of container-1 is available in the container.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0113__section13829152011595"><h4 class="sectiontitle">Adding Environment Variables</h4><ol id="cce_10_0113__ol4904646935"><li id="cce_10_0113__li330462393220"><span>Log in to the CCE console.</span></li><li id="cce_10_0113__li2075471341"><span>Click the cluster name to go to the cluster console, choose <strong id="cce_10_0113__b1794501219430">Workloads</strong> in the navigation pane, and click the <strong id="cce_10_0113__b11945131216432">Create Workload</strong> in the upper right corner.</span></li><li id="cce_10_0113__li190412461831"><span>When creating a workload, modify the container information in <strong id="cce_10_0113__b101361766447">Container Settings</strong> and click the <strong id="cce_10_0113__b8169124424315">Environment Variables</strong> tab.</span></li><li id="cce_10_0113__li468251942720"><span>Configure environment variables.</span><p><div class="fignone" id="cce_10_0113__fig164568529317"><a name="cce_10_0113__fig164568529317"></a><a name="fig164568529317"></a><span class="figcap"><b>Figure 1 </b>Configuring environment variables</span><br><span><img id="cce_10_0113__image131385146481" src="en-us_image_0000001950317180.png"></span></div>
|
||||
<div class="section" id="cce_10_0113__section13829152011595"><h4 class="sectiontitle">Adding Environment Variables</h4><ol id="cce_10_0113__ol4904646935"><li id="cce_10_0113__li330462393220"><span>Log in to the CCE console.</span></li><li id="cce_10_0113__li2075471341"><span>Click the cluster name to go to the cluster console, choose <strong id="cce_10_0113__b1794501219430">Workloads</strong> in the navigation pane, and click the <strong id="cce_10_0113__b11945131216432">Create Workload</strong> in the upper right corner.</span></li><li id="cce_10_0113__li190412461831"><span>When creating a workload, modify the container information in <strong id="cce_10_0113__b101361766447">Container Settings</strong> and click the <strong id="cce_10_0113__b8169124424315">Environment Variables</strong> tab.</span></li><li id="cce_10_0113__li468251942720"><span>Configure environment variables.</span><p><ul id="cce_10_0113__ul825183111398"><li id="cce_10_0113__li8251203123915">To add environment variables one by one, click <span class="uicontrol" id="cce_10_0113__uicontrol1280917944713"><b>Adding a Variable</b></span> and configure its parameters.</li><li id="cce_10_0113__li12438193416413">To add environment variables in batches, click <span class="uicontrol" id="cce_10_0113__uicontrol185881419472"><b>Editing Custom Variables in Batches</b></span>. Then, in the displayed dialog box, enter environment variables in the format of "Variable name=Variable or variable reference".</li></ul>
|
||||
<div class="fignone" id="cce_10_0113__fig164568529317"><a name="cce_10_0113__fig164568529317"></a><a name="fig164568529317"></a><span class="figcap"><b>Figure 1 </b>Configuring environment variables</span><br><span><img id="cce_10_0113__image131385146481" src="en-us_image_0000002101597485.png"></span></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0113__section19591158201313"><h4 class="sectiontitle">YAML Example</h4><pre class="screen" id="cce_10_0113__screen1034117614147">apiVersion: apps/v1
|
||||
@ -92,7 +93,7 @@ env-example-695b759569-lx9jp 1/1 Running 0 17m
|
||||
$ kubectl exec env-example-695b759569-lx9jp -- printenv
|
||||
/ # env
|
||||
key=value # Custom environment variable
|
||||
ey1=configmap_value # Added from ConfigMap key
|
||||
key1=configmap_value # Added from ConfigMap key
|
||||
key2=secret_value # Added from secret key
|
||||
key3=env-example-695b759569-lx9jp # metadata.name defined by the pod
|
||||
key4=1 # limits.cpu defined by container1. The value is rounded up, in unit of cores.
|
||||
|
||||
@ -1,8 +1,7 @@
|
||||
<a name="cce_10_0125"></a><a name="cce_10_0125"></a>
|
||||
|
||||
<h1 class="topictitle1">SFS Turbo</h1>
|
||||
<div id="body0000001538521545"><p id="cce_10_0125__p8060118"></p>
|
||||
</div>
|
||||
<div id="body0000001538521545"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0624.html">Overview</a></strong><br>
|
||||
@ -13,7 +12,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>
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@
|
||||
</div>
|
||||
<div class="section" id="cce_10_0127__section776571919194"><h4 class="sectiontitle">Installing the Add-on</h4><p id="cce_10_0127__p11975102684817">This add-on has been installed by default. If it is uninstalled due to some reasons, you can reinstall it by performing the following steps:</p>
|
||||
<p id="cce_10_0127__p21112429503">If storage-driver is not installed in a cluster, perform the following steps to install it:</p>
|
||||
<ol id="cce_10_0127__ol9183433182510"><li id="cce_10_0127__li13183153352515"><span>Log in to the CCE console and click the cluster name to access the cluster console. Choose <strong id="cce_10_0127__b9141193415148"><span id="cce_10_0127__text1114113345145">Add-ons</span></strong> in the navigation pane, 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>
|
||||
<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>
|
||||
<div>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -22,8 +22,6 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0397.html">Configuring Workload Upgrade Policies</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0232.html">Scheduling Policies (Affinity/Anti-affinity)</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0728.html">Configuring Tolerance Policies</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0386.html">Configuring Labels and Annotations</a></strong><br>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -12,6 +12,8 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0864.html">Configuring a Cluster's API Server for Internet Access</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0744.html">Revoking a Cluster Access Credential</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -2,12 +2,12 @@
|
||||
|
||||
<h1 class="topictitle1">NodePort</h1>
|
||||
<div id="body1553224785332"><div class="section" id="cce_10_0142__section13654155944916"><h4 class="sectiontitle">Scenario</h4><p id="cce_10_0142__p028915126124">A Service is exposed on each node's IP address at a static port (NodePort). When you create a NodePort Service, Kubernetes automatically allocates an internal IP address (ClusterIP) of the cluster. When clients outside the cluster access <NodeIP>:<NodePort>, the traffic will be forwarded to the target pod through the ClusterIP of the NodePort Service.</p>
|
||||
<div class="fignone" id="cce_10_0142__fig6819133414131"><span class="figcap"><b>Figure 1 </b>NodePort access</span><br><span><img id="cce_10_0142__image10510139711" src="en-us_image_0000001950316596.png"></span></div>
|
||||
<div class="fignone" id="cce_10_0142__fig6819133414131"><span class="figcap"><b>Figure 1 </b>NodePort access</span><br><span><img id="cce_10_0142__image10510139711" src="en-us_image_0000002101678557.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0142__section8501151104219"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="cce_10_0142__ul1685519569431"><li id="cce_10_0142__li1585575616436">By default, a NodePort Service is accessed within a VPC. To use an EIP to access a NodePort Service through public networks, bind an EIP to the node in the cluster in advance.</li><li id="cce_10_0142__li128551156114310">After a Service is created, if the affinity setting is switched from the cluster level to the node level, the connection tracing table will not be cleared. Do not modify the Service affinity setting after the Service is created. To modify it, create a Service again.</li><li id="cce_10_0142__li62831358182017">In a CCE Turbo cluster, node-level affinity is supported only when the Service backend is connected to a HostNetwork pod.</li><li id="cce_10_0142__li217783916207">In VPC network mode, when container A is published through a NodePort service and the service affinity is set to the node level (that is, <strong id="cce_10_0142__b1291203218520">externalTrafficPolicy</strong> is set to <strong id="cce_10_0142__b11911632135217">local</strong>), container B deployed on the same node cannot access container A through the node IP address and NodePort service.</li><li id="cce_10_0142__li14613571073">When a NodePort service is created in a cluster of v1.21.7 or later, the port on the node is not displayed using <strong id="cce_10_0142__b13256143512525">netstat</strong> by default. If the cluster forwarding mode is <strong id="cce_10_0142__b42563350522">iptables</strong>, run the <strong id="cce_10_0142__b62561135115212">iptables -t nat -L</strong> command to view the port. If the cluster forwarding mode is <strong id="cce_10_0142__b925763515218">IPVS</strong>, run the <strong id="cce_10_0142__b23917223106">ipvsadm -Ln</strong> command to view the port.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0142__section1325012312139"><h4 class="sectiontitle">Creating a NodePort Service</h4><ol id="cce_10_0142__ol751935681319"><li id="cce_10_0142__li41731123658"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_10_0142__li1651955651312"><span>In the navigation pane, choose <strong id="cce_10_0142__b169702128151"><span id="cce_10_0142__text9765124722315">Services & Ingresses</span></strong>. In the upper right corner, click <span class="uicontrol" id="cce_10_0142__uicontrol69701128153"><b>Create Service</b></span>.</span></li><li id="cce_10_0142__li185190567138"><span>Configure intra-cluster access parameters.</span><p><ul id="cce_10_0142__ul4446314017144"><li id="cce_10_0142__li6462394317144"><strong id="cce_10_0142__b845613814287">Service Name</strong>: Specify a Service name, which can be the same as the workload name.</li><li id="cce_10_0142__li89543531070"><strong id="cce_10_0142__b106597277362">Service Type</strong>: Select <span class="uicontrol" id="cce_10_0142__uicontrol5666142710366"><b>NodePort</b></span>.</li><li id="cce_10_0142__li4800017144"><strong id="cce_10_0142__b1263193014367">Namespace</strong>: namespace that the workload belongs to.</li><li id="cce_10_0142__li1758110116149"><strong id="cce_10_0142__b38118349367">Service Affinity</strong>: For details, see <a href="cce_10_0249.html#cce_10_0249__section18134208069">externalTrafficPolicy (Service Affinity)</a>.<ul id="cce_10_0142__ul158101161412"><li id="cce_10_0142__li105815113141"><strong id="cce_10_0142__b2674164185210">Cluster level</strong>: The IP addresses and access ports of all nodes in a cluster can access the workload associated with the Service. Service access will cause performance loss due to route redirection, and the source IP address of the client cannot be obtained.</li><li id="cce_10_0142__li185817117145"><strong id="cce_10_0142__b465617445525">Node level</strong>: Only the IP address and access port of the node where the workload is located can access the workload associated with the Service. Service access will not cause performance loss due to route redirection, and the source IP address of the client can be obtained.</li></ul>
|
||||
</li><li id="cce_10_0142__li43200017144"><strong id="cce_10_0142__b2600143835813">Selector</strong>: Add a label and click <strong id="cce_10_0142__b260020382582">Confirm</strong>. The Service will use this label to select pods. You can also click <strong id="cce_10_0142__b354965233619">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_0142__b16550125293615">OK</strong>.</li><li id="cce_10_0142__li142435567390"><strong id="cce_10_0142__b13720100181614">IPv6</strong>: This function is disabled by default. After this function is enabled, the cluster IP address of the Service changes to an IPv6 address. <strong id="cce_10_0142__b14552143617309">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_0142__li388800117144"><strong id="cce_10_0142__b451552415715">Ports</strong><ul id="cce_10_0142__ul3499201217144"><li id="cce_10_0142__li4649265917144"><strong id="cce_10_0142__b28899114374">Protocol</strong>: protocol used by the Service.</li><li id="cce_10_0142__li353122153610"><strong id="cce_10_0142__b1852318551688">Service Port</strong>: port used by the Service. The port number ranges from 1 to 65535.</li><li id="cce_10_0142__li1578074917144"><strong id="cce_10_0142__b19416443712">Container Port</strong>: listener port of the workload. For example, Nginx uses port 80 by default.</li><li id="cce_10_0142__li780902117144"><strong id="cce_10_0142__b11763931199">Node Port</strong>: You are advised to select <strong id="cce_10_0142__b1198741292">Auto</strong>. You can also specify a port. The default port ranges from 30000 to 32767.</li></ul>
|
||||
</li><li id="cce_10_0142__li43200017144"><strong id="cce_10_0142__b2600143835813">Selector</strong>: Add a label and click <strong id="cce_10_0142__b260020382582">Confirm</strong>. The Service will use this label to select pods. You can also click <strong id="cce_10_0142__b354965233619">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_0142__b16550125293615">OK</strong>.</li><li id="cce_10_0142__li142435567390"><strong id="cce_10_0142__b13720100181614">IPv6</strong>: This function is disabled by default. After this function is enabled, the cluster IP address of the Service changes to an IPv6 address. <strong id="cce_10_0142__b14552143617309">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_0142__li388800117144"><strong id="cce_10_0142__b451552415715">Ports</strong><ul id="cce_10_0142__ul3499201217144"><li id="cce_10_0142__li4649265917144"><strong id="cce_10_0142__b28899114374">Protocol</strong>: protocol used by the Service.</li><li id="cce_10_0142__li353122153610"><strong id="cce_10_0142__b1852318551688">Service Port</strong>: port used by the Service. The port number ranges from 1 to 65535.</li><li id="cce_10_0142__li1578074917144"><strong id="cce_10_0142__b19416443712">Container Port</strong>: listener port of the workload. For example, Nginx uses port 80 by default.</li><li id="cce_10_0142__li780902117144"><strong id="cce_10_0142__b11763931199">Node Port</strong>: You are advised to select <strong id="cce_10_0142__b1198741292">Auto</strong>. You can also specify a port. The default port ranges from 30000 to 32767.</li></ul>
|
||||
</li></ul>
|
||||
</p></li><li id="cce_10_0142__li552017569135"><span>Click <strong id="cce_10_0142__b1012031216378">OK</strong>.</span></li></ol>
|
||||
</div>
|
||||
@ -58,10 +58,10 @@ spec:
|
||||
<pre class="screen" id="cce_10_0142__screen184796131354">NAME READY STATUS RESTARTS AGE
|
||||
<strong id="cce_10_0142__b128512503516">nginx-2601814895-qhxqv 1/1 Running 0 9s</strong></pre>
|
||||
</p></li><li id="cce_10_0142__li72314917413"><span>Create a Service.</span><p><p id="cce_10_0142__p410057205911"><strong id="cce_10_0142__b16534131413598">kubectl create -f nginx-nodeport-svc.yaml</strong></p>
|
||||
<p id="cce_10_0142__p82261925113913">If information similar to the following is displayed, the Service is being created.</p>
|
||||
<p id="cce_10_0142__p82261925113913">If information similar to the following is displayed, the Service is being created:</p>
|
||||
<pre class="screen" id="cce_10_0142__screen206204581359">service "nginx-nodeport" created</pre>
|
||||
<p id="cce_10_0142__p1025119113593"><strong id="cce_10_0142__b1253721413598">kubectl get svc</strong></p>
|
||||
<p id="cce_10_0142__p16843163318393">If information similar to the following is displayed, the Service has been created.</p>
|
||||
<p id="cce_10_0142__p16843163318393">If information similar to the following is displayed, the Service has been created:</p>
|
||||
<pre class="screen" id="cce_10_0142__screen250841013612"># kubectl get svc
|
||||
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
||||
kubernetes ClusterIP 10.247.0.1 <none> 443/TCP 4d8h
|
||||
|
||||
@ -33,7 +33,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="78%" headers="mcps1.3.3.3.2.4.2.2.3.1.2 "><p id="cce_10_0146__p1678472115013">Describes configuration parameters required by templates.</p>
|
||||
<div class="notice" id="cce_10_0146__note11415171194911"><span class="noticetitle"> NOTICE: </span><div class="noticebody"><p id="cce_10_0146__p394216481648">Make sure that the image address set in the <strong id="cce_10_0146__b169837156417">values.yaml</strong> file is the same as the image address in the container image repository. Otherwise, an exception occurs when you create a workload, and the system displays a message indicating that the image fails to be pulled.</p>
|
||||
<p id="cce_10_0146__p04177113498">To obtain the image address, perform the following operations: Log in to the CCE console. In the navigation pane, choose <strong id="cce_10_0146__b860412174116">Image Repository</strong> to access the SWR console. Choose <strong id="cce_10_0146__b10171926114117">My Images</strong> > <strong id="cce_10_0146__b12372684119">Private Images</strong> and click the name of the uploaded image. On the <strong id="cce_10_0146__b223726104111">Image Tags</strong> tab page, obtain the image address from the pull command. You can click <span><img id="cce_10_0146__image292113414153" src="en-us_image_0000001981276393.png"></span> to copy the command in the <strong id="cce_10_0146__b723192619418">Image Pull Command</strong> column.</p>
|
||||
<p id="cce_10_0146__p04177113498">To obtain the image address, perform the following operations: Log in to the CCE console. In the navigation pane, choose <strong id="cce_10_0146__b860412174116">Image Repository</strong> to access the SWR console. Choose <strong id="cce_10_0146__b10171926114117">My Images</strong> > <strong id="cce_10_0146__b12372684119">Private Images</strong> and click the name of the uploaded image. On the <strong id="cce_10_0146__b223726104111">Image Tags</strong> tab page, obtain the image address from the pull command. You can click <span><img id="cce_10_0146__image292113414153" src="en-us_image_0000002101678825.png"></span> to copy the command in the <strong id="cce_10_0146__b723192619418">Image Pull Command</strong> column.</p>
|
||||
</div></div>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@ -83,7 +83,7 @@
|
||||
<div class="p" id="cce_10_0150__p310913521612"><strong id="cce_10_0150__b104487882335241">(Optional) Advanced Settings</strong><ul id="cce_10_0150__ul67010503227"><li id="cce_10_0150__li179714209414"><strong id="cce_10_0150__cce_10_0047_b562135212518">Labels and Annotations</strong>: Add labels or annotations for pods using key-value pairs. After entering the key and value, click <strong id="cce_10_0150__cce_10_0047_b1439805716617">Confirm</strong>. For details about how to use and configure labels and annotations, see <a href="cce_10_0386.html">Configuring Labels and Annotations</a>.</li></ul>
|
||||
<ul id="cce_10_0150__ul142811417"><li id="cce_10_0150__li1981131361"><strong id="cce_10_0150__b31333382212">Job Settings</strong><ul id="cce_10_0150__ul3224164372"><li id="cce_10_0150__li153401527710"><strong id="cce_10_0150__b58521141142118">Parallel Pods</strong>: Maximum number of pods that can run in parallel during job execution. The value cannot be greater than the total number of pods in the job.</li><li id="cce_10_0150__li10287691771"><strong id="cce_10_0150__b143534522119">Timeout (s)</strong>: Once a job reaches this time, the job status becomes failed and all pods in this job will be deleted. If you leave this parameter blank, the job will never time out.</li><li id="cce_10_0150__li138103518153">Completion Mode<ul id="cce_10_0150__ul51723941512"><li id="cce_10_0150__li17920114315153"><strong id="cce_10_0150__b699913411252">Non-indexed</strong>: A job is considered complete when all the pods are successfully executed. Each pod completion is homologous to each other.</li><li id="cce_10_0150__li1358717341155"><strong id="cce_10_0150__b6574144582718">Indexed</strong>: Each pod gets an associated completion index from 0 to the number of pods minus 1. The job is considered complete when every pod allocated with an index is successfully executed. For an indexed job, pods are named in the format of $(job-name)-$(index).</li></ul>
|
||||
</li><li id="cce_10_0150__li5539150161613"><strong id="cce_10_0150__b28515464300">Suspend Job</strong>: By default, a job is executed immediately after being created. The job's execution will be suspended if you enable this option, and resumed after you disable it.</li></ul>
|
||||
</li><li id="cce_10_0150__li34513820295"><strong id="cce_10_0150__cce_10_0047_b563938103113">Network Configuration</strong><ul id="cce_10_0150__cce_10_0047_ul101792551538"><li id="cce_10_0150__cce_10_0047_li1985863319162">Pod ingress/egress bandwidth limitation: You can set ingress/egress bandwidth limitation for pods. For details, see <a href="cce_10_0382.html">Configuring QoS for a Pod</a>.</li><li id="cce_10_0150__cce_10_0047_li053620118549">IPv6 shared bandwidth: available only for clusters that support this function. After this function is enabled, you can configure a shared bandwidth for a pod with IPv6 dual-stack ENIs. For details, see <a href="cce_10_0604.html">Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack ENIs</a>.</li></ul>
|
||||
</li><li id="cce_10_0150__li34513820295"><strong id="cce_10_0150__cce_10_0047_b563938103113">Network Configuration</strong><ul id="cce_10_0150__cce_10_0047_ul101792551538"><li id="cce_10_0150__cce_10_0047_li1985863319162">Pod ingress/egress bandwidth limitation: You can set ingress/egress bandwidth limitation for pods. For details, see <a href="cce_10_0382.html">Configuring QoS for a Pod</a>.</li><li id="cce_10_0150__cce_10_0047_li1898141443111">Whether to enable a specified container network configuration: available only for clusters that support this function. After you enable a specified container network configuration, the workload will be created using the container subnet and security group in the configuration. For details, see <a href="cce_10_0196.html">Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configuration</a>.</li><li id="cce_10_0150__cce_10_0047_li465673203314">Specify the container network configuration name: Only the custom container network configuration whose associated resource type is workload can be selected.</li><li id="cce_10_0150__cce_10_0047_li053620118549">IPv6 shared bandwidth: available only for clusters that support this function. After this function is enabled, you can configure a shared bandwidth for a pod with IPv6 dual-stack ENIs. For details, see <a href="cce_10_0604.html">Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack ENIs</a>.</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
</p></li><li id="cce_10_0150__li01417411620"><span>Click <strong id="cce_10_0150__b2573105264313">Create Workload</strong> in the lower right corner.</span></li></ol>
|
||||
@ -188,7 +188,7 @@ myjob-29qlw 0/1 Completed 0 4m5s
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0150__row17717577287"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.5.3.2.3.1.1 "><p id="cce_10_0150__p147711757162810">Editing a YAML file</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.5.3.2.3.1.2 "><p id="cce_10_0150__p15771257142816">Click <strong id="cce_10_0150__b29531155122112">More</strong> > <strong id="cce_10_0150__b6953255132119">Edit YAML</strong> next to the job name to edit the YAML file corresponding to the current job.</p>
|
||||
<td class="cellrowborder" valign="top" width="81%" headers="mcps1.3.5.3.2.3.1.2 "><p id="cce_10_0150__p15771257142816">Click <strong id="cce_10_0150__b29531155122112">More</strong> > <strong id="cce_10_0150__b6953255132119">Edit YAML</strong> next to the job name to edit the YAML file of the current job.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0150__r27a8f438ed1d4cbba2ad07f7a08acb06"><td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.5.3.2.3.1.1 "><p id="cce_10_0150__a1f9f2bb06252439c82b01c1d4bbb9ab0">Deleting a job</p>
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user