forked from docs/doc-exports
qiujiandong1
affc0093ff
Reviewed-by: Gergo-Bence Lorincz <a200452876@noreply.gitea.eco.tsi-dev.otc-service.com> Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com> Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
121 lines
23 KiB
HTML
121 lines
23 KiB
HTML
<a name="cce_10_0341"></a><a name="cce_10_0341"></a>
|
|
|
|
<h1 class="topictitle1">Space Allocation of a Data Disk</h1>
|
|
<div id="body32001227"><p id="cce_10_0341__en-us_topic_0000002467676973_p12279151419394">This section describes how to allocate data disk space to nodes so that you can configure the data disk space accordingly.</p>
|
|
<div class="section" id="cce_10_0341__en-us_topic_0000002467676973_section280501719205"><h4 class="sectiontitle">Allocating Default Data Disk Space</h4><div class="note" id="cce_10_0341__en-us_topic_0000002467676973_note1376101183712"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="cce_10_0341__en-us_topic_0000002467676973_ul595011464213"><li id="cce_10_0341__en-us_topic_0000002467676973_li12950111419422">In clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.29.4-r0, or v1.28.8-r0, a default data disk will be added to the node for the container runtime and kubelet components. You can customize the space allocation of the default data disk.</li><li id="cce_10_0341__en-us_topic_0000002467676973_li199501714144212">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, a default data disk will be added to the node for the container runtime and kubelet components only if <span class="uicontrol" id="cce_10_0341__en-us_topic_0000002467676973_uicontrol2621173512497"><b>System Component Storage</b></span> is set to <span class="uicontrol" id="cce_10_0341__en-us_topic_0000002467676973_uicontrol19561032184918"><b>Data Disk</b></span>. You can customize the space allocation of the default data disk.</li></ul>
|
|
</div></div>
|
|
<p id="cce_10_0341__en-us_topic_0000002467676973_p8060118">When creating a node, you can customize <span class="keyword" id="cce_10_0341__en-us_topic_0000002467676973_keyword1734120221669">Data Disk Space Allocation</span> in the expanded area of <span class="uicontrol" id="cce_10_0341__en-us_topic_0000002467676973_uicontrol121091440172612"><b>Data Disk</b></span>.</p>
|
|
<p id="cce_10_0341__en-us_topic_0000002467676973_p1034712531457"></p>
|
|
<ul id="cce_10_0341__en-us_topic_0000002467676973_ul131071177194"><li id="cce_10_0341__en-us_topic_0000002467676973_li75465483589"><a href="#cce_10_0341__en-us_topic_0000002467676973_section10653143445411">Space Allocation for Container Engines</a><ul id="cce_10_0341__en-us_topic_0000002467676973_ul2083615352295"><li id="cce_10_0341__en-us_topic_0000002467676973_li98166257293">Specified disk space: CCE divides the data disk space for two parts by default. One part is used to store the Docker/containerd working directories, container image data, and image metadata. The other is reserved for kubelet and emptyDir volumes. The available container engine space affects image pulls and container startup and running.<ul id="cce_10_0341__en-us_topic_0000002467676973_ul173317395216"><li id="cce_10_0341__en-us_topic_0000002467676973_li369761103910"><span class="keyword" id="cce_10_0341__en-us_topic_0000002467676973_keyword15707281608">Container engine and container image space</span> (90% by default): stores the container runtime working directories, container image data, and image metadata.</li><li id="cce_10_0341__en-us_topic_0000002467676973_li173353922114">kubelet and emptyDir space (10% by default): stores pod configuration files, secrets, and mounted storage such as emptyDir volumes.</li></ul>
|
|
<div class="note" id="cce_10_0341__en-us_topic_0000002467676973_note16934142310486"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="cce_10_0341__en-us_topic_0000002467676973_p793416236481">If the sum of the <span class="keyword" id="cce_10_0341__en-us_topic_0000002467676973_keyword14248183414481">container engine and container image space</span> and the kubelet and emptyDir space is less than 100%, the remaining space will be allocated for user data. You can mount the storage volume to a service path. Do not leave the path empty or set it to a key OS path such as the root directory.</p>
|
|
</div></div>
|
|
</li></ul>
|
|
</li><li id="cce_10_0341__en-us_topic_0000002467676973_li1046332121913"><a href="#cce_10_0341__en-us_topic_0000002467676973_section12119191161518">Space Allocation for Pods</a>: indicates the <span class="keyword" id="cce_10_0341__en-us_topic_0000002467676973_keyword97051130195211">basesize</span> of a pod. You can set an upper limit for the disk space occupied by each workload pod (including the space occupied by container images). This setting prevents the pods from taking all the disk space available, which may cause service exceptions. It is recommended that the value is less than or equal to 80% of the container engine space. This parameter is related to the node OS and container storage Rootfs and is not supported in some scenarios. For details, see <a href="#cce_10_0341__en-us_topic_0000002467676973_section1473612279214">Mapping Between OS and Container Storage Rootfs</a>.</li><li id="cce_10_0341__en-us_topic_0000002467676973_li11911416113819">Write Mode<ul id="cce_10_0341__en-us_topic_0000002467676973_ul1149264515384"><li id="cce_10_0341__en-us_topic_0000002467676973_li16761544143818"><strong id="cce_10_0341__en-us_topic_0000002467676973_b26931023676">Linear</strong>: A linear logical volume integrates one or more physical volumes. Data is written to the next physical volume when the previous one is used up.</li><li id="cce_10_0341__en-us_topic_0000002467676973_li1325295210387"><strong id="cce_10_0341__en-us_topic_0000002467676973_b1019114112715">Striped</strong>: available only if there are at least two data disks. A striped logical volume stripes data into blocks of the same size and stores them in multiple physical volumes in sequence. This allows data to be concurrently read and written. A storage pool consisting of striped volumes cannot be scaled-out.</li></ul>
|
|
</li></ul>
|
|
</div>
|
|
<div class="section" id="cce_10_0341__en-us_topic_0000002467676973_section10653143445411"><a name="cce_10_0341__en-us_topic_0000002467676973_section10653143445411"></a><a name="en-us_topic_0000002467676973_section10653143445411"></a><h4 class="sectiontitle">Space Allocation for Container Engines</h4><p id="cce_10_0341__en-us_topic_0000002467676973_p1980613586544">For a node using a non-shared data disk (100 GiB for example), the division of the disk space varies depending on the container storage Rootfs type <strong id="cce_10_0341__en-us_topic_0000002467676973_b172952024203719">Device Mapper</strong> or <strong id="cce_10_0341__en-us_topic_0000002467676973_b17854162617429">OverlayFS</strong>. For details about the container storage Rootfs corresponding to different OSs, see <a href="#cce_10_0341__en-us_topic_0000002467676973_section1473612279214">Mapping Between OS and Container Storage Rootfs</a>.</p>
|
|
<ul id="cce_10_0341__en-us_topic_0000002467676973_ul20369135562510"><li id="cce_10_0341__en-us_topic_0000002467676973_li7709101613457"><strong id="cce_10_0341__en-us_topic_0000002467676973_b3645191661515">Rootfs (Device Mapper)</strong><div class="p" id="cce_10_0341__en-us_topic_0000002467676973_p269110559348">By default, the container engine and image space, occupying 90% of the data disk, can be divided into the following two parts:<ul id="cce_10_0341__en-us_topic_0000002467676973_ul129621654173420"><li id="cce_10_0341__en-us_topic_0000002467676973_li1796075493411">The <strong id="cce_10_0341__en-us_topic_0000002467676973_b694023312424">/var/lib/docker</strong> directory is used as the Docker working directory and occupies 20% of the container engine and container image space by default. (Space size of the <strong id="cce_10_0341__en-us_topic_0000002467676973_b694093304218">/var/lib/docker</strong> directory = <strong id="cce_10_0341__en-us_topic_0000002467676973_b49411533184217">Data disk space x 90% x 20%</strong>)</li><li id="cce_10_0341__en-us_topic_0000002467676973_li1596055410343">The thin pool is used to store container image data, image metadata, and container data, and occupies 80% of the container engine and container image space by default. (Thin pool space = <strong id="cce_10_0341__en-us_topic_0000002467676973_b4914114964218">Data disk space x 90% x 80%</strong>)<p id="cce_10_0341__en-us_topic_0000002467676973_p1996075413345">The thin pool is dynamically mounted. You can view it by running the <strong id="cce_10_0341__en-us_topic_0000002467676973_b16273758244">lsblk</strong> command on a node, but not the <strong id="cce_10_0341__en-us_topic_0000002467676973_b13637955182316">df -h</strong> command.</p>
|
|
</li></ul>
|
|
</div>
|
|
<div class="fignone" id="cce_10_0341__en-us_topic_0000002467676973_fig94268305322"><span class="figcap"><b>Figure 1 </b>Space allocation for container engines of Device Mapper</span><br><span><img id="cce_10_0341__en-us_topic_0000002467676973_image1096215543342" src="en-us_image_0000002434080444.png" title="Click to enlarge" class="imgResize"></span></div>
|
|
</li></ul>
|
|
<ul id="cce_10_0341__en-us_topic_0000002467676973_ul20849165711250"><li id="cce_10_0341__en-us_topic_0000002467676973_li162571641195915"><strong id="cce_10_0341__en-us_topic_0000002467676973_b32761419101513">Rootfs (OverlayFS)</strong><p id="cce_10_0341__en-us_topic_0000002467676973_p98354212596">No separate thin pool. The entire container engine and container image space (90% of the data disk by default) are in the <strong id="cce_10_0341__en-us_topic_0000002467676973_b460816824418">/var/lib/docker</strong> directory.</p>
|
|
<div class="fignone" id="cce_10_0341__en-us_topic_0000002467676973_fig1848319318116"><span class="figcap"><b>Figure 2 </b>Space allocation for container engines of OverlayFS</span><br><span><img id="cce_10_0341__en-us_topic_0000002467676973_image154991612555" src="en-us_image_0000002467718921.png" title="Click to enlarge" class="imgResize"></span></div>
|
|
</li></ul>
|
|
</div>
|
|
<div class="section" id="cce_10_0341__en-us_topic_0000002467676973_section12119191161518"><a name="cce_10_0341__en-us_topic_0000002467676973_section12119191161518"></a><a name="en-us_topic_0000002467676973_section12119191161518"></a><h4 class="sectiontitle">Space Allocation for Pods</h4><p id="cce_10_0341__en-us_topic_0000002467676973_p1680512513583">The customized pod container space (<span class="keyword" id="cce_10_0341__en-us_topic_0000002467676973_keyword202982058153813">basesize</span>) is related to the node OS and container storage Rootfs. For details about the container storage Rootfs, see <a href="#cce_10_0341__en-us_topic_0000002467676973_section1473612279214">Mapping Between OS and Container Storage Rootfs</a>.</p>
|
|
<ul id="cce_10_0341__en-us_topic_0000002467676973_ul5416437104217"><li id="cce_10_0341__en-us_topic_0000002467676973_li1741663794216">Device Mapper supports custom pod basesize. The default value is 10 GiB.</li><li id="cce_10_0341__en-us_topic_0000002467676973_li9444184454215">In OverlayFS mode, the pod container space is not limited by default.</li></ul>
|
|
<p id="cce_10_0341__en-us_topic_0000002467676973_p14092029191414">When configuring <strong id="cce_10_0341__en-us_topic_0000002467676973_b4225240145017">basesize</strong>, consider the maximum number of pods allowed on one node. The container engine space should be greater than the total disk space used by containers. Formula: <strong id="cce_10_0341__en-us_topic_0000002467676973_b0931349183616">Container engine space and container image space (90% by default)</strong> > <strong id="cce_10_0341__en-us_topic_0000002467676973_b18772923134215">Number of containers</strong> x <strong id="cce_10_0341__en-us_topic_0000002467676973_b127724231421">basesize</strong>. Otherwise, the container engine space allocated to the node may be insufficient and the container cannot be started.</p>
|
|
<p id="cce_10_0341__en-us_topic_0000002467676973_p552122284915">For nodes that support <strong id="cce_10_0341__en-us_topic_0000002467676973_b162431026193013">basesize</strong>, when Device Mapper is used, although you can limit the size of the <strong id="cce_10_0341__en-us_topic_0000002467676973_b14451113615217">/home</strong> directory of a single container (to 10 GiB by default), all containers on the node still share the thin pool of the node for storage. They are not completely isolated. When the sum of the thin pool space used by certain containers reaches the upper limit, other containers cannot run properly.</p>
|
|
<p id="cce_10_0341__en-us_topic_0000002467676973_p8521222154918">In addition, after a file is deleted in the <strong id="cce_10_0341__en-us_topic_0000002467676973_b84841451241">/home</strong> directory of the container, the thin pool space occupied by the file is not released immediately. Therefore, even if <strong id="cce_10_0341__en-us_topic_0000002467676973_b114845454243">basesize</strong> is set to 10 GiB, the thin pool space occupied by files keeps increasing until 10 GiB when files are created in the container. The space released after file deletion will be reused but after a while. If <strong id="cce_10_0341__en-us_topic_0000002467676973_b722334192516">the number of containers on the node multiplied by basesize</strong> is greater than the thin pool space size of the node, there is a possibility that the thin pool space has been used up.</p>
|
|
</div>
|
|
<div class="section" id="cce_10_0341__en-us_topic_0000002467676973_section1473612279214"><a name="cce_10_0341__en-us_topic_0000002467676973_section1473612279214"></a><a name="en-us_topic_0000002467676973_section1473612279214"></a><h4 class="sectiontitle">Mapping Between OS and <span class="keyword" id="cce_10_0341__en-us_topic_0000002467676973_keyword79621840806">Container Storage Rootfs</span></h4>
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0341__en-us_topic_0000002467676973_table2291621581" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Node OSs and container engines in CCE clusters</caption><thead align="left"><tr id="cce_10_0341__en-us_topic_0000002467676973_row910219215812"><th align="left" class="cellrowborder" valign="top" width="22.45%" id="mcps1.3.5.2.2.4.1.1"><p id="cce_10_0341__en-us_topic_0000002467676973_p148202181680">OS</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="32.67%" id="mcps1.3.5.2.2.4.1.2"><p id="cce_10_0341__en-us_topic_0000002467676973_p141021721812">Container Storage Rootfs</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="44.879999999999995%" id="mcps1.3.5.2.2.4.1.3"><p id="cce_10_0341__en-us_topic_0000002467676973_p12255122218253">Custom Basesize</p>
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr id="cce_10_0341__en-us_topic_0000002467676973_row1153401803319"><td class="cellrowborder" valign="top" width="22.45%" headers="mcps1.3.5.2.2.4.1.1 "><p id="cce_10_0341__en-us_topic_0000002467676973_p13535121833315">EulerOS 2.9</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="32.67%" headers="mcps1.3.5.2.2.4.1.2 "><p id="cce_10_0341__en-us_topic_0000002467676973_p8103122088">OverlayFS</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="44.879999999999995%" headers="mcps1.3.5.2.2.4.1.3 "><p id="cce_10_0341__en-us_topic_0000002467676973_p146141851459">Supported by Docker clusters of v1.19.16-r0, v1.21.3-r0, v1.23.3-r0, or later. There are no limits by default.</p>
|
|
<p id="cce_10_0341__en-us_topic_0000002467676973_p16669811710">Supported by containerd clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later. There are no limits by default.</p>
|
|
<p id="cce_10_0341__en-us_topic_0000002467676973_p12255142214254">Not supported by clusters of a version earlier than v1.19.16-r0, v1.21.3-r0, or v1.23.3-r0.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_10_0341__en-us_topic_0000002467676973_row87181182054"><td class="cellrowborder" valign="top" width="22.45%" headers="mcps1.3.5.2.2.4.1.1 "><p id="cce_10_0341__en-us_topic_0000002467676973_p197217221559">Ubuntu 22.04</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="32.67%" headers="mcps1.3.5.2.2.4.1.2 "><p id="cce_10_0341__en-us_topic_0000002467676973_p8729224511">OverlayFS</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="44.879999999999995%" headers="mcps1.3.5.2.2.4.1.3 "><p id="cce_10_0341__en-us_topic_0000002467676973_p37212219511">Not supported</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_10_0341__en-us_topic_0000002467676973_row12606181719193"><td class="cellrowborder" valign="top" width="22.45%" headers="mcps1.3.5.2.2.4.1.1 "><p id="cce_10_0341__en-us_topic_0000002467676973_p164141322191916">HCE OS 2.0</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="32.67%" headers="mcps1.3.5.2.2.4.1.2 "><p id="cce_10_0341__en-us_topic_0000002467676973_p241472219193">OverlayFS</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="44.879999999999995%" headers="mcps1.3.5.2.2.4.1.3 "><p id="cce_10_0341__en-us_topic_0000002467676973_p54142022201913">Supported only by Docker clusters of a version earlier than v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, or v1.28.4-r0. There are no limits by default.</p>
|
|
<p id="cce_10_0341__en-us_topic_0000002467676973_p681832319530">Supported by both Docker and containerd clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later. There are no limits by default.</p>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_10_0341__en-us_topic_0000002467676973_table16263135182120" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Node OSs and container engines in CCE Turbo clusters</caption><thead align="left"><tr id="cce_10_0341__en-us_topic_0000002467676973_row444785162113"><th align="left" class="cellrowborder" valign="top" width="22.4977502249775%" id="mcps1.3.5.3.2.4.1.1"><p id="cce_10_0341__en-us_topic_0000002467676973_p84481757216">OS</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="32.82671732826717%" id="mcps1.3.5.3.2.4.1.2"><p id="cce_10_0341__en-us_topic_0000002467676973_p10448195142119">Container Storage Rootfs</p>
|
|
</th>
|
|
<th align="left" class="cellrowborder" valign="top" width="44.67553244675532%" id="mcps1.3.5.3.2.4.1.3"><p id="cce_10_0341__en-us_topic_0000002467676973_p5446124410527">Custom Basesize</p>
|
|
</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr id="cce_10_0341__en-us_topic_0000002467676973_row89561427184811"><td class="cellrowborder" valign="top" width="22.4977502249775%" headers="mcps1.3.5.3.2.4.1.1 "><p id="cce_10_0341__en-us_topic_0000002467676973_p358483615484">Ubuntu 22.04</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="32.82671732826717%" headers="mcps1.3.5.3.2.4.1.2 "><p id="cce_10_0341__en-us_topic_0000002467676973_p20584536184810">OverlayFS</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="44.67553244675532%" headers="mcps1.3.5.3.2.4.1.3 "><p id="cce_10_0341__en-us_topic_0000002467676973_p1358473664817">Not supported</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_10_0341__en-us_topic_0000002467676973_row1448850219"><td class="cellrowborder" valign="top" width="22.4977502249775%" headers="mcps1.3.5.3.2.4.1.1 "><p id="cce_10_0341__en-us_topic_0000002467676973_p14485513216">EulerOS 2.9</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="32.82671732826717%" headers="mcps1.3.5.3.2.4.1.2 "><p id="cce_10_0341__en-us_topic_0000002467676973_p43525218374">OverlayFS</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="44.67553244675532%" headers="mcps1.3.5.3.2.4.1.3 "><p id="cce_10_0341__en-us_topic_0000002467676973_p3156126115411">Supported when Rootfs is set to OverlayFS and the runtime is Docker. There are no limits by default. Supported by both Docker and containerd clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later.</p>
|
|
</td>
|
|
</tr>
|
|
<tr id="cce_10_0341__en-us_topic_0000002467676973_row02212032205"><td class="cellrowborder" valign="top" width="22.4977502249775%" headers="mcps1.3.5.3.2.4.1.1 "><p id="cce_10_0341__en-us_topic_0000002467676973_p691113246201">HCE OS 2.0</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="32.82671732826717%" headers="mcps1.3.5.3.2.4.1.2 "><p id="cce_10_0341__en-us_topic_0000002467676973_p59111245206">OverlayFS</p>
|
|
</td>
|
|
<td class="cellrowborder" valign="top" width="44.67553244675532%" headers="mcps1.3.5.3.2.4.1.3 "><p id="cce_10_0341__en-us_topic_0000002467676973_p1911192410200">Supported only by Docker clusters of a version earlier than v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, or v1.28.4-r0. There are no limits by default.</p>
|
|
<p id="cce_10_0341__en-us_topic_0000002467676973_p9783205579">Supported by both Docker and containerd clusters of v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later. There are no limits by default.</p>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</div>
|
|
<div class="section" id="cce_10_0341__en-us_topic_0000002467676973_section1926415516193"><h4 class="sectiontitle"><span class="keyword" id="cce_10_0341__en-us_topic_0000002467676973_keyword1531375015014">Garbage Collection Policies for Container Images</span></h4><p id="cce_10_0341__en-us_topic_0000002467676973_p972681822011">When the container engine space is insufficient, image garbage collection is triggered.</p>
|
|
<p id="cce_10_0341__en-us_topic_0000002467676973_p116561726135115">The policy for garbage collecting images takes two factors into consideration: <strong id="cce_10_0341__en-us_topic_0000002467676973_b16515235351">HighThresholdPercent</strong> and <strong id="cce_10_0341__en-us_topic_0000002467676973_b1455317361951">LowThresholdPercent</strong>. Disk usage exceeding the high threshold (default: 80%) will trigger garbage collection. The garbage collection will delete least recently used images until the low threshold (default: 70%) is met.</p>
|
|
</div>
|
|
<div class="section" id="cce_10_0341__en-us_topic_0000002467676973_section41701981545"><h4 class="sectiontitle">Recommended Configuration for the Container Engine Space</h4><ul id="cce_10_0341__en-us_topic_0000002467676973_ul65481047181516"><li id="cce_10_0341__en-us_topic_0000002467676973_li154817478159">The container engine space should be greater than the total disk space used by containers. Formula: <strong id="cce_10_0341__en-us_topic_0000002467676973_b13845101714162">Container engine space</strong> > <strong id="cce_10_0341__en-us_topic_0000002467676973_b16845151761614">Number of containers</strong> x <strong id="cce_10_0341__en-us_topic_0000002467676973_b28467178162">basesize</strong></li><li id="cce_10_0341__en-us_topic_0000002467676973_li2845145154411">You are advised to create and delete files of containerized services in local storage volumes (such as emptyDir and hostPath volumes) or cloud storage directories mounted to the containers. In this way, the thin pool space is not occupied. emptyDir volumes occupy the kubelet space. Therefore, properly plan the size of the kubelet space.</li><li id="cce_10_0341__en-us_topic_0000002467676973_li3257185416717">You can deploy services on nodes that use the OverlayFS (for details, see <a href="#cce_10_0341__en-us_topic_0000002467676973_section1473612279214">Mapping Between OS and Container Storage Rootfs</a>) so that the disk space occupied by files created or deleted in containers can be released immediately.</li></ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_02_0083.html">Appendix</a></div>
|
|
</div>
|
|
</div>
|
|
|
|
|
|
<script language="JavaScript">
|
|
<!--
|
|
image_size('.imgResize');
|
|
var msg_imageMax = "view original image";
|
|
var msg_imageClose = "close";
|
|
//--></script> |