vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/cce/umn/cce_bestpractice_00198.html
Dong, Qiu Jian 86fb05065f CCE UMN for 24.2.0 version -20240428 
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com>
Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
2024-06-10 08:19:07 +00:00

193 lines
26 KiB
HTML
Raw Blame History

<a name="cce_bestpractice_00198"></a><a name="cce_bestpractice_00198"></a>
<h1 class="topictitle1">Expanding the Storage Space</h1>
<div id="body8662426"><p id="cce_bestpractice_00198__p1677017533016">The storage classes that can be expanded for CCE nodes are as follows:</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="cce_bestpractice_00198__table563851813313" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Capacity expansion methods</caption><thead align="left"><tr id="cce_bestpractice_00198__row86381318332"><th align="left" class="cellrowborder" valign="top" width="12.73%" id="mcps1.3.2.2.5.1.1"><p id="cce_bestpractice_00198__p87752238272">Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="13.91%" id="mcps1.3.2.2.5.1.2"><p id="cce_bestpractice_00198__p263814185312">Name</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="37.64%" id="mcps1.3.2.2.5.1.3"><p id="cce_bestpractice_00198__p116381181432">Purpose</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="35.72%" id="mcps1.3.2.2.5.1.4"><p id="cce_bestpractice_00198__p06389182315">Capacity Expansion Method</p>
</th>
</tr>
</thead>
<tbody><tr id="cce_bestpractice_00198__row8638151816310"><td class="cellrowborder" rowspan="2" valign="top" width="12.73%" headers="mcps1.3.2.2.5.1.1 "><p id="cce_bestpractice_00198__p1377510237277">Node disk</p>
</td>
<td class="cellrowborder" valign="top" width="13.91%" headers="mcps1.3.2.2.5.1.2 "><p id="cce_bestpractice_00198__p7638111810312">System disk</p>
</td>
<td class="cellrowborder" valign="top" width="37.64%" headers="mcps1.3.2.2.5.1.3 "><p id="cce_bestpractice_00198__p3638191810318">A disk attached to a node for installing the operating system</p>
</td>
<td class="cellrowborder" valign="top" width="35.72%" headers="mcps1.3.2.2.5.1.4 "><p id="cce_bestpractice_00198__p16381618234"><a href="#cce_bestpractice_00198__en-us_topic_0196817407_section9671812194910">Expanding System Disk Capacity</a></p>
</td>
</tr>
<tr id="cce_bestpractice_00198__row126386180317"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.1.1 "><p id="cce_bestpractice_00198__p663841813319">Data disk</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.1.2 "><p id="cce_bestpractice_00198__p10638518935">A disk that must be attached to a node for the container engine and kubelet</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.1.3 "><ul id="cce_bestpractice_00198__ul183265813195"><li id="cce_bestpractice_00198__li93261811191"><a href="#cce_bestpractice_00198__en-us_topic_0196817407_section155006183017">Expanding the Capacity of a Data Disk Used by Container Engines</a></li><li id="cce_bestpractice_00198__li2032611814193"><a href="#cce_bestpractice_00198__section181915191968">Expanding the Capacity of a Data Disk Used by kubelet</a></li></ul>
</td>
</tr>
<tr id="cce_bestpractice_00198__row18722175492719"><td class="cellrowborder" rowspan="2" valign="top" width="12.73%" headers="mcps1.3.2.2.5.1.1 "><p id="cce_bestpractice_00198__p1072255414272">Container storage</p>
</td>
<td class="cellrowborder" valign="top" width="13.91%" headers="mcps1.3.2.2.5.1.2 "><p id="cce_bestpractice_00198__p6722195462711">Pod container space</p>
</td>
<td class="cellrowborder" valign="top" width="37.64%" headers="mcps1.3.2.2.5.1.3 "><p id="cce_bestpractice_00198__p117221254112716">The base size of a container, which is, the upper limit of the disk space occupied by each pod (including the storage space occupied by container images)</p>
</td>
<td class="cellrowborder" valign="top" width="35.72%" headers="mcps1.3.2.2.5.1.4 "><p id="cce_bestpractice_00198__p1272285492718"><a href="#cce_bestpractice_00198__en-us_topic_0196817407_section3621141347">Expanding the Capacity of a Data Disk Used by Pod (basesize)</a></p>
</td>
</tr>
<tr id="cce_bestpractice_00198__row14888434143316"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.1.1 "><p id="cce_bestpractice_00198__p178897342333">PVC</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.1.2 "><p id="cce_bestpractice_00198__p14889163415330">Storage resources mounted to the containers</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.1.3 "><p id="cce_bestpractice_00198__p158892034113311"><a href="#cce_bestpractice_00198__section1623491210348">Expanding a PVC</a></p>
</td>
</tr>
</tbody>
</table>
</div>
<div class="section" id="cce_bestpractice_00198__en-us_topic_0196817407_section9671812194910"><a name="cce_bestpractice_00198__en-us_topic_0196817407_section9671812194910"></a><a name="en-us_topic_0196817407_section9671812194910"></a><h4 class="sectiontitle">Expanding System Disk Capacity</h4><p id="cce_bestpractice_00198__p123331632121216">EulerOS 2.9 is used as the sample OS. There is only one partition (<strong id="cce_bestpractice_00198__b102641143620">/dev/vda1</strong>) with a capacity of 50 GiB in the system disk <strong id="cce_bestpractice_00198__b11563062369">/dev/vda</strong>, and then 50 GiB is added to the system disk. In this example, the additional 50 GiB is allocated to the existing <strong id="cce_bestpractice_00198__b1629914115299">/dev/vda1</strong> partition.</p>
<ol id="cce_bestpractice_00198__en-us_topic_0196817407_ol336654010496"><li id="cce_bestpractice_00198__en-us_topic_0196817407_li11366940174919"><span>Expand the capacity of the system disk on the EVS console.</span></li><li id="cce_bestpractice_00198__en-us_topic_0196817407_li116943521116"><span>Log in to the node and run the <strong id="cce_bestpractice_00198__b1477102513304">growpart</strong> command to check whether growpart has been installed.</span><p><p id="cce_bestpractice_00198__p149881945121718">If the tool operation guide is displayed, the growpart has been installed. Otherwise, run the following command to install growpart:</p>
<pre class="screen" id="cce_bestpractice_00198__screen15904115011181">yum install cloud-utils-growpart</pre>
</p></li><li id="cce_bestpractice_00198__li12528258171818"><span>Run the following command to view the total capacity of the system disk <strong id="cce_bestpractice_00198__b1511142413615">/dev/vda</strong>:</span><p><pre class="screen" id="cce_bestpractice_00198__screen142914415194">fdisk -l</pre>
<p id="cce_bestpractice_00198__p441672315475">If the following information is displayed, the total capacity of <strong id="cce_bestpractice_00198__b4381557153118">/dev/vda</strong> is 100 GiB.</p>
<pre class="screen" id="cce_bestpractice_00198__screen166071332203">[root@test-48162 ~]# fdisk -l
<strong id="cce_bestpractice_00198__b14238983341">Disk /dev/vda: 100 GiB, 107374182400 bytes, 209715200 sectors</strong>
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x78d88f0b
Device Boot Start End Sectors Size Id Type
/dev/vda1 * 2048 104857566 104855519 50G 83 Linux
Disk /dev/vdb: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/vgpaas-dockersys: 90 GiB, 96632569856 bytes, 188735488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/vgpaas-kubernetes: 10 GiB, 10733223936 bytes, 20963328 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes</pre>
</p></li><li id="cce_bestpractice_00198__li849281818811"><span>Run the following command to check the capacity of the system disk partition <strong id="cce_bestpractice_00198__b4847112712">/dev/vda1</strong>:</span><p><pre class="screen" id="cce_bestpractice_00198__screen173851816103417">df -TH</pre>
<p id="cce_bestpractice_00198__p3209194412317">Information similar to the following is displayed:</p>
<pre class="screen" id="cce_bestpractice_00198__screen635811382344">[root@test-48162 ~]# df -TH
Filesystem Type Size Used Avail Use% Mounted on
devtmpfs devtmpfs 1.8G 0 1.8G 0% /dev
tmpfs tmpfs 1.8G 0 1.8G 0% /dev/shm
tmpfs tmpfs 1.8G 13M 1.8G 1% /run
tmpfs tmpfs 1.8G 0 1.8G 0% /sys/fs/cgroup
<strong id="cce_bestpractice_00198__b2528182273519">/dev/vda1 ext4 53G 3.3G 47G 7% /</strong>
tmpfs tmpfs 1.8G 75M 1.8G 5% /tmp
/dev/mapper/vgpaas-dockersys ext4 95G 1.3G 89G 2% /var/lib/docker
/dev/mapper/vgpaas-kubernetes ext4 11G 39M 10G 1% /mnt/paas/kubernetes/kubelet
...</pre>
</p></li><li id="cce_bestpractice_00198__li9334102043710"><span>Run the following command to extend the partition using growpart:</span><p><pre class="screen" id="cce_bestpractice_00198__screen136012011378"><strong id="cce_bestpractice_00198__b291316441337">growpart</strong> <em id="cce_bestpractice_00198__i18325351153218">System disk</em> <em id="cce_bestpractice_00198__i193251051113217">Partition number</em></pre>
<p id="cce_bestpractice_00198__p23611620193714">The partition number is <strong id="cce_bestpractice_00198__b173761128133312">1</strong> because there is only one <strong id="cce_bestpractice_00198__b6402152512339">/dev/vda1</strong> partition in the system disk, as shown in the following command:</p>
<pre class="screen" id="cce_bestpractice_00198__screen336172010375">growpart /dev/vda 1</pre>
<p id="cce_bestpractice_00198__p16361820153711">Information similar to the following is displayed:</p>
<pre class="screen" id="cce_bestpractice_00198__screen736112010375">CHANGED: partition=1 start=2048 old: size=104855519 end=104857567 new: size=209713119 end=209715167</pre>
</p></li><li id="cce_bestpractice_00198__li1337615183713"><span>Run the following command to extend the file system:</span><p><pre class="screen" id="cce_bestpractice_00198__screen3635164715362"><strong id="cce_bestpractice_00198__b1224734018339">resize2fs</strong> <em id="cce_bestpractice_00198__i16248140133319">Disk partition</em></pre>
<p id="cce_bestpractice_00198__p2036091517376">An example command is as follows:</p>
<pre class="screen" id="cce_bestpractice_00198__screen153601315173716">resize2fs /dev/vda1</pre>
<p id="cce_bestpractice_00198__p163601515113710">Information similar to the following is displayed:</p>
<pre class="screen" id="cce_bestpractice_00198__screen771332753719">resize2fs 1.45.6 (20-Mar-2020)
Filesystem at /dev/vda1 is mounted on /; on-line resizing required
old_desc_blocks = 7, new_desc_blocks = 13
The filesystem on /dev/vda1 is now 26214139 (4k) blocks long.</pre>
</p></li><li id="cce_bestpractice_00198__li107161013817"><span>Run the following command to view the new capacity of the <strong id="cce_bestpractice_00198__b15378721153412">/dev/vda1</strong> partition:</span><p><pre class="screen" id="cce_bestpractice_00198__screen1782952418377">df -TH</pre>
<p id="cce_bestpractice_00198__p58241093819">Information similar to the following is displayed:</p>
<pre class="screen" id="cce_bestpractice_00198__screen192841217380">[root@test-48162 ~]# df -TH
Filesystem Type Size Used Avail Use% Mounted on
devtmpfs devtmpfs 1.8G 0 1.8G 0% /dev
tmpfs tmpfs 1.8G 0 1.8G 0% /dev/shm
tmpfs tmpfs 1.8G 13M 1.8G 1% /run
tmpfs tmpfs 1.8G 0 1.8G 0% /sys/fs/cgroup
<strong id="cce_bestpractice_00198__b08391433203813">/dev/vda1 ext4 106G 3.3G 98G 4% /</strong>
tmpfs tmpfs 1.8G 75M 1.8G 5% /tmp
/dev/mapper/vgpaas-dockersys ext4 95G 1.3G 89G 2% /var/lib/docker
/dev/mapper/vgpaas-kubernetes ext4 11G 39M 10G 1% /mnt/paas/kubernetes/kubelet
...</pre>
</p></li><li id="cce_bestpractice_00198__li134261257132518"><span>Log in to the CCE console and click the cluster. In the navigation pane, choose <strong id="cce_bestpractice_00198__b78661034103413">Nodes</strong>. Click <strong id="cce_bestpractice_00198__b3866193411349">More</strong> &gt; <strong id="cce_bestpractice_00198__b10866534143415">Sync Server Data</strong> in the row containing the target node.</span></li></ol>
</div>
<div class="section" id="cce_bestpractice_00198__en-us_topic_0196817407_section155006183017"><a name="cce_bestpractice_00198__en-us_topic_0196817407_section155006183017"></a><a name="en-us_topic_0196817407_section155006183017"></a><h4 class="sectiontitle">Expanding the Capacity of a Data Disk Used by Container Engines</h4><p id="cce_bestpractice_00198__p107904753311">CCE divides the data disk space for two parts by default. One part is used to store the Docker/containerd working directories, container images, 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. This section uses Docker as an example to describe how to expand the container engine capacity.</p>
<ol id="cce_bestpractice_00198__en-us_topic_0196817407_ol99174381202"><li id="cce_bestpractice_00198__en-us_topic_0196817407_li1091823811013"><span>Expand the capacity of the data disk on the EVS console.</span></li><li id="cce_bestpractice_00198__li15327184914542"><span>Log in to the CCE console and click the cluster. In the navigation pane, choose <strong id="cce_bestpractice_00198__b176491516203817">Nodes</strong>. Click <strong id="cce_bestpractice_00198__b464971673810">More</strong> &gt; <strong id="cce_bestpractice_00198__b9649161615380">Sync Server Data</strong> in the row containing the target node.</span></li><li id="cce_bestpractice_00198__en-us_topic_0196817407_li209187382011"><span>Log in to the target node.</span></li><li id="cce_bestpractice_00198__li128005014232"><span>Run the <strong id="cce_bestpractice_00198__b6455184022316">lsblk</strong> command to check the block device information of the node.</span><p><p id="cce_bestpractice_00198__p980018092312">A data disk is divided depending on the container storage <strong id="cce_bestpractice_00198__b687813596016">Rootfs</strong>:</p>
<ul id="cce_bestpractice_00198__ul89731919102417"><li id="cce_bestpractice_00198__li1536084418247">Overlayfs: No independent thin pool is allocated. Image data is stored in the <strong id="cce_bestpractice_00198__b14504233414">dockersys</strong> disk.<pre class="screen" id="cce_bestpractice_00198__screen736044442417"># lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 8:0 0 50G 0 disk
└─vda1 8:1 0 50G 0 part /
<strong id="cce_bestpractice_00198__b9542144551613">vdb</strong> 8:16 0 200G 0 disk
├─vgpaas-dockersys 253:0 0 90G 0 lvm /var/lib/docker # Space used by the container engine
└─vgpaas-kubernetes 253:1 0 10G 0 lvm /mnt/paas/kubernetes/kubelet # Space used by Kubernetes</pre>
<p id="cce_bestpractice_00198__p1599151113360">Run the following commands on the node to add the new disk capacity to the <strong id="cce_bestpractice_00198__b746642417811">dockersys</strong> disk:</p>
<pre class="screen" id="cce_bestpractice_00198__screen10503202016363">pvresize /dev/vdb
lvextend -l+100%FREE -n vgpaas/dockersys
resize2fs /dev/vgpaas/dockersys</pre>
</li><li id="cce_bestpractice_00198__li7973131913245">Devicemapper: A thin pool is allocated to store image data.<pre class="screen" id="cce_bestpractice_00198__screen10480142251"># lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 8:0 0 50G 0 disk
└─vda1 8:1 0 50G 0 part /
<strong id="cce_bestpractice_00198__b9505458151516">vdb</strong> 8:16 0 200G 0 disk
├─<strong id="cce_bestpractice_00198__b170511380163">vgpaas-dockersys</strong> 253:0 0 18G 0 lvm /var/lib/docker
├─vgpaas-thinpool_tmeta 253:1 0 3G 0 lvm
│ └─<strong id="cce_bestpractice_00198__b10865144019161">vgpaas-thinpool</strong> 253:3 0 67G 0 lvm # Space used by thinpool
│ ...
├─vgpaas-thinpool_tdata 253:2 0 67G 0 lvm
│ └─vgpaas-thinpool 253:3 0 67G 0 lvm
│ ...
└─vgpaas-kubernetes 253:4 0 10G 0 lvm /mnt/paas/kubernetes/kubelet</pre>
<ul id="cce_bestpractice_00198__ul151541148142616"><li id="cce_bestpractice_00198__li8154948152611">Run the following commands on the node to add the new disk capacity to the <strong id="cce_bestpractice_00198__b169691932144611">thinpool</strong> disk:<pre class="screen" id="cce_bestpractice_00198__screen1941742617282">pvresize /dev/vdb
lvextend -l+100%FREE -n vgpaas/thinpool</pre>
</li><li id="cce_bestpractice_00198__li715464810269">Run the following commands on the node to add the new disk capacity to the <strong id="cce_bestpractice_00198__b143201925134616">dockersys</strong> disk:<pre class="screen" id="cce_bestpractice_00198__screen3309227102613">pvresize /dev/vdb
lvextend -l+100%FREE -n vgpaas/dockersys
resize2fs /dev/vgpaas/dockersys</pre>
</li></ul>
</li></ul>
</p></li></ol>
</div>
<div class="section" id="cce_bestpractice_00198__section181915191968"><a name="cce_bestpractice_00198__section181915191968"></a><a name="section181915191968"></a><h4 class="sectiontitle">Expanding the Capacity of a Data Disk Used by kubelet</h4><p id="cce_bestpractice_00198__p156501326103518">CCE divides the data disk space for container engines and pods. The container engine space stores the Docker/containerd working directories, container images, and image metadata. The other is reserved for kubelet and emptyDir volumes. To expand the kubelet space, perform the following steps:</p>
<ol id="cce_bestpractice_00198__ol138464209616"><li id="cce_bestpractice_00198__li584617201265"><span>Expand the capacity of the data disk on the EVS console.</span></li><li id="cce_bestpractice_00198__li18658756175420"><span>Log in to the CCE console and click the cluster. In the navigation pane, choose <strong id="cce_bestpractice_00198__b56631616143811">Nodes</strong>. Click <strong id="cce_bestpractice_00198__b566311616382">More</strong> &gt; <strong id="cce_bestpractice_00198__b866312165381">Sync Server Data</strong> in the row containing the target node.</span></li><li id="cce_bestpractice_00198__li584616201663"><span>Log in to the target node.</span></li><li id="cce_bestpractice_00198__li1895412515108"><span>Run <strong id="cce_bestpractice_00198__b194521223145310">lsblk</strong> to view the block device information of the node.</span><p><pre class="screen" id="cce_bestpractice_00198__screen18150135111010"># lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 8:0 0 50G 0 disk
└─vda1 8:1 0 50G 0 part /
<strong id="cce_bestpractice_00198__b17784185119157">vdb</strong> 8:16 0 200G 0 disk
├─vgpaas-dockersys 253:0 0 90G 0 lvm /var/lib/docker # Space used by the container engine
└─<strong id="cce_bestpractice_00198__b8689184712153">vgpaas-kubernetes</strong> 253:1 0 10G 0 lvm /mnt/paas/kubernetes/kubelet # Space used by Kubernetes</pre>
</p></li><li id="cce_bestpractice_00198__li1484615201963"><span>Run the following commands on the node to add the new disk capacity to the Kubernetes disk:</span><p><pre class="screen" id="cce_bestpractice_00198__screen3846120468">pvresize /dev/vdb
lvextend -l+100%FREE -n vgpaas/kubernetes
resize2fs /dev/vgpaas/kubernetes</pre>
</p></li></ol>
</div>
<div class="section" id="cce_bestpractice_00198__en-us_topic_0196817407_section3621141347"><a name="cce_bestpractice_00198__en-us_topic_0196817407_section3621141347"></a><a name="en-us_topic_0196817407_section3621141347"></a><h4 class="sectiontitle">Expanding the Capacity of a Data Disk Used by Pod (basesize)</h4><ol id="cce_bestpractice_00198__ol511417164101"><li id="cce_bestpractice_00198__cce_faq_00224_li736715181515"><span>Log in to the CCE console and click the cluster name to access the cluster console.</span></li><li id="cce_bestpractice_00198__cce_faq_00224_li24942528521"><span>Choose <strong id="cce_bestpractice_00198__cce_faq_00224_b189750130475">Nodes</strong> from the navigation pane.</span></li><li id="cce_bestpractice_00198__cce_faq_00224_li133072217550"><span>Click the Nodes tab, locate the row containing the target node, and choose <strong id="cce_bestpractice_00198__cce_faq_00224_b148551937125020">More</strong> &gt; <strong id="cce_bestpractice_00198__cce_faq_00224_b15370249135015">Reset Node</strong> in the <strong id="cce_bestpractice_00198__cce_faq_00224_b1144520506">Operation</strong> column.</span><p><div class="notice" id="cce_bestpractice_00198__cce_faq_00224_note093161765617"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="cce_bestpractice_00198__cce_faq_00224_p1315771818569">Resetting a node may make unavailable the node-specific resources (such as local storage and workloads scheduled to this node). Exercise caution when performing this operation to avoid impact on running services.</p>
</div></div>
</p></li><li id="cce_bestpractice_00198__cce_faq_00224_li0372105918556"><span>Click <strong id="cce_bestpractice_00198__cce_faq_00224_b446472655112">Yes</strong>.</span></li><li id="cce_bestpractice_00198__cce_faq_00224_li38415459464"><span>Reconfigure node parameters.</span><p><p id="cce_bestpractice_00198__cce_faq_00224_p1823115541465">If you need to adjust the container storage space, pay attention to the following configurations:</p>
<p id="cce_bestpractice_00198__cce_faq_00224_p15736830111319"><strong id="cce_bestpractice_00198__cce_faq_00224_b174806251917">Storage Settings</strong>: Click <strong id="cce_bestpractice_00198__cce_faq_00224_b44431201211">Expand</strong> next to the data disk to set the following parameters:</p>
<p id="cce_bestpractice_00198__cce_faq_00224_p760410529815"><strong id="cce_bestpractice_00198__cce_faq_00224_b1189853893318">Space Allocation for Pods</strong>: indicates the <span class="keyword" id="cce_bestpractice_00198__cce_faq_00224_keyword360416521088">base size</span> of a pod. It is the maximum size that a workload's pods (including the container images) can grow to in the disk space. Proper settings can prevent pods from taking all the disk space available and avoid 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.html">Data Disk Space Allocation</a>.</p>
<p id="cce_bestpractice_00198__cce_faq_00224_p1285841220720"></p>
</p></li><li id="cce_bestpractice_00198__cce_faq_00224_li427018141128"><span>After the node is reset, log in to the node and run the following command to access the container and check whether the container storage capacity has been expanded:</span><p><p id="cce_bestpractice_00198__cce_faq_00224_p17270914525"><strong id="cce_bestpractice_00198__cce_faq_00224_b76172021151918">docker exec -it</strong> <em id="cce_bestpractice_00198__cce_faq_00224_i9617132119193">container_id</em><strong id="cce_bestpractice_00198__cce_faq_00224_b2617421171919"> /bin/sh</strong> or <strong id="cce_bestpractice_00198__cce_faq_00224_b161782141917">kubectl exec -it</strong> <em id="cce_bestpractice_00198__cce_faq_00224_i161719214190">container_id</em> <strong id="cce_bestpractice_00198__cce_faq_00224_b156171421121911">/bin/sh</strong></p>
<p id="cce_bestpractice_00198__cce_faq_00224_p12270131414213"><strong id="cce_bestpractice_00198__cce_faq_00224_b5270151414218">df -h</strong></p>
<p id="cce_bestpractice_00198__cce_faq_00224_p12704144214"><span><img id="cce_bestpractice_00198__cce_faq_00224_image9270141414215" src="en-us_image_0000001851585112.png"></span></p>
</p></li></ol>
</div>
<div class="section" id="cce_bestpractice_00198__section1623491210348"><a name="cce_bestpractice_00198__section1623491210348"></a><a name="section1623491210348"></a><h4 class="sectiontitle">Expanding a PVC</h4><p id="cce_bestpractice_00198__p15381144916298">Cloud storage:</p>
<ul id="cce_bestpractice_00198__ul1869614814303"><li id="cce_bestpractice_00198__li8696981301">OBS and SFS: There is no storage restriction and capacity expansion is not required.</li><li id="cce_bestpractice_00198__li36961480308">EVS:<ul id="cce_bestpractice_00198__ul15846183333014"><li id="cce_bestpractice_00198__li9917629123010">You can expand the capacity of automatically created volumes on the console. The procedure is as follows:<ol id="cce_bestpractice_00198__ol439664125615"><li id="cce_bestpractice_00198__cce_10_0614_li1338117994616">Choose <strong id="cce_bestpractice_00198__cce_10_0614_b1368191245415"><span id="cce_bestpractice_00198__cce_10_0614_text12129183442716">Storage</span></strong> in the navigation pane and click the <strong id="cce_bestpractice_00198__cce_10_0614_b1136919126549">PVCs</strong> tab. Click <strong id="cce_bestpractice_00198__cce_10_0614_b209111042125414">More</strong> in the <strong id="cce_bestpractice_00198__cce_10_0614_b189131642165410">Operation</strong> column of the target PVC and select <strong id="cce_bestpractice_00198__cce_10_0614_b159124426547">Scale-out</strong>.</li><li id="cce_bestpractice_00198__cce_10_0614_li8399165264618">Enter the capacity to be added and click <strong id="cce_bestpractice_00198__cce_10_0614_b697085695816">OK</strong>.</li></ol>
</li></ul>
</li><li id="cce_bestpractice_00198__li136961681306">For SFS Turbo, expand the capacity on the SFS console and then change the capacity in the PVC.</li></ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_bestpractice_0053.html">Storage</a></div>
</div>
</div>
View Git Blame Copy Permalink