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

CCE UMN 20260323 version

Browse Source 
Reviewed-by: Gergo-Bence Lorincz <a200452876@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
This commit is contained in:
Dong, Qiu Jian
2026-03-24 15:35:48 +00:00
committed by zuul
parent 842e8f4dce
commit 5bfde208c6
26 changed files with 2743 additions and 2328 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

File diff suppressed because it is too large Load Diff

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

File diff suppressed because it is too large Load Diff

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

@ -8,7 +8,13 @@
</th>
</tr>
</thead>
<tbody><tr id="cce_01_0300__row111071551569"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p410735185615">2026-03-11</p>
<tbody><tr id="cce_01_0300__row047745519291"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p1747705515291"><span id="cce_01_0300__ph17657328307">2026-03-25</span></p>
</td>
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p854717933014">Add:</p>
<ul id="cce_01_0300__ul13222613133018"><li id="cce_01_0300__li12224131301">Added <a href="cce_10_0055.html">Configuring APM</a></li><li id="cce_01_0300__li13945922153011">Added <a href="en-us_topic_0000002516078019.html">Configuring Alarms for Java Applications on APM</a></li></ul>
</td>
</tr>
<tr id="cce_01_0300__row111071551569"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p410735185615">2026-03-11</p>
</td>
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p22962515610">Update:</p>
<ul id="cce_01_0300__ul157941134115615"><li id="cce_01_0300__li1579416349568">Updated <a href="cce_10_0405.html">Patch Version Release Notes</a></li><li id="cce_01_0300__li45780361560">Updated <a href="cce_10_0617.html">SFS Overview</a></li><li id="cce_01_0300__li17417193505812">Updated <a href="cce_10_0734.html">Configuring an EIP for a Pod in a CCE Turbo Cluster</a></li></ul>

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

@ -2,66 +2,10 @@
<h1 class="topictitle1">Viewing CTS Traces in the Trace List</h1>
<div id="body1525226397666"><div class="section" id="cce_10_0026__en-us_topic_0179639644_section5470822195238"><h4 class="sectiontitle">Scenarios</h4><p id="cce_10_0026__en-us_topic_0179639644_p5235541767">Cloud Trace Service (CTS) records operations performed on cloud service resources. A record contains information such as the user who performed the operation, IP address, operation content, and returned response message. These records facilitate security auditing, issue tracking, and resource locating. They also help you plan and use resources, and identify high-risk or non-compliant operations.</p>
<p id="cce_10_0026__en-us_topic_0179639644_p5961487316">This section describes how to query or export operation records of the last seven days on the CTS console.</p>
</div>
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section036851413573"><h4 class="sectiontitle">What Is a Trace?</h4><p id="cce_10_0026__en-us_topic_0179639644_p7344192412579">A trace is an operation log for a cloud service resource, tracked and stored by CTS. Traces record operations such as adding, modifying, or deleting cloud service resources. You can view them to identify who performed operations and when for detailed tracking.</p>
</div>
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section19271975203"><h4 class="sectiontitle">Viewing Traces in the Trace List</h4><ol id="cce_10_0026__en-us_topic_0179639644_ol143115612115"><li id="cce_10_0026__en-us_topic_0179639644_li1629194722218"><span>Log in to the management console, click <span><img id="cce_10_0026__en-us_topic_0179639644_image1229124714224" src="en-us_image_0000002359774578.png"></span> in the upper left corner, and choose <strong id="cce_10_0026__en-us_topic_0179639644_b0101171161313">Management &amp; Deployment</strong> &gt; <strong id="cce_10_0026__en-us_topic_0179639644_b17101511131310">Cloud Trace Service</strong>.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li1443115692119"><span>In the navigation pane, choose <strong id="cce_10_0026__en-us_topic_0179639644_b5352121921314">Trace List</strong>.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li1468123811239"><span>In the upper right corner of the page, select a desired query time range: <strong id="cce_10_0026__en-us_topic_0179639644_b192893416490">Last 1 hour</strong>, <strong id="cce_10_0026__en-us_topic_0179639644_b122899464911">Last 1 day</strong>, or <strong id="cce_10_0026__en-us_topic_0179639644_b19289147490">Last 1 week</strong>. You can also specify a custom time range within the last seven days.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li243155612119"><span>Set filters to search for your desired traces, as shown in <a href="#cce_10_0026__en-us_topic_0179639644_fig139361441134311">Figure 1</a>.</span><p><div class="fignone" id="cce_10_0026__en-us_topic_0179639644_fig139361441134311"><a name="cce_10_0026__en-us_topic_0179639644_fig139361441134311"></a><a name="en-us_topic_0179639644_fig139361441134311"></a><span class="figcap"><b>Figure 1 </b>Filters</span><br><span><img id="cce_10_0026__en-us_topic_0179639644_image14936144112433" src="en-us_image_0000001744598325.png"></span></div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0026__en-us_topic_0179639644_table147746583014" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Trace filtering parameters</caption><thead align="left"><tr id="cce_10_0026__en-us_topic_0179639644_row1877510573019"><th align="left" class="cellrowborder" valign="top" width="18.95%" id="mcps1.3.3.2.4.2.2.2.3.1.1"><p id="cce_10_0026__en-us_topic_0179639644_p1877512593016">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="81.05%" id="mcps1.3.3.2.4.2.2.2.3.1.2"><p id="cce_10_0026__en-us_topic_0179639644_p57751859302">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="cce_10_0026__en-us_topic_0179639644_row1285411013373"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p28541510143716">Trace Type</p>
</td>
<td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p08541510193711">Select <strong id="cce_10_0026__en-us_topic_0179639644_b14902228784">Management</strong> or <strong id="cce_10_0026__en-us_topic_0179639644_b129020281815">Data</strong>.</p>
<ul id="cce_10_0026__en-us_topic_0179639644_ul1060181493817"><li id="cce_10_0026__en-us_topic_0179639644_li156071412384">Management traces record operations performed by users on cloud service resources, including creation, modification, and deletion.</li><li id="cce_10_0026__en-us_topic_0179639644_li1385816156388">Data traces are reported by OBS and record operations performed on data in OBS buckets, including uploads and downloads.</li></ul>
</td>
</tr>
<tr id="cce_10_0026__en-us_topic_0179639644_row113186562383"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p157759523017">Trace Source</p>
</td>
<td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p177757543019">Select the name of the cloud service that triggers a trace from the drop-down list.</p>
</td>
</tr>
<tr id="cce_10_0026__en-us_topic_0179639644_row531111429400"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p167757553018">Resource type</p>
</td>
<td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p1677513515307">Select the type of the resource involved in a trace from the drop-down list.</p>
<p id="cce_10_0026__en-us_topic_0179639644_p1077535173016">For details about the resource types of each cloud service, see section "Supported Services and Operations" in the <em id="cce_10_0026__en-us_topic_0179639644_i1090794613497">Cloud Trace Service User Guide</em>.</p>
</td>
</tr>
<tr id="cce_10_0026__en-us_topic_0179639644_row17951953163817"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p17951145393815">Search By</p>
</td>
<td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p1866016362423">Select one of the following options:</p>
<ul id="cce_10_0026__en-us_topic_0179639644_ul8324201518432"><li id="cce_10_0026__en-us_topic_0179639644_li1332441519434"><strong id="cce_10_0026__en-us_topic_0179639644_b17755195192214">Resource ID</strong>: ID of the cloud resource involved in a trace.<p id="cce_10_0026__en-us_topic_0179639644_p927319140446">Leave this field empty if the resource has no resource ID or if resource creation failed.</p>
</li><li id="cce_10_0026__en-us_topic_0179639644_li19324111594319"><strong id="cce_10_0026__en-us_topic_0179639644_b20740051162314">Trace name</strong>: name of a trace.<p id="cce_10_0026__en-us_topic_0179639644_p162131756164314">For details about the operations that can be audited for each cloud service, see section "Supported Services and Operations" in the <em id="cce_10_0026__en-us_topic_0179639644_i185782113507">Cloud Trace Service User Guide</em>.</p>
</li><li id="cce_10_0026__en-us_topic_0179639644_li53251315144311"><strong id="cce_10_0026__en-us_topic_0179639644_b113836152512">Resource name</strong>: name of the cloud resource involved in a trace.<p id="cce_10_0026__en-us_topic_0179639644_p546964974419">If the cloud resource involved in the trace does not have a resource name or the corresponding API operation does not involve the resource name parameter, leave this field empty.</p>
</li></ul>
</td>
</tr>
<tr id="cce_10_0026__en-us_topic_0179639644_row10776105103014"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p47761954309">Operator</p>
</td>
<td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p17761455309">User who triggers a trace.</p>
<p id="cce_10_0026__en-us_topic_0179639644_p1577616513018">Select one or more operators from the drop-down list.</p>
<p id="cce_10_0026__en-us_topic_0179639644_p47761952302">If the value of <strong id="cce_10_0026__en-us_topic_0179639644_b1470691118286">trace_type</strong> in a trace is <strong id="cce_10_0026__en-us_topic_0179639644_b18706191132818">SystemAction</strong>, the operation is triggered by the service and the trace's operator may be empty.</p>
</td>
</tr>
<tr id="cce_10_0026__en-us_topic_0179639644_row1377615153014"><td class="cellrowborder" valign="top" width="18.95%" headers="mcps1.3.3.2.4.2.2.2.3.1.1 "><p id="cce_10_0026__en-us_topic_0179639644_p877615519306">Trace Status</p>
</td>
<td class="cellrowborder" valign="top" width="81.05%" headers="mcps1.3.3.2.4.2.2.2.3.1.2 "><p id="cce_10_0026__en-us_topic_0179639644_p10776115133014">Select one of the following options:</p>
<ul id="cce_10_0026__en-us_topic_0179639644_ul177767517302"><li id="cce_10_0026__en-us_topic_0179639644_li177617583015"><strong id="cce_10_0026__en-us_topic_0179639644_b14380125823418">Normal</strong>: The operation succeeded.</li><li id="cce_10_0026__en-us_topic_0179639644_li1077665143015"><strong id="cce_10_0026__en-us_topic_0179639644_b128046471357">Warning</strong>: The operation failed.</li><li id="cce_10_0026__en-us_topic_0179639644_li19776135143018"><strong id="cce_10_0026__en-us_topic_0179639644_b134361033365">Incident</strong>: The operation caused a fault that is more serious than a normal failure, for example, causing other faults.</li></ul>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li class="subitemlist" id="cce_10_0026__en-us_topic_0179639644_li124311756172111"><span>Click <strong id="cce_10_0026__en-us_topic_0179639644_b158561654073256">Query</strong>.</span></li><li id="cce_10_0026__en-us_topic_0179639644_li7432056192112"><span>On the <strong id="cce_10_0026__en-us_topic_0179639644_b176911834143214">Trace List</strong> page, you can also export and refresh the trace list.</span><p><ul id="cce_10_0026__en-us_topic_0179639644_ul119414175448"><li id="cce_10_0026__en-us_topic_0179639644_li12946170445">Click <strong id="cce_10_0026__en-us_topic_0179639644_b8907168171714">Export</strong> to export all traces in the query result as a CSV file. The file can contain up to 5,000 records.</li><li id="cce_10_0026__en-us_topic_0179639644_li394151717445">Click <span><img id="cce_10_0026__en-us_topic_0179639644_image109421716440" src="en-us_image_0000001696678850.png"></span> to view the latest information about traces.</li></ul>
</p></li><li id="cce_10_0026__en-us_topic_0179639644_li15432145622119"><span>Click <span><img id="cce_10_0026__en-us_topic_0179639644_image9947176447" src="en-us_image_0000001744678489.jpg"></span> on the left of a trace to expand its details.</span><p><p id="cce_10_0026__en-us_topic_0179639644_p1294101714446"></p>
<p id="cce_10_0026__en-us_topic_0179639644_p1694171715446"><span><img id="cce_10_0026__en-us_topic_0179639644_image1767234653119" src="en-us_image_0000001942942816.png"></span></p>
<p id="cce_10_0026__en-us_topic_0179639644_p145491156142711"></p>
</p></li><li id="cce_10_0026__en-us_topic_0179639644_li143245616217"><span>Click <strong id="cce_10_0026__en-us_topic_0179639644_b139145611337">View Trace</strong> in the <strong id="cce_10_0026__en-us_topic_0179639644_b1591756103313">Operation</strong> column. The trace details are displayed.</span><p><p id="cce_10_0026__en-us_topic_0179639644_p1695161714447"><span><img id="cce_10_0026__en-us_topic_0179639644_image1904172011220" src="en-us_image_0000001758618249.png"></span></p>
</p></li></ol>
</div>
<div class="section" id="cce_10_0026__en-us_topic_0179639644_section18501734161612"><h4 class="sectiontitle">Helpful Links</h4><ul id="cce_10_0026__en-us_topic_0179639644_ul19442019172"><li id="cce_10_0026__en-us_topic_0179639644_li547715311275">For details about the key fields in the trace structure, see <a href="https://docs.otc.t-systems.com/cloud-trace-service/umn/user_guide/trace_references/trace_structure.html#cts-03-0010" target="_blank" rel="noopener noreferrer">Trace Structure</a> and <a href="https://docs.otc.t-systems.com/cloud-trace-service/umn/user_guide/trace_references/example_traces.html" target="_blank" rel="noopener noreferrer">Example Traces</a>.</li></ul>
</div>
</div>

321
docs/cce/umn/cce_10_0055.html Normal file
View File

File diff suppressed because it is too large Load Diff

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

@ -20,6 +20,8 @@
</li>
<li class="ulchildlink"><strong><a href="cce_10_0113.html">Configuring Environment Variables</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0055.html">Configuring APM</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0397.html">Upgrading and Rolling Back a Workload</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="cce_10_0728.html">Configuring Tolerance Policies</a></strong><br>

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

@ -424,7 +424,7 @@ spec:
<td class="cellrowborder" valign="top" width="10%" headers="mcps1.3.9.2.2.5.1.2 "><p id="cce_10_0385__p17474532410">String</p>
</td>
<td class="cellrowborder" valign="top" width="53%" headers="mcps1.3.9.2.2.5.1.3 "><p id="cce_10_0385__p17475535414">ID of an ELB certificate, which is used as the HTTPS server certificate.</p>
<p id="cce_10_0385__p315916934311">How to obtain: Log in to the <span id="cce_10_0385__ph13532316978">ELB console</span> and choose <strong id="cce_10_0385__b125272088328">Certificates</strong>. In the load balancer list, copy the ID under the target certificate name.</p>
<p id="cce_10_0385__p315916934311">How to obtain: Log in to the <span id="cce_10_0385__ph13532316978">ELB console</span> and choose <strong id="cce_10_0385__b125272088328">Certificates</strong>. In the certificate list, copy the ID under the target certificate name.</p>
</td>
<td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.9.2.2.5.1.4 "><p id="cce_10_0385__p47471953945">v1.19.16 or later</p>
</td>
@ -450,7 +450,7 @@ spec:
<td class="cellrowborder" valign="top" width="10.101010101010102%" headers="mcps1.3.10.2.2.5.1.2 "><p id="cce_10_0385__p13881637164220">String</p>
</td>
<td class="cellrowborder" valign="top" width="53.535353535353536%" headers="mcps1.3.10.2.2.5.1.3 "><p id="cce_10_0385__p178811937194219">In ELB, the IDs of SNI certificates that must contain a domain name are separated by commas (,).</p>
<p id="cce_10_0385__p11881133710426">How to obtain: Log in to the <span id="cce_10_0385__ph1391418222320">ELB console</span> and choose <strong id="cce_10_0385__b14915152216320">Certificates</strong>. In the load balancer list, copy the ID under the target certificate name.</p>
<p id="cce_10_0385__p11881133710426">How to obtain: Log in to the <span id="cce_10_0385__ph1391418222320">ELB console</span> and choose <strong id="cce_10_0385__b14915152216320">Certificates</strong>. In the certificate list, copy the ID under the target certificate name.</p>
</td>
<td class="cellrowborder" valign="top" width="18.181818181818183%" headers="mcps1.3.10.2.2.5.1.4 "><p id="cce_10_0385__p977642114211">v1.23.13-r0, v1.25.8-r0, v1.27.5-r0, v1.28.3-r0, or later</p>
</td>
@ -619,7 +619,7 @@ spec:
</td>
<td class="cellrowborder" valign="top" width="56.99999999999999%" headers="mcps1.3.14.2.2.5.1.3 "><p id="cce_10_0385__p18882328885">This annotation can be used by the Service only if the pod uses the host network. After this annotation is used, ELB forwards requests to the host network.</p>
<p id="cce_10_0385__p128822282088">Options:</p>
<ul id="cce_10_0385__ul6882202812817"><li id="cce_10_0385__li1888220285811"><strong id="cce_10_0385__b1730800371">true</strong>: enabled</li><li id="cce_10_0385__li1988219284818"><strong id="cce_10_0385__b131375249434210">false</strong> (default): disabled</li></ul>
<ul id="cce_10_0385__ul6882202812817"><li id="cce_10_0385__li1888220285811"><strong id="cce_10_0385__b693798197">true</strong>: enabled</li><li id="cce_10_0385__li1988219284818"><strong id="cce_10_0385__b131375249434210">false</strong> (default): disabled</li></ul>
</td>
<td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.14.2.2.5.1.4 "><p id="cce_10_0385__p1688232810812">v1.9 or later</p>
</td>

8
docs/cce/umn/cce_10_0687.html
View File

@ -323,7 +323,7 @@ ingress-test cce * 121.**.**.** 80,443 10s</pre>
</table>
</div>
<p id="cce_10_0687__p1467381895320"></p>
</p></li><li id="cce_10_0687__li874244415242"><span>Click <span class="uicontrol" id="cce_10_0687__uicontrol1301269740"><b>OK</b></span>.</span></li></ol>
</p></li><li id="cce_10_0687__li874244415242"><span>Click <span class="uicontrol" id="cce_10_0687__uicontrol1580857236"><b>OK</b></span>.</span></li></ol>
</div>
<div class="section" id="cce_10_0687__section820220311361"><h4 class="sectiontitle">Using kubectl to Configure a Certificate Created on the ELB Console</h4><p id="cce_10_0687__p1998210519381">To use an ELB certificate, you can specify the <strong id="cce_10_0687__b5003159810232">kubernetes.io/elb.tls-certificate-ids</strong> annotation.</p>
<div class="note" id="cce_10_0687__note12311184013456"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0687__cce_10_0687_ul367510252127"><li id="cce_10_0687__cce_10_0687_li1167522518126">If both an ELB certificate and a TLS certificate are specified for the same ingress, the ingress will use the ELB certificate.</li><li id="cce_10_0687__cce_10_0687_li867522513128">CCE does not check whether an ELB certificate is valid. It only checks whether the certificate is present.</li><li id="cce_10_0687__cce_10_0687_li467519255120">Only ingresses in clusters of v1.19.16-r2, v1.21.5-r0, v1.23.3-r0, or later support ELB certificates.</li></ul>
@ -349,9 +349,9 @@ spec:
- path: '/'
backend:
service:
name: <i><span class="varname" id="cce_10_0687__varname327995205">&lt;your_service_name&gt;</span></i> # Replace it with the name of your target Service.
name: <i><span class="varname" id="cce_10_0687__varname951834834">&lt;your_service_name&gt;</span></i> # Replace it with the name of your target Service.
port:
number: <i><span class="varname" id="cce_10_0687__varname1752423225">80</span></i> # Replace it with the port number of your target Service.
number: <i><span class="varname" id="cce_10_0687__varname2094360933">80</span></i> # Replace it with the port number of your target Service.
property:
ingress.beta.kubernetes.io/url-match-mode: STARTS_WITH
pathType: ImplementationSpecific
@ -395,7 +395,7 @@ spec:
</td>
<td class="cellrowborder" valign="top" width="65%" headers="mcps1.3.8.4.2.2.6.2.4.1.3 "><p id="cce_10_0687__p158991292302">ELB certificate IDs, which are separated by comma (,). The list length is greater than or equal to 1. The first ID in the list is the server certificate, and the other IDs are SNI certificates in which a domain name must be contained.</p>
<p id="cce_10_0687__p14975881269">If an SNI certificate cannot be found based on the domain name requested by the client, the server certificate will be returned by default.</p>
<p id="cce_10_0687__p266917129452">To obtain the certificate, log in to the CCE console, choose <strong id="cce_10_0687__b119308133251157">Service List</strong> &gt; <strong id="cce_10_0687__b116436220051157">Networking</strong> &gt; <strong id="cce_10_0687__b166591680851157">Elastic Load Balance</strong>, and click <strong id="cce_10_0687__b65643199651157">Certificates</strong> in the navigation pane. In the load balancer list, copy the ID under the target certificate name.</p>
<p id="cce_10_0687__p266917129452">To obtain the certificate, log in to the CCE console, choose <strong id="cce_10_0687__b119308133251157">Service List</strong> &gt; <strong id="cce_10_0687__b116436220051157">Networking</strong> &gt; <strong id="cce_10_0687__b166591680851157">Elastic Load Balance</strong>, and click <strong id="cce_10_0687__b65643199651157">Certificates</strong> in the navigation pane. In the certificate list, copy the ID under the target certificate name.</p>
</td>
</tr>
</tbody>

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

@ -254,7 +254,7 @@ spec:
paths:
- path: '/'
backend:
serviceName: <i><span class="varname" id="cce_10_0688__varname2063351624">&lt;your_service_name&gt;</span></i> # Replace it with the name of your target Service.
serviceName: <i><span class="varname" id="cce_10_0688__varname427638310">&lt;your_service_name&gt;</span></i> # Replace it with the name of your target Service.
servicePort: <i><span class="varname" id="cce_10_0688__varname3353338184710">80</span></i>
property:
ingress.beta.kubernetes.io/url-match-mode: STARTS_WITH</pre>
@ -273,7 +273,7 @@ spec:
</td>
<td class="cellrowborder" valign="top" width="55.32%" headers="mcps1.3.8.4.2.2.6.2.4.1.3 "><p id="cce_10_0688__p158991292302">ELB certificate IDs, which are separated by comma (,). The list length is greater than or equal to 1. The first ID in the list is the server certificate, and the other IDs are SNI certificates in which a domain name must be contained.</p>
<p id="cce_10_0688__p14975881269">If an SNI certificate cannot be found based on the domain name requested by the client, the server certificate will be returned by default.</p>
<p id="cce_10_0688__p266917129452">To obtain the certificate, log in to the CCE console, choose <strong id="cce_10_0688__b1064885535912">Service List</strong> &gt; <strong id="cce_10_0688__b664812556596">Networking</strong> &gt; <strong id="cce_10_0688__b564916553595">Elastic Load Balance</strong>, and click <strong id="cce_10_0688__b664910552598">Certificates</strong> in the navigation pane. In the load balancer list, copy the ID under the target certificate name.</p>
<p id="cce_10_0688__p266917129452">To obtain the certificate, log in to the CCE console, choose <strong id="cce_10_0688__b1064885535912">Service List</strong> &gt; <strong id="cce_10_0688__b664812556596">Networking</strong> &gt; <strong id="cce_10_0688__b564916553595">Elastic Load Balance</strong>, and click <strong id="cce_10_0688__b664910552598">Certificates</strong> in the navigation pane. In the certificate list, copy the ID under the target certificate name.</p>
</td>
</tr>
</tbody>

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

@ -208,7 +208,7 @@
<td class="cellrowborder" valign="top" width="11%" headers="mcps1.3.6.3.2.5.1.2 "><p id="cce_10_0695__p1336355581017">String</p>
</td>
<td class="cellrowborder" valign="top" width="54%" headers="mcps1.3.6.3.2.5.1.3 "><p id="cce_10_0695__p936395571019">ELB certificate IDs, which are separated by comma (,). The list length is greater than or equal to 1. The first ID in the list is the server certificate, and the other IDs are SNI certificates in which a domain name must be contained.</p>
<p id="cce_10_0695__p836325512106">How to obtain: Log in to the <span id="cce_10_0695__ph17828524353211">ELB console</span> and choose <strong id="cce_10_0695__b146660099653211">Certificates</strong>. In the load balancer list, copy the ID under the target certificate name.</p>
<p id="cce_10_0695__p836325512106">How to obtain: Log in to the <span id="cce_10_0695__ph17828524353211">ELB console</span> and choose <strong id="cce_10_0695__b146660099653211">Certificates</strong>. In the certificate list, copy the ID under the target certificate name.</p>
</td>
<td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.6.3.2.5.1.4 "><p id="cce_10_0695__p11346174616104">v1.19.16-r2, v1.21.5-r0, v1.23.3-r0, or later</p>
</td>
@ -282,7 +282,7 @@
</td>
<td class="cellrowborder" valign="top" width="10.101010101010102%" headers="mcps1.3.8.3.2.5.1.2 "><p id="cce_10_0695__p152717184211">String</p>
</td>
<td class="cellrowborder" valign="top" width="49.494949494949495%" headers="mcps1.3.8.3.2.5.1.3 "><p id="cce_10_0695__p1271218624">To interconnect with HTTPS backend services, set this parameter to <strong id="cce_10_0695__b1349438342">https</strong>.</p>
<td class="cellrowborder" valign="top" width="49.494949494949495%" headers="mcps1.3.8.3.2.5.1.3 "><p id="cce_10_0695__p1271218624">To interconnect with HTTPS backend services, set this parameter to <strong id="cce_10_0695__b1279597121">https</strong>.</p>
</td>
<td class="cellrowborder" valign="top" width="24.242424242424242%" headers="mcps1.3.8.3.2.5.1.4 "><p id="cce_10_0695__p82713181929">v1.23.8, v1.25.3, or later</p>
</td>

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

@ -56,7 +56,7 @@ spec:
<p id="cce_10_0735__p123836441445"><strong id="cce_10_0735__b48051057174410">Clusters later than v1.23 support this field.</strong></p>
<p id="cce_10_0735__p428125093618">The slow start duration ranges from <strong id="cce_10_0735__b473722194516">30</strong> to <strong id="cce_10_0735__b673712144513">1200</strong>.</p>
<p id="cce_10_0735__p0995160145214">Duration of slow start, in seconds.</p>
<ul id="cce_10_0735__ul999560145215"><li id="cce_10_0735__li599560145216">Grayscale release applies only to dedicated load balancers.</li><li id="cce_10_0735__li10995150195219">This parameter is valid only when the allocation policy of the target Service is weighted round robin (WRR) and sticky session is disabled.</li></ul>
<ul id="cce_10_0735__ul999560145215"><li id="cce_10_0735__li599560145216">This configuration applies only to dedicated load balancers.</li><li id="cce_10_0735__li10995150195219">This parameter is valid only when the allocation policy of the target Service is weighted round robin (WRR) and sticky session is disabled.</li></ul>
</td>
</tr>
</tbody>

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

@ -12,6 +12,8 @@
</li>
<li class="ulchildlink"><strong><a href="cce_10_1027.html">Switching the AOM Instance Connected to Grafana</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="en-us_topic_0000002516078019.html">Configuring Alarms for Java Applications on APM</a></strong><br>
</li>
</ul>
<div class="familylinks">

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

@ -11,7 +11,7 @@
</div>
<div class="section" id="cce_10_0841__section83941158134"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0841__ol11182813184815"><li id="cce_10_0841__li330462393220"><span>Log in to the <span id="cce_10_0841__cce_10_0004_ph18314322182">CCE console</span> and click the cluster name to access the cluster console.</span></li><li id="cce_10_0841__li1651955651312"><span>In the navigation pane, choose <strong id="cce_10_0841__b201890535353443"><span id="cce_10_0841__text9765124722315">Services &amp; Ingresses</span></strong>. In the upper right corner, click <span class="uicontrol" id="cce_10_0841__uicontrol2882149653443"><b>Create Service</b></span>.</span></li><li id="cce_10_0841__li185190567138"><span>Configure Service parameters. In this example, only mandatory parameters required for using SNI are listed. For details about how to configure other parameters, see <a href="cce_10_0681.html#cce_10_0681__section84162025538">Using the CCE Console</a>.</span><p><ul id="cce_10_0841__ul4446314017144"><li id="cce_10_0841__li6462394317144"><strong id="cce_10_0841__b1851101893514">Service Name</strong>: Specify a Service name, which can be the same as the workload name.</li><li id="cce_10_0841__li89543531070"><strong id="cce_10_0841__b183914845043028">Service Type</strong>: Select <strong id="cce_10_0841__b87235632443028">LoadBalancer</strong>.</li><li id="cce_10_0841__li43200017144"><strong id="cce_10_0841__b8342741205392">Selector</strong>: Add a label and click <strong id="cce_10_0841__b13174691915392">Confirm</strong>. The Service will use this label to select pods. You can also click <strong id="cce_10_0841__b174805016653947">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_0841__b18755929353947">OK</strong>.</li><li id="cce_10_0841__li14384123818176"><strong id="cce_10_0841__b193232001141941">Load Balancer</strong>: Select a load balancer type and creation mode.<ul id="cce_10_0841__ul589211413819"><li id="cce_10_0841__li1995101610373"><a name="cce_10_0841__li1995101610373"></a><a name="li1995101610373"></a>A load balancer can be dedicated or shared. To enable HTTP/HTTPS on the listener port of a dedicated load balancer, the type of the load balancer must be <span class="uicontrol" id="cce_10_0841__uicontrol64548119954342"><b>Application (HTTP/HTTPS)</b></span> or <span class="uicontrol" id="cce_10_0841__uicontrol87936278254342"><b>Network (TCP/UDP) &amp; Application (HTTP/HTTPS)</b></span>.</li><li id="cce_10_0841__li13266657143911">This section uses an existing load balancer as an example. For details about the parameters for automatically creating a load balancer, see <a href="cce_10_0681.html#cce_10_0681__table026610571395">Table 1</a>.</li></ul>
</li><li id="cce_10_0841__li158271501592"><strong id="cce_10_0841__b85720294244218">Port</strong><ul id="cce_10_0841__ul3499201217144"><li id="cce_10_0841__li4649265917144"><strong id="cce_10_0841__b65605381955555">Protocol</strong>: Select <strong id="cce_10_0841__b42436443655555">TCP</strong>. If you select <strong id="cce_10_0841__b14574129655555">UDP</strong>, HTTP and HTTPS will be unavailable.</li><li id="cce_10_0841__li353122153610"><strong id="cce_10_0841__b128325988855610">Service Port</strong>: the port used by the Service. The port ranges from 1 to 65535.</li><li id="cce_10_0841__li475042104417"><strong id="cce_10_0841__b31482107294">Container Port</strong>: the port that the workload listens on. For example, Nginx uses port 80 by default.</li><li id="cce_10_0841__li8911126175719"><strong id="cce_10_0841__b432164634917">Frontend Protocol</strong>: In this example, HTTPS must be enabled for the Service to use SNI. For a <a href="#cce_10_0841__li1995101610373">dedicated load balancer</a>, to use HTTP/HTTPS, the type of the load balancer must be <strong id="cce_10_0841__b11146919366">Application (HTTP/HTTPS)</strong>.</li></ul>
</li><li id="cce_10_0841__li1567510365916"><strong id="cce_10_0841__b58302540544328">Listener</strong><ul id="cce_10_0841__ul38353035910"><li id="cce_10_0841__li187883173610"><strong id="cce_10_0841__b105526309618">SSL Authentication</strong>: Select this option if <strong id="cce_10_0841__b16552730564">Frontend Protocol</strong> is set to <strong id="cce_10_0841__b175523301661">HTTPS</strong>. Dedicated load balancers are available in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later. <ul id="cce_10_0841__ul1710811473613"><li id="cce_10_0841__li1837443723520"><strong id="cce_10_0841__b267574460">One-way authentication</strong>: Only the backend server is authenticated. If you also need to authenticate the identity of the client, select two-way authentication.</li><li id="cce_10_0841__li6964158133615"><strong id="cce_10_0841__b12319195365020">Two-way authentication</strong>: Both the clients and the load balancer authenticate each other. This ensures only authenticated clients can access the load balancer. No additional backend server configuration is required if you select this option.</li></ul>
</li><li id="cce_10_0841__li1567510365916"><strong id="cce_10_0841__b58302540544328">Listener</strong><ul id="cce_10_0841__ul38353035910"><li id="cce_10_0841__li187883173610"><strong id="cce_10_0841__b105526309618">SSL Authentication</strong>: Select this option if <strong id="cce_10_0841__b16552730564">Frontend Protocol</strong> is set to <strong id="cce_10_0841__b175523301661">HTTPS</strong>. Dedicated load balancers are available in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later. <ul id="cce_10_0841__ul1710811473613"><li id="cce_10_0841__li1837443723520"><strong id="cce_10_0841__b637951000">One-way authentication</strong>: Only the backend server is authenticated. If you also need to authenticate the identity of the client, select two-way authentication.</li><li id="cce_10_0841__li6964158133615"><strong id="cce_10_0841__b12319195365020">Two-way authentication</strong>: Both the clients and the load balancer authenticate each other. This ensures only authenticated clients can access the load balancer. No additional backend server configuration is required if you select this option.</li></ul>
</li><li id="cce_10_0841__li1219103263614"><strong id="cce_10_0841__b1629193155117">CA Certificate</strong>: If <strong id="cce_10_0841__b166291837515">SSL Authentication</strong> is set to <strong id="cce_10_0841__b2063012313513">Two-way authentication</strong>, add a CA certificate to authenticate the client. A CA certificate is issued by a Certificate Authority (CA) and is used to verify the issuer of the client's certificate. If HTTPS two-way authentication is enabled, HTTPS connections can be established only if the client provides a certificate issued by a specific CA.</li><li id="cce_10_0841__li983517014595"><strong id="cce_10_0841__b714659077405">Server Certificate</strong>: Select a server certificate as the default certificate. </li><li id="cce_10_0841__li1883511013595"><strong id="cce_10_0841__b18841032142713">SNI</strong>: Add an SNI certificate containing a domain name. <p id="cce_10_0841__p166921451713">If the server cannot find an SNI certificate matching the client-requested domain name, it will return the default server certificate.</p>
</li><li id="cce_10_0841__li1027969193913"><strong id="cce_10_0841__b16572102116488">Security Policy</strong>: If <strong id="cce_10_0841__b9572122117488">Frontend Protocol</strong> is set to <strong id="cce_10_0841__b8572202104816">HTTPS</strong>, you can select a security policy. This parameter is available only in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later.</li><li id="cce_10_0841__li142441213914"><strong id="cce_10_0841__b2118799243103815">Backend Protocol</strong>: If <strong id="cce_10_0841__b139371322201610">Frontend Protocol</strong> is set to <strong id="cce_10_0841__b17937142213161">HTTPS</strong>, HTTP or HTTPS can be used to access the backend server. The default value is <strong id="cce_10_0841__b494173409103815">HTTP</strong>. This parameter is available only in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later.</li></ul>
</li></ul>
@ -68,7 +68,7 @@ spec:
<td class="cellrowborder" valign="top" width="12%" headers="mcps1.3.6.3.2.4.1.2 "><p id="cce_10_0841__p8519144510532">String</p>
</td>
<td class="cellrowborder" valign="top" width="64%" headers="mcps1.3.6.3.2.4.1.3 "><p id="cce_10_0841__p1266517186536">ID of an ELB certificate, which is used as the HTTPS server certificate.</p>
<p id="cce_10_0841__p6842101018719">How to obtain: Log in to the <span id="cce_10_0841__ph181898315611">ELB console</span> and choose <strong id="cce_10_0841__b177919597389">Certificates</strong>. In the load balancer list, copy the ID under the target certificate name.</p>
<p id="cce_10_0841__p6842101018719">How to obtain: Log in to the <span id="cce_10_0841__ph181898315611">ELB console</span> and choose <strong id="cce_10_0841__b177919597389">Certificates</strong>. In the certificate list, copy the ID under the target certificate name.</p>
</td>
</tr>
<tr id="cce_10_0841__row189919913017"><td class="cellrowborder" valign="top" width="24%" headers="mcps1.3.6.3.2.4.1.1 "><p id="cce_10_0841__p1887122073013">kubernetes.io/elb.tls-certificate-ids</p>

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

@ -10,7 +10,7 @@
</div>
<div class="section" id="cce_10_0842__section112955584"><h4 class="sectiontitle">Using the CCE Console</h4><ol id="cce_10_0842__ol11182813184815"><li id="cce_10_0842__li330462393220"><span>Log in to the <span id="cce_10_0842__cce_10_0004_ph18314322182">CCE console</span> and click the cluster name to access the cluster console.</span></li><li id="cce_10_0842__li1651955651312"><span>In the navigation pane, choose <strong id="cce_10_0842__b119360049953444"><span id="cce_10_0842__text9765124722315">Services &amp; Ingresses</span></strong>. In the upper right corner, click <span class="uicontrol" id="cce_10_0842__uicontrol160898021553444"><b>Create Service</b></span>.</span></li><li id="cce_10_0842__li185190567138"><span>Configure Service parameters. In this example, only mandatory parameters are listed. For details about how to configure other parameters, see <a href="cce_10_0681.html#cce_10_0681__section84162025538">Using the CCE Console</a>.</span><p><ul id="cce_10_0842__ul4446314017144"><li id="cce_10_0842__li6462394317144"><strong id="cce_10_0842__b114677863842449">Service Name</strong>: Specify a Service name, which can be the same as the workload name.</li><li id="cce_10_0842__li89543531070"><strong id="cce_10_0842__b190685509043029">Service Type</strong>: Select <strong id="cce_10_0842__b105165345543029">LoadBalancer</strong>.</li><li id="cce_10_0842__li43200017144"><strong id="cce_10_0842__b12655684945393">Selector</strong>: Add a label and click <strong id="cce_10_0842__b1390317105393">Confirm</strong>. The Service will use this label to select pods. You can also click <strong id="cce_10_0842__b212286449353948">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_0842__b25887632553948">OK</strong>.</li><li id="cce_10_0842__li14384123818176"><strong id="cce_10_0842__b103001266141942">Load Balancer</strong>: Select a load balancer type and creation mode.<ul id="cce_10_0842__ul589211413819"><li id="cce_10_0842__li1995101610373"><a name="cce_10_0842__li1995101610373"></a><a name="li1995101610373"></a>A load balancer can be dedicated or shared. To enable HTTP/HTTPS on the listener port of a dedicated load balancer, the type of the load balancer must be <span class="uicontrol" id="cce_10_0842__uicontrol65106158254343"><b>Application (HTTP/HTTPS)</b></span> or <span class="uicontrol" id="cce_10_0842__uicontrol161484302054343"><b>Network (TCP/UDP) &amp; Application (HTTP/HTTPS)</b></span>.</li><li id="cce_10_0842__li13266657143911">This section uses an existing load balancer as an example. For details about the parameters for automatically creating a load balancer, see <a href="cce_10_0681.html#cce_10_0681__table026610571395">Table 1</a>.</li></ul>
</li><li id="cce_10_0842__li158271501592"><strong id="cce_10_0842__b133787816944219">Port</strong><ul id="cce_10_0842__ul3499201217144"><li id="cce_10_0842__li4649265917144"><strong id="cce_10_0842__b13964133019298">Protocol</strong>: Select <strong id="cce_10_0842__b19965163020292">TCP</strong>. If you select <strong id="cce_10_0842__b59651830152912">UDP</strong>, HTTP and HTTPS will be unavailable.</li><li id="cce_10_0842__li353122153610"><strong id="cce_10_0842__b69081136355610">Service Port</strong>: the port used by the Service. The port ranges from 1 to 65535.</li><li id="cce_10_0842__li475042104417"><strong id="cce_10_0842__b98583464761352">Container Port</strong>: the port that the workload listens on. For example, Nginx uses port 80 by default.</li><li id="cce_10_0842__li8911126175719"><strong id="cce_10_0842__b145662413914">Frontend Protocol</strong>: In this example, HTTPS must be enabled for the Service to use HTTP/2. For a <a href="#cce_10_0842__li1995101610373">dedicated load balancer</a>, to use HTTP/HTTPS, the type of the load balancer must be <strong id="cce_10_0842__b12781201317362">Application (HTTP/HTTPS)</strong>.</li></ul>
</li><li id="cce_10_0842__li1567510365916"><strong id="cce_10_0842__b176682727844329">Listener</strong><ul id="cce_10_0842__ul38353035910"><li id="cce_10_0842__li187883173610">SSL authentication is available only in dedicated load balancers in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later versions. <ul id="cce_10_0842__ul1710811473613"><li id="cce_10_0842__li1837443723520"><strong id="cce_10_0842__b2028005243">One-way authentication</strong>: Only the backend server is authenticated. If you also need to authenticate the identity of the client, select two-way authentication.</li><li id="cce_10_0842__li6964158133615"><strong id="cce_10_0842__b987718476303">Two-way authentication</strong>: Both the clients and the load balancer authenticate each other. This ensures only authenticated clients can access the load balancer. No additional backend server configuration is required if you select this option.</li></ul>
</li><li id="cce_10_0842__li1567510365916"><strong id="cce_10_0842__b176682727844329">Listener</strong><ul id="cce_10_0842__ul38353035910"><li id="cce_10_0842__li187883173610">SSL authentication is available only in dedicated load balancers in clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later versions. <ul id="cce_10_0842__ul1710811473613"><li id="cce_10_0842__li1837443723520"><strong id="cce_10_0842__b245045275">One-way authentication</strong>: Only the backend server is authenticated. If you also need to authenticate the identity of the client, select two-way authentication.</li><li id="cce_10_0842__li6964158133615"><strong id="cce_10_0842__b987718476303">Two-way authentication</strong>: Both the clients and the load balancer authenticate each other. This ensures only authenticated clients can access the load balancer. No additional backend server configuration is required if you select this option.</li></ul>
</li><li id="cce_10_0842__li1219103263614"><strong id="cce_10_0842__b10247115843010">CA Certificate</strong>: If <strong id="cce_10_0842__b1224711587303">SSL Authentication</strong> is set to <strong id="cce_10_0842__b202471958153017">Two-way authentication</strong>, add a CA certificate to authenticate the client. A CA certificate is issued by a Certificate Authority (CA) and is used to verify the issuer of the client's certificate. If HTTPS two-way authentication is enabled, HTTPS connections can be established only if the client provides a certificate issued by a specific CA.</li><li id="cce_10_0842__li983517014595"><strong id="cce_10_0842__b01886592409">Server Certificate</strong>: Select a server certificate when HTTPS is used. </li><li id="cce_10_0842__li1883511013595"><strong id="cce_10_0842__b500300385103450">SNI</strong>: Add an SNI certificate containing a domain name. </li><li id="cce_10_0842__li6249544109"><strong id="cce_10_0842__b14281826103614">Advanced Options</strong>: Click <strong id="cce_10_0842__b042882618363">Add advanced options</strong> and enable HTTP/2.</li></ul>
</li></ul>
</p></li><li id="cce_10_0842__li179082217613"><span>Click <strong id="cce_10_0842__b758203002019">OK</strong>.</span></li></ol>
@ -70,7 +70,7 @@ spec:
<td class="cellrowborder" valign="top" width="11.4%" headers="mcps1.3.5.5.2.4.1.2 "><p id="cce_10_0842__p8519144510532">String</p>
</td>
<td class="cellrowborder" valign="top" width="61.68%" headers="mcps1.3.5.5.2.4.1.3 "><p id="cce_10_0842__p1266517186536">ID of an ELB certificate, which is used as the HTTPS server certificate.</p>
<p id="cce_10_0842__p266917129452">How to obtain: Log in to the <span id="cce_10_0842__ph181898315611">ELB console</span> and choose <strong id="cce_10_0842__b9784370624495">Certificates</strong>. In the load balancer list, copy the ID under the target certificate name.</p>
<p id="cce_10_0842__p266917129452">How to obtain: Log in to the <span id="cce_10_0842__ph181898315611">ELB console</span> and choose <strong id="cce_10_0842__b9784370624495">Certificates</strong>. In the certificate list, copy the ID under the target certificate name.</p>
</td>
</tr>
<tr id="cce_10_0842__row1068843915351"><td class="cellrowborder" valign="top" width="26.919999999999998%" headers="mcps1.3.5.5.2.4.1.1 "><p id="cce_10_0842__p3286145014363">kubernetes.io/elb.http2-enable</p>

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

@ -57,7 +57,7 @@
<td class="cellrowborder" valign="top" width="13.021302130213023%" headers="mcps1.3.6.2.3.2.1.1.4.1.4.1.2 "><p id="cce_10_0947__p16546252112814">String</p>
</td>
<td class="cellrowborder" valign="top" width="53.64536453645364%" headers="mcps1.3.6.2.3.2.1.1.4.1.4.1.3 "><p id="cce_10_0947__p15790747103112">ID of the ELB certificate.</p>
<p id="cce_10_0947__p73661022182818">To obtain the certificate, log in to the CCE console, choose <strong id="cce_10_0947__b1491218249446">Service List</strong> &gt; <strong id="cce_10_0947__b391342410443">Networking</strong> &gt; <strong id="cce_10_0947__b49139245444">Elastic Load Balance</strong>, and click <strong id="cce_10_0947__b2913224154410">Certificates</strong> in the navigation pane. In the load balancer list, copy the ID under the target certificate name.</p>
<p id="cce_10_0947__p73661022182818">To obtain the certificate, log in to the CCE console, choose <strong id="cce_10_0947__b1491218249446">Service List</strong> &gt; <strong id="cce_10_0947__b391342410443">Networking</strong> &gt; <strong id="cce_10_0947__b49139245444">Elastic Load Balance</strong>, and click <strong id="cce_10_0947__b2913224154410">Certificates</strong> in the navigation pane. In the certificate list, copy the ID under the target certificate name.</p>
</td>
</tr>
</tbody>

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

@ -28,7 +28,7 @@
</tr>
<tr id="cce_bestpractice_0307__row142701925191817"><td class="cellrowborder" valign="top" headers="mcps1.3.2.4.1.2.4.1.1 "><p id="cce_bestpractice_0307__p527042511814">PersistentVolumes (PVs) mounted to containers</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.4.1.2.4.1.2 "><p id="cce_bestpractice_0307__p1227022517184">Due to restrictions of the restic tool, migration is not supported for the hostPath storage volume. For details about how to solve the problem, see <a href="cce_bestpractice_0314.html#cce_bestpractice_0314__section11197194820367">Storage Volumes of the HostPath Type Cannot Be Backed Up</a>.</p>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.4.1.2.4.1.2 "><p id="cce_bestpractice_0307__p1227022517184">Due to restrictions of the restic tool, migration is not supported for the hostPath storage volume. For details about how to solve the problem, see <a href="cce_bestpractice_0314.html#cce_bestpractice_0314__section11197194820367">hostPath Volumes Cannot Be Backed Up</a>.</p>
</td>
</tr>
<tr id="cce_bestpractice_0307__row17561521201920"><td class="cellrowborder" rowspan="3" valign="top" width="18.371837183718373%" headers="mcps1.3.2.4.1.2.4.1.1 "><p id="cce_bestpractice_0307__p16561521131919">Resources outside a cluster</p>

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

@ -1,7 +1,7 @@
<a name="cce_bestpractice_0314"></a><a name="cce_bestpractice_0314"></a>
<h1 class="topictitle1">Troubleshooting</h1>
<div id="body0000001217423605"><div class="section" id="cce_bestpractice_0314__section11197194820367"><a name="cce_bestpractice_0314__section11197194820367"></a><a name="section11197194820367"></a><h4 class="sectiontitle">Storage Volumes of the HostPath Type Cannot Be Backed Up</h4><p id="cce_bestpractice_0314__p47071330142913">Both hostPath and local volumes are local storage volumes. However, restic, which is integrated into Velero, cannot back up hostPath PVs. It only supports the local type. So, you need to replace the storage volumes of the hostPath type with the local type in the source cluster.</p>
<div id="body0000001217423605"><div class="section" id="cce_bestpractice_0314__section11197194820367"><a name="cce_bestpractice_0314__section11197194820367"></a><a name="section11197194820367"></a><h4 class="sectiontitle">hostPath Volumes Cannot Be Backed Up</h4><p id="cce_bestpractice_0314__p47071330142913">Both hostPath and local volumes are local storage volumes. However, restic, which is integrated into Velero, cannot back up hostPath PVs. It only supports the local type. So, you need to replace the storage volumes of the hostPath type with the local type in the source cluster.</p>
<div class="note" id="cce_bestpractice_0314__note1315018672419"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_bestpractice_0314__p171503692410">It is recommended that Local volumes be used in Kubernetes v1.10 or later and can only be statically created. For details, see <a href="https://kubernetes.io/docs/concepts/storage/volumes/#local" target="_blank" rel="noopener noreferrer">local</a>.</p>
</div></div>
<ol id="cce_bestpractice_0314__ol1490212317367"><li id="cce_bestpractice_0314__li790253163613"><span>Create a storage class for the Local volume.</span><p><div class="p" id="cce_bestpractice_0314__p2575101774514">Example YAML:<pre class="screen" id="cce_bestpractice_0314__screen563461684510">apiVersion: storage.k8s.io/v1

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

@ -98,13 +98,13 @@ spec:
</div>
</p></li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li1597836795"><span>After the creation is complete, log in to the container. The content of the <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b20348529161919">/var/run/secrets/tokens/oidc-token</strong> file is the service account token generated by Kubernetes.</span><p><div class="note" id="cce_bestpractice_0333__en-us_topic_0000001280331044_note209921935201012"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p999210357107">If the service account token is valid for more than 24 hours or 80% of its expiration time, kubelet will automatically rotate the service account token.</p>
</div></div>
</p></li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li89609511115"><span>Use the OIDC token to call the API for <a href="https://docs.otc.t-systems.com/en-us/api/iam/iam_13_0605.html" target="_blank" rel="noopener noreferrer">Obtaining a Token with an OpenID Connect ID Token</a>. The <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b21822532317">X-Subject-Token</strong> field in the response header is the IAM token. Then, you can use this token to access cloud services.</span><p><p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p8607177517">The following shows an example:</p>
<pre class="screen" id="cce_bestpractice_0333__en-us_topic_0000001280331044_screen12632921195416">curl -i --location --request POST 'https://<strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b181044375517"><i><span class="varname" id="cce_bestpractice_0333__en-us_topic_0000001280331044_varname2037412543141">{{iam endpoint}}</span></i></strong>/v3.0/OS-AUTH/id-token/tokens' \
</p></li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li89609511115"><span>Use the OIDC token to call the API for <a href="https://docs.otc.t-systems.com/en-us/api/iam/iam_13_0605.html" target="_blank" rel="noopener noreferrer">Obtaining a Token with an OpenID Connect ID Token</a>. The <strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b1989232810114">X-Subject-Token</strong> field in the response header is the IAM token. Then, you can use this token to access cloud services.</span><p><p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p8607177517">The following shows an example:</p>
<pre class="screen" id="cce_bestpractice_0333__en-us_topic_0000001280331044_screen12632921195416">curl -iv --location --request POST 'https://<strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b181044375517"><i><span class="varname" id="cce_bestpractice_0333__en-us_topic_0000001280331044_varname2037412543141">{{iam endpoint}}</span></i></strong>/v3.0/OS-AUTH/id-token/tokens' \
--header '<strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b1067820478568">X-Idp-Id: <i><span class="varname" id="cce_bestpractice_0333__en-us_topic_0000001280331044_varname8889551205611">workload_identity</span></i></strong>' \
--header 'Content-Type: application/json' \
--data @<strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b1830152521417"><i><span class="varname" id="cce_bestpractice_0333__en-us_topic_0000001280331044_varname216110454146">token_body.json</span></i></strong></pre>
<p id="cce_bestpractice_0333__en-us_topic_0000001280331044_p467644104113">Where:</p>
<ul id="cce_bestpractice_0333__en-us_topic_0000001280331044_ul1167285918426"><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li12672145944213"><em id="cce_bestpractice_0333__en-us_topic_0000001280331044_i169162411237">{{iam endpoint}}</em> indicates the endpoint of IAM. For details, see <a href="https://docs.otc.t-systems.com/regions-and-endpoints/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li0673259144213"><em id="cce_bestpractice_0333__en-us_topic_0000001280331044_i19622335114818">workload_identity</em> is the identity provider name, which is the same as that configured in <a href="#cce_bestpractice_0333__en-us_topic_0000001280331044_section18167152865013">Step 2: Configure an Identity Provider</a>.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li067305914215"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b756886131510">token_body.json</strong> is a local file and its content is as follows:<pre class="screen" id="cce_bestpractice_0333__en-us_topic_0000001280331044_screen16886553181715"> {
<ul id="cce_bestpractice_0333__en-us_topic_0000001280331044_ul1167285918426"><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li12672145944213"><em id="cce_bestpractice_0333__en-us_topic_0000001280331044_i3232135141111">{{iam endpoint}}</em> indicates the endpoint of IAM. For details, see <a href="https://docs.otc.t-systems.com/regions-and-endpoints/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li0673259144213"><em id="cce_bestpractice_0333__en-us_topic_0000001280331044_i19622335114818">workload_identity</em> is the identity provider name, which is the same as that configured in <a href="#cce_bestpractice_0333__en-us_topic_0000001280331044_section18167152865013">Step 2: Configure an Identity Provider</a>.</li><li id="cce_bestpractice_0333__en-us_topic_0000001280331044_li067305914215"><strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b756886131510">token_body.json</strong> is a local file and its content is as follows:<pre class="screen" id="cce_bestpractice_0333__en-us_topic_0000001280331044_screen16886553181715"> {
"auth" : {
"id_token" : {
<strong id="cce_bestpractice_0333__en-us_topic_0000001280331044_b19576175817239">"id" : <i><span class="varname" id="cce_bestpractice_0333__en-us_topic_0000001280331044_varname1664085112234">"eyJhbGciOiJSU..."</span></i></strong>

BIN
docs/cce/umn/en-us_image_0000001696678850.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 565 B

BIN
docs/cce/umn/en-us_image_0000001744598325.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 32 KiB

BIN
docs/cce/umn/en-us_image_0000001744678489.jpg
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 744 B

BIN
docs/cce/umn/en-us_image_0000001758618249.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 19 KiB

BIN
docs/cce/umn/en-us_image_0000001942942816.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 38 KiB

BIN
docs/cce/umn/en-us_image_0000002359774578.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 180 B

BIN
docs/cce/umn/en-us_image_0000002516079173.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 58 KiB

86
docs/cce/umn/en-us_topic_0000002516078019.html Normal file
View File

@ -0,0 +1,86 @@
<a name="EN-US_TOPIC_0000002516078019"></a><a name="EN-US_TOPIC_0000002516078019"></a>
<h1 class="topictitle1">Configuring Alarms for Java Applications on APM</h1>
<div id="body0000002473587749"><p id="EN-US_TOPIC_0000002516078019__p376610485194">Application Performance Management (APM) monitors and manages the performance and faults of cloud applications in real time. It helps O&amp;M personnel detect performance bottlenecks and identify fault causes, ensuring user experience. To monitor a Java workload that is deployed in a CCE standard or Turbo cluster, simply enable APM probes. There is no need to modify code. The APM probes help identify errors and slow APIs, reproduce calling parameters, and detect system bottlenecks. This greatly improves the efficiency of diagnosing online problems.</p>
<p id="EN-US_TOPIC_0000002516078019__p8060118">APM allows you to configure application alarms to quickly learn about the service exceptions and rectify the faults to avoid service loss. APM provides recommended basic alarm templates. For example, you can detect the JVM memory pressure in advance through garbage collection (GC) alarms.</p>
<div class="section" id="EN-US_TOPIC_0000002516078019__section0518620205812"><h4 class="sectiontitle">Configuring APM</h4><ol id="EN-US_TOPIC_0000002516078019__ol14424361089"><li id="EN-US_TOPIC_0000002516078019__li330462393220"><span>Log in to the <span id="EN-US_TOPIC_0000002516078019__cce_10_0004_ph18314322182">CCE console</span> and click the cluster name to access the cluster console.</span></li><li id="EN-US_TOPIC_0000002516078019__li2075471341"><span>In the navigation pane, choose <span class="uicontrol" id="EN-US_TOPIC_0000002516078019__uicontrol773134013469"><b>Workloads</b></span>. In the upper right corner of the displayed page, click <span class="uicontrol" id="EN-US_TOPIC_0000002516078019__uicontrol373154034614"><b>Create Workload</b></span>.</span></li><li id="EN-US_TOPIC_0000002516078019__li1996294115"><span>In the <span class="uicontrol" id="EN-US_TOPIC_0000002516078019__uicontrol15740514165212"><b>Advanced Settings</b></span> area, click <strong id="EN-US_TOPIC_0000002516078019__b7741121425211">APM Settings</strong> and enable a probe. APM 2.0 is recommended.</span></li><li id="EN-US_TOPIC_0000002516078019__li10424369815"><span>Configure probe parameters. For details, see <a href="cce_10_0055.html">Configuring APM</a>.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="EN-US_TOPIC_0000002516078019__table15800314167" frame="border" border="1" rules="all"><caption><b>Table 1 </b>APM 2.0 probe parameter settings</caption><thead align="left"><tr id="EN-US_TOPIC_0000002516078019__cce_10_0055_row857933111169"><th align="left" class="cellrowborder" valign="top" width="9.68096809680968%" id="mcps1.3.3.2.4.2.1.2.4.1.1"><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p17579193118161">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="13.121312131213122%" id="mcps1.3.3.2.4.2.1.2.4.1.2"><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p85795314162">Example Value</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="77.1977197719772%" id="mcps1.3.3.2.4.2.1.2.4.1.3"><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p457993118164">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="EN-US_TOPIC_0000002516078019__cce_10_0055_row1557911311162"><td class="cellrowborder" valign="top" width="9.68096809680968%" headers="mcps1.3.3.2.4.2.1.2.4.1.1 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p12579831181619">Probe Version</p>
</td>
<td class="cellrowborder" valign="top" width="13.121312131213122%" headers="mcps1.3.3.2.4.2.1.2.4.1.2 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p3579931131612">2.5.2</p>
</td>
<td class="cellrowborder" valign="top" width="77.1977197719772%" headers="mcps1.3.3.2.4.2.1.2.4.1.3 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p157920314168">Select a probe version as required based on the following considerations:</p>
<ul id="EN-US_TOPIC_0000002516078019__cce_10_0055_ul135791631181610"><li id="EN-US_TOPIC_0000002516078019__cce_10_0055_li1557963121613">The <strong id="EN-US_TOPIC_0000002516078019__cce_10_0055_b135413011338">latest</strong> probe version does not necessarily correspond to the most recent version. For details about the probe capabilities of different versions, see <a href="https://docs.otc.t-systems.com/application-performance-management/umn/service_overview/javaagent_updates.html" target="_blank" rel="noopener noreferrer">JavaAgent Updates</a>.</li><li id="EN-US_TOPIC_0000002516078019__cce_10_0055_li85791731171614">Probes support multiple CPU architectures (such as x86 and Arm). Select a probe version matching the architecture of the node where the workload is deployed. If the probe version does not contain <strong id="EN-US_TOPIC_0000002516078019__cce_10_0055_b66781211207">x86_64</strong> or <strong id="EN-US_TOPIC_0000002516078019__cce_10_0055_b36781821502">aarch64</strong>, CCE will align it with the node architecture.</li></ul>
</td>
</tr>
<tr id="EN-US_TOPIC_0000002516078019__cce_10_0055_row185791531131610"><td class="cellrowborder" valign="top" width="9.68096809680968%" headers="mcps1.3.3.2.4.2.1.2.4.1.1 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p2579203151612">Probe Upgrade Policy</p>
</td>
<td class="cellrowborder" valign="top" width="13.121312131213122%" headers="mcps1.3.3.2.4.2.1.2.4.1.2 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p175798317164">Auto upgrade upon restart</p>
</td>
<td class="cellrowborder" valign="top" width="77.1977197719772%" headers="mcps1.3.3.2.4.2.1.2.4.1.3 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p1157993161619">Select an option to define how a probe will be upgraded. It defaults to <strong id="EN-US_TOPIC_0000002516078019__cce_10_0055_b222211614198">Auto upgrade upon restart</strong>. Options include:</p>
<ul id="EN-US_TOPIC_0000002516078019__cce_10_0055_ul19579143119163"><li id="EN-US_TOPIC_0000002516078019__cce_10_0055_li1257910312166"><strong id="EN-US_TOPIC_0000002516078019__cce_10_0055_b119110250192">Auto upgrade upon restart</strong>: The probe image is always re-downloaded when the workload restarts.</li><li id="EN-US_TOPIC_0000002516078019__cce_10_0055_li5579631141618"><strong id="EN-US_TOPIC_0000002516078019__cce_10_0055_b16539142192017">Manual upgrade upon restart</strong>: If the probe image is available locally, the local image will be used. Otherwise, the image will be re-downloaded.</li></ul>
</td>
</tr>
<tr id="EN-US_TOPIC_0000002516078019__cce_10_0055_row1858093161612"><td class="cellrowborder" valign="top" width="9.68096809680968%" headers="mcps1.3.3.2.4.2.1.2.4.1.1 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p358063110169">APM Environment</p>
</td>
<td class="cellrowborder" valign="top" width="13.121312131213122%" headers="mcps1.3.3.2.4.2.1.2.4.1.2 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p158053181617">N/A</p>
</td>
<td class="cellrowborder" valign="top" width="77.1977197719772%" headers="mcps1.3.3.2.4.2.1.2.4.1.3 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p13580103114161">(Optional) Enter an environment name. APM will create an environment for the workload. APM environments help distinguish performance data across different deployment phases, such as production and testing, for classified management and precise analysis of application performance.</p>
</td>
</tr>
<tr id="EN-US_TOPIC_0000002516078019__cce_10_0055_row0580143141611"><td class="cellrowborder" valign="top" width="9.68096809680968%" headers="mcps1.3.3.2.4.2.1.2.4.1.1 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p9580631101612">APM App</p>
</td>
<td class="cellrowborder" valign="top" width="13.121312131213122%" headers="mcps1.3.3.2.4.2.1.2.4.1.2 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p1758010315168">default</p>
</td>
<td class="cellrowborder" valign="top" width="77.1977197719772%" headers="mcps1.3.3.2.4.2.1.2.4.1.3 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p658012315167">Select an existing application from APM. APM applications help organize monitoring data by function module, allowing unified management and analysis.</p>
</td>
</tr>
<tr id="EN-US_TOPIC_0000002516078019__cce_10_0055_row185809314167"><td class="cellrowborder" valign="top" width="9.68096809680968%" headers="mcps1.3.3.2.4.2.1.2.4.1.1 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p19580193131617">Sub-app</p>
</td>
<td class="cellrowborder" valign="top" width="13.121312131213122%" headers="mcps1.3.3.2.4.2.1.2.4.1.2 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p15580431161618">N/A</p>
</td>
<td class="cellrowborder" valign="top" width="77.1977197719772%" headers="mcps1.3.3.2.4.2.1.2.4.1.3 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p75801231121613">(Optional) Enter an APM sub-application name for more refined management.</p>
<p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p85801031171614">If the sub-application already exists in APM, the workload will be associated with the sub-application. Otherwise, CCE will create the specified sub-application.</p>
</td>
</tr>
<tr id="EN-US_TOPIC_0000002516078019__cce_10_0055_row1558073117162"><td class="cellrowborder" valign="top" width="9.68096809680968%" headers="mcps1.3.3.2.4.2.1.2.4.1.1 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p958018312165">Access Key</p>
</td>
<td class="cellrowborder" valign="top" width="13.121312131213122%" headers="mcps1.3.3.2.4.2.1.2.4.1.2 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p11580143131617"><strong id="EN-US_TOPIC_0000002516078019__cce_10_0055_b4491341132113">AK:</strong> <em id="EN-US_TOPIC_0000002516078019__cce_10_0055_i2757183611218">xxx</em></p>
<p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p45801331191613"><strong id="EN-US_TOPIC_0000002516078019__cce_10_0055_b1152605162118">SK:</strong> <em id="EN-US_TOPIC_0000002516078019__cce_10_0055_i3277344142112">xxx</em></p>
</td>
<td class="cellrowborder" valign="top" width="77.1977197719772%" headers="mcps1.3.3.2.4.2.1.2.4.1.3 "><p id="EN-US_TOPIC_0000002516078019__cce_10_0055_p1758083112165">Enter the APM AK/SK, which are used to obtain the permissions to report data. <strong id="EN-US_TOPIC_0000002516078019__cce_10_0055_b458073118169">CCE will retrieve the APM AK/SK for you.</strong></p>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="EN-US_TOPIC_0000002516078019__li186296116411"><span>Configure other parameters and click <span class="uicontrol" id="EN-US_TOPIC_0000002516078019__uicontrol86186242521"><b>Create Workload</b></span>. After the workload status changes to <strong id="EN-US_TOPIC_0000002516078019__b166511526195214">Running</strong>, wait for about 3 minutes. The application data will be displayed on the APM console.</span></li></ol>
</div>
<div class="section" id="EN-US_TOPIC_0000002516078019__section1026011611310"><h4 class="sectiontitle">Configuring GC Alarms for Applications on APM</h4><p id="EN-US_TOPIC_0000002516078019__p2746101315506">You can create an alarm policy based on the GC alarm template on APM and apply the alarm policy to the CCE cluster. For details, see <a href="https://docs.otc.t-systems.com/application-performance-management/umn/alarm_management/alarm_policies/recommended_alarm_templates.html" target="_blank" rel="noopener noreferrer">Recommended Alarm Templates</a>.</p>
<ol id="EN-US_TOPIC_0000002516078019__ol19316731171319"><li id="EN-US_TOPIC_0000002516078019__li29627313133"><span>Log in to the <span id="EN-US_TOPIC_0000002516078019__ph10127154519139">APM console</span>.</span></li><li id="EN-US_TOPIC_0000002516078019__li1896263112133"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000002516078019__b05013011584">Application Monitoring</strong> &gt; <strong id="EN-US_TOPIC_0000002516078019__b135377313584">Metrics</strong>. In the navigation tree, click the target application to access its metric details page.</span></li><li id="EN-US_TOPIC_0000002516078019__li1669891310484"><span>Switch to the <span class="uicontrol" id="EN-US_TOPIC_0000002516078019__uicontrol18611440103719"><b>Alarm Templates</b></span> tab and click <span class="uicontrol" id="EN-US_TOPIC_0000002516078019__uicontrol142331646113714"><b>Recommended Templates</b></span> to view the configured alarm templates.</span><p><p id="EN-US_TOPIC_0000002516078019__p11774744173616"></p>
<p id="EN-US_TOPIC_0000002516078019__p2092755815425"></p>
</p></li><li id="EN-US_TOPIC_0000002516078019__li18838111034918"><span>Locate the GC template and click <strong id="EN-US_TOPIC_0000002516078019__b133881026713">Copy</strong> in the <strong id="EN-US_TOPIC_0000002516078019__b414145718106">Operation</strong> column to copy the recommended template to the template list. You can define the template name as needed.</span><p><p id="EN-US_TOPIC_0000002516078019__p53809612715"></p>
<p id="EN-US_TOPIC_0000002516078019__p1913176073"></p>
</p></li><li id="EN-US_TOPIC_0000002516078019__li1190725434919"><span>Click <strong id="EN-US_TOPIC_0000002516078019__b066817235114">Yes</strong>. The copied alarm template is displayed on the template list.</span></li><li id="EN-US_TOPIC_0000002516078019__li108910274386"><span>Click <strong id="EN-US_TOPIC_0000002516078019__b1855628191512">Modify</strong> in the <strong id="EN-US_TOPIC_0000002516078019__b115562851514">Operation</strong> column and bind the node to make the copied template to take effect. In this example, select <strong id="EN-US_TOPIC_0000002516078019__b206081436175314">All</strong> for <strong id="EN-US_TOPIC_0000002516078019__b2781716131610">Node Type</strong>. New nodes will be automatically bound. This means if a workload added to a CCE cluster is connected to APM, the workload will be automatically bound to the alarm template.</span><p><div class="note" id="EN-US_TOPIC_0000002516078019__note1534318542713"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="EN-US_TOPIC_0000002516078019__p163437518279">The nodes here refer to those in the application directory tree, not the nodes defined in Kubernetes clusters.</p>
</div></div>
<p id="EN-US_TOPIC_0000002516078019__p7258551201712"></p>
<p id="EN-US_TOPIC_0000002516078019__p20811160144313"></p>
</p></li></ol>
</div>
<div class="section" id="EN-US_TOPIC_0000002516078019__section1678114586546"><h4 class="sectiontitle">Viewing GC Alarms of an Application</h4><ol id="EN-US_TOPIC_0000002516078019__ol1770518281559"><li id="EN-US_TOPIC_0000002516078019__li5567103455512"><span>Log in to the <span id="EN-US_TOPIC_0000002516078019__ph1356713344552">APM console</span>.</span></li><li id="EN-US_TOPIC_0000002516078019__li165586126562"><span>In the navigation pane, choose <strong id="EN-US_TOPIC_0000002516078019__b1634620227235">Alarm Center</strong> &gt; <strong id="EN-US_TOPIC_0000002516078019__b317319253233">Alarms</strong>. Select an application from the application drop-down list and view alarms of the application.</span><p><p id="EN-US_TOPIC_0000002516078019__p1136919541482">For details about how to configure the notification receiving mode (such as email or SMS), see <a href="https://docs.otc.t-systems.com/application-performance-management/umn/alarm_management/alarm_notification.html" target="_blank" rel="noopener noreferrer">Alarm Notification</a>.</p>
</p></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0811.html">O&amp;M Best Practices</a></div>
</div>
</div>