forked from docs/doc-exports
Compare commits
1 Commits
hcdc3
...
cce_umn_20
| Author | SHA1 | Date | |
|---|---|---|---|
| af58d555be |
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -8,7 +8,31 @@
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<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>
|
||||
<tbody><tr id="cce_01_0300__row3809184972218"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p2810134916225">2025-03-12</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p1913318296232">Add:</p>
|
||||
<ul id="cce_01_0300__ul10133192915237"><li id="cce_01_0300__li1213317296237">Supported SFS 3.0, Added <a href="cce_10_0914.html">Creating an SFS Subdirectory Using a Dynamic PV</a>.</li></ul>
|
||||
<p id="cce_01_0300__p1752113714233">Update:</p>
|
||||
<ul id="cce_01_0300__ul12752133717238"><li id="cce_01_0300__li1752123782310">Supported SFS 3.0, Updated <a href="cce_10_0111.html">Scalable File Service</a>.</li><li id="cce_01_0300__li14412143710354">Updated <a href="cce_10_0212.html">Deleting a Cluster</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_01_0300__row176951955145713"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p2695135595716">2025-03-10</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p13369114325817">Add:</p>
|
||||
<ul id="cce_01_0300__ul53691243145816"><li id="cce_01_0300__li18369154315583">Added <a href="cce_10_0416.html">Cloud Native Log Collection</a>.</li><li id="cce_01_0300__li1821495310520">Added <a href="cce_10_0799.html">FAQ</a>.</li><li id="cce_01_0300__li197821142755">Added <a href="cce_bestpractice_10021.html">Reporting Prometheus Monitoring Data to a Third-Party Monitoring Platform</a>.</li></ul>
|
||||
<p id="cce_01_0300__p786213367018">Update:</p>
|
||||
<ul id="cce_01_0300__ul12862173616011"><li id="cce_01_0300__li15862103618010">Updated <a href="cce_10_0553.html">Logging</a>.</li><li id="cce_01_0300__li246418364115">Updated <a href="cce_10_0028.html">Creating a CCE Standard/Turbo Cluster</a>.</li></ul>
|
||||
<p id="cce_01_0300__p1517175911">Delete:</p>
|
||||
<ul id="cce_01_0300__ul10511195911"><li id="cce_01_0300__li154113599">Deleted "Kubernetes Version Policy".</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_01_0300__row8219537163217"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p162191037193218">2025-02-28</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><p id="cce_01_0300__p13785184816323">Update:</p>
|
||||
<ul id="cce_01_0300__ul18785104819325"><li id="cce_01_0300__li12785104843215">Updated <a href="cce_10_0150.html">Creating a Job</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<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>
|
||||
@ -21,7 +45,7 @@
|
||||
<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>
|
||||
<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__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>
|
||||
@ -78,7 +102,7 @@
|
||||
</tr>
|
||||
<tr id="cce_01_0300__row058713234347"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p25882023143415">2024-06-26</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><ul id="cce_01_0300__ul118110437342"><li id="cce_01_0300__li38254316343">Supported the creation of clusters of v1.29. For details, see <a href="cce_bulletin_0089.html">Kubernetes 1.29 Release Notes</a> and <a href="cce_10_0405.html">Patch Version Release Notes</a>.</li><li id="cce_01_0300__li668895417342">Added the Cloud Native Cluster Monitoring add-on. For details, see <a href="cce_10_0406.html">Cloud Native Cluster Monitoring</a>.</li><li id="cce_01_0300__li16457344123612">Added <a href="cce_10_0373.html">Monitoring Custom Metrics Using Cloud Native Cluster Monitoring</a>.</li><li id="cce_01_0300__li19403177171618">Deleted section "Kubernetes Version Support Mechanism".</li><li id="cce_01_0300__li184038711166">Added <a href="cce_bulletin_0033.html">Kubernetes Version Policy</a>.</li><li id="cce_01_0300__li7668108144413">Added <a href="cce_10_0734.html">Configuring an EIP for a Pod</a>.</li><li id="cce_01_0300__li1389051010459">Added <a href="cce_10_0651.html">Configuring a Static EIP for a Pod</a>.</li><li id="cce_01_0300__li14982191412301">Update <a href="cce_10_0476.html">Node OS</a>.</li><li id="cce_01_0300__li38112312311">Update <a href="cce_productdesc_0005.html">Notes and Constraints</a>.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="80.99%" headers="mcps1.3.1.2.3.1.2 "><ul id="cce_01_0300__ul118110437342"><li id="cce_01_0300__li38254316343">Supported the creation of clusters of v1.29. For details, see <a href="cce_bulletin_0089.html">Kubernetes 1.29 Release Notes</a> and <a href="cce_10_0405.html">Patch Version Release Notes</a>.</li><li id="cce_01_0300__li668895417342">Added the Cloud Native Cluster Monitoring add-on. For details, see <a href="cce_10_0406.html">Cloud Native Cluster Monitoring</a>.</li><li id="cce_01_0300__li16457344123612">Added <a href="cce_10_0373.html">Monitoring Custom Metrics Using Cloud Native Cluster Monitoring</a>.</li><li id="cce_01_0300__li19403177171618">Deleted section "Kubernetes Version Support Mechanism".</li><li id="cce_01_0300__li184038711166">Added Kubernetes Version Policy.</li><li id="cce_01_0300__li7668108144413">Added <a href="cce_10_0734.html">Configuring an EIP for a Pod</a>.</li><li id="cce_01_0300__li1389051010459">Added <a href="cce_10_0651.html">Configuring a Static EIP for a Pod</a>.</li><li id="cce_01_0300__li14982191412301">Update <a href="cce_10_0476.html">Node OS</a>.</li><li id="cce_01_0300__li38112312311">Update <a href="cce_productdesc_0005.html">Notes and Constraints</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_01_0300__row450133482720"><td class="cellrowborder" valign="top" width="19.009999999999998%" headers="mcps1.3.1.2.3.1.1 "><p id="cce_01_0300__p1051163432712">2024-05-30</p>
|
||||
|
||||
@ -67,7 +67,7 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0003__cce_10_0198_row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.4.2.5.2.3.1.2.3.1.1 "><p id="cce_10_0003__cce_10_0198_p0669147185817">Data Disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.2.5.2.3.1.2.3.1.2 "><p id="cce_10_0003__cce_10_0198_p17207615113820"><strong id="cce_10_0003__cce_10_0198_b18519306218">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_0003__cce_10_0198_b17851123017214">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong></p>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.2.5.2.3.1.2.3.1.2 "><p id="cce_10_0003__cce_10_0198_p17207615113820"><strong id="cce_10_0003__cce_10_0198_b147901020218">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_0003__cce_10_0198_b347913105215">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong></p>
|
||||
<p id="cce_10_0003__cce_10_0198_p16639453192911">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_0003__cce_10_0198_uicontrol138446827241742"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0003__cce_10_0198_uicontrol130024400641742"><b>System Disk</b></span>, you have the option not to add the default data disk.</p>
|
||||
<p id="cce_10_0003__cce_10_0198_p3752312011">Click <strong id="cce_10_0003__cce_10_0198_b513813367555">Expand</strong> to configure <strong id="cce_10_0003__cce_10_0198_b13265825195416">Data Disk Space Allocation</strong>, which is used to allocate 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>.</p>
|
||||
<p id="cce_10_0003__cce_10_0198_p1391618153118">For other data disks, a raw disk is created without any processing by default. You can also click <strong id="cce_10_0003__cce_10_0198_b16127101911540">Expand</strong> and select <strong id="cce_10_0003__cce_10_0198_b21351519135417">Mount Disk</strong> to mount the data disk to a specified directory. </p>
|
||||
|
||||
@ -92,7 +92,7 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0012__cce_10_0363_row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.1 "><p id="cce_10_0012__cce_10_0363_p0669147185817">Data Disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.6.1.2.3.1.2 "><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>
|
||||
<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_b1172475762013">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_b147252057182019">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>
|
||||
|
||||
@ -2,10 +2,8 @@
|
||||
|
||||
<h1 class="topictitle1">Viewing CTS Traces in the Trace List</h1>
|
||||
<div id="body1525226397666"><div class="section" id="cce_10_0026__en-us_topic_0179639644_section5470822195238"><h4 class="sectiontitle">Scenarios</h4><p id="cce_10_0026__en-us_topic_0179639644_p333055219577">After you enable 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>
|
||||
</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="section" id="cce_10_0026__en-us_topic_0179639644_section19271975203"><h4 class="sectiontitle">Viewing Real-Time Traces in the Trace List</h4><ol id="cce_10_0026__en-us_topic_0179639644_ol4845175152710"><li id="cce_10_0026__en-us_topic_0179639644_li791871844313">Log in to the management console.</li><li id="cce_10_0026__en-us_topic_0179639644_li79188188435">Click <span><img id="cce_10_0026__en-us_topic_0179639644_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_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>
|
||||
@ -16,7 +14,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_i327125153611">CTS User Guide</em>.</li></ol>
|
||||
</li><li id="cce_10_0026__en-us_topic_0179639644_li129561719446">For details about key fields in the trace structure, see <a href="https://docs.otc.t-systems.com/cloud-trace-service/umn/user_guide/trace_references/trace_structure.html#cts-03-0010" target="_blank" rel="noopener noreferrer">Trace Structure</a> and <a href="https://docs.otc.t-systems.com/cloud-trace-service/umn/user_guide/trace_references/example_traces.html" target="_blank" rel="noopener noreferrer">Example Traces</a> in the <em id="cce_10_0026__en-us_topic_0179639644_i327125153611">CTS User Guide</em>.</li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
@ -163,7 +163,7 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0028__row1420021516223"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.11.1.3.1.1 "><p id="cce_10_0028__p14925192081010">Certificate Authentication</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.4.11.1.3.1.2 "><ul id="cce_10_0028__ul149256204107"><li id="cce_10_0028__li3925120181012">If <strong id="cce_10_0028__b196068988871353">Automatically generated</strong> is selected, the X509-based authentication mode will be enabled by default. X509 is a commonly used certificate format.</li><li id="cce_10_0028__li892532021013">If <strong id="cce_10_0028__b145716273971353">Bring your own</strong> is selected, the cluster can identify users based on the header in the request body for authentication.<p id="cce_10_0028__p18925192017100">Upload your CA root certificate, client certificate, and private key.</p>
|
||||
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.4.11.1.3.1.2 "><ul id="cce_10_0028__ul149256204107"><li id="cce_10_0028__li3925120181012">If <strong id="cce_10_0028__b196068988871353">Automatically generated</strong> is selected, the X.509-based authentication mode will be enabled by default. X.509 is a commonly used certificate format.</li><li id="cce_10_0028__li892532021013">If <strong id="cce_10_0028__b145716273971353">Bring your own</strong> is selected, the cluster can identify users based on the header in the request body for authentication.<p id="cce_10_0028__p18925192017100">Upload your CA root certificate, client certificate, and private key.</p>
|
||||
<div class="caution" id="cce_10_0028__note20925220121012"><span class="cautiontitle"> CAUTION: </span><div class="cautionbody"><ul id="cce_10_0028__ul992511206102"><li id="cce_10_0028__li29251205103">Upload a file <strong id="cce_10_0028__b199411240122414">smaller than 1 MB</strong>. The CA certificate and client certificate can be in <strong id="cce_10_0028__b1195014407247">.crt</strong> or <strong id="cce_10_0028__b15950140182418">.cer</strong> format. The private key of the client certificate can only be uploaded <strong id="cce_10_0028__b199501540102417">unencrypted</strong>.</li><li id="cce_10_0028__li6925192051013">The validity period of the client certificate must be longer than five years.</li><li id="cce_10_0028__li39254207102">The uploaded CA root certificate is used by the authentication proxy and for configuring the kube-apiserver aggregation layer. <strong id="cce_10_0028__b2292133172913">If any of the uploaded certificates is invalid, the cluster cannot be created.</strong> </li><li id="cce_10_0028__li492522031010">Starting from v1.25, Kubernetes no longer supports certificate authentication generated using the SHA1WithRSA or ECDSAWithSHA1 algorithm. The certificate authentication generated using the SHA256 algorithm is supported instead.</li></ul>
|
||||
</div></div>
|
||||
</li></ul>
|
||||
@ -199,7 +199,7 @@
|
||||
<tr id="cce_10_0028__row11925142091019"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.11.1.3.1.1 "><p id="cce_10_0028__p129241206101">Resource Tag</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.4.11.1.3.1.2 "><p id="cce_10_0028__p10924220161020">You can add resource tags to classify resources. A maximum of 20 resource tags can be added.</p>
|
||||
<p id="cce_10_0028__p992432014101">You can create <span class="uicontrol" id="cce_10_0028__uicontrol1919112925819"><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_0028__p992432014101">You can create <span class="uicontrol" id="cce_10_0028__uicontrol592462011017"><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>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0028__row5925122011010"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.4.11.1.3.1.1 "><p id="cce_10_0028__p129253204106">Description</p>
|
||||
@ -245,7 +245,17 @@
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0028__row179261420161011"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.5.5.2.1.3.1.1 "><p id="cce_10_0028__p44622153710">CCE Node Problem Detector</p>
|
||||
<tbody><tr id="cce_10_0028__row12836181383713"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.5.5.2.1.3.1.1 "><p id="cce_10_0028__p1259551415374">Cloud Native Cluster Monitoring</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.5.5.2.1.3.1.2 "><p id="cce_10_0028__p3595141413374">(Optional) If selected, this add-on (<a href="cce_10_0406.html">Cloud Native Cluster Monitoring</a>) will be automatically installed. Cloud Native Cluster Monitoring collects monitoring metrics for your cluster and reports the metrics to AOM. The agent mode does not support HPA based on custom Prometheus statements. If related functions are required, install this add-on manually after the cluster is created.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0028__row150417113372"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.5.5.2.1.3.1.1 "><p id="cce_10_0028__p226011337383">Cloud Native Log Collection</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.5.5.2.1.3.1.2 "><p id="cce_10_0028__p57421653163817">(Optional) If selected, this add-on (<a href="cce_10_0416.html">Cloud Native Log Collection</a>) will be automatically installed. Cloud Native Log Collection helps report logs to LTS. After the cluster is created, you are allowed to obtain and manage collection rules on the <strong id="cce_10_0028__b1891614901117">Logging</strong> page of the CCE cluster console.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0028__row179261420161011"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.5.5.2.1.3.1.1 "><p id="cce_10_0028__p44622153710">CCE Node Problem Detector</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.5.5.2.1.3.1.2 "><p id="cce_10_0028__p1192622071012">(Optional) If selected, this add-on (<a href="cce_10_0132.html">CCE Node Problem Detector</a>) will be automatically installed to detect faults and isolate nodes for prompt cluster troubleshooting.</p>
|
||||
</td>
|
||||
@ -289,7 +299,19 @@
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0028__row52959235477"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.6.5.2.1.3.1.1 "><p id="cce_10_0028__p16295172334719">CCE Node Problem Detector</p>
|
||||
<tbody><tr id="cce_10_0028__row16295523154716"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.6.5.2.1.3.1.1 "><p id="cce_10_0028__p8295182318471">Cloud Native Cluster Monitoring</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.6.5.2.1.3.1.2 "><p id="cce_10_0028__p13142125105312">Select an AOM instance for Cloud Native Cluster Monitoring to report metrics. If no AOM instance is available, click <strong id="cce_10_0028__b13662840164819">Creating Instance</strong> to create one.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0028__row18295122316476"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.6.5.2.1.3.1.1 "><p id="cce_10_0028__p4295223184712">Cloud Native Log Collection</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.6.5.2.1.3.1.2 "><p id="cce_10_0028__p13295122316471">Select the logs to be collected. If enabled, a log group named <strong id="cce_10_0028__b1071702911920">k8s-log-</strong><em id="cce_10_0028__i156933321695">{clusterId}</em> will be automatically created, and a log stream will be created for each selected log type.</p>
|
||||
<ul id="cce_10_0028__ul14907126135720"><li id="cce_10_0028__li1290712615573"><strong id="cce_10_0028__b898312574462">Container log</strong>: Standard output logs of containers are collected. The corresponding log stream is named in the format of <strong id="cce_10_0028__b1898313351517">stdout-</strong><em id="cce_10_0028__i14043374150">{Cluster ID}</em>.</li><li id="cce_10_0028__li16907186185714"><strong id="cce_10_0028__b208491554719">Kubernetes Events</strong>: Kubernetes logs are collected. The corresponding log stream is named in the format of <strong id="cce_10_0028__b1470624814247">event-</strong><em id="cce_10_0028__i23521010251">{Cluster ID}</em>.</li><li id="cce_10_0028__li372831085712"><strong id="cce_10_0028__b944682418475">Kubernetes Audit Logs</strong>: Audit logs of the master nodes are collected. The corresponding log stream is named in the format of <strong id="cce_10_0028__b191491447132512">audit-</strong><em id="cce_10_0028__i13566145914255">{Cluster ID}</em>.</li><li id="cce_10_0028__li19365181713571"><strong id="cce_10_0028__b838957134814">Control Plane Logs</strong>: Logs of components like kube-apiserver, kube-controller-manage, and kube-scheduler that run on the master nodes are collected. The corresponding log streams are named in the format of <strong id="cce_10_0028__b64769389112">kube-apiserver-</strong><em id="cce_10_0028__i1293912509118">{Cluster ID}</em>, <strong id="cce_10_0028__b1860415551119">kube-controller-manage-</strong><em id="cce_10_0028__i142615412214">{Cluster ID}</em>, and <strong id="cce_10_0028__b102511991821">kube-scheduler-</strong><em id="cce_10_0028__i456113204214">{Cluster ID}</em>, respectively.</li></ul>
|
||||
<p id="cce_10_0028__p667710564">If log collection is disabled, choose <strong id="cce_10_0028__b63515316102">Logging</strong> in the navigation pane of the cluster console after the cluster is created and enable this function.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0028__row52959235477"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.6.5.2.1.3.1.1 "><p id="cce_10_0028__p16295172334719">CCE Node Problem Detector</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="80%" headers="mcps1.3.6.5.2.1.3.1.2 "><p id="cce_10_0028__p158281157145915">This add-on is unconfigurable. After the cluster is created, choose <strong id="cce_10_0028__b18358104693712">Add-ons</strong> in the navigation pane of the cluster console and modify the configuration.</p>
|
||||
</td>
|
||||
|
||||
@ -19,7 +19,7 @@
|
||||
<div class="section" id="cce_10_0034__section1152424015224"><a name="cce_10_0034__section1152424015224"></a><a name="section1152424015224"></a><h4 class="sectiontitle">Installing the Add-on</h4><ol id="cce_10_0034__ol595195015265"><li id="cce_10_0034__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_0034__b09296116387"><span id="cce_10_0034__text77103384818">Add-ons</span></strong>, locate <strong id="cce_10_0034__b189291711193814">NGINX Ingress Controller</strong> on the right, and click <strong id="cce_10_0034__b189301611123814">Install</strong>.</span></li><li id="cce_10_0034__li6185135511235"><span>On the <strong id="cce_10_0034__b168313930105924">Install Add-on</strong> page, configure the specifications as needed.</span><p><p id="cce_10_0034__p12804745248">You can adjust the number of add-on instances and resource quotas as required. High availability is not possible with a single pod. If an error occurs on the node where the add-on instance runs, the add-on will fail.</p>
|
||||
</p></li><li id="cce_10_0034__li584045813266"><span>Configure the add-on parameters.</span><p><ul id="cce_10_0034__ul741422082911"><li id="cce_10_0034__li0953175016455"><a name="cce_10_0034__li0953175016455"></a><a name="li0953175016455"></a><strong id="cce_10_0034__b15671611202516">Ingress Class</strong>: Enter a custom controller name, which uniquely identifies an Ingress controller. The name of each controller in the same cluster must be unique and cannot be set to <strong id="cce_10_0034__b8831138419">cce</strong>. (<strong id="cce_10_0034__b14982036941">cce</strong> is the unique identifier of the ELB Ingress Controller.) When creating an Ingress, you can specify the controller name to declare which controller should manage this Ingress.</li><li id="cce_10_0034__li43911954164512"><strong id="cce_10_0034__b87211241203016">Namespace for add-on installation</strong>: Select a namespace for the ingress controller.</li><li id="cce_10_0034__li194268504296"><strong id="cce_10_0034__b7357351122419">Load Balancer</strong>: Select a shared or dedicated load balancer. If no load balancer is available, create one. The load balancer has at least two listeners, and ports 80 and 443 are not occupied by listeners.</li><li id="cce_10_0034__li19869530141118"><strong id="cce_10_0034__b266512513184">Admission Check</strong>: Admission control is performed on Ingresses to ensure that the controller can generate valid configurations. Admission verification is performed on the configuration of Nginx Ingresses. If the verification fails, the request will be intercepted. For details about admission verification, see <a href="https://kubernetes.github.io/ingress-nginx/e2e-tests/#admission-admission-controller" target="_blank" rel="noopener noreferrer">Access Control</a>.<div class="note" id="cce_10_0034__note13941342101413"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0034__ul13288250171411"><li id="cce_10_0034__li1228817507146">Admission check slows down the responses to Ingress requests.</li><li id="cce_10_0034__li172581224167">Only add-ons of version 2.4.1 or later support admission verification.</li></ul>
|
||||
</div></div>
|
||||
</li><li id="cce_10_0034__li66142206315"><strong id="cce_10_0034__b6241732145011">Nginx Parameters</strong>: You can configure the <strong id="cce_10_0034__b1463512386289">nginx.conf</strong> file, which will affect all managed ingresses. You can select <strong id="cce_10_0034__b8319105215309">GUI</strong> or <strong id="cce_10_0034__b1631919529308">YAML</strong>. <strong id="cce_10_0034__b11319452103017">GUI</strong> is supported by the NGINX Ingress Controller of version 2.2.75, 2.6.26, 3.0.1, or later.<p id="cce_10_0034__p1512810221947">To configure custom parameters supported by the Kubernetes community, choose <strong id="cce_10_0034__b13526125716301">YAML</strong> and find the related parameters in <a href="https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/" target="_blank" rel="noopener noreferrer">ConfigMaps</a>. For example, you can use the <strong id="cce_10_0034__b19750151011317">keep-alive-requests</strong> parameter to describe how to set the maximum number of requests for keeping active connections to 100.</p>
|
||||
</li><li id="cce_10_0034__li66142206315"><strong id="cce_10_0034__b6241732145011">Nginx Parameters</strong>: You can configure the <strong id="cce_10_0034__b1463512386289">nginx.conf</strong> file, which will affect all managed ingresses. You can select <strong id="cce_10_0034__b729563715259">GUI</strong> or <strong id="cce_10_0034__b152962375254">YAML</strong>. <strong id="cce_10_0034__b0296103716256">GUI</strong> is supported by the NGINX Ingress Controller of version 2.2.75, 2.6.26, 3.0.1, or later.<p id="cce_10_0034__p1512810221947">To configure custom parameters supported by the Kubernetes community, choose <strong id="cce_10_0034__b8748942142517">YAML</strong> and find the related parameters in <a href="https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/" target="_blank" rel="noopener noreferrer">ConfigMaps</a>. For example, you can use the <strong id="cce_10_0034__b19750151011317">keep-alive-requests</strong> parameter to describe how to set the maximum number of requests for keeping active connections to 100.</p>
|
||||
<pre class="screen" id="cce_10_0034__screen6950408718">{
|
||||
"keep-alive-requests": "100"
|
||||
}</pre>
|
||||
|
||||
@ -463,7 +463,7 @@
|
||||
<p id="cce_10_0066__en-us_topic_0000001559534258_p774595219571">v1.27</p>
|
||||
<p id="cce_10_0066__en-us_topic_0000001559534258_p9635155419571">v1.28</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="59.31593159315932%" headers="mcps1.3.6.2.2.4.1.3 "><p id="cce_10_0066__en-us_topic_0000001559534258_p2169114418574">CCE clusters 1.28 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="59.31593159315932%" headers="mcps1.3.6.2.2.4.1.3 "><p id="cce_10_0066__en-us_topic_0000001559534258_p2169114418574">CCE clusters v1.28 are supported.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0066__en-us_topic_0000001559534258_row156681058121613"><td class="cellrowborder" valign="top" width="15.51155115511551%" headers="mcps1.3.6.2.2.4.1.1 "><p id="cce_10_0066__en-us_topic_0000001559534258_p6718151181712">2.1.51</p>
|
||||
|
||||
@ -10,6 +10,8 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0620.html">Using an SFS File System Through a Dynamic PV</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0914.html">Creating an SFS Subdirectory Using a Dynamic PV</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0337.html">Configuring SFS Volume Mount Options</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@ -12,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_0.html">Dynamically Creating an SFS Turbo Subdirectory Using StorageClass</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="cce_bestpractice_00253.html">Dynamically Creating an SFS Turbo Subdirectory Using StorageClass</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
||||
@ -379,7 +379,7 @@ $configBlock
|
||||
<p id="cce_10_0129__en-us_topic_0000001608265441_p163861919102814">v1.29</p>
|
||||
<p id="cce_10_0129__en-us_topic_0000001608265441_p4322155817299">v1.30</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><ul id="cce_10_0129__en-us_topic_0000001608265441_ul959843133118"><li id="cce_10_0129__en-us_topic_0000001608265441_li55981031163115">Supported Corefile configurations.</li><li id="cce_10_0129__en-us_topic_0000001608265441_li1536393312317">CCE clusters 1.30 are supported.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><ul id="cce_10_0129__en-us_topic_0000001608265441_ul959843133118"><li id="cce_10_0129__en-us_topic_0000001608265441_li55981031163115">Supported Corefile configurations.</li><li id="cce_10_0129__en-us_topic_0000001608265441_li1536393312317">CCE clusters v1.30 are supported.</li></ul>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="17.65%" headers="mcps1.3.7.2.2.5.1.4 "><p id="cce_10_0129__en-us_topic_0000001608265441_p838681918281"><a href="https://github.com/coredns/coredns/releases/tag/v1.10.1" target="_blank" rel="noopener noreferrer">1.10.1</a></p>
|
||||
</td>
|
||||
@ -393,7 +393,7 @@ $configBlock
|
||||
<p id="cce_10_0129__en-us_topic_0000001608265441_p1222813194207">v1.28</p>
|
||||
<p id="cce_10_0129__en-us_topic_0000001608265441_p1984171972010">v1.29</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0129__en-us_topic_0000001608265441_p1854492818204">CCE clusters 1.29 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0129__en-us_topic_0000001608265441_p1854492818204">CCE clusters v1.29 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="17.65%" headers="mcps1.3.7.2.2.5.1.4 "><p id="cce_10_0129__en-us_topic_0000001608265441_p1186923362019"><a href="https://github.com/coredns/coredns/releases/tag/v1.10.1" target="_blank" rel="noopener noreferrer">1.10.1</a></p>
|
||||
</td>
|
||||
@ -432,7 +432,7 @@ $configBlock
|
||||
<p id="cce_10_0129__en-us_topic_0000001608265441_p18218176131710">v1.27</p>
|
||||
<p id="cce_10_0129__en-us_topic_0000001608265441_p59913710177">v1.28</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0129__en-us_topic_0000001608265441_p24318167176">CCE clusters 1.28 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0129__en-us_topic_0000001608265441_p24318167176">CCE clusters v1.28 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="17.65%" headers="mcps1.3.7.2.2.5.1.4 "><p id="cce_10_0129__en-us_topic_0000001608265441_p14767420161720"><a href="https://github.com/coredns/coredns/releases/tag/v1.10.1" target="_blank" rel="noopener noreferrer">1.10.1</a></p>
|
||||
</td>
|
||||
@ -469,7 +469,7 @@ $configBlock
|
||||
<p id="cce_10_0129__en-us_topic_0000001608265441_p18614122118719">v1.23</p>
|
||||
<p id="cce_10_0129__en-us_topic_0000001608265441_p136141421978">v1.25</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0129__en-us_topic_0000001608265441_p929522405512">CCE clusters 1.25 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0129__en-us_topic_0000001608265441_p929522405512">CCE clusters v1.25 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="17.65%" headers="mcps1.3.7.2.2.5.1.4 "><p id="cce_10_0129__en-us_topic_0000001608265441_p17331021301"><a href="https://github.com/coredns/coredns/releases/tag/v1.8.4" target="_blank" rel="noopener noreferrer">1.8.4</a></p>
|
||||
</td>
|
||||
@ -495,7 +495,7 @@ $configBlock
|
||||
<p id="cce_10_0129__en-us_topic_0000001608265441_p63963541475">v1.21</p>
|
||||
<p id="cce_10_0129__en-us_topic_0000001608265441_p9396154772">v1.23</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0129__en-us_topic_0000001608265441_p127232835516">CCE clusters 1.23 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0129__en-us_topic_0000001608265441_p127232835516">CCE clusters v1.23 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="17.65%" headers="mcps1.3.7.2.2.5.1.4 "><p id="cce_10_0129__en-us_topic_0000001608265441_p1734664055618"><a href="https://github.com/coredns/coredns/releases/tag/v1.8.4" target="_blank" rel="noopener noreferrer">1.8.4</a></p>
|
||||
</td>
|
||||
@ -507,7 +507,7 @@ $configBlock
|
||||
<p id="cce_10_0129__en-us_topic_0000001608265441_p1043810591373">v1.19</p>
|
||||
<p id="cce_10_0129__en-us_topic_0000001608265441_p8438159878">v1.21</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0129__en-us_topic_0000001608265441_p135431929145515">CCE clusters 1.21 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0129__en-us_topic_0000001608265441_p135431929145515">CCE clusters v1.21 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="17.65%" headers="mcps1.3.7.2.2.5.1.4 "><p id="cce_10_0129__en-us_topic_0000001608265441_p1335434055619"><a href="https://github.com/coredns/coredns/releases/tag/v1.8.4" target="_blank" rel="noopener noreferrer">1.8.4</a></p>
|
||||
</td>
|
||||
@ -528,7 +528,7 @@ $configBlock
|
||||
<td class="cellrowborder" valign="top" width="29.42%" headers="mcps1.3.7.2.2.5.1.2 "><p id="cce_10_0129__en-us_topic_0000001608265441_p432614101985">v1.17</p>
|
||||
<p id="cce_10_0129__en-us_topic_0000001608265441_p5326210787">v1.19</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0129__en-us_topic_0000001608265441_p787113235510">CCE clusters 1.19 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="35.29%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0129__en-us_topic_0000001608265441_p787113235510">CCE clusters v1.19 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="17.65%" headers="mcps1.3.7.2.2.5.1.4 "><p id="cce_10_0129__en-us_topic_0000001608265441_p61351334205617"><a href="https://github.com/coredns/coredns/releases/tag/v1.6.5" target="_blank" rel="noopener noreferrer">1.6.5</a></p>
|
||||
</td>
|
||||
|
||||
@ -4,7 +4,7 @@
|
||||
<div id="body1544406897523"><div class="section" id="cce_10_0132__section173631312185614"><h4 class="sectiontitle">Introduction</h4><p id="cce_10_0132__p37354218618">CCE Node Problem Detector (NPD) is an add-on that monitors abnormal events of cluster nodes and connects to a third-party monitoring platform. It is a daemon running on each node. It collects node issues from different daemons and reports them to the API server. This add-on can run as a DaemonSet or a daemon.</p>
|
||||
<p id="cce_10_0132__p152804433415">For more information, see <a href="https://github.com/kubernetes/node-problem-detector" target="_blank" rel="noopener noreferrer">node-problem-detector</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0132__section119671349192611"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="cce_10_0132__ul55121521141010"><li id="cce_10_0132__li8512142151010">When using this add-on, do not format or partition node disks.</li><li id="cce_10_0132__li151217213101">Each NPD process occupies 30 m CPU and 100 MiB of memory.</li><li id="cce_10_0132__li1462834917375">If the NPD version is 1.18.45 or later, the EulerOS version of the host machine must be 2.5 or later.</li></ul>
|
||||
<div class="section" id="cce_10_0132__section119671349192611"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="cce_10_0132__ul55121521141010"><li id="cce_10_0132__li8512142151010">When using this add-on, do not format or partition node disks.</li><li id="cce_10_0132__li151217213101">Each NPD process occupies 30m CPUs and 100 MiB of memory.</li><li id="cce_10_0132__li1462834917375">If the NPD version is 1.18.45 or later, the EulerOS version of the host machine must be 2.5 or later.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0132__section158021093142"><h4 class="sectiontitle">Permissions</h4><p id="cce_10_0132__p17541021171417">To monitor kernel logs, the NPD add-on needs to read the host <strong id="cce_10_0132__b96321135103716">/dev/kmsg</strong>. Therefore, the privileged mode must be enabled. For details, see <a href="https://kubernetes.io/docs/concepts/policy/pod-security-policy/#privileged" target="_blank" rel="noopener noreferrer">privileged</a>.</p>
|
||||
<p id="cce_10_0132__p1992131751419">In addition, CCE mitigates risks according to the least privilege principle. Only the following privileges are available for NPD running:</p>
|
||||
@ -100,7 +100,7 @@
|
||||
<p id="cce_10_0132__p2317112419618">Typical scenario: Disk I/O suspension causes process suspension.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33%" headers="mcps1.3.6.4.1.2.2.4.1.3 "><p id="cce_10_0132__p16872758114011">Warning event</p>
|
||||
<p id="cce_10_0132__p173071159247">Listening object: <strong id="cce_10_0132__b1783717768">/dev/kmsg</strong></p>
|
||||
<p id="cce_10_0132__p173071159247">Listening object: <strong id="cce_10_0132__b2054558210">/dev/kmsg</strong></p>
|
||||
<p id="cce_10_0132__p153079591241">Matching rule: "task \\S+:\\w+ blocked for more than \\w+ seconds\\."</p>
|
||||
</td>
|
||||
</tr>
|
||||
@ -112,7 +112,7 @@
|
||||
</div></div>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33%" headers="mcps1.3.6.4.1.2.2.4.1.3 "><p id="cce_10_0132__p944535317711">Warning event</p>
|
||||
<p id="cce_10_0132__p183981710948">Listening object: <strong id="cce_10_0132__b1235710589">/dev/kmsg</strong></p>
|
||||
<p id="cce_10_0132__p183981710948">Listening object: <strong id="cce_10_0132__b810243499">/dev/kmsg</strong></p>
|
||||
<p id="cce_10_0132__p83993101042">Matching rule: <strong id="cce_10_0132__b15200817134219">Remounting filesystem read-only</strong></p>
|
||||
</td>
|
||||
</tr>
|
||||
@ -562,7 +562,7 @@ problem_gauge{reason="CRIIsUp",type="CRIProblem"} 0
|
||||
<p id="cce_10_0132__en-us_topic_0000001559693886_p14916719175914">v1.27</p>
|
||||
<p id="cce_10_0132__en-us_topic_0000001559693886_p8630152045911">v1.28</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="38.07%" headers="mcps1.3.10.2.2.5.1.3 "><p id="cce_10_0132__en-us_topic_0000001559693886_p2169114418574">CCE clusters 1.28 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="38.07%" headers="mcps1.3.10.2.2.5.1.3 "><p id="cce_10_0132__en-us_topic_0000001559693886_p2169114418574">CCE clusters v1.28 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="14.87%" headers="mcps1.3.10.2.2.5.1.4 "><p id="cce_10_0132__en-us_topic_0000001559693886_p12442172917188"><a href="https://github.com/kubernetes/node-problem-detector/releases/tag/v0.8.10" target="_blank" rel="noopener noreferrer">0.8.10</a></p>
|
||||
</td>
|
||||
|
||||
@ -98,7 +98,7 @@ cd /usr/local/nvidia/bin && ./nvidia-smi</pre>
|
||||
<p id="cce_10_0141__en-us_topic_0000001559693890_p0532121144210">v1.29</p>
|
||||
<p id="cce_10_0141__en-us_topic_0000001559693890_p82341123174214">v1.30</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="42.85428542854286%" headers="mcps1.3.8.2.2.4.1.3 "><ul id="cce_10_0141__en-us_topic_0000001559693890_ul16128144911429"><li id="cce_10_0141__en-us_topic_0000001559693890_li1212884911427">Supported xGPU configuration by node pool.</li><li id="cce_10_0141__en-us_topic_0000001559693890_li1712874904213">Supported GPU rendering.</li><li id="cce_10_0141__en-us_topic_0000001559693890_li18254145234218">Clusters 1.30 are supported.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="42.85428542854286%" headers="mcps1.3.8.2.2.4.1.3 "><ul id="cce_10_0141__en-us_topic_0000001559693890_ul16128144911429"><li id="cce_10_0141__en-us_topic_0000001559693890_li1212884911427">Supported xGPU configuration by node pool.</li><li id="cce_10_0141__en-us_topic_0000001559693890_li1712874904213">Supported GPU rendering.</li><li id="cce_10_0141__en-us_topic_0000001559693890_li18254145234218">Clusters v1.30 are supported.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0141__en-us_topic_0000001559693890_row129815138462"><td class="cellrowborder" valign="top" width="21.432143214321435%" headers="mcps1.3.8.2.2.4.1.1 "><p id="cce_10_0141__en-us_topic_0000001559693890_p86679446461">2.6.4</p>
|
||||
@ -128,7 +128,7 @@ cd /usr/local/nvidia/bin && ./nvidia-smi</pre>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="35.71357135713571%" headers="mcps1.3.8.2.2.4.1.2 "><p id="cce_10_0141__en-us_topic_0000001559693890_p2165417104714">v1.28</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="42.85428542854286%" headers="mcps1.3.8.2.2.4.1.3 "><p id="cce_10_0141__en-us_topic_0000001559693890_p153531470473">Clusters 1.28 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="42.85428542854286%" headers="mcps1.3.8.2.2.4.1.3 "><p id="cce_10_0141__en-us_topic_0000001559693890_p153531470473">Clusters v1.28 are supported.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0141__en-us_topic_0000001559693890_row549213258470"><td class="cellrowborder" valign="top" width="21.432143214321435%" headers="mcps1.3.8.2.2.4.1.1 "><p id="cce_10_0141__en-us_topic_0000001559693890_p19494202554712">2.0.69</p>
|
||||
@ -189,7 +189,7 @@ cd /usr/local/nvidia/bin && ./nvidia-smi</pre>
|
||||
<p id="cce_10_0141__en-us_topic_0000001559693890_p161341734182114">v1.21</p>
|
||||
<p id="cce_10_0141__en-us_topic_0000001559693890_p1813453442110">v1.23</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="42.85428542854286%" headers="mcps1.3.8.2.2.4.1.3 "><p id="cce_10_0141__en-us_topic_0000001559693890_p2763830181411">CCE clusters 1.23 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="42.85428542854286%" headers="mcps1.3.8.2.2.4.1.3 "><p id="cce_10_0141__en-us_topic_0000001559693890_p2763830181411">CCE clusters v1.23 are supported.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0141__en-us_topic_0000001559693890_row19850201865813"><td class="cellrowborder" valign="top" width="21.432143214321435%" headers="mcps1.3.8.2.2.4.1.1 "><p id="cce_10_0141__en-us_topic_0000001559693890_p180611510016">1.2.9</p>
|
||||
@ -199,7 +199,7 @@ cd /usr/local/nvidia/bin && ./nvidia-smi</pre>
|
||||
<p id="cce_10_0141__en-us_topic_0000001559693890_p138716372212">v1.19</p>
|
||||
<p id="cce_10_0141__en-us_topic_0000001559693890_p153876371212">v1.21</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="42.85428542854286%" headers="mcps1.3.8.2.2.4.1.3 "><p id="cce_10_0141__en-us_topic_0000001559693890_p1481363411410">CCE clusters 1.21 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="42.85428542854286%" headers="mcps1.3.8.2.2.4.1.3 "><p id="cce_10_0141__en-us_topic_0000001559693890_p1481363411410">CCE clusters v1.21 are supported.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0141__en-us_topic_0000001559693890_row1331711107"><td class="cellrowborder" valign="top" width="21.432143214321435%" headers="mcps1.3.8.2.2.4.1.1 "><p id="cce_10_0141__en-us_topic_0000001559693890_p16807151519016">1.2.2</p>
|
||||
|
||||
@ -174,8 +174,6 @@ myjob-29qlw 0/1 Completed 0 4m5s
|
||||
...</pre>
|
||||
<p id="cce_10_0150__p1493240155016">If the status is <strong id="cce_10_0150__b87899363419">Completed</strong>, the job is complete.</p>
|
||||
</p></li><li id="cce_10_0150__li31584441491"><span>View the pod logs.</span><p><p id="cce_10_0150__p131821814115110"><strong id="cce_10_0150__b17171154917510">kubectl logs <pod_name></strong></p>
|
||||
<pre class="screen" id="cce_10_0150__screen1181615335512"># kubectl logs myjob-29qlw
|
||||
3.1415926535897932384626433832795028841971693993751058209749445923078164062862089986280348253421170679821480865132823066470938446095505822317253594081284811174502841027019385211055596446229489549303819644288109756659334461284756482337867831652712019091456485669234603486104543266482133936072602491412737245870066063155881748815209209628292540917153643678925903600113305305488204665213841469519415116094330572703657595919530921861173819326117931051185480744623799627495673518857527248912279381830119491298336733624406566430860213949463952247371907021798609437027705392171762931767523846748184676694051320005681271452635608277857713427577896091736371787214684409012249534301465495853710507922796892589235420199561121290219608640344181598136297747713099605187072113499999983729780499510597317328160963185950244594553469083026425223082533446850352619311881710100031378387528865875332083814206171776691473035982534904287554687311595628638823537875937519577818577805321712268066130019278766111959092164201989380952572010654858632788659361533818279682303019520353018529689957736225994138912497217752834791315155748572424541506959508295331168617278558890750983817546374649393192550604009277016711390098488240128583616035637076601047101819429555961989467678374494482553797747268471040475346462080466842590694912933136770289891521047521620569660240580381501935112533824300355876402474964732639141992726042699227967823547816360093417216412199245863150302861829745557067498385054945885869269956909272107975093029553211653449872027559602364806654991198818347977535663698074265425278625518184175746728909777727938000816470600161452491921732172147723501414419735685481613611573525521334757418494684385233239073941433345477624168625189835694855620992192221842725502542568876717904946016534668049886272327917860857843838279679766814541009538837863609506800642251252051173929848960841284886269456042419652850222106611863067442786220391949450471237137869609563643719172874677646575739624138908658326459958133904780275901</pre>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0150__s9bef0428158a4935b466ea150ccae961"><h4 class="sectiontitle">Related Operations</h4><p id="cce_10_0150__ad9af09fde5934e8095af1d02ba2948c8">After a one-off job is created, you can perform operations listed in <a href="#cce_10_0150__t84075653e7544394939d13740fad0c20">Table 2</a>.</p>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -4,6 +4,8 @@
|
||||
<div id="body0000001757642125"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0555.html">Collecting Container Logs Using Cloud Native Log Collection</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0018.html">Collecting Container Logs Using ICAgent</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@ -929,7 +929,7 @@ tolerations:
|
||||
<p id="cce_10_0193__en-us_topic_0000001609894173_p474210820312">v1.27</p>
|
||||
<p id="cce_10_0193__en-us_topic_0000001609894173_p17428863113">v1.28</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.7.3.2.4.1.3 "><ul id="cce_10_0193__en-us_topic_0000001609894173_ul176081014153116"><li id="cce_10_0193__en-us_topic_0000001609894173_li4608141443119">Supported Kubernetes 1.28.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li3608114193113">Supported load-aware scheduling.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li760821417312">Updated image OS to HCE 2.0.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li176081014123118">Optimized CSI resource preemption.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li166081714103120">Optimized load-aware rescheduling.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li1608141453118">Optimized preemption in hybrid deployment scenarios.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.7.3.2.4.1.3 "><ul id="cce_10_0193__en-us_topic_0000001609894173_ul176081014153116"><li id="cce_10_0193__en-us_topic_0000001609894173_li4608141443119">Supported Kubernetes v1.28.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li3608114193113">Supported load-aware scheduling.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li760821417312">The image OS is updated to HCE OS 2.0.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li176081014123118">Optimized CSI resource preemption.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li166081714103120">Optimized load-aware rescheduling.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li1608141453118">Optimized preemption in hybrid deployment scenarios.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0193__en-us_topic_0000001609894173_row292137208"><td class="cellrowborder" valign="top" width="15.21%" headers="mcps1.3.7.3.2.4.1.1 "><p id="cce_10_0193__en-us_topic_0000001609894173_p82755117013">1.11.6</p>
|
||||
@ -940,7 +940,7 @@ tolerations:
|
||||
<p id="cce_10_0193__en-us_topic_0000001609894173_p152761119019">v1.25</p>
|
||||
<p id="cce_10_0193__en-us_topic_0000001609894173_p06631925908">v1.27</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.7.3.2.4.1.3 "><ul id="cce_10_0193__en-us_topic_0000001609894173_ul071414332003"><li id="cce_10_0193__en-us_topic_0000001609894173_li19714103315017">Supported Kubernetes 1.27.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li187141633201">Supported rescheduling.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li3715163318016">Supported affinity scheduling of nodes in the node pool.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li107157331202">Optimized the scheduling performance.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.7.3.2.4.1.3 "><ul id="cce_10_0193__en-us_topic_0000001609894173_ul071414332003"><li id="cce_10_0193__en-us_topic_0000001609894173_li19714103315017">Supported Kubernetes v1.27.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li187141633201">Supported rescheduling.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li3715163318016">Supported affinity scheduling of nodes in the node pool.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li107157331202">Optimized the scheduling performance.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0193__en-us_topic_0000001609894173_row546617333191"><td class="cellrowborder" valign="top" width="15.21%" headers="mcps1.3.7.3.2.4.1.1 "><p id="cce_10_0193__en-us_topic_0000001609894173_p246663341914">1.9.1</p>
|
||||
@ -950,7 +950,7 @@ tolerations:
|
||||
<p id="cce_10_0193__en-us_topic_0000001609894173_p4910191692212">v1.23</p>
|
||||
<p id="cce_10_0193__en-us_topic_0000001609894173_p091021662211">v1.25</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.7.3.2.4.1.3 "><ul id="cce_10_0193__en-us_topic_0000001609894173_ul72541248141916"><li id="cce_10_0193__en-us_topic_0000001609894173_li122546488191">Fixes the issue that the counting pipeline pod of the networkresource add-on occupies supplementary network interfaces (Sub-ENI).</li><li id="cce_10_0193__en-us_topic_0000001609894173_li16254248191912">Fixes the issue where the binpack add-on scores nodes with insufficient resources.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li8254204861913">Fixes the issue of processing resources in the pod with unknown end status.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li2255448151914">Optimizes event output.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li1525519484195">Supports HA deployment by default.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.7.3.2.4.1.3 "><ul id="cce_10_0193__en-us_topic_0000001609894173_ul72541248141916"><li id="cce_10_0193__en-us_topic_0000001609894173_li122546488191">Fixed the issue that the counting pipeline pod of the networkresource add-on occupies supplementary network interfaces (sub-ENIs).</li><li id="cce_10_0193__en-us_topic_0000001609894173_li16254248191912">Fixed the issue where the binpack add-on scores nodes with insufficient resources.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li8254204861913">Fixed the issue of processing resources in the pod with unknown end status.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li2255448151914">Optimized event output.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li1525519484195">Supported HA deployment by default.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0193__en-us_topic_0000001609894173_row328716461974"><td class="cellrowborder" valign="top" width="15.21%" headers="mcps1.3.7.3.2.4.1.1 "><p id="cce_10_0193__en-us_topic_0000001609894173_p132879461770">1.7.1</p>
|
||||
@ -960,7 +960,7 @@ tolerations:
|
||||
<p id="cce_10_0193__en-us_topic_0000001609894173_p18825132313">v1.23</p>
|
||||
<p id="cce_10_0193__en-us_topic_0000001609894173_p888165152320">v1.25</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.7.3.2.4.1.3 "><p id="cce_10_0193__en-us_topic_0000001609894173_p13744731163113">Adapts to clusters 1.25.</p>
|
||||
<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.7.3.2.4.1.3 "><p id="cce_10_0193__en-us_topic_0000001609894173_p13744731163113">Supported clusters v1.25.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0193__en-us_topic_0000001609894173_row340212477539"><td class="cellrowborder" valign="top" width="15.21%" headers="mcps1.3.7.3.2.4.1.1 "><p id="cce_10_0193__en-us_topic_0000001609894173_p2402947155311">1.4.5</p>
|
||||
@ -969,7 +969,7 @@ tolerations:
|
||||
<p id="cce_10_0193__en-us_topic_0000001609894173_p15763524122317">v1.19</p>
|
||||
<p id="cce_10_0193__en-us_topic_0000001609894173_p8763132442320">v1.21</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.7.3.2.4.1.3 "><p id="cce_10_0193__en-us_topic_0000001609894173_p1423247151310">Changes the deployment mode of volcano-scheduler from <strong id="cce_10_0193__en-us_topic_0000001609894173_b13786112371014">statefulset</strong> to <strong id="cce_10_0193__en-us_topic_0000001609894173_b6786102361013">deployment</strong>, and fixes the issue that pods cannot be automatically migrated when the node is abnormal.</p>
|
||||
<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.7.3.2.4.1.3 "><p id="cce_10_0193__en-us_topic_0000001609894173_p1423247151310">Changed the deployment mode of Volcano Scheduler from StatefulSet to Deployment, and fixed the issue that pods cannot be automatically migrated when the node is abnormal.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0193__en-us_topic_0000001609894173_row11369153312315"><td class="cellrowborder" valign="top" width="15.21%" headers="mcps1.3.7.3.2.4.1.1 "><p id="cce_10_0193__en-us_topic_0000001609894173_p1811415316237">1.3.7</p>
|
||||
@ -979,7 +979,7 @@ tolerations:
|
||||
<p id="cce_10_0193__en-us_topic_0000001609894173_p1366373832317">v1.19</p>
|
||||
<p id="cce_10_0193__en-us_topic_0000001609894173_p2663338182315">v1.21</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.7.3.2.4.1.3 "><ul id="cce_10_0193__en-us_topic_0000001609894173_ul67351117245"><li id="cce_10_0193__en-us_topic_0000001609894173_li47318111245">Supports hybrid deployment of online and offline jobs and resource oversubscription.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li373611102419">Optimizes the scheduling throughput for clusters.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li1573151114240">Fixes the issue where the scheduler panics in certain scenarios.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li673161112248">Fixes the issue that the volumes.secret verification of the volcano job in the CCE clusters 1.15 fails.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li17314117246">Fixes the issue that jobs fail to be scheduled when volumes are mounted.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="51.42%" headers="mcps1.3.7.3.2.4.1.3 "><ul id="cce_10_0193__en-us_topic_0000001609894173_ul67351117245"><li id="cce_10_0193__en-us_topic_0000001609894173_li47318111245">Supported hybrid deployment of online and offline jobs and resource oversubscription.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li373611102419">Optimized the scheduling throughput for clusters.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li1573151114240">Fixed the issue where the scheduler panics in certain scenarios.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li673161112248">Fixed the issue that the volumes.secret verification of the volcano job in the CCE clusters v1.15 fails.</li><li id="cce_10_0193__en-us_topic_0000001609894173_li17314117246">Fixed the issue that jobs fail to be scheduled when volumes are mounted.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
||||
@ -76,7 +76,7 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0198__row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.4.2.3.2.4.1.2.3.1.1 "><p id="cce_10_0198__p0669147185817">Data Disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.2.3.2.4.1.2.3.1.2 "><p id="cce_10_0198__p17207615113820"><strong id="cce_10_0198__b18519306218">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_0198__b17851123017214">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong></p>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.2.3.2.4.1.2.3.1.2 "><p id="cce_10_0198__p17207615113820"><strong id="cce_10_0198__b147901020218">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_0198__b347913105215">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong></p>
|
||||
<p id="cce_10_0198__p16639453192911">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_0198__uicontrol138446827241742"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0198__uicontrol130024400641742"><b>System Disk</b></span>, you have the option not to add the default data disk.</p>
|
||||
<p id="cce_10_0198__p3752312011">Click <strong id="cce_10_0198__b513813367555">Expand</strong> to configure <strong id="cce_10_0198__b13265825195416">Data Disk Space Allocation</strong>, which is used to allocate 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>.</p>
|
||||
<p id="cce_10_0198__p1391618153118">For other data disks, a raw disk is created without any processing by default. You can also click <strong id="cce_10_0198__b16127101911540">Expand</strong> and select <strong id="cce_10_0198__b21351519135417">Mount Disk</strong> to mount the data disk to a specified directory. </p>
|
||||
|
||||
@ -80,7 +80,7 @@
|
||||
<p id="cce_10_0205__en-us_topic_0000001610054101_p1560152584011">v1.29</p>
|
||||
<p id="cce_10_0205__en-us_topic_0000001610054101_p12826164018">v1.30</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0205__en-us_topic_0000001610054101_p14503154015405">CCE clusters 1.30 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0205__en-us_topic_0000001610054101_p14503154015405">CCE clusters v1.30 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23.44%" headers="mcps1.3.7.2.2.5.1.4 "><p id="cce_10_0205__en-us_topic_0000001610054101_p11793246124019"><a href="https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.6.2" target="_blank" rel="noopener noreferrer">0.6.2</a></p>
|
||||
</td>
|
||||
@ -94,7 +94,7 @@
|
||||
<p id="cce_10_0205__en-us_topic_0000001610054101_p1713317244441">v1.28</p>
|
||||
<p id="cce_10_0205__en-us_topic_0000001610054101_p15583172610443">v1.29</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0205__en-us_topic_0000001610054101_p1854492818204">CCE clusters 1.29 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0205__en-us_topic_0000001610054101_p1854492818204">CCE clusters v1.29 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23.44%" headers="mcps1.3.7.2.2.5.1.4 "><p id="cce_10_0205__en-us_topic_0000001610054101_p1713392412448"><a href="https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.6.2" target="_blank" rel="noopener noreferrer">0.6.2</a></p>
|
||||
</td>
|
||||
@ -120,7 +120,7 @@
|
||||
<p id="cce_10_0205__en-us_topic_0000001610054101_p127061021181118">v1.27</p>
|
||||
<p id="cce_10_0205__en-us_topic_0000001610054101_p43751222191112">v1.28</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0205__en-us_topic_0000001610054101_p11726241111116">CCE clusters 1.28 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0205__en-us_topic_0000001610054101_p11726241111116">CCE clusters v1.28 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23.44%" headers="mcps1.3.7.2.2.5.1.4 "><p id="cce_10_0205__en-us_topic_0000001610054101_p5773929152111"><a href="https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.6.2" target="_blank" rel="noopener noreferrer">0.6.2</a></p>
|
||||
</td>
|
||||
@ -157,7 +157,7 @@
|
||||
<p id="cce_10_0205__en-us_topic_0000001610054101_p15342640191318">v1.23</p>
|
||||
<p id="cce_10_0205__en-us_topic_0000001610054101_p17980114341316">v1.25</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0205__en-us_topic_0000001610054101_p1348644981118">CCE clusters 1.25 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0205__en-us_topic_0000001610054101_p1348644981118">CCE clusters v1.25 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23.44%" headers="mcps1.3.7.2.2.5.1.4 "><p id="cce_10_0205__en-us_topic_0000001610054101_p1752950459"><a href="https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.6.2" target="_blank" rel="noopener noreferrer">0.6.2</a></p>
|
||||
</td>
|
||||
@ -168,7 +168,7 @@
|
||||
<p id="cce_10_0205__en-us_topic_0000001610054101_p2902141171214">v1.21</p>
|
||||
<p id="cce_10_0205__en-us_topic_0000001610054101_p690215418128">v1.23</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0205__en-us_topic_0000001610054101_p193531050161116">CCE clusters 1.23 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0205__en-us_topic_0000001610054101_p193531050161116">CCE clusters v1.23 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23.44%" headers="mcps1.3.7.2.2.5.1.4 "><p id="cce_10_0205__en-us_topic_0000001610054101_p7747930162017"><a href="https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.4.4" target="_blank" rel="noopener noreferrer">0.4.4</a></p>
|
||||
</td>
|
||||
@ -180,7 +180,7 @@
|
||||
<p id="cce_10_0205__en-us_topic_0000001610054101_p7236175551316">v1.19</p>
|
||||
<p id="cce_10_0205__en-us_topic_0000001610054101_p3236355181318">v1.21</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0205__en-us_topic_0000001610054101_p2041135112115">CCE clusters 1.21 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.7.2.2.5.1.3 "><p id="cce_10_0205__en-us_topic_0000001610054101_p2041135112115">CCE clusters v1.21 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23.44%" headers="mcps1.3.7.2.2.5.1.4 "><p id="cce_10_0205__en-us_topic_0000001610054101_p974713012207"><a href="https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.4.4" target="_blank" rel="noopener noreferrer">0.4.4</a></p>
|
||||
</td>
|
||||
|
||||
@ -26,7 +26,7 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0212__row97681533153914"><td class="cellrowborder" valign="top" width="18.891889188918892%" headers="mcps1.3.2.3.3.2.1.1.2.2.1.4.1.1 "><p id="cce_10_0212__p147681338393">SFS</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="28.642864286428644%" headers="mcps1.3.2.3.3.2.1.1.2.2.1.4.1.2 "><p id="cce_10_0212__p197683338397">SFS Capacity-Oriented</p>
|
||||
<td class="cellrowborder" valign="top" width="28.642864286428644%" headers="mcps1.3.2.3.3.2.1.1.2.2.1.4.1.2 "><p id="cce_10_0212__p197683338397">SFS Capacity-Oriented or SFS 3.0</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="52.465246524652464%" headers="mcps1.3.2.3.3.2.1.1.2.2.1.4.1.3 "><p id="cce_10_0212__p18768133163912">Yes</p>
|
||||
</td>
|
||||
@ -53,6 +53,13 @@
|
||||
<p id="cce_10_0212__p0769103323910">If you choose to retain the node, the logical volumes will not be deleted. If you choose to delete or reset the node, the logical volumes will be deleted.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0212__row5769203318393"><td class="cellrowborder" valign="top" width="18.891889188918892%" headers="mcps1.3.2.3.3.2.1.1.2.2.1.4.1.1 "><p id="cce_10_0212__p0769143311392">SFS 3.0 subdirectory</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="28.642864286428644%" headers="mcps1.3.2.3.3.2.1.1.2.2.1.4.1.2 "><p id="cce_10_0212__p1376913330398">A directory in SFS 3.0</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="52.465246524652464%" headers="mcps1.3.2.3.3.2.1.1.2.2.1.4.1.3 "><p id="cce_10_0212__p876993318399">No</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0212__row87691133103917"><td class="cellrowborder" valign="top" width="18.891889188918892%" headers="mcps1.3.2.3.3.2.1.1.2.2.1.4.1.1 "><p id="cce_10_0212__p476963333915">SFS Turbo subdirectory</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="28.642864286428644%" headers="mcps1.3.2.3.3.2.1.1.2.2.1.4.1.2 "><p id="cce_10_0212__p15769113343912">A directory in SFS Turbo</p>
|
||||
|
||||
@ -170,7 +170,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.2.2.3.2.2.2.5.1.3 "><p id="cce_10_0213__p5347223152718">QPS for communicating with kube-apiserver.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.2.2.5.1.4 "><ul id="cce_10_0213__ul394475419177"><li id="cce_10_0213__li1794414545171">If the number of nodes in a cluster is less than 1000, the default value is <strong id="cce_10_0213__b41151520101812">100</strong>.</li><li id="cce_10_0213__li7944135413179">If the number of nodes in a cluster is 1000 or more, the default value is <strong id="cce_10_0213__b18469114119183">200</strong>.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.2.2.5.1.4 "><ul id="cce_10_0213__ul394475419177"><li id="cce_10_0213__li1794414545171">If the number of nodes in a cluster is less than 1,000, the default value is <strong id="cce_10_0213__b41151520101812">100</strong>.</li><li id="cce_10_0213__li7944135413179">If the number of nodes in a cluster is 1,000 or more, the default value is <strong id="cce_10_0213__b18469114119183">200</strong>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0213__row73472023162715"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.2.2.5.1.1 "><p id="cce_10_0213__p164682027151215">Burst for communicating with kube-apiserver</p>
|
||||
@ -179,7 +179,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.2.2.3.2.2.2.5.1.3 "><p id="cce_10_0213__p134814230272">Burst for communicating with kube-apiserver.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.2.2.5.1.4 "><ul id="cce_10_0213__ul10944115410176"><li id="cce_10_0213__li9944954101710">If the number of nodes in a cluster is less than 1000, the default value is <strong id="cce_10_0213__b2577132320188">100</strong>.</li><li id="cce_10_0213__li09441354111715">If the number of nodes in a cluster is 1000 or more, the default value is <strong id="cce_10_0213__b1223517424188">200</strong>.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.2.2.5.1.4 "><ul id="cce_10_0213__ul10944115410176"><li id="cce_10_0213__li9944954101710">If the number of nodes in a cluster is less than 1,000, the default value is <strong id="cce_10_0213__b2577132320188">100</strong>.</li><li id="cce_10_0213__li09441354111715">If the number of nodes in a cluster is 1000 or more, the default value is <strong id="cce_10_0213__b1223517424188">200</strong>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0213__row51731335114"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.2.2.5.1.1 "><p id="cce_10_0213__p84681527151217">Whether to enable GPU sharing</p>
|
||||
@ -224,7 +224,7 @@
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.3.2.5.1.4 "><p id="cce_10_0213__p1099614952515">Default: 5</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0213__row59961149132519"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.3.2.5.1.1 "><p id="cce_10_0213__p62331155191813">Concurrent number of garbage collector</p>
|
||||
<tr id="cce_10_0213__row59961149132519"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.3.2.5.1.1 "><p id="cce_10_0213__p62331155191813">Concurrent number of garbage collectors</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.3.2.5.1.2 "><p id="cce_10_0213__p1999610493252">concurrent-gc-syncs</p>
|
||||
</td>
|
||||
@ -332,7 +332,7 @@
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.3.2.5.1.2 "><p id="cce_10_0213__p15998174913252">horizontal-pod-autoscaler-sync-period</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.2.2.3.2.3.2.5.1.3 "><p id="cce_10_0213__p246842473013">Period for the horizontal pod autoscaler to perform auto scaling on pods. A smaller value will result in a faster auto scaling response and higher CPU load.</p>
|
||||
<div class="note" id="cce_10_0213__note5420181233013"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0213__p1142012127304">Make sure to configure this parameter properly as a lengthy period can cause the controller to respond slowly, while a short period may overload the cluster control plane.</p>
|
||||
<div class="note" id="cce_10_0213__note5420181233013"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0213__p1142012127304">Make sure to configure this parameter properly as a lengthy period can cause the controller to respond slowly, while a short period may overload the cluster management plane.</p>
|
||||
</div></div>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.3.2.5.1.4 "><p id="cce_10_0213__p16998949172510">Default: 15 seconds</p>
|
||||
@ -380,7 +380,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.2.2.3.2.3.2.5.1.3 "><p id="cce_10_0213__p129981849202512">QPS for communicating with kube-apiserver</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.3.2.5.1.4 "><ul id="cce_10_0213__ul203961484174"><li id="cce_10_0213__li1839616482179">If the number of nodes in a cluster is less than 1000, the default value is <strong id="cce_10_0213__b65792023141817">100</strong>.</li><li id="cce_10_0213__li43967483173">If the number of nodes in a cluster is 1000 or more, the default value is <strong id="cce_10_0213__b1223610425188">200</strong>.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.3.2.5.1.4 "><ul id="cce_10_0213__ul203961484174"><li id="cce_10_0213__li1839616482179">If the number of nodes in a cluster is less than 1,000, the default value is <strong id="cce_10_0213__b65792023141817">100</strong>.</li><li id="cce_10_0213__li43967483173">If the number of nodes in a cluster is 1,000 or more, the default value is <strong id="cce_10_0213__b1223610425188">200</strong>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0213__row999824912254"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.3.2.5.1.1 "><p id="cce_10_0213__p182341955191812">Burst for communicating with kube-apiserver</p>
|
||||
@ -389,7 +389,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="40%" headers="mcps1.3.2.2.3.2.3.2.5.1.3 "><p id="cce_10_0213__p8998349162517">Burst for communicating with kube-apiserver</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.3.2.5.1.4 "><ul id="cce_10_0213__ul4822145051718"><li id="cce_10_0213__li1182215031718">If the number of nodes in a cluster is less than 1000, the default value is <strong id="cce_10_0213__b18580182311813">100</strong>.</li><li id="cce_10_0213__li15822205015172">If the number of nodes in a cluster is 1000 or more, the default value is <strong id="cce_10_0213__b8238134216187">200</strong>.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.3.2.5.1.4 "><ul id="cce_10_0213__ul4822145051718"><li id="cce_10_0213__li1182215031718">If the number of nodes in a cluster is less than 1,000, the default value is <strong id="cce_10_0213__b18580182311813">100</strong>.</li><li id="cce_10_0213__li15822205015172">If the number of nodes in a cluster is 1,000 or more, the default value is <strong id="cce_10_0213__b8238134216187">200</strong>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0213__row399894912515"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.3.2.3.2.5.1.1 "><p id="cce_10_0213__p20234105541817">The maximum number of terminated pods that can be kept before the Pod GC deletes the terminated pod</p>
|
||||
|
||||
@ -119,7 +119,7 @@
|
||||
<p id="cce_10_0240__en-us_topic_0000001610213713_p35031537155411">v1.27</p>
|
||||
<p id="cce_10_0240__en-us_topic_0000001610213713_p14300123865418">v1.28</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="42.85%" headers="mcps1.3.6.2.2.4.1.3 "><p id="cce_10_0240__en-us_topic_0000001610213713_p20166455511">CCE clusters 1.28 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="42.85%" headers="mcps1.3.6.2.2.4.1.3 "><p id="cce_10_0240__en-us_topic_0000001610213713_p20166455511">CCE clusters v1.28 are supported.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0240__en-us_topic_0000001610213713_row10867135317161"><td class="cellrowborder" valign="top" width="21.41%" headers="mcps1.3.6.2.2.4.1.1 "><p id="cce_10_0240__en-us_topic_0000001610213713_p129421456121613">1.3.14</p>
|
||||
@ -130,7 +130,7 @@
|
||||
<p id="cce_10_0240__en-us_topic_0000001610213713_p1194255618164">v1.25</p>
|
||||
<p id="cce_10_0240__en-us_topic_0000001610213713_p875593711713">v1.27</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="42.85%" headers="mcps1.3.6.2.2.4.1.3 "><p id="cce_10_0240__en-us_topic_0000001610213713_p11320115115519">CCE clusters 1.27 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="42.85%" headers="mcps1.3.6.2.2.4.1.3 "><p id="cce_10_0240__en-us_topic_0000001610213713_p11320115115519">CCE clusters v1.27 are supported.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
||||
@ -42,6 +42,11 @@
|
||||
<td class="cellrowborder" valign="top" width="76.67%" headers="mcps1.3.4.2.1.3.1.2 "><p id="cce_10_0277__p1939292732913">This add-on uses Prometheus-operator and Prometheus to provide easy-to-use, end-to-end Kubernetes cluster monitoring.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0277__row1686914202299"><td class="cellrowborder" valign="top" width="23.330000000000002%" headers="mcps1.3.4.2.1.3.1.1 "><p id="cce_10_0277__p5392227182919"><a href="cce_10_0416.html">Cloud Native Log Collection</a></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.67%" headers="mcps1.3.4.2.1.3.1.2 "><p id="cce_10_0277__p53920277291">This add-on collects logs and is built based on open-source Fluent Bit and OpenTelemetry. It supports CRD-based log collection policies. It collects and forwards stdout logs, container file logs, node logs, and Kubernetes event logs in a cluster based on configured policies.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0277__row9745144716292"><td class="cellrowborder" valign="top" width="23.330000000000002%" headers="mcps1.3.4.2.1.3.1.1 "><p id="cce_10_0277__p33251155132916"><a href="cce_10_0132.html">CCE Node Problem Detector</a></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="76.67%" headers="mcps1.3.4.2.1.3.1.2 "><p id="cce_10_0277__p19325155112912">This add-on monitors abnormal events of cluster nodes and connects to a third-party monitoring platform. It is a daemon running on each node. It collects node issues from different daemons and reports them to the API server. It can run as a DaemonSet or a daemon.</p>
|
||||
|
||||
@ -162,6 +162,7 @@
|
||||
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.2 "><p id="cce_10_0307__p19521418111910">TB</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.3 "><p id="cce_10_0307__p095211871914">SFS 1.0: PB</p>
|
||||
<p id="cce_10_0307__p8811113613390">SFS 3.0: EB</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.4 "><p id="cce_10_0307__p1975513539427">General-purpose: TB</p>
|
||||
</td>
|
||||
@ -173,6 +174,7 @@
|
||||
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.2 "><p id="cce_10_0307__p07991430122212">1–2 ms</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.3 "><p id="cce_10_0307__p97991230122210">SFS 1.0: 3–20 ms</p>
|
||||
<p id="cce_10_0307__p42481125173916">SFS 3.0: 10 ms</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.4 "><p id="cce_10_0307__p10755115318424">General-purpose: 1–5 ms</p>
|
||||
</td>
|
||||
@ -184,6 +186,7 @@
|
||||
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.2 "><p id="cce_10_0307__p14736184122317">2200–256000, depending on flavors</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.3 "><p id="cce_10_0307__p1373618414230">SFS 1.0: 2000</p>
|
||||
<p id="cce_10_0307__p175671083406">SFS 3.0: millions</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.4 "><p id="cce_10_0307__p11755115354210">General-purpose: up to 100,000</p>
|
||||
</td>
|
||||
@ -195,6 +198,7 @@
|
||||
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.2 "><p id="cce_10_0307__p3736124102318">MB/s</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.3 "><p id="cce_10_0307__p97361041234">SFS 1.0: GB/s</p>
|
||||
<p id="cce_10_0307__p54131356144012">SFS 3.0: TB/s</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="21.95121951219512%" headers="mcps1.3.4.2.1.6.1.4 "><p id="cce_10_0307__p177557530423">General-purpose: up to GB/s</p>
|
||||
</td>
|
||||
|
||||
@ -85,12 +85,13 @@ spec:
|
||||
csi:
|
||||
driver: nas.csi.everest.io # Dependent storage driver for the mounting
|
||||
fsType: nfs
|
||||
volumeHandle: <i><span class="varname" id="cce_10_0337__varname198781448171915"><your_volume_id></span></i> # ID of the SFS Capacity-Oriented volume
|
||||
volumeHandle: <i><span class="varname" id="cce_10_0337__varname198994011512"><your_volume_id></span></i> # ID of the SFS Capacity-Oriented volume or the SFS volume name when SFS 3.0 is used
|
||||
volumeAttributes:
|
||||
everest.io/share-export-location: <i><span class="varname" id="cce_10_0337__varname28789482191"><your_location></span></i> # Shared path of the SFS volume
|
||||
storage.kubernetes.io/csiProvisionerIdentity: everest-csi-provisioner
|
||||
everest.io/sfs-version: sfs3.0 # SFS 3.0 is used.
|
||||
persistentVolumeReclaimPolicy: Retain # Reclaim policy
|
||||
storageClassName: <i><span class="varname" id="cce_10_0337__varname18878448101912">csi-nas</span></i> # StorageClass name.
|
||||
storageClassName: <i><span class="varname" id="cce_10_0337__varname209451124168">csi-nas</span></i> # Storage class name. <strong id="cce_10_0337__b494552171614">csi-nas</strong> indicates that SFS Capacity-Oriented is used. <strong id="cce_10_0337__b179451026166">csi-sfs</strong> indicates that SFS 3.0 is used.
|
||||
<strong id="cce_10_0337__b58781748161917">mountOptions:</strong> # Mount options
|
||||
<strong id="cce_10_0337__b5878134810190"> - <i><span class="varname" id="cce_10_0337__varname787804816194">vers=3</span></i></strong>
|
||||
<strong id="cce_10_0337__b13878948191910"> - <i><span class="varname" id="cce_10_0337__varname18878104818196">nolock</span></i></strong>
|
||||
@ -116,6 +117,7 @@ parameters:
|
||||
csi.storage.k8s.io/csi-driver-name: nas.csi.everest.io
|
||||
csi.storage.k8s.io/fstype: nfs
|
||||
everest.io/share-access-to: <i><span class="varname" id="cce_10_0337__varname1524719214412"><your_vpc_id></span></i> # VPC ID of the cluster
|
||||
everest.io/sfs-version: sfs3.0 # SFS 3.0 is used. This parameter is not required for SFS Capacity-Oriented.
|
||||
reclaimPolicy: Delete
|
||||
volumeBindingMode: Immediate
|
||||
<strong id="cce_10_0337__b183867368219">mountOptions:</strong> # Mount options
|
||||
|
||||
@ -31,7 +31,10 @@
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.1.3.1.5.1.4 "><p id="cce_10_0342__cce_productdesc_0001_p529674301415">For users who have higher requirements on performance, resource utilization, and full-scenario coverage</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0342__cce_productdesc_0001_row17655747151910"><td class="cellrowborder" rowspan="5" valign="top" width="16.666666666666664%" headers="mcps1.3.1.3.1.5.1.1 "><p id="cce_10_0342__cce_productdesc_0001_p5596162515206">Specification difference</p>
|
||||
<tr id="cce_10_0342__cce_productdesc_0001_row17655747151910"><td class="cellrowborder" rowspan="4" valign="top" width="16.666666666666664%" headers="mcps1.3.1.3.1.5.1.1 "><p id="cce_10_0342__cce_productdesc_0001_p5596162515206">Specification difference</p>
|
||||
<p id="cce_10_0342__cce_productdesc_0001_p94317550531"></p>
|
||||
<p id="cce_10_0342__cce_productdesc_0001_p11431655125312"></p>
|
||||
<p id="cce_10_0342__cce_productdesc_0001_p184335514530"></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="16.666666666666664%" headers="mcps1.3.1.3.1.5.1.2 "><p id="cce_10_0342__cce_productdesc_0001_p19601423625">Network model</p>
|
||||
</td>
|
||||
@ -63,13 +66,6 @@
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.1.3.1.5.1.3 "><ul id="cce_10_0342__cce_productdesc_0001_ul465110531239"><li id="cce_10_0342__cce_productdesc_0001_li206514534317">VM-level isolation is supported for secure containers that run only on physical machines.</li><li id="cce_10_0342__cce_productdesc_0001_li76511653839">cgroups are used to isolate common containers.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0342__cce_productdesc_0001_row1029833314127"><td class="cellrowborder" valign="top" headers="mcps1.3.1.3.1.5.1.1 "><p id="cce_10_0342__cce_productdesc_0001_p10611023527">Edge infrastructure management</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.1.3.1.5.1.2 "><p id="cce_10_0342__cce_productdesc_0001_p52986338127">Not supported</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.1.3.1.5.1.3 "><p id="cce_10_0342__cce_productdesc_0001_p112988339123">Management of CloudPond edge sites</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
|
||||
@ -94,7 +94,7 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0363__row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.4.3.3.2.4.1.2.3.1.1 "><p id="cce_10_0363__p0669147185817">Data Disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.3.3.2.4.1.2.3.1.2 "><div class="p" id="cce_10_0363__p246755017336"><strong id="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_0363__b58051819219">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong><ul id="cce_10_0363__ul324262033711"><li id="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_0363__li6177165413374">Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.4.3.3.2.4.1.2.3.1.2 "><div class="p" id="cce_10_0363__p246755017336"><strong id="cce_10_0363__b1172475762013">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_0363__b147252057182019">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong><ul id="cce_10_0363__ul324262033711"><li id="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_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_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_0363__uicontrol2621173512497"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="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_0363__note95411755120"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="cce_10_0363__ul1388875765811"><li id="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_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>
|
||||
|
||||
@ -32,7 +32,7 @@ spec:
|
||||
property:
|
||||
ingress.beta.kubernetes.io/url-match-mode: STARTS_WITH
|
||||
pathType: ImplementationSpecific
|
||||
<strong id="cce_10_0364__b390065116541">ingressClassName: <i><span class="varname" id="cce_10_0364__varname13587111333413">nginx</span></i></strong> # Nginx Ingress is used. If multiple Nginx Ingress controllers are installed in the cluster, replace <em id="cce_10_0364__i719762118811">nginx</em> with the custom <a href="cce_10_0034.html#cce_10_0034__li0953175016455">name of the controller</a> associated with the ingress.</pre>
|
||||
<strong id="cce_10_0364__b390065116541">ingressClassName: <i><span class="varname" id="cce_10_0364__varname13587111333413">nginx</span></i></strong> # Nginx Ingress is used. If multiple NGINX Ingress Controllers are installed in the cluster, replace <em id="cce_10_0364__i719762118811">nginx</em> with the custom <a href="cce_10_0034.html#cce_10_0034__li0953175016455">name of the controller</a> associated with the ingress.</pre>
|
||||
</div>
|
||||
<div class="p" id="cce_10_0364__p1021712417523"><strong id="cce_10_0364__b1848175514817">For clusters of v1.21 or earlier:</strong><pre class="screen" id="cce_10_0364__screen119671360523">apiVersion: networking.k8s.io/v1beta1
|
||||
kind: Ingress
|
||||
@ -78,7 +78,7 @@ spec:
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="12.871287128712872%" headers="mcps1.3.4.2.2.2.5.3.2.5.1.3 "><p id="cce_10_0364__p15565195316403">String</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="47.524752475247524%" headers="mcps1.3.4.2.2.2.5.3.2.5.1.4 "><p id="cce_10_0364__p356545324010"><strong id="cce_10_0364__b769722682517">nginx</strong>: indicates that Nginx Ingress is used. This option is available only after the <span id="cce_10_0364__text5648114614202">NGINX Ingress Controller</span> add-on is installed. If multiple NGINX Ingress Controllers are installed in the cluster, replace <em id="cce_10_0364__i138231443889">nginx</em> with the custom <a href="cce_10_0034.html#cce_10_0034__li0953175016455">name of the controller</a> associated with the ingress.</p>
|
||||
<td class="cellrowborder" valign="top" width="47.524752475247524%" headers="mcps1.3.4.2.2.2.5.3.2.5.1.4 "><p id="cce_10_0364__p356545324010"><strong id="cce_10_0364__b769722682517">nginx</strong>: indicates that Nginx Ingress is used. This option is available only after the <span id="cce_10_0364__text5648114614202">NGINX Ingress Controller</span> add-on is installed. If multiple NGINX Ingress Controllers are installed in the cluster, replace <em id="cce_10_0364__i5486135492218">nginx</em> with the custom <a href="cce_10_0034.html#cce_10_0034__li0953175016455">name of the controller</a> associated with the ingress.</p>
|
||||
<p id="cce_10_0364__p2604185681818">Multiple <span id="cce_10_0364__text19866141417271">NGINX Ingress Controller</span> add-ons can be installed in one cluster if the add-on version is 2.5.4 or later. In this case, the value of this parameter must be the <a href="cce_10_0034.html#cce_10_0034__li0953175016455">controller name</a> customized during controller installation, which indicates that the ingress is managed by the controller.</p>
|
||||
<p id="cce_10_0364__p35651853114012">This parameter is mandatory when an ingress is created by calling the API.</p>
|
||||
</td>
|
||||
|
||||
@ -170,8 +170,8 @@ metadata:
|
||||
<strong id="cce_10_0378__b11409823104618">everest.io/reclaim-policy: retain-volume-only</strong>
|
||||
name: pv-evs-test
|
||||
labels:
|
||||
<strong id="cce_10_0378__b747539855"> </strong>failure-domain.beta.kubernetes.io/region: <i><span class="varname" id="cce_10_0378__varname1735169612"><your_region></span></i> # Region of the node where the application is to be deployed
|
||||
failure-domain.beta.kubernetes.io/zone: <i><span class="varname" id="cce_10_0378__varname348658370"><your_zone></span></i> # AZ of the node where the application is to be deployed
|
||||
<strong id="cce_10_0378__b1572065542"> </strong>failure-domain.beta.kubernetes.io/region: <i><span class="varname" id="cce_10_0378__varname704354107"><your_region></span></i> # Region of the node where the application is to be deployed
|
||||
failure-domain.beta.kubernetes.io/zone: <i><span class="varname" id="cce_10_0378__varname1488648867"><your_zone></span></i> # AZ of the node where the application is to be deployed
|
||||
spec:
|
||||
accessModes:
|
||||
- ReadWriteOnce
|
||||
|
||||
@ -48,6 +48,7 @@ NAME PROVISIONER AGE
|
||||
csi-disk everest-csi-provisioner 17d # EVS disk
|
||||
csi-disk-topology everest-csi-provisioner 17d # EVS disks created with delay
|
||||
csi-nas everest-csi-provisioner 17d # SFS 1.0
|
||||
csi-sfs everest-csi-provisioner 17d # SFS 3.0
|
||||
csi-obs everest-csi-provisioner 17d # OBS
|
||||
csi-sfsturbo everest-csi-provisioner 17d # SFS Turbo</pre>
|
||||
<div class="p" id="cce_10_0380__p18907106309">Each StorageClass contains the default parameters used for dynamically creating a PV. The following is an example of StorageClass for EVS disks:<pre class="screen" id="cce_10_0380__screen15484956183012">kind: StorageClass
|
||||
|
||||
@ -219,7 +219,7 @@ preemptionPolicy: PreemptLowerPriority
|
||||
value: -90000
|
||||
|
||||
EOF</pre>
|
||||
</p></li><li id="cce_10_0384__li8503750144419"><span>Deploy online and offline jobs and configure priorityClasses for these jobs.</span><p><p id="cce_10_0384__p16825144217223">The <strong id="cce_10_0384__b26751520144020">volcano.sh/qos-level</strong> annotation needs to be added to distinguish offline jobs. The value is an integer ranging from -7 to 7. If the value is less than 0, the job is an offline job. If the value is greater than or equal to 0, the job is an online job. You do not need to set this annotation for online jobs. For both online and offline jobs, set <strong id="cce_10_0384__b328785995">schedulerName</strong> to <strong id="cce_10_0384__b1116777117">volcano</strong> to enable Volcano.</p>
|
||||
</p></li><li id="cce_10_0384__li8503750144419"><span>Deploy online and offline jobs and configure priorityClasses for these jobs.</span><p><p id="cce_10_0384__p16825144217223">The <strong id="cce_10_0384__b26751520144020">volcano.sh/qos-level</strong> annotation needs to be added to distinguish offline jobs. The value is an integer ranging from -7 to 7. If the value is less than 0, the job is an offline job. If the value is greater than or equal to 0, the job is an online job. You do not need to set this annotation for online jobs. For both online and offline jobs, set <strong id="cce_10_0384__b584328753">schedulerName</strong> to <strong id="cce_10_0384__b562977157">volcano</strong> to enable Volcano.</p>
|
||||
<div class="note" id="cce_10_0384__note881010430447"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0384__p7811184318442">The priorities between online jobs and between offline jobs are not differentiated, and the value validity is not verified. If the value of <strong id="cce_10_0384__b1330893254011">volcano.sh/qos-level</strong> of an offline job is not a negative integer ranging from -7 to 0, the job is processed as an online job.</p>
|
||||
</div></div>
|
||||
<p id="cce_10_0384__p84551082233">For an offline job:</p>
|
||||
|
||||
@ -507,7 +507,7 @@ spec:
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="56.99999999999999%" headers="mcps1.3.11.2.2.5.1.3 "><p id="cce_10_0385__p18882328885">If the pod uses <strong id="cce_10_0385__b192375332571">hostNetwork</strong>, the ELB forwards the request to the host network after this annotation is used.</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__b1584339651">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__b87647312">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.11.2.2.5.1.4 "><p id="cce_10_0385__p1688232810812">v1.9 or later</p>
|
||||
</td>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -16,8 +16,8 @@
|
||||
<ul id="cce_10_0406__ul117815436270"><li id="cce_10_0406__li20178743182710">cap_dac_override: reads the Docker info data.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0406__section186134814119"><h4 class="sectiontitle">Installing the Add-on</h4><div class="note" id="cce_10_0406__note152084181520"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0406__p1752024116150">The Cloud Native Cluster Monitoring add-on automatically selects a deployment mode based on <strong id="cce_10_0406__b1389013472818"><a href="#cce_10_0406__li15556183414307">Data Storage Configuration</a></strong>. This is supported by Cloud Native Cluster Monitoring 3.7.1 or later.</p>
|
||||
<ul id="cce_10_0406__ul128792089306"><li id="cce_10_0406__li6656205432717">Original agent mode: Disable <strong id="cce_10_0406__b11381125313412">Local data storage</strong> and enable at least one of <strong id="cce_10_0406__b16381135313412">Report Monitoring Data to AOM</strong> and <strong id="cce_10_0406__b9381753173410">Report Monitoring Data to a Third-Party Platform</strong>.</li></ul>
|
||||
<ul id="cce_10_0406__ul565575402715"><li id="cce_10_0406__li5655175432710">Original server mode: Enable <strong id="cce_10_0406__b17654134718298">Local data storage</strong> and <strong id="cce_10_0406__b6339837132716">Report Monitoring Data to AOM</strong> or <strong id="cce_10_0406__b165474711290">Report Monitoring Data to a Third-Party Platform</strong>.</li></ul>
|
||||
<ul id="cce_10_0406__ul128792089306"><li id="cce_10_0406__li6656205432717">Original agent mode: Disable <strong id="cce_10_0406__b181671350142419">Local data storage</strong> and enable at least one of <strong id="cce_10_0406__b1116785018246">Report Monitoring Data to AOM</strong> and <strong id="cce_10_0406__b51681350202417">Report Monitoring Data to a Third-Party Platform</strong>.</li></ul>
|
||||
<ul id="cce_10_0406__ul565575402715"><li id="cce_10_0406__li5655175432710">Original server mode: Enable <strong id="cce_10_0406__b59795150252">Local data storage</strong> and <strong id="cce_10_0406__b209799153259">Report Monitoring Data to AOM</strong> or <strong id="cce_10_0406__b10980715152516">Report Monitoring Data to a Third-Party Platform</strong>.</li></ul>
|
||||
</div></div>
|
||||
<ol id="cce_10_0406__ol9183433182510"><li id="cce_10_0406__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_0406__b9129133220287"><span id="cce_10_0406__text77103384818">Add-ons</span></strong>, locate <strong id="cce_10_0406__b81291932132813">Cloud Native Cluster Monitoring</strong> on the right, and click <strong id="cce_10_0406__b812963252813">Install</strong>.</span></li><li id="cce_10_0406__li15556183414307"><a name="cce_10_0406__li15556183414307"></a><a name="li15556183414307"></a><span>On the <strong id="cce_10_0406__b1813011813218">Install Add-on</strong> page, enable at least one item in the <span class="uicontrol" id="cce_10_0406__uicontrol738210234336"><b>Data Storage Configuration</b></span> area.</span><p><ul id="cce_10_0406__ul14526143113393"><li id="cce_10_0406__li953119336397"><strong id="cce_10_0406__b143131455124117">Reporting Monitoring Data to AOM</strong>: Report Prometheus data to AOM. After this function is enabled, you can select the corresponding AOM instance. The collected basic metrics are free of charge. Custom metrics are charged by AOM. To interconnect with AOM, you must have certain permissions. Only <strong id="cce_10_0406__b75491191223">users in the </strong><strong id="cce_10_0406__b1254918920225">admin</strong><strong id="cce_10_0406__b954914912224"> user group</strong> can perform this operation.</li><li id="cce_10_0406__li2526203153919"><strong id="cce_10_0406__b5956191316337">Reporting Monitoring Data to a Third-Party Platform</strong>: To report Prometheus data to a third-party monitoring system, you need to enter the address and token of the third-party monitoring system and determine whether to skip certificate authentication.</li><li id="cce_10_0406__li185331058123918"><strong id="cce_10_0406__b108317571412">Local data storage</strong>: Select the type and size of a disk for storing monitoring data to store Prometheus data in PVCs in the cluster. <strong id="cce_10_0406__b12961482422">Storage volumes are not deleted along with the add-on.</strong> If local data storage is enabled, all components will be deployed. For details, see <a href="#cce_10_0406__section0377457163618">Components</a>.<div class="note" id="cce_10_0406__note59616874216"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0406__p1197168134212">An available PVC named <strong id="cce_10_0406__b1517373112412">pvc-prometheus-server</strong> exists in namespace <strong id="cce_10_0406__b417315362417">monitoring</strong> and will be used as the storage source.</p>
|
||||
</div></div>
|
||||
@ -226,7 +226,7 @@ custom-metrics-apiserver-d4f556ff9-l2j2m 38m 44Mi
|
||||
<p id="cce_10_0406__en-us_topic_0000001559534266_p10734145144610">v1.29</p>
|
||||
<p id="cce_10_0406__en-us_topic_0000001559534266_p16594859184612">v1.30</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.9.2.2.5.1.3 "><p id="cce_10_0406__en-us_topic_0000001559534266_p98111922164615">CCE clusters 1.30 are supported.</p>
|
||||
<td class="cellrowborder" valign="top" width="38.9%" headers="mcps1.3.9.2.2.5.1.3 "><p id="cce_10_0406__en-us_topic_0000001559534266_p98111922164615">CCE clusters v1.30 are supported.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23.44%" headers="mcps1.3.9.2.2.5.1.4 "><p id="cce_10_0406__en-us_topic_0000001559534266_p147341745134611"><a href="https://github.com/prometheus/prometheus/releases/tag/v2.37.8" target="_blank" rel="noopener noreferrer">2.37.8</a></p>
|
||||
</td>
|
||||
|
||||
177
docs/cce/umn/cce_10_0416.html
Normal file
177
docs/cce/umn/cce_10_0416.html
Normal file
File diff suppressed because it is too large
Load Diff
@ -85,7 +85,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="13.489999999999998%" headers="mcps1.3.2.2.2.7.1.3 mcps1.3.2.2.2.7.2.3 "><p id="cce_10_0476__p9985144614919">√</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="13.51%" headers="mcps1.3.2.2.2.7.1.3 "><p id="cce_10_0476__p1098515460915">x</p>
|
||||
<td class="cellrowborder" valign="top" width="13.51%" headers="mcps1.3.2.2.2.7.1.3 "><p id="cce_10_0476__p1098515460915">×</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="12.72%" headers="mcps1.3.2.2.2.7.1.4 "><p id="cce_10_0476__p119851446898">√</p>
|
||||
</td>
|
||||
@ -96,7 +96,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.2 mcps1.3.2.2.2.7.2.2 "><p id="cce_10_0476__p321017531171">√</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.3 mcps1.3.2.2.2.7.2.3 "><p id="cce_10_0476__p621045361710">x</p>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.3 mcps1.3.2.2.2.7.2.3 "><p id="cce_10_0476__p621045361710">×</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.3 "><p id="cce_10_0476__p102107538176">√</p>
|
||||
</td>
|
||||
@ -107,7 +107,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.2 mcps1.3.2.2.2.7.2.2 "><p id="cce_10_0476__p14448114717177">√</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.3 mcps1.3.2.2.2.7.2.3 "><p id="cce_10_0476__p1844894713176">x</p>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.3 mcps1.3.2.2.2.7.2.3 "><p id="cce_10_0476__p1844894713176">×</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.3 "><p id="cce_10_0476__p19449164716173">√</p>
|
||||
</td>
|
||||
@ -118,7 +118,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.2 mcps1.3.2.2.2.7.2.2 "><p id="cce_10_0476__p13194181491817">√</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.3 mcps1.3.2.2.2.7.2.3 "><p id="cce_10_0476__p91941914141813">x</p>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.3 mcps1.3.2.2.2.7.2.3 "><p id="cce_10_0476__p91941914141813">×</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.3 "><p id="cce_10_0476__p6194191401817">√</p>
|
||||
</td>
|
||||
@ -129,7 +129,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.2 mcps1.3.2.2.2.7.2.2 "><p id="cce_10_0476__p11986164611915">√</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.3 mcps1.3.2.2.2.7.2.3 "><p id="cce_10_0476__p1598617461491">x</p>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.3 mcps1.3.2.2.2.7.2.3 "><p id="cce_10_0476__p1598617461491">×</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.7.1.3 "><p id="cce_10_0476__p13986946493">√</p>
|
||||
</td>
|
||||
|
||||
@ -8,6 +8,12 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0182.html">Collecting Container Logs</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0793.html">Collecting Kubernetes Events</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0554.html">Collecting Control Plane Component Logs</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="cce_10_0792.html">Collecting Audit Logs</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
|
||||
67
docs/cce/umn/cce_10_0554.html
Normal file
67
docs/cce/umn/cce_10_0554.html
Normal file
@ -0,0 +1,67 @@
|
||||
<a name="cce_10_0554"></a><a name="cce_10_0554"></a>
|
||||
|
||||
<h1 class="topictitle1">Collecting Control Plane Component Logs</h1>
|
||||
<div id="body0000001709722974"><p id="cce_10_0554__p58681151939">CCE supports logging for master nodes. On the <strong id="cce_10_0554__b102311591311"><span id="cce_10_0554__text1164315336613">Logging</span></strong> page, you can select one or more control plane components (kube-controller-manager, kube-apiserver, and kube-scheduler) whose logs need to be reported.</p>
|
||||
<div class="section" id="cce_10_0554__section15915571101"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0554__ul1145273617100"><li id="cce_10_0554__li124521636151014">The cluster version must be v1.21.7-r0 or later, v1.23.5-r0 or later, or 1.25.</li><li id="cce_10_0554__li945218367100">There is required LTS resource quota.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0554__section133166619593"><a name="cce_10_0554__section133166619593"></a><a name="section133166619593"></a><h4 class="sectiontitle">Control Plane Components</h4><p id="cce_10_0554__p11944191815598">There are three control plane log types. Each log stream corresponds to a component of the Kubernetes control plane. To learn more about these components, see <a href="https://kubernetes.io/docs/concepts/overview/components/" target="_blank" rel="noopener noreferrer">Kubernetes Components</a>.</p>
|
||||
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0554__table513517459590" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Control plane components</caption><thead align="left"><tr id="cce_10_0554__row1114954515918"><th align="left" class="cellrowborder" valign="top" width="12.01%" id="mcps1.3.3.3.2.5.1.1"><p id="cce_10_0554__p191491845145919">Log Type</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="17.669999999999998%" id="mcps1.3.3.3.2.5.1.2"><p id="cce_10_0554__p714994595910">Component</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="25.09%" id="mcps1.3.3.3.2.5.1.3"><p id="cce_10_0554__p8149204510594">Log Stream</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="45.23%" id="mcps1.3.3.3.2.5.1.4"><p id="cce_10_0554__p151497452591">Description</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0554__row17149154575911"><td class="cellrowborder" rowspan="3" valign="top" width="12.01%" headers="mcps1.3.3.3.2.5.1.1 "><p id="cce_10_0554__p1714918451591">Control plane component logs</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="17.669999999999998%" headers="mcps1.3.3.3.2.5.1.2 "><p id="cce_10_0554__p111492451593">kube-apiserver</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="25.09%" headers="mcps1.3.3.3.2.5.1.3 "><p id="cce_10_0554__p1014994515916">kube-apiserver-{{clusterID}}</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="45.23%" headers="mcps1.3.3.3.2.5.1.4 "><p id="cce_10_0554__p12149134512598">It exposes Kubernetes APIs. For more information, see <a href="https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/" target="_blank" rel="noopener noreferrer">kube-apiserver</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0554__row101497452599"><td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.5.1.1 "><p id="cce_10_0554__p41495458590">kube-controller-manager</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.5.1.2 "><p id="cce_10_0554__p13149045115915">kube-controller-manager-{{clusterID}}</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.5.1.3 "><p id="cce_10_0554__p17149104510597">It manages controllers and embeds the core control loops shipped with Kubernetes. For more information, see <a href="https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/" target="_blank" rel="noopener noreferrer">kube-controller-manager</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0554__row1314918459590"><td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.5.1.1 "><p id="cce_10_0554__p1414914454595">kube-scheduler</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.5.1.2 "><p id="cce_10_0554__p141501645175916">kube-scheduler-{{clusterID}}</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.5.1.3 "><p id="cce_10_0554__p1415016451593">It manages when and where to run Pods in your cluster. For more information, see <a href="https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/" target="_blank" rel="noopener noreferrer">kube-scheduler</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0554__section1883701101111"><h4 class="sectiontitle">Enabling Control Plane Logging</h4><p id="cce_10_0554__p126238295311"><strong id="cce_10_0554__b1180172663417">Enabling control plane logging during cluster creation</strong></p>
|
||||
<ol id="cce_10_0554__ol7219545201112"><li id="cce_10_0554__li6836511185811">Log in to the CCE console.</li><li id="cce_10_0554__li1283621110581">In the upper right corner, click <strong id="cce_10_0554__b15789814153210">Create Cluster</strong>. Then, configure the parameters and click <strong id="cce_10_0554__b15285133215474">Next: Select Add-on</strong>.</li><li id="cce_10_0554__li1932603355813">On the displayed page, select <strong id="cce_10_0554__b690818158491">Cloud Native Log Collection</strong> and click <strong id="cce_10_0554__b5831345494">Next: Add-on Configuration</strong>.</li><li id="cce_10_0554__li1483631175820">On the displayed page, select <strong id="cce_10_0554__b331813114518">Control Plane Logs</strong> for <strong id="cce_10_0554__b15645137105118">Cloud Native Log Collection</strong>.</li><li id="cce_10_0554__li189746151115">Click <strong id="cce_10_0554__b358214685212">Next: Confirm configuration</strong>.</li></ol>
|
||||
<div class="p" id="cce_10_0554__p871324410308"><strong id="cce_10_0554__b97823310164">Enabling control plane logging for an existing cluster</strong><ol id="cce_10_0554__ol38732022182716"><li id="cce_10_0554__li13873172219274">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_0554__b628517393918">Logging</strong>.</li><li id="cce_10_0554__li17873022162717">Click the <strong id="cce_10_0554__b177716167186">Control Plane Logs</strong> tab and modify the settings in <strong id="cce_10_0554__b238610581918">Logging Settings</strong>.<div class="fignone" id="cce_10_0554__fig98810154215"><span class="figcap"><b>Figure 1 </b>Modifying logging settings</span><br><span><img id="cce_10_0554__image153861344516" src="en-us_image_0000002194626492.png"></span></div>
|
||||
</li><li id="cce_10_0554__li198731722132710">Determine whether to enable logging for each component. If yes, click <span><img id="cce_10_0554__image34861534151720" src="en-us_image_0000002065480294.png"></span>.</li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0554__section69816278134"><h4 class="sectiontitle">Viewing Control Plane Component Logs of the Target Cluster</h4><p id="cce_10_0554__p1415353118133"><strong id="cce_10_0554__b326912208394">Viewing control plane component logs of the target cluster on the CCE console</strong></p>
|
||||
<ol id="cce_10_0554__ol10360346161319"><li id="cce_10_0554__li736014469130">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_0554__b1130419651214"><span id="cce_10_0554__text1373515717710">Logging</span></strong>.</li><li id="cce_10_0554__li1360204610135">Click the <strong id="cce_10_0554__b10966142395111">Control Plane Logs</strong> tab and select the topic of logs to be viewed. For details about available control plane log types, see <a href="#cce_10_0554__section133166619593">Control Plane Components</a>. For details about related operations, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/lts/lts_04_1053.html" target="_blank" rel="noopener noreferrer">LTS User Guide</a>.</li></ol>
|
||||
<p id="cce_10_0554__p1372461963219"><strong id="cce_10_0554__b1769651124019">Viewing control plane component logs of the target cluster on the LTS console</strong></p>
|
||||
<ol id="cce_10_0554__ol110492218358"><li id="cce_10_0554__li010416221356">Log in to the LTS console and choose <strong id="cce_10_0554__b1496271643713">Log Management</strong>.</li><li id="cce_10_0554__li4104132212350">Search for the log group by cluster ID and click the log group name to view the log streams. For details, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/lts/lts_04_1053.html" target="_blank" rel="noopener noreferrer">LTS User Guide</a>.</li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0554__section1450954712188"><h4 class="sectiontitle">Disabling Control Plane Logging</h4><ol id="cce_10_0554__ol1060255016193"><li id="cce_10_0554__li660375011919">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_0554__b105785542178"><span id="cce_10_0554__text13171173217555">Logging</span></strong>.</li><li id="cce_10_0554__li10603450121916">Click the <strong id="cce_10_0554__b171893112562">Control Plane Logs</strong> tab. Then, modify the log setting.</li><li id="cce_10_0554__li1696341572112">Determine whether to enable logging for each component. If yes, click <span><img id="cce_10_0554__image1537119771814" src="en-us_image_0000002101597193.png"></span>.<div class="note" id="cce_10_0554__note76261859132113"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0554__p17627059162114">After you disable control plane logging, logs are no longer written to the original log stream, but the existing logs will not be deleted and expenses may be incurred for this.</p>
|
||||
</div></div>
|
||||
</li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0553.html">Logging</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
83
docs/cce/umn/cce_10_0555.html
Normal file
83
docs/cce/umn/cce_10_0555.html
Normal file
@ -0,0 +1,83 @@
|
||||
<a name="cce_10_0555"></a><a name="cce_10_0555"></a>
|
||||
|
||||
<h1 class="topictitle1">Collecting Container Logs Using Cloud Native Log Collection</h1>
|
||||
<div id="body0000001757561941"><p id="cce_10_0555__p1525318481827">The Cloud Native Log Collection add-on (<a href="cce_10_0416.html">Cloud Native Log Collection</a>) is built based on Fluent Bit and OpenTelemetry for collecting logs and Kubernetes events. This add-on supports CRD-based log collection policies. It collects and forwards stdout logs, container file logs, node logs, and Kubernetes events in a cluster based on configured policies.</p>
|
||||
<div class="section" id="cce_10_0555__section1995018241214"><h4 class="sectiontitle">Constraints</h4><ul id="cce_10_0555__ul38996572032"><li id="cce_10_0555__li1437118282351">A maximum of 50 log rules can be created for each cluster.</li><li id="cce_10_0555__li3899057134">The Cloud Native Log Collection add-on cannot collect .gz, .tar, and .zip logs and cannot access symbolic links of logs.</li><li id="cce_10_0555__li48992575320">If the node <a href="cce_10_0341.html#cce_10_0341__section1473612279214">storage driver</a> is Device Mapper, container file logs must be collected from the path where the data disk is attached to the node.</li><li id="cce_10_0555__li789910571632">If the container runtime is containerd, each stdout log cannot be in multiple lines. (This does not apply to the Cloud Native Log Collection add-on of version 1.3.0 or later.)</li><li id="cce_10_0555__li1319974510478">If a volume is attached to the data directory of a service container, this add-on cannot collect data from the parent directory. In this case, you need to configure a complete data directory.</li><li id="cce_10_0555__li930217527219">If the lifetime of a container is less than 1 minute, logs cannot be collected in a timely manner. As a result, logs may be lost.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0555__section53625241484"><h4 class="sectiontitle">Configuring Log Collection on the Console</h4><ol id="cce_10_0555__ol7318196796"><li id="cce_10_0555__li03181161493"><span>Enable log collection.</span><p><p id="cce_10_0555__p18411191814578"><strong id="cce_10_0555__b7437453122312">Enabling log collection during cluster creation</strong></p>
|
||||
<ol type="a" id="cce_10_0555__ol183617113584"><li id="cce_10_0555__li6836511185811">Log in to the CCE console.</li><li id="cce_10_0555__li1283621110581">Click <strong id="cce_10_0555__b1081016564140">Create</strong><strong id="cce_10_0555__b1236194719215"> Cluster</strong> from the top menu.</li><li id="cce_10_0555__li163681377132">On the <strong id="cce_10_0555__b553513241554">Select Add-on</strong> page, select <strong id="cce_10_0555__b25361624053">Cloud Native Log Collection</strong>.</li><li id="cce_10_0555__en-us_topic_0000001757561941_li1483631175820">Click <strong id="cce_10_0555__b1787703317193">Next: Add-on Configuration</strong> in the lower right corner and select the required logs.<ul id="cce_10_0555__ul15382152171319"><li id="cce_10_0555__li11382142171315">Container logs: A log collection policy named <strong id="cce_10_0555__b112473414364">default-stdout</strong> will be created, and stdout logs in all namespaces will be reported to LTS.</li><li id="cce_10_0555__li03821021171318">Kubernetes events: A log collection policy named <strong id="cce_10_0555__b1952854915384">default-event</strong> will be created, and Kubernetes events in all namespaces will be reported to LTS.</li></ul>
|
||||
</li><li id="cce_10_0555__en-us_topic_0000001757561941_li19681527171613">Click <strong id="cce_10_0555__b205211845354">Next: Confirm configuration</strong> in the lower right corner. On the displayed page, click <strong id="cce_10_0555__b55217452057">Submit</strong>.</li></ol>
|
||||
</p></li><li id="cce_10_0555__li193114172910"><span>View and configure log collection policies.</span><p><ol type="a" id="cce_10_0555__ol1431973318574"><li id="cce_10_0555__li1931973335715">On the CCE console, click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0555__b15558833102218"><span id="cce_10_0555__text67912038372">Logging</span></strong>.</li><li id="cce_10_0555__li10603839205711"><p id="cce_10_0555__p2604131442418"><a name="cce_10_0555__li10603839205711"></a><a name="li10603839205711"></a>In the upper right corner, click <strong id="cce_10_0555__b17604111432413">View Log Collection Policies</strong>.</p>
|
||||
<p id="cce_10_0555__li10603839205711p0">All log collection policies reported to LTS are displayed.</p>
|
||||
</li><li id="cce_10_0555__li1876513521447">In the upper right corner, click <strong id="cce_10_0555__b14931123151011">Create Log Collection Policy</strong>.<div class="note" id="cce_10_0555__note9771843165312"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0555__ul970311961213"><li id="cce_10_0555__li1676544725820">To avoid log disorder, you are advised to select different log streams for reporting logs in the log collection policies of various log types.</li><li id="cce_10_0555__li87655474588"><a name="cce_10_0555__li87655474588"></a><a name="li87655474588"></a>The following are requirements for configuring the container and node file log paths:<ul id="cce_10_0555__ul10247101135917"><li id="cce_10_0555__li170317918123">Log directory: Enter an absolute path, for example, <strong id="cce_10_0555__b643314810145">/log</strong>. The path must start with a slash (/) and contain a maximum of 512 characters. Only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), slashes (/), asterisks (*), and question marks (?) are allowed.</li><li id="cce_10_0555__li370349101210">Log file name: It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), asterisks (*), question marks (?), and periods (.). Logs in the format of .gz, .tar, and .zip are not supported.</li></ul>
|
||||
<p id="cce_10_0555__p18533101418205">The directory and file names must be complete and support asterisks (*) and question marks (?) as wildcards. A maximum of three levels of directories can be matched using wildcards. The level-1 directory does not support wildcards. An asterisk (*) can match multiple characters. A question mark (?) can match only one character. For example:</p>
|
||||
<ul id="cce_10_0555__ul1272693314525"><li id="cce_10_0555__li19409105316435">If the directory is <strong id="cce_10_0555__b1629982310212">/var/logs/*</strong> and the file name is <strong id="cce_10_0555__b2426182882119">*.log</strong>, the match expression is <strong id="cce_10_0555__b19572195941013">/var/logs/*/*.log</strong>, indicating that any files with the extension .log in all level-1 directories in the <strong id="cce_10_0555__b111644610221">/var/logs</strong> directory are matched. Note that this expression cannot match any files with the extension .log in the <strong id="cce_10_0555__b3668181723119">/var/logs</strong> directory and multi-level directories in the <strong id="cce_10_0555__b121751355241">/var/logs</strong> directory.</li><li id="cce_10_0555__li572643318529">If the directory is <strong id="cce_10_0555__b152661611261">/var/logs/app_*</strong> and the file name is <strong id="cce_10_0555__b1252610167265">*.log</strong>, any log files with the extension .log in all directories that match app_* in the <strong id="cce_10_0555__b15526171652614">/var/logs</strong> directory will be reported.</li></ul>
|
||||
</li></ul>
|
||||
</div></div>
|
||||
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0555__table677417101169" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Custom policy parameters</caption><thead align="left"><tr id="cce_10_0555__row1579111101961"><th align="left" class="cellrowborder" valign="top" id="mcps1.3.3.2.2.2.1.3.3.2.6.1.1"><p id="cce_10_0555__p5791161012618">Parameter</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" colspan="4" valign="top" id="mcps1.3.3.2.2.2.1.3.3.2.6.1.2"><p id="cce_10_0555__p64191419155411">Description</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0555__row06816173819"><td class="cellrowborder" valign="top" width="8%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.1 "><p id="cce_10_0555__p61501924189">Log Type</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p1015012241383"><strong id="cce_10_0555__b20259161811450">Container standard output</strong>: used to collect container stdout logs. You can create a log collection policy by namespace, workload name, or instance label.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p615014249814"><strong id="cce_10_0555__b174211216144512">Container file log</strong>: used to collect text logs. You can specify a workload or instance label to create a log collection policy.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p11501524986"><strong id="cce_10_0555__b77221313114510">Node file log</strong>: used to collect logs from a node. Only one file path can be configured for a log collection policy.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p1930312593485"><strong id="cce_10_0555__b58031127125617">Kubernetes Events</strong>: used to collect Kubernetes events. You can configure collection policies by namespace.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0555__row17912103614"><td class="cellrowborder" valign="top" width="8%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.1 "><p id="cce_10_0555__p14791111015611">Log Source</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><ul id="cce_10_0555__ul19401112015549"><li id="cce_10_0555__li1401122085410"><strong id="cce_10_0555__b116831092452">All containers</strong>: You can specify all containers in a namespace. If this parameter is not specified, logs of containers in all namespaces will be collected.</li><li id="cce_10_0555__li1540172015413"><strong id="cce_10_0555__b1381276204515">Workload</strong>: You can specify a workload and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.</li><li id="cce_10_0555__li12401162095416"><strong id="cce_10_0555__b38036324518">Workload with target label</strong>: You can specify a workload by label and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.</li></ul>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><ul id="cce_10_0555__ul1939610303549"><li id="cce_10_0555__li133251632185415"><strong id="cce_10_0555__b12017154510">Workload</strong>: You can specify a workload and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.</li><li id="cce_10_0555__li153251032195414"><strong id="cce_10_0555__b7626165684411">Workload with target label</strong>: You can specify a workload by label and its containers. If this parameter is not specified, logs of all containers running the workload will be collected.</li></ul>
|
||||
<p id="cce_10_0555__p4372813366">You also need to specify the log collection path. For details, see the <a href="#cce_10_0555__li87655474588">log path configuration requirements</a>.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p24321118144814"><strong id="cce_10_0555__b14942135616284">Collection Path</strong>: used to configure the log collection path. For details, see the <a href="#cce_10_0555__li87655474588">log path configuration requirements</a>.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p230325994811">You can specify a namespace whose Kubernetes events are to be collected. If no namespace is specified, Kubernetes events in all namespaces are collected.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0555__row079116101616"><td class="cellrowborder" valign="top" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.1 "><p id="cce_10_0555__p6791610565">Log Format</p>
|
||||
</td>
|
||||
<td class="cellrowborder" colspan="4" valign="top" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><ul id="cce_10_0555__ul1791101016613"><li id="cce_10_0555__li1179118107617"><strong id="cce_10_0555__b1776355124512">Single-line</strong><p id="cce_10_0555__p6791191012614">Each log contains only one line of text. The newline character \n denotes the start of a new log.</p>
|
||||
</li><li id="cce_10_0555__li167911310863"><strong id="cce_10_0555__b182891108451">Multi-line</strong><p id="cce_10_0555__p2791111011616">Some programs (for example, Java program) print a log that occupies multiple lines. By default, logs are collected by line. If you want to display logs as a single message, you can enable multi-line logging and use the regular pattern. When you select <strong id="cce_10_0555__b102361854144712">Multi-line</strong>, configure <strong id="cce_10_0555__b17663182414463">Log Matching Format</strong>.</p>
|
||||
<p id="cce_10_0555__p27925104610">For example, if logs need to be collected by line and each log starts with a date and occupies three lines, you can set <strong id="cce_10_0555__b189751636145113">Log Matching Format</strong> to the regular expression of the date, for example, <strong id="cce_10_0555__b179125675210">\d{4}-\d{2}-\d{2} \d{2}\:\d{2}\:\d{2}.*</strong>.</p>
|
||||
<div class="p" id="cce_10_0555__p137921102618">The three lines starting with the date are regarded as a log.<pre class="screen" id="cce_10_0555__screen158231642418">2022-01-01 00:00:00 Exception in thread "main" java.lang.RuntimeException: Something has gone wrong, aborting!
|
||||
at com.myproject.module.MyProject.badMethod(MyProject.java:22)
|
||||
at com.myproject.module.MyProject.oneMoreMethod(MyProject.java:18)</pre>
|
||||
</div>
|
||||
</li></ul>
|
||||
<p id="cce_10_0555__p153031259154813"></p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0555__row1817910451901"><td class="cellrowborder" valign="top" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.1 "><p id="cce_10_0555__p1521153432817">LTS Collection</p>
|
||||
</td>
|
||||
<td class="cellrowborder" colspan="4" valign="top" headers="mcps1.3.3.2.2.2.1.3.3.2.6.1.2 "><p id="cce_10_0555__p1426803105016">This parameter is used to configure the log group and log stream for log reporting.</p>
|
||||
<ul id="cce_10_0555__ul182871144212"><li id="cce_10_0555__li428774412116"><strong id="cce_10_0555__b1331453617213">Centralized</strong>: The default log group (<strong id="cce_10_0555__b2025961711224">k8s-log-</strong><em id="cce_10_0555__i9663522112214">{Cluster ID}</em>) and default log stream (<strong id="cce_10_0555__b62936263228">stdout-</strong><em id="cce_10_0555__i20398331102216">{Cluster ID}</em>) are automatically selected.</li><li id="cce_10_0555__li10593161413219"><strong id="cce_10_0555__b195492059184216">Custom</strong>: You can select any log group and log stream.<ul id="cce_10_0555__ul670713256568"><li id="cce_10_0555__li1474402185613"><strong id="cce_10_0555__b15831121832114">Log Group</strong>: A log group is the basic unit for LTS to manage logs. If you do not have a log group, CCE prompts you to create one. The default name is <strong id="cce_10_0555__b19437734311">k8s-log-</strong><em id="cce_10_0555__i1044577437">{Cluster ID}</em>, for example, <strong id="cce_10_0555__b164410724320">k8s-log-bb7eaa87-07dd-11ed-ab6c-0255ac1001b3</strong>.</li><li id="cce_10_0555__li529512810560"><strong id="cce_10_0555__b1021264713229">Log Stream</strong>: A log stream is the basic unit for reading and writing logs. You can put different types of logs into different streams to ease management. When you install the add-on or create a log collection policy based on the policy template, the following log streams are automatically created:<p id="cce_10_0555__p842710398561">- <strong id="cce_10_0555__b0432131914317">stdout-</strong><em id="cce_10_0555__i1843218195437">{Cluster ID}</em> for container logs, for example, <strong id="cce_10_0555__b2432191994311">stdout-bb7eaa87-07dd-11ed-ab6c-0255ac1001b3</strong></p>
|
||||
<p id="cce_10_0555__p36215428565">- <strong id="cce_10_0555__b35325223433">event-</strong><em id="cce_10_0555__i053219223431">{Cluster ID}</em> for Kubernetes events, for example, <strong id="cce_10_0555__b1353215228436">event-bb7eaa87-07dd-11ed-ab6c-0255ac1001b3</strong></p>
|
||||
</li></ul>
|
||||
</li></ul>
|
||||
<p id="cce_10_0555__p7303259124816"></p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</li></ol>
|
||||
</p></li><li id="cce_10_0555__li1174231917561"><span>View the logs.</span><p><ol type="a" id="cce_10_0555__ol260314783813"><li id="cce_10_0555__li166037715381">On the CCE console, click the cluster name to access the cluster console. In the navigation pane, choose <strong id="cce_10_0555__b17388135411315">Logging</strong>.</li><li id="cce_10_0555__li1679622425113">View different types of logs:</li><li id="cce_10_0555__li13713194763818">Click <strong id="cce_10_0555__b194631452163115">View Log Collection Policies</strong> in the upper right corner. Locate the log collection policy and click <strong id="cce_10_0555__b191892222324">View Log</strong> to go to the log list.</li></ol>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_10_0182.html">Collecting Container Logs</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -1,8 +1,9 @@
|
||||
<a name="cce_10_0557"></a><a name="cce_10_0557"></a>
|
||||
|
||||
<h1 class="topictitle1">Overview</h1>
|
||||
<div id="body0000001709722970"><p id="cce_10_0557__p15811134085211">Kubernetes logs allow you to locate and rectify faults. This section describes how you can manage Kubernetes logs generated for CCE.</p>
|
||||
<ul id="cce_10_0557__ul1581124010529"><li id="cce_10_0557__li72390542383">Connect CCE to AOM. For details, see <a href="cce_10_0018.html">Collecting Container Logs Using ICAgent</a>.</li></ul>
|
||||
<div id="body0000001709722970"><p id="cce_10_0557__p15811134085211">Kubernetes logs allow you to locate and rectify faults. This section describes methods for managing Kubernetes logs.</p>
|
||||
<p id="cce_10_0557__p1581110407521">Kubernetes log management methods:</p>
|
||||
<ul id="cce_10_0557__ul1581124010529"><li id="cce_10_0557__li1581184015527">Use the Cloud Native Log Collection add-on to collect application logs and report them to LTS that provides log statistics and analysis. For details, see <a href="cce_10_0555.html">Collecting Container Logs Using Cloud Native Log Collection</a>.</li><li id="cce_10_0557__li72390542383">Connect CCE to AOM. For details, see <a href="cce_10_0018.html">Collecting Container Logs Using ICAgent</a>.</li><li id="cce_10_0557__li1811240125214">Collect control plane component logs and Kubernetes audit logs from the CCE control plane and add them to the LTS log streams in your account. For details, see <a href="cce_10_0554.html">Collecting Control Plane Component Logs</a> and <a href="cce_10_0792.html">Collecting Audit Logs</a>.</li><li id="cce_10_0557__li08111840105213">Collect Kubernetes events and add them to the LTS log stream in your account for persistent storage and statistical analysis. For details, see <a href="cce_10_0793.html">Collecting Kubernetes Events</a>.</li></ul>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
|
||||
@ -111,7 +111,7 @@ status:
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0605__section21721238184220"><h4 class="sectiontitle">Drainage Through APIs</h4><ol id="cce_10_0605__ol144744325913"><li id="cce_10_0605__li094614815920"><span>Obtain the token in the region where the cluster is located. </span></li><li id="cce_10_0605__li1480227758"><span>Based on the API format, find the URL for the node drainage API.</span><p><div class="p" id="cce_10_0605__p1820543504810">URL of the API for draining a node:<pre class="screen" id="cce_10_0605__screen18205133515481">https://<i><span class="varname" id="cce_10_0605__varname1320512350489">{clusterid}</span></i>.<i><span class="varname" id="cce_10_0605__varname142051135194812">Endpoint</span></i>/apis/node.cce.io/v1/drainages</pre>
|
||||
<ul id="cce_10_0605__ul3205143514489"><li id="cce_10_0605__li22051635134811"><strong id="cce_10_0605__b196051701446">{clusterid}</strong>: cluster ID, which can be obtained on the <span class="uicontrol" id="cce_10_0605__uicontrol720517353480"><b><span id="cce_10_0605__text1020510353482">Overview</span></b></span> page of the CCE console.</li><li id="cce_10_0605__li120543510481"><strong id="cce_10_0605__b52054352483">Endpoint</strong>: endpoint of CCE in the region where the cluster is located.<p id="cce_10_0605__p1920573519482">For details about the value, see <a href="https://docs.otc.t-systems.com/regions-and-endpoints/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</p>
|
||||
<ul id="cce_10_0605__ul3205143514489"><li id="cce_10_0605__li22051635134811"><strong id="cce_10_0605__b196051701446">{clusterid}</strong>: cluster ID, which can be obtained on the <span class="uicontrol" id="cce_10_0605__uicontrol720517353480"><b><span id="cce_10_0605__text1020510353482">Overview</span></b></span> page of the CCE console.</li><li id="cce_10_0605__li120543510481"><strong id="cce_10_0605__b52054352483">Endpoint</strong>: endpoint of CCE in the region where the cluster is located.<p id="cce_10_0605__p1920573519482">For details about its value, see <a href="https://docs.otc.t-systems.com/regions-and-endpoints/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
</p></li><li id="cce_10_0605__li14348643202220"><span>Use the <strong id="cce_10_0605__b4432105414149">POST</strong> request method and configure request header parameters.</span><p><pre class="screen" id="cce_10_0605__screen8939174210332">curl --location --request POST '<i><span class="varname" id="cce_10_0605__varname1561813471122">https://{clusterid}.Endpoint/apis/node.cce.io/v1/drainages</span></i>' \
|
||||
@ -218,7 +218,7 @@ status:
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0605__section27122019181316"><h4 class="sectiontitle">Cancellation Through APIs</h4><ol id="cce_10_0605__ol197061325191311"><li id="cce_10_0605__li14706192571316"><span>Obtain the token in the region where the cluster is located. </span></li><li id="cce_10_0605__li97062254132"><span>Based on the API format, find the URL for the node drainage API.</span><p><div class="p" id="cce_10_0605__p18787920151515">URL of the API for canceling node drainage:<pre class="screen" id="cce_10_0605__screen290793916154">https://<i><span class="varname" id="cce_10_0605__varname14623715167">{clusterid}</span></i>.<i><span class="varname" id="cce_10_0605__varname1711183318466">Endpoint</span></i>/apis/node.cce.io/v1/drainages/<i><span class="varname" id="cce_10_0605__varname9938111414169">{drainageName}</span></i></pre>
|
||||
<ul id="cce_10_0605__ul1070716255137"><li id="cce_10_0605__li3707172517131"><strong id="cce_10_0605__b175142132614">{clusterid}</strong>: cluster ID, which can be obtained on the <span class="uicontrol" id="cce_10_0605__uicontrol6707132591314"><b><span id="cce_10_0605__text20707325131311">Overview</span></b></span> page of the CCE console.</li><li id="cce_10_0605__li14233154233918"><strong id="cce_10_0605__b1424854018591">Endpoint</strong>: endpoint of CCE in the region where the cluster is located.<p id="cce_10_0605__p19964248113911">For details about the value, see <a href="https://docs.otc.t-systems.com/regions-and-endpoints/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</p>
|
||||
<ul id="cce_10_0605__ul1070716255137"><li id="cce_10_0605__li3707172517131"><strong id="cce_10_0605__b175142132614">{clusterid}</strong>: cluster ID, which can be obtained on the <span class="uicontrol" id="cce_10_0605__uicontrol6707132591314"><b><span id="cce_10_0605__text20707325131311">Overview</span></b></span> page of the CCE console.</li><li id="cce_10_0605__li14233154233918"><strong id="cce_10_0605__b1424854018591">Endpoint</strong>: endpoint of CCE in the region where the cluster is located.<p id="cce_10_0605__p19964248113911">For details about its value, see <a href="https://docs.otc.t-systems.com/regions-and-endpoints/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</p>
|
||||
</li><li id="cce_10_0605__li1121021991715"><strong id="cce_10_0605__b3365172691715">{drainageName}</strong>: name of the drainage resource, which can be obtained by running the <strong id="cce_10_0605__b182995558179">kubectl get drainages</strong> command.</li></ul>
|
||||
</div>
|
||||
</p></li><li id="cce_10_0605__li2707142541313"><span>Use the <strong id="cce_10_0605__b957153616181">PATCH</strong> request method and configure request header parameters.</span><p><pre class="screen" id="cce_10_0605__screen7707172571318">curl --location --request PATCH '<i><span class="varname" id="cce_10_0605__varname20707192512138">https://{clusterid}.Endpoint/apis/node.cce.io/v1/drainages</span></i>/<i><span class="varname" id="cce_10_0605__varname16480164733112">{drainageName}</span></i>' \
|
||||
|
||||
@ -72,7 +72,7 @@
|
||||
<tr id="cce_10_0616__row42401835164617"><td class="cellrowborder" valign="top" width="22.88%" headers="mcps1.3.3.2.4.2.1.2.1.3.1.1 "><p id="cce_10_0616__p846111461379">Resource Tag</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="77.12%" headers="mcps1.3.3.2.4.2.1.2.1.3.1.2 "><p id="cce_10_0616__p14909254174019">You can add resource tags to classify resources, which is supported only when the Everest version in the cluster is 2.1.39 or later.</p>
|
||||
<p id="cce_10_0616__p39964137498">You can create <span class="uicontrol" id="cce_10_0616__uicontrol11865124765418"><b>predefined tags</b></span> on the <span id="cce_10_0616__ph125782541923">TMS</span> 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_0616__p39964137498">You can create <span class="uicontrol" id="cce_10_0616__uicontrol11865124765418"><b>predefined tags</b></span> on the <span id="cce_10_0616__ph19633122053517">TMS</span> 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_0616__p1738110524401">CCE automatically creates system tags <strong id="cce_10_0616__b97432908843030">CCE-Cluster-ID=</strong><em id="cce_10_0616__i167059465043030">{Cluster ID}</em>, <strong id="cce_10_0616__b193483387143030">CCE-Cluster-Name=</strong><em id="cce_10_0616__i96254406343030">{Cluster name}</em>, and <strong id="cce_10_0616__b46602048143030">CCE-Namespace=</strong><em id="cce_10_0616__i164724177943030">{Namespace name}</em>. These tags cannot be modified.</p>
|
||||
<div class="note" id="cce_10_0616__note1625537165313"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0616__p7255271533">After a dynamic PV of the EVS type is created, the resource tags cannot be updated on the CCE console. To update these resource tags, go to the EVS console.</p>
|
||||
</div></div>
|
||||
|
||||
@ -5,6 +5,50 @@
|
||||
<p id="cce_10_0617__p142061844581">Expandable to petabytes, SFS provides fully hosted shared file storage, highly available and stable to handle data- and bandwidth-intensive applications</p>
|
||||
<ul id="cce_10_0617__ul10598125623816"><li id="cce_10_0617__li3598556163813"><strong id="cce_10_0617__b537118393312">Standard file protocols</strong>: You can mount file systems as volumes to servers, the same as using local directories.</li><li id="cce_10_0617__li45981656153819"><strong id="cce_10_0617__b14788171632410">Data sharing</strong>: The same file system can be mounted to multiple servers, so that data can be shared.</li><li id="cce_10_0617__li1859895616386"><strong id="cce_10_0617__b494142517243">Private network</strong>: Users can access data only in private networks of data centers.</li><li id="cce_10_0617__li1359865617380"><strong id="cce_10_0617__b1895782612291">Capacity and performance</strong>: The capacity of a single file system is high (PB level) and the performance is excellent (ms-level I/O latency).</li><li id="cce_10_0617__li953501813619"><strong id="cce_10_0617__b86341030112914">Use cases</strong>: Deployments/StatefulSets in the ReadWriteMany mode and jobs created for high-performance computing (HPC), media processing, content management, web services, big data analysis, and workload process analysis</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0617__section834645511456"><h4 class="sectiontitle">Performance</h4><div class="p" id="cce_10_0617__p24575564399">CCE supports SFS Capacity-Oriented and SFS 3.0. For details about file system types, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/sfs/sfs_01_0005.html" target="_blank" rel="noopener noreferrer">File System Types </a>.<div class="note" id="cce_10_0617__note24185259412"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0617__ul338418312448"><li id="cce_10_0617__li938414324413">SFS Capacity-Oriented file systems are sold out and cannot be used to create PVs on the CCE console. However, you can still create PVs using existing SFS Capacity-Oriented file systems through <a href="cce_10_0619.html#cce_10_0619__section99931811195117">kubectl</a>.</li></ul>
|
||||
</div></div>
|
||||
</div>
|
||||
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0617__table96842242313" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Performance</caption><thead align="left"><tr id="cce_10_0617__row36859218231"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.3.2.4.1.1"><p id="cce_10_0617__p2685162112314">Parameter</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.3.2.4.1.2"><p id="cce_10_0617__p1668518219236">SFS Capacity-Oriented</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.3.2.4.1.3"><p id="cce_10_0617__p7861816205319">SFS 3.0</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="cce_10_0617__row1068511202310"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.3.2.4.1.1 "><p id="cce_10_0617__p868511272311">Maximum bandwidth</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.3.2.4.1.2 "><p id="cce_10_0617__p1490415513546">2 GB/s</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.3.2.4.1.3 "><p id="cce_10_0617__p1996531820540">1.25 TB/s</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0617__row568552182317"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.3.2.4.1.1 "><p id="cce_10_0617__p10685162152318">Maximum IOPS</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.3.2.4.1.2 "><p id="cce_10_0617__p196506714327">2000</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.3.2.4.1.3 "><p id="cce_10_0617__p378361973219">Million</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0617__row1685172152315"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.3.2.4.1.1 "><p id="cce_10_0617__p10685182122315">Latency</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.3.2.4.1.2 "><p id="cce_10_0617__p11934511163317">3–20 ms</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.3.2.4.1.3 "><p id="cce_10_0617__p59341911163313">10 ms</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="cce_10_0617__row19571517152720"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.3.2.4.1.1 "><p id="cce_10_0617__p10571417132715">Maximum capacity</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.3.2.4.1.2 "><p id="cce_10_0617__p2754882347">4 PB</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.3.2.4.1.3 "><p id="cce_10_0617__p860901812341">EB</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0617__section68331626505"><h4 class="sectiontitle">Application Scenarios</h4><p id="cce_10_0617__p280442065010">SFS supports the following mounting modes based on application scenarios:</p>
|
||||
<ul id="cce_10_0617__ul1334371835116"><li id="cce_10_0617__li63431218125114"><a href="cce_10_0619.html">Using an Existing SFS File System Through a Static PV</a>: static creation mode, where you use an existing SFS volume to create a PV and then mount storage to the workload through a PVC. This mode applies if the underlying storage is available.</li><li id="cce_10_0617__li1384127155117"><a href="cce_10_0620.html">Using an SFS File System Through a Dynamic PV</a>: dynamic creation mode, in which you do not need to create SFS file systems beforehand. Instead, specify a StorageClass when creating a PVC. Then, a file system and PV will be created automatically. This mode applies to scenarios where no underlying storage is available.</li></ul>
|
||||
</div>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -6,7 +6,7 @@
|
||||
<ul id="cce_10_0624__ul222119314424"><li id="cce_10_0624__li82215317429"><strong id="cce_10_0624__b6806185013511">Standard file protocols</strong>: You can mount file systems as volumes to servers, the same as using local directories.</li><li id="cce_10_0624__li522115314210"><strong id="cce_10_0624__b457155935118">Data sharing</strong>: The same file system can be mounted to multiple servers, so that data can be shared.</li><li id="cce_10_0624__li422120318427"><strong id="cce_10_0624__b1030817408219">Private network</strong>: Users can access data only in private networks of data centers.</li><li id="cce_10_0624__li202212036421"><strong id="cce_10_0624__b1906796275105057">Data isolation</strong>: The on-cloud storage service provides exclusive cloud file storage, which delivers data isolation and ensures IOPS performance.</li><li id="cce_10_0624__li122283134215"><strong id="cce_10_0624__b11762193905219">Use cases</strong>: Deployments/StatefulSets in the ReadWriteMany mode, DaemonSets, and jobs created for high-traffic websites, log storage, DevOps, and enterprise OA applications</li></ul>
|
||||
</div>
|
||||
<div class="section" id="cce_10_0624__section68331626505"><h4 class="sectiontitle">Application Scenarios</h4><p id="cce_10_0624__p280442065010">SFS Turbo supports the following mounting modes:</p>
|
||||
<ul id="cce_10_0624__ul1334371835116"><li id="cce_10_0624__li63431218125114"><a href="cce_10_0625.html">Using an Existing SFS Turbo File System Through a Static PV</a>: static creation mode, where you use an existing SFS volume to create a PV and then mount storage to the workload through a PVC.</li><li id="cce_10_0624__li14472144211428"><a href="cce_bestpractice_00253_0.html">Dynamically Creating an SFS Turbo Subdirectory Using StorageClass</a>: SFS Turbo allows you to dynamically create subdirectories and mount them to containers so that SFS Turbo can be shared and the SFS Turbo storage capacity can be used more economically and properly.</li></ul>
|
||||
<ul id="cce_10_0624__ul1334371835116"><li id="cce_10_0624__li63431218125114"><a href="cce_10_0625.html">Using an Existing SFS Turbo File System Through a Static PV</a>: static creation mode, where you use an existing SFS volume to create a PV and then mount storage to the workload through a PVC.</li><li id="cce_10_0624__li14472144211428"><a href="cce_bestpractice_00253.html">Dynamically Creating an SFS Turbo Subdirectory Using StorageClass</a>: SFS Turbo allows you to dynamically create subdirectories and mount them to containers so that SFS Turbo can be shared and the SFS Turbo storage capacity can be used more economically and properly.</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -95,7 +95,7 @@
|
||||
</tr>
|
||||
<tr id="cce_10_0653__en-us_topic_0000001199021246_row1966913718588"><td class="cellrowborder" valign="top" width="20.02%" headers="mcps1.3.2.2.3.2.3.2.2.3.1.1 "><p id="cce_10_0653__en-us_topic_0000001199021246_p0669147185817">Data Disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.3.2.2.3.1.2 "><div class="p" id="cce_10_0653__en-us_topic_0000001199021246_p246755017336"><strong id="cce_10_0653__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_0653__cce_10_0363_b58051819219">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong><ul id="cce_10_0653__cce_10_0363_ul324262033711"><li id="cce_10_0653__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_0653__cce_10_0363_li6177165413374">Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="79.97999999999999%" headers="mcps1.3.2.2.3.2.3.2.2.3.1.2 "><div class="p" id="cce_10_0653__en-us_topic_0000001199021246_p246755017336"><strong id="cce_10_0653__cce_10_0363_b1172475762013">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_0653__cce_10_0363_b147252057182019">This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.</strong><ul id="cce_10_0653__cce_10_0363_ul324262033711"><li id="cce_10_0653__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_0653__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>
|
||||
<div class="note" id="cce_10_0653__note21798915509"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0653__p13544143175218">After the data disk configuration is modified, the modification takes effect only on newly added nodes. The configuration cannot be synchronized to existing nodes even if they are reset.</p>
|
||||
</div></div>
|
||||
@ -103,8 +103,8 @@
|
||||
<p id="cce_10_0653__en-us_topic_0000001199021246_p3752312011">Expand the area and configure the following parameters:</p>
|
||||
<ul id="cce_10_0653__en-us_topic_0000001199021246_ul197721145155911"><li id="cce_10_0653__en-us_topic_0000001199021246_li12110343014"><strong id="cce_10_0653__b11121533832215">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>.<div class="note" id="cce_10_0653__note165242505419"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0653__p196522251548">After the data disk space allocation configuration is modified, the modification takes effect only for new nodes. The configuration cannot take effect for the existing nodes even if they are reset.</p>
|
||||
</div></div>
|
||||
</li><li id="cce_10_0653__en-us_topic_0000001199021246_li1095641711169"><strong id="cce_10_0653__b71171410204510">Enabled</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_0653__en-us_topic_0000001199021246_ul1924511512168"><li id="cce_10_0653__en-us_topic_0000001199021246_li4245181561611"><strong id="cce_10_0653__b297387065">Not encrypted</strong> is selected by default.</li><li id="cce_10_0653__en-us_topic_0000001199021246_li17245415121616">After setting <strong id="cce_10_0653__b119442517458">Data Disk Encryption</strong> to <strong id="cce_10_0653__b6194192554518">Enabled</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0653__b2019512253459">View Key List</strong> and create a key. After the key is created, click the refresh icon next to the key text box.</li></ul>
|
||||
<div class="note" id="cce_10_0653__note17572111875311"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0653__p05729189537">After the <strong id="cce_10_0653__b7507148121716">Data Disk Encryption</strong> is modified, the modification takes effect only on newly added nodes. The configuration cannot be synchronized to existing nodes even if they are reset.</p>
|
||||
</li><li id="cce_10_0653__en-us_topic_0000001199021246_li1095641711169"><strong id="cce_10_0653__b71171410204510">Enabled</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_0653__en-us_topic_0000001199021246_ul1924511512168"><li id="cce_10_0653__en-us_topic_0000001199021246_li4245181561611"><strong id="cce_10_0653__b853762100">Not encrypted</strong> is selected by default.</li><li id="cce_10_0653__en-us_topic_0000001199021246_li17245415121616">After setting <strong id="cce_10_0653__b119442517458">Data Disk Encryption</strong> to <strong id="cce_10_0653__b6194192554518">Enabled</strong>, choose an existing key. If no key is available, click <strong id="cce_10_0653__b2019512253459">View Key List</strong> and create a key. After the key is created, click the refresh icon next to the key text box.</li></ul>
|
||||
<div class="note" id="cce_10_0653__note17572111875311"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="cce_10_0653__p05729189537">After the <strong id="cce_10_0653__b118125422100">Data Disk Encryption</strong> is modified, the modification takes effect only on newly added nodes. The configuration cannot be synchronized to existing nodes even if they are reset.</p>
|
||||
</div></div>
|
||||
</li></ul>
|
||||
<p id="cce_10_0653__en-us_topic_0000001199021246_p1391618153118"><strong id="cce_10_0653__b5178902844730">Adding data disks</strong></p>
|
||||
|
||||
@ -69,7 +69,7 @@
|
||||
<p id="cce_10_0659__cce_10_0132_p2317112419618">Typical scenario: Disk I/O suspension causes process suspension.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33%" headers="mcps1.3.5.4.1.2.2.4.1.3 "><p id="cce_10_0659__cce_10_0132_p16872758114011">Warning event</p>
|
||||
<p id="cce_10_0659__cce_10_0132_p173071159247">Listening object: <strong id="cce_10_0659__cce_10_0132_b1783717768">/dev/kmsg</strong></p>
|
||||
<p id="cce_10_0659__cce_10_0132_p173071159247">Listening object: <strong id="cce_10_0659__cce_10_0132_b2054558210">/dev/kmsg</strong></p>
|
||||
<p id="cce_10_0659__cce_10_0132_p153079591241">Matching rule: "task \\S+:\\w+ blocked for more than \\w+ seconds\\."</p>
|
||||
</td>
|
||||
</tr>
|
||||
@ -81,7 +81,7 @@
|
||||
</div></div>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33%" headers="mcps1.3.5.4.1.2.2.4.1.3 "><p id="cce_10_0659__cce_10_0132_p944535317711">Warning event</p>
|
||||
<p id="cce_10_0659__cce_10_0132_p183981710948">Listening object: <strong id="cce_10_0659__cce_10_0132_b1235710589">/dev/kmsg</strong></p>
|
||||
<p id="cce_10_0659__cce_10_0132_p183981710948">Listening object: <strong id="cce_10_0659__cce_10_0132_b810243499">/dev/kmsg</strong></p>
|
||||
<p id="cce_10_0659__cce_10_0132_p83993101042">Matching rule: <strong id="cce_10_0659__cce_10_0132_b15200817134219">Remounting filesystem read-only</strong></p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user