From 71d5c814e7cd147ecf1616dcdb847abdd12996f9 Mon Sep 17 00:00:00 2001 From: qiujiandong1 Date: Mon, 16 Jun 2025 14:58:53 +0000 Subject: [PATCH] CCE UMN 20250311 version Reviewed-by: Eotvos, Oliver Co-authored-by: qiujiandong1 Co-committed-by: qiujiandong1 --- docs/cce/umn/ALL_META.TXT.json | 2335 ++++++++------ docs/cce/umn/CLASS.TXT.json | 2693 +++++++++-------- docs/cce/umn/cce_01_0300.html | 47 +- docs/cce/umn/cce_10_0002.html | 4 +- docs/cce/umn/cce_10_0003.html | 19 +- docs/cce/umn/cce_10_0007.html | 2 +- docs/cce/umn/cce_10_0009.html | 2 +- docs/cce/umn/cce_10_0010.html | 10 +- docs/cce/umn/cce_10_0011.html | 61 +- docs/cce/umn/cce_10_0012.html | 41 +- docs/cce/umn/cce_10_0014.html | 4 +- docs/cce/umn/cce_10_0015.html | 28 +- docs/cce/umn/cce_10_0016.html | 22 +- docs/cce/umn/cce_10_0018.html | 14 +- docs/cce/umn/cce_10_0024.html | 2 +- docs/cce/umn/cce_10_0026.html | 10 +- docs/cce/umn/cce_10_0028.html | 218 +- docs/cce/umn/cce_10_0031.html | 2 +- docs/cce/umn/cce_10_0034.html | 94 +- docs/cce/umn/cce_10_00356.html | 4 +- docs/cce/umn/cce_10_0047.html | 37 +- docs/cce/umn/cce_10_0048.html | 38 +- docs/cce/umn/cce_10_0054.html | 132 +- docs/cce/umn/cce_10_0059.html | 170 +- docs/cce/umn/cce_10_0063.html | 4 +- docs/cce/umn/cce_10_0066.html | 26 +- docs/cce/umn/cce_10_0068.html | 4 +- docs/cce/umn/cce_10_0081.html | 5 +- docs/cce/umn/cce_10_0084.html | 2 +- docs/cce/umn/cce_10_0091.html | 4 +- docs/cce/umn/cce_10_0094.html | 34 +- docs/cce/umn/cce_10_0107.html | 30 +- docs/cce/umn/cce_10_0111.html | 3 +- docs/cce/umn/cce_10_0112.html | 2 +- docs/cce/umn/cce_10_0113.html | 2 +- docs/cce/umn/cce_10_0125.html | 5 +- docs/cce/umn/cce_10_0129.html | 59 +- docs/cce/umn/cce_10_0132.html | 52 +- docs/cce/umn/cce_10_0140.html | 2 +- docs/cce/umn/cce_10_0141.html | 131 +- docs/cce/umn/cce_10_0142.html | 56 +- docs/cce/umn/cce_10_0144.html | 24 +- docs/cce/umn/cce_10_0146.html | 4 +- docs/cce/umn/cce_10_0150.html | 48 +- docs/cce/umn/cce_10_0151.html | 77 +- docs/cce/umn/cce_10_0152.html | 30 +- docs/cce/umn/cce_10_0153.html | 18 +- docs/cce/umn/cce_10_0154.html | 664 ++-- docs/cce/umn/cce_10_0163.html | 4 +- docs/cce/umn/cce_10_0164.html | 2 + docs/cce/umn/cce_10_0175.html | 14 +- docs/cce/umn/cce_10_0180.html | 2 +- docs/cce/umn/cce_10_0182.html | 2 + docs/cce/umn/cce_10_0185.html | 10 +- docs/cce/umn/cce_10_0186.html | 4 +- docs/cce/umn/cce_10_0187.html | 2 +- docs/cce/umn/cce_10_0188.html | 23 +- docs/cce/umn/cce_10_0189.html | 169 +- docs/cce/umn/cce_10_0190.html | 22 +- docs/cce/umn/cce_10_0191.html | 2 +- docs/cce/umn/cce_10_0193.html | 858 +++--- docs/cce/umn/cce_10_0196.html | 32 +- docs/cce/umn/cce_10_0197.html | 60 +- docs/cce/umn/cce_10_0198.html | 13 +- docs/cce/umn/cce_10_0201.html | 30 +- docs/cce/umn/cce_10_0205.html | 38 +- docs/cce/umn/cce_10_0208.html | 2 +- docs/cce/umn/cce_10_0209.html | 211 +- docs/cce/umn/cce_10_0210.html | 2 +- docs/cce/umn/cce_10_0212.html | 52 +- docs/cce/umn/cce_10_0213.html | 590 ++-- docs/cce/umn/cce_10_0214.html | 3 +- docs/cce/umn/cce_10_0215.html | 2 +- docs/cce/umn/cce_10_0216.html | 33 +- docs/cce/umn/cce_10_0240.html | 30 +- docs/cce/umn/cce_10_0245.html | 4 +- docs/cce/umn/cce_10_0249.html | 6 +- docs/cce/umn/cce_10_0251.html | 88 +- docs/cce/umn/cce_10_0252.html | 318 +- docs/cce/umn/cce_10_0275.html | 8 +- docs/cce/umn/cce_10_0276.html | 4 +- docs/cce/umn/cce_10_0277.html | 18 +- docs/cce/umn/cce_10_0278.html | 31 +- docs/cce/umn/cce_10_0279.html | 4 +- docs/cce/umn/cce_10_0281.html | 8 +- docs/cce/umn/cce_10_0282.html | 6 +- docs/cce/umn/cce_10_0283.html | 16 +- docs/cce/umn/cce_10_0284.html | 20 +- docs/cce/umn/cce_10_0285.html | 6 +- docs/cce/umn/cce_10_0288.html | 2 +- docs/cce/umn/cce_10_0290.html | 2 +- docs/cce/umn/cce_10_0291.html | 5 +- docs/cce/umn/cce_10_0293.html | 3 +- docs/cce/umn/cce_10_0296.html | 4 +- docs/cce/umn/cce_10_0300.html | 14 +- docs/cce/umn/cce_10_0302.html | 18 +- docs/cce/umn/cce_10_0307.html | 6 +- docs/cce/umn/cce_10_0336.html | 13 +- docs/cce/umn/cce_10_0337.html | 10 +- docs/cce/umn/cce_10_0341.html | 8 +- docs/cce/umn/cce_10_0342.html | 11 +- docs/cce/umn/cce_10_0345.html | 14 +- docs/cce/umn/cce_10_0348.html | 2 +- docs/cce/umn/cce_10_0349.html | 4 +- docs/cce/umn/cce_10_0351.html | 8 +- docs/cce/umn/cce_10_0355.html | 7 +- docs/cce/umn/cce_10_0360.html | 4 +- docs/cce/umn/cce_10_0363.html | 21 +- docs/cce/umn/cce_10_0364.html | 10 +- docs/cce/umn/cce_10_0365.html | 32 +- docs/cce/umn/cce_10_0367.html | 39 +- docs/cce/umn/cce_10_0373.html | 12 +- docs/cce/umn/cce_10_0377.html | 12 +- docs/cce/umn/cce_10_0378.html | 10 +- docs/cce/umn/cce_10_0379.html | 44 +- docs/cce/umn/cce_10_0380.html | 189 +- docs/cce/umn/cce_10_0381.html | 5 +- docs/cce/umn/cce_10_0382.html | 68 +- docs/cce/umn/cce_10_0384.html | 8 +- docs/cce/umn/cce_10_0385.html | 200 +- docs/cce/umn/cce_10_0386.html | 2 +- docs/cce/umn/cce_10_0388.html | 24 +- docs/cce/umn/cce_10_0390.html | 4 +- docs/cce/umn/cce_10_0391.html | 3 +- docs/cce/umn/cce_10_0399.html | 10 +- docs/cce/umn/cce_10_0400.html | 10 +- docs/cce/umn/cce_10_0402.html | 2 +- docs/cce/umn/cce_10_0403.html | 12 +- docs/cce/umn/cce_10_0405.html | 779 ++--- docs/cce/umn/cce_10_0406.html | 49 +- docs/cce/umn/cce_10_0415.html | 24 +- docs/cce/umn/cce_10_0416.html | 246 ++ docs/cce/umn/cce_10_0420.html | 29 +- docs/cce/umn/cce_10_0425.html | 6 +- docs/cce/umn/cce_10_0426.html | 2 +- docs/cce/umn/cce_10_0430.html | 48 +- docs/cce/umn/cce_10_0431.html | 2 +- docs/cce/umn/cce_10_0432.html | 2 +- docs/cce/umn/cce_10_0437.html | 4 +- docs/cce/umn/cce_10_0441.html | 14 +- docs/cce/umn/cce_10_0442.html | 6 +- docs/cce/umn/cce_10_0448.html | 2 +- docs/cce/umn/cce_10_0450.html | 4 +- docs/cce/umn/cce_10_0452.html | 4 +- docs/cce/umn/cce_10_0456.html | 2 +- docs/cce/umn/cce_10_0459.html | 6 +- docs/cce/umn/cce_10_0460.html | 2 +- docs/cce/umn/cce_10_0462.html | 42 +- docs/cce/umn/cce_10_0463.html | 2 +- docs/cce/umn/cce_10_0476.html | 167 +- docs/cce/umn/cce_10_0477.html | 2 +- docs/cce/umn/cce_10_0493.html | 2 +- docs/cce/umn/cce_10_0495.html | 2 +- docs/cce/umn/cce_10_0498.html | 2 +- docs/cce/umn/cce_10_0503.html | 10 +- docs/cce/umn/cce_10_0508.html | 10 +- docs/cce/umn/cce_10_0511.html | 4 +- docs/cce/umn/cce_10_0513.html | 4 +- docs/cce/umn/cce_10_0521.html | 4 +- docs/cce/umn/cce_10_0522.html | 2 +- docs/cce/umn/cce_10_0525.html | 6 +- docs/cce/umn/cce_10_0527.html | 15 + docs/cce/umn/cce_10_0528.html | 27 + docs/cce/umn/cce_10_0529.html | 15 + docs/cce/umn/cce_10_0530.html | 21 + docs/cce/umn/cce_10_0531.html | 16 + docs/cce/umn/cce_10_0549.html | 53 +- docs/cce/umn/cce_10_0550.html | 16 +- docs/cce/umn/cce_10_0551.html | 3 +- docs/cce/umn/cce_10_0552.html | 8 +- docs/cce/umn/cce_10_0553.html | 8 +- docs/cce/umn/cce_10_0554.html | 68 + docs/cce/umn/cce_10_0555.html | 83 + docs/cce/umn/cce_10_0557.html | 5 +- docs/cce/umn/cce_10_0566.html | 2 +- docs/cce/umn/cce_10_0601.html | 4 +- docs/cce/umn/cce_10_0602.html | 22 +- docs/cce/umn/cce_10_0603.html | 2 +- docs/cce/umn/cce_10_0604.html | 2 +- docs/cce/umn/cce_10_0605.html | 8 +- docs/cce/umn/cce_10_0614.html | 41 +- docs/cce/umn/cce_10_0615.html | 50 +- docs/cce/umn/cce_10_0616.html | 31 +- docs/cce/umn/cce_10_0617.html | 32 + docs/cce/umn/cce_10_0619.html | 85 +- docs/cce/umn/cce_10_0620.html | 47 +- docs/cce/umn/cce_10_0624.html | 2 +- docs/cce/umn/cce_10_0625.html | 117 +- docs/cce/umn/cce_10_0626.html | 6 +- docs/cce/umn/cce_10_0630.html | 33 +- docs/cce/umn/cce_10_0631.html | 143 +- docs/cce/umn/cce_10_0633.html | 6 +- docs/cce/umn/cce_10_0634.html | 37 +- docs/cce/umn/cce_10_0635.html | 15 +- docs/cce/umn/cce_10_0636.html | 7 +- docs/cce/umn/cce_10_0637.html | 2 +- docs/cce/umn/cce_10_0638.html | 16 +- docs/cce/umn/cce_10_0649.html | 4 +- docs/cce/umn/cce_10_0652.html | 68 +- docs/cce/umn/cce_10_0653.html | 24 +- docs/cce/umn/cce_10_0654.html | 2 +- docs/cce/umn/cce_10_0656.html | 4 +- docs/cce/umn/cce_10_0658.html | 2 +- docs/cce/umn/cce_10_0659.html | 20 +- docs/cce/umn/cce_10_0672.html | 3 +- docs/cce/umn/cce_10_0673.html | 2 +- docs/cce/umn/cce_10_0674.html | 8 +- docs/cce/umn/cce_10_0675.html | 2 + docs/cce/umn/cce_10_0678.html | 4 +- docs/cce/umn/cce_10_0680.html | 2 +- docs/cce/umn/cce_10_0681.html | 518 ++-- docs/cce/umn/cce_10_0683.html | 12 +- docs/cce/umn/cce_10_0684.html | 79 +- docs/cce/umn/cce_10_0686.html | 4 + docs/cce/umn/cce_10_0687.html | 32 +- docs/cce/umn/cce_10_0688.html | 26 +- docs/cce/umn/cce_10_0689.html | 4 +- docs/cce/umn/cce_10_0691.html | 4 +- docs/cce/umn/cce_10_0692.html | 2 + docs/cce/umn/cce_10_0693.html | 19 +- docs/cce/umn/cce_10_0694.html | 55 +- docs/cce/umn/cce_10_0695.html | 418 +-- docs/cce/umn/cce_10_0697.html | 2 +- docs/cce/umn/cce_10_0698.html | 2 +- docs/cce/umn/cce_10_0699.html | 50 +- docs/cce/umn/cce_10_0704.html | 2 +- docs/cce/umn/cce_10_0705.html | 12 +- docs/cce/umn/cce_10_0709.html | 8 +- docs/cce/umn/cce_10_0720.html | 10 +- docs/cce/umn/cce_10_0721.html | 2 +- docs/cce/umn/cce_10_0722.html | 46 +- docs/cce/umn/cce_10_0726.html | 8 +- docs/cce/umn/cce_10_0729.html | 16 +- docs/cce/umn/cce_10_0730.html | 39 +- docs/cce/umn/cce_10_0735.html | 2 +- docs/cce/umn/cce_10_0744.html | 36 +- docs/cce/umn/cce_10_0766.html | 239 +- docs/cce/umn/cce_10_0767.html | 4 +- docs/cce/umn/cce_10_0768.html | 3 +- docs/cce/umn/cce_10_0773.html | 2 +- docs/cce/umn/cce_10_0774.html | 3 +- docs/cce/umn/cce_10_0775.html | 14 +- docs/cce/umn/cce_10_0776.html | 3 +- docs/cce/umn/cce_10_0777.html | 2 +- docs/cce/umn/cce_10_0782.html | 5 +- docs/cce/umn/cce_10_0783.html | 4 +- docs/cce/umn/cce_10_0784.html | 23 +- docs/cce/umn/cce_10_0785.html | 10 +- docs/cce/umn/cce_10_0786.html | 74 +- docs/cce/umn/cce_10_0787.html | 10 +- docs/cce/umn/cce_10_0788.html | 3 +- docs/cce/umn/cce_10_0789.html | 325 +- docs/cce/umn/cce_10_0792.html | 53 + docs/cce/umn/cce_10_0793.html | 57 + docs/cce/umn/cce_10_0799.html | 15 + docs/cce/umn/cce_10_0809.html | 79 + docs/cce/umn/cce_10_0811.html | 4 +- docs/cce/umn/cce_10_0813.html | 2 +- docs/cce/umn/cce_10_0831.html | 12 +- docs/cce/umn/cce_10_0832.html | 20 +- docs/cce/umn/cce_10_0836.html | 6 +- docs/cce/umn/cce_10_0839.html | 102 +- docs/cce/umn/cce_10_0841.html | 2 +- docs/cce/umn/cce_10_0842.html | 2 +- docs/cce/umn/cce_10_0859.html | 6 +- docs/cce/umn/cce_10_0864.html | 6 +- docs/cce/umn/cce_10_0886.html | 2 +- docs/cce/umn/cce_10_0889.html | 3 +- docs/cce/umn/cce_10_0891.html | 2 +- docs/cce/umn/cce_10_0892.html | 8 +- docs/cce/umn/cce_10_0893.html | 52 +- docs/cce/umn/cce_10_0896.html | 18 +- docs/cce/umn/cce_10_0897.html | 2 +- docs/cce/umn/cce_10_0906.html | 13 +- docs/cce/umn/cce_10_0908.html | 2 + docs/cce/umn/cce_10_0909.html | 8 +- docs/cce/umn/cce_10_0916.html | 2 +- docs/cce/umn/cce_10_0919.html | 100 + docs/cce/umn/cce_10_0924.html | 8 +- docs/cce/umn/cce_10_0925.html | 4 +- docs/cce/umn/cce_10_0927.html | 2 +- docs/cce/umn/cce_10_0934.html | 11 +- docs/cce/umn/cce_10_0935.html | 2 + docs/cce/umn/cce_10_0936.html | 4 + docs/cce/umn/cce_10_0937.html | 18 +- docs/cce/umn/cce_10_0939.html | 6 +- docs/cce/umn/cce_10_0940.html | 12 +- docs/cce/umn/cce_10_0944.html | 2 +- docs/cce/umn/cce_10_0945.html | 136 + docs/cce/umn/cce_10_0947.html | 89 + docs/cce/umn/cce_10_0949.html | 409 +++ docs/cce/umn/cce_10_0950.html | 83 + docs/cce/umn/cce_10_0954.html | 61 + docs/cce/umn/cce_10_0955.html | 350 +++ docs/cce/umn/cce_10_0957.html | 118 + docs/cce/umn/cce_10_0967.html | 55 + docs/cce/umn/cce_10_0968.html | 35 + docs/cce/umn/cce_bestpractice_00004.html | 24 +- docs/cce/umn/cce_bestpractice_00006.html | 27 +- docs/cce/umn/cce_bestpractice_0002.html | 2 +- docs/cce/umn/cce_bestpractice_0003.html | 2 +- docs/cce/umn/cce_bestpractice_00035.html | 18 +- docs/cce/umn/cce_bestpractice_0004.html | 2 +- docs/cce/umn/cce_bestpractice_0008.html | 6 +- docs/cce/umn/cce_bestpractice_0009.html | 2 +- docs/cce/umn/cce_bestpractice_0010.html | 10 +- docs/cce/umn/cce_bestpractice_0013.html | 2 +- docs/cce/umn/cce_bestpractice_0014.html | 6 +- docs/cce/umn/cce_bestpractice_00162.html | 18 +- docs/cce/umn/cce_bestpractice_00198.html | 50 +- docs/cce/umn/cce_bestpractice_00199.html | 10 +- docs/cce/umn/cce_bestpractice_00221.html | 18 +- docs/cce/umn/cce_bestpractice_00222.html | 20 +- docs/cce/umn/cce_bestpractice_00226.html | 2 +- docs/cce/umn/cce_bestpractice_00227.html | 44 +- docs/cce/umn/cce_bestpractice_00228.html | 28 +- docs/cce/umn/cce_bestpractice_00231.html | 6 +- docs/cce/umn/cce_bestpractice_0024.html | 36 +- docs/cce/umn/cce_bestpractice_00253.html | 80 +- docs/cce/umn/cce_bestpractice_00253_0.html | 80 +- docs/cce/umn/cce_bestpractice_00254.html | 4 +- docs/cce/umn/cce_bestpractice_00281.html | 255 +- docs/cce/umn/cce_bestpractice_00282.html | 14 +- docs/cce/umn/cce_bestpractice_00284.html | 4 +- docs/cce/umn/cce_bestpractice_0050.html | 2 +- docs/cce/umn/cce_bestpractice_0052.html | 2 +- docs/cce/umn/cce_bestpractice_0053.html | 2 +- docs/cce/umn/cce_bestpractice_0055.html | 2 +- docs/cce/umn/cce_bestpractice_0107.html | 4 +- docs/cce/umn/cce_bestpractice_0300.html | 8 +- docs/cce/umn/cce_bestpractice_0307.html | 12 +- docs/cce/umn/cce_bestpractice_0310.html | 44 +- docs/cce/umn/cce_bestpractice_0312.html | 2 +- docs/cce/umn/cce_bestpractice_0313.html | 2 +- docs/cce/umn/cce_bestpractice_0314.html | 8 +- docs/cce/umn/cce_bestpractice_0324.html | 32 +- docs/cce/umn/cce_bestpractice_0325.html | 31 +- docs/cce/umn/cce_bestpractice_0333.html | 25 +- docs/cce/umn/cce_bestpractice_0348.html | 2 +- docs/cce/umn/cce_bestpractice_0357.html | 6 +- docs/cce/umn/cce_bestpractice_10001.html | 14 +- docs/cce/umn/cce_bestpractice_10002.html | 8 +- docs/cce/umn/cce_bestpractice_10008.html | 2 + docs/cce/umn/cce_bestpractice_10009.html | 12 +- docs/cce/umn/cce_bestpractice_10010.html | 4 +- docs/cce/umn/cce_bestpractice_10012.html | 113 +- docs/cce/umn/cce_bestpractice_10016.html | 64 +- docs/cce/umn/cce_bestpractice_10017.html | 4 +- docs/cce/umn/cce_bestpractice_10020.html | 22 +- docs/cce/umn/cce_bestpractice_10020_0.html | 22 +- docs/cce/umn/cce_bestpractice_10021.html | 34 + docs/cce/umn/cce_bestpractice_10024.html | 4 +- docs/cce/umn/cce_bestpractice_10041.html | 6 +- docs/cce/umn/cce_bulletin_0000.html | 2 - docs/cce/umn/cce_bulletin_0026.html | 4 +- docs/cce/umn/cce_bulletin_0027.html | 4 +- docs/cce/umn/cce_bulletin_0033.html | 182 -- docs/cce/umn/cce_bulletin_0058.html | 4 +- docs/cce/umn/cce_bulletin_0059.html | 2 +- docs/cce/umn/cce_bulletin_0068.html | 2 +- docs/cce/umn/cce_bulletin_0089.html | 2 +- docs/cce/umn/cce_bulletin_0095.html | 2 +- docs/cce/umn/cce_bulletin_0099.html | 30 + docs/cce/umn/cce_faq_00004.html | 2 +- docs/cce/umn/cce_faq_00006.html | 10 +- docs/cce/umn/cce_faq_00012.html | 6 +- docs/cce/umn/cce_faq_00015.html | 110 +- docs/cce/umn/cce_faq_00018.html | 89 +- docs/cce/umn/cce_faq_00020.html | 4 +- docs/cce/umn/cce_faq_00021.html | 2 + docs/cce/umn/cce_faq_00027.html | 24 +- docs/cce/umn/cce_faq_00029.html | 8 +- docs/cce/umn/cce_faq_00037.html | 2 + docs/cce/umn/cce_faq_00038.html | 11 +- docs/cce/umn/cce_faq_00039.html | 23 +- docs/cce/umn/cce_faq_00040.html | 2 +- docs/cce/umn/cce_faq_00041.html | 2 +- docs/cce/umn/cce_faq_00089.html | 4 +- docs/cce/umn/cce_faq_00090.html | 7 +- docs/cce/umn/cce_faq_00097.html | 2 +- docs/cce/umn/cce_faq_00098.html | 136 +- docs/cce/umn/cce_faq_00106.html | 2 +- docs/cce/umn/cce_faq_00107.html | 4 +- docs/cce/umn/cce_faq_00109.html | 6 +- docs/cce/umn/cce_faq_00111.html | 2 +- docs/cce/umn/cce_faq_00120.html | 60 +- docs/cce/umn/cce_faq_00134.html | 37 +- docs/cce/umn/cce_faq_00140.html | 8 +- docs/cce/umn/cce_faq_00146.html | 2 +- docs/cce/umn/cce_faq_00185.html | 2 +- docs/cce/umn/cce_faq_00195.html | 4 +- docs/cce/umn/cce_faq_00197.html | 6 +- docs/cce/umn/cce_faq_00200.html | 95 +- docs/cce/umn/cce_faq_00201.html | 47 +- docs/cce/umn/cce_faq_00202.html | 14 +- docs/cce/umn/cce_faq_00203.html | 4 +- docs/cce/umn/cce_faq_00204.html | 3 +- docs/cce/umn/cce_faq_00205.html | 2 + docs/cce/umn/cce_faq_00209.html | 16 +- docs/cce/umn/cce_faq_00210.html | 2 +- docs/cce/umn/cce_faq_00218.html | 2 +- docs/cce/umn/cce_faq_00224.html | 12 +- docs/cce/umn/cce_faq_00230.html | 2 +- docs/cce/umn/cce_faq_00235.html | 2 +- docs/cce/umn/cce_faq_00260.html | 2 +- docs/cce/umn/cce_faq_00263.html | 2 +- docs/cce/umn/cce_faq_00265.html | 381 +-- docs/cce/umn/cce_faq_00266.html | 2 +- docs/cce/umn/cce_faq_00280.html | 2 +- docs/cce/umn/cce_faq_00281.html | 2 +- docs/cce/umn/cce_faq_00284.html | 2 + docs/cce/umn/cce_faq_00286.html | 8 +- docs/cce/umn/cce_faq_00296.html | 2 +- docs/cce/umn/cce_faq_00307.html | 30 +- docs/cce/umn/cce_faq_00311.html | 4 +- docs/cce/umn/cce_faq_00319.html | 4 +- docs/cce/umn/cce_faq_00321.html | 2 +- docs/cce/umn/cce_faq_00322.html | 10 +- docs/cce/umn/cce_faq_00325.html | 4 +- docs/cce/umn/cce_faq_00326.html | 2 +- docs/cce/umn/cce_faq_00394.html | 6 +- docs/cce/umn/cce_faq_00397.html | 2 + docs/cce/umn/cce_faq_00398.html | 2 +- docs/cce/umn/cce_faq_00402.html | 2 +- docs/cce/umn/cce_faq_00404.html | 313 ++ docs/cce/umn/cce_faq_00409.html | 2 +- docs/cce/umn/cce_faq_00417.html | 2 +- docs/cce/umn/cce_faq_00418.html | 22 + docs/cce/umn/cce_faq_00429.html | 4 +- docs/cce/umn/cce_faq_00432.html | 5 +- docs/cce/umn/cce_faq_00438.html | 2 +- docs/cce/umn/cce_faq_00440.html | 4 +- docs/cce/umn/cce_faq_00446.html | 4 +- docs/cce/umn/cce_faq_00447.html | 2 +- docs/cce/umn/cce_faq_00455.html | 60 + docs/cce/umn/cce_faq_00460.html | 21 +- docs/cce/umn/cce_faq_00468.html | 486 +++ docs/cce/umn/cce_faq_00484.html | 29 + docs/cce/umn/cce_faq_00487.html | 29 + docs/cce/umn/cce_productdesc_0001.html | 15 +- docs/cce/umn/cce_productdesc_0002.html | 12 +- docs/cce/umn/cce_productdesc_0003.html | 10 +- docs/cce/umn/cce_productdesc_0005.html | 133 +- docs/cce/umn/cce_productdesc_0007.html | 6 +- docs/cce/umn/cce_productdesc_0008.html | 4 +- docs/cce/umn/cce_productdesc_0017.html | 4 +- docs/cce/umn/cce_productdesc_0018.html | 4 +- docs/cce/umn/cce_productdesc_0021.html | 2 +- docs/cce/umn/cce_qs_0000.html | 2 +- docs/cce/umn/cce_qs_0001.html | 14 +- docs/cce/umn/cce_qs_0003.html | 14 +- docs/cce/umn/cce_qs_0004.html | 8 +- docs/cce/umn/cce_qs_0005.html | 18 +- docs/cce/umn/cce_qs_0006.html | 4 +- docs/cce/umn/cce_qs_0007.html | 4 +- docs/cce/umn/cce_qs_0008.html | 93 +- docs/cce/umn/cce_qs_0009.html | 4 +- docs/cce/umn/en-us_image_0000001332989461.png | Bin 11864 -> 0 bytes docs/cce/umn/en-us_image_0000001751308190.png | Bin 55984 -> 0 bytes ...4.png => en-us_image_0000001851742516.png} | Bin docs/cce/umn/en-us_image_0000001851742548.png | Bin 0 -> 30194 bytes ...5.png => en-us_image_0000001851742596.png} | Bin ...2.png => en-us_image_0000001851742644.png} | Bin ...6.png => en-us_image_0000001851742664.png} | Bin ...5.png => en-us_image_0000001851742724.png} | Bin ...3.png => en-us_image_0000001898022705.png} | Bin ...1.png => en-us_image_0000001898022793.png} | Bin ...4.png => en-us_image_0000001898022857.png} | Bin docs/cce/umn/en-us_image_0000002065478774.gif | Bin 300833 -> 0 bytes docs/cce/umn/en-us_image_0000002065478874.png | Bin 9081 -> 0 bytes docs/cce/umn/en-us_image_0000002065479138.png | Bin 13601 -> 0 bytes docs/cce/umn/en-us_image_0000002065479674.png | Bin 31088 -> 0 bytes docs/cce/umn/en-us_image_0000002065480910.png | Bin 57904 -> 0 bytes docs/cce/umn/en-us_image_0000002065636318.png | Bin 48799 -> 0 bytes docs/cce/umn/en-us_image_0000002065636326.png | Bin 21229 -> 0 bytes docs/cce/umn/en-us_image_0000002065637230.png | Bin 12442 -> 0 bytes docs/cce/umn/en-us_image_0000002065637498.png | Bin 142212 -> 0 bytes docs/cce/umn/en-us_image_0000002065639022.png | Bin 33699 -> 0 bytes docs/cce/umn/en-us_image_0000002065639130.png | Bin 53292 -> 0 bytes docs/cce/umn/en-us_image_0000002065639146.png | Bin 6870 -> 0 bytes docs/cce/umn/en-us_image_0000002065639262.png | Bin 295492 -> 0 bytes docs/cce/umn/en-us_image_0000002101595681.gif | Bin 221101 -> 0 bytes docs/cce/umn/en-us_image_0000002101596485.png | Bin 24175 -> 0 bytes docs/cce/umn/en-us_image_0000002101596565.png | Bin 74307 -> 0 bytes docs/cce/umn/en-us_image_0000002101597089.png | Bin 15776 -> 0 bytes docs/cce/umn/en-us_image_0000002101597829.png | Bin 16260 -> 0 bytes docs/cce/umn/en-us_image_0000002101677169.gif | Bin 207048 -> 0 bytes docs/cce/umn/en-us_image_0000002101677565.png | Bin 44849 -> 0 bytes docs/cce/umn/en-us_image_0000002101678921.png | Bin 201588 -> 0 bytes docs/cce/umn/en-us_image_0000002101679293.png | Bin 49030 -> 0 bytes ...9.png => en-us_image_0000002218657498.png} | Bin ...5.png => en-us_image_0000002218657514.png} | Bin ...6.png => en-us_image_0000002218658206.png} | Bin ...9.png => en-us_image_0000002218658310.png} | Bin ...5.png => en-us_image_0000002218658322.png} | Bin ...7.png => en-us_image_0000002218658326.png} | Bin ...3.png => en-us_image_0000002218658406.png} | Bin ...9.png => en-us_image_0000002218658418.png} | Bin ...0.png => en-us_image_0000002218658506.png} | Bin docs/cce/umn/en-us_image_0000002218658526.png | Bin 0 -> 22490 bytes ...7.png => en-us_image_0000002218658606.png} | Bin ...4.png => en-us_image_0000002218658614.png} | Bin docs/cce/umn/en-us_image_0000002218658654.png | Bin 0 -> 106794 bytes ...0.png => en-us_image_0000002218658786.png} | Bin ...9.png => en-us_image_0000002218658854.png} | Bin ...1.png => en-us_image_0000002218658914.png} | Bin ...7.jpg => en-us_image_0000002218658934.jpg} | Bin ...5.png => en-us_image_0000002218658938.png} | Bin ...4.png => en-us_image_0000002218659046.png} | Bin ...5.png => en-us_image_0000002218659098.png} | Bin ...8.png => en-us_image_0000002218659110.png} | Bin ...8.png => en-us_image_0000002218659118.png} | Bin ...8.png => en-us_image_0000002218659142.png} | Bin ...4.png => en-us_image_0000002218659174.png} | Bin ...0.jpg => en-us_image_0000002218659182.jpg} | Bin ...6.png => en-us_image_0000002218659242.png} | Bin ...2.png => en-us_image_0000002218659254.png} | Bin ...8.png => en-us_image_0000002218659274.png} | Bin docs/cce/umn/en-us_image_0000002218659302.png | Bin 0 -> 44578 bytes docs/cce/umn/en-us_image_0000002218659314.png | Bin 0 -> 14555 bytes ...7.png => en-us_image_0000002218659818.png} | Bin ...5.png => en-us_image_0000002218659822.png} | Bin ...8.png => en-us_image_0000002218659866.png} | Bin ...2.png => en-us_image_0000002218659906.png} | Bin ...8.png => en-us_image_0000002218659930.png} | Bin ...0.png => en-us_image_0000002218659938.png} | Bin ...9.png => en-us_image_0000002218660018.png} | Bin docs/cce/umn/en-us_image_0000002218660022.png | Bin 0 -> 492 bytes ...3.png => en-us_image_0000002218660194.png} | Bin ...0.png => en-us_image_0000002218660226.png} | Bin ...9.png => en-us_image_0000002218660238.png} | Bin ...7.png => en-us_image_0000002218660286.png} | Bin ...4.png => en-us_image_0000002218660294.png} | Bin ...8.png => en-us_image_0000002218660298.png} | Bin docs/cce/umn/en-us_image_0000002218660366.png | Bin 0 -> 492 bytes ...8.png => en-us_image_0000002218660418.png} | Bin ...8.png => en-us_image_0000002218660430.png} | Bin ...6.png => en-us_image_0000002218660438.png} | Bin docs/cce/umn/en-us_image_0000002218660466.png | Bin 0 -> 119867 bytes docs/cce/umn/en-us_image_0000002218660474.png | Bin 0 -> 119867 bytes docs/cce/umn/en-us_image_0000002218660478.png | Bin 0 -> 297839 bytes ...5.png => en-us_image_0000002218660486.png} | Bin ...1.png => en-us_image_0000002218660514.png} | Bin ...0.png => en-us_image_0000002218660566.png} | Bin ...3.png => en-us_image_0000002218660654.png} | Bin ...3.png => en-us_image_0000002218660706.png} | Bin ...7.png => en-us_image_0000002218660710.png} | Bin ...6.png => en-us_image_0000002218660718.png} | Bin ...2.png => en-us_image_0000002218660734.png} | Bin docs/cce/umn/en-us_image_0000002218660782.png | Bin 0 -> 50716 bytes ...2.png => en-us_image_0000002218660810.png} | Bin docs/cce/umn/en-us_image_0000002218817314.png | Bin 0 -> 134506 bytes docs/cce/umn/en-us_image_0000002218817326.png | Bin 0 -> 21978 bytes ...2.png => en-us_image_0000002218818034.png} | Bin ...2.png => en-us_image_0000002218818126.png} | Bin ...7.png => en-us_image_0000002218818142.png} | Bin ...4.png => en-us_image_0000002218818146.png} | Bin ...4.png => en-us_image_0000002218818158.png} | Bin ...9.png => en-us_image_0000002218818218.png} | Bin docs/cce/umn/en-us_image_0000002218818222.png | Bin 0 -> 24238 bytes ...1.png => en-us_image_0000002218818234.png} | Bin ...8.png => en-us_image_0000002218818246.png} | Bin ...2.png => en-us_image_0000002218818310.png} | Bin docs/cce/umn/en-us_image_0000002218818366.png | Bin 0 -> 207898 bytes docs/cce/umn/en-us_image_0000002218818382.png | Bin 0 -> 25312 bytes docs/cce/umn/en-us_image_0000002218818386.png | Bin 0 -> 412100 bytes docs/cce/umn/en-us_image_0000002218818398.png | Bin 0 -> 26963 bytes ...1.jpg => en-us_image_0000002218818442.jpg} | Bin ...5.png => en-us_image_0000002218818446.png} | Bin ...2.png => en-us_image_0000002218818458.png} | Bin docs/cce/umn/en-us_image_0000002218818490.png | Bin 0 -> 17753 bytes ...1.png => en-us_image_0000002218818530.png} | Bin ...8.png => en-us_image_0000002218818546.png} | Bin ...8.png => en-us_image_0000002218818590.png} | Bin ...4.png => en-us_image_0000002218818630.png} | Bin ...6.png => en-us_image_0000002218818686.png} | Bin ...7.png => en-us_image_0000002218818734.png} | Bin ...8.png => en-us_image_0000002218818738.png} | Bin ...8.jpg => en-us_image_0000002218818770.jpg} | Bin ...2.png => en-us_image_0000002218818914.png} | Bin ...7.png => en-us_image_0000002218818934.png} | Bin ...0.png => en-us_image_0000002218818946.png} | Bin ...1.png => en-us_image_0000002218818954.png} | Bin ...2.png => en-us_image_0000002218818982.png} | Bin ...8.png => en-us_image_0000002218818994.png} | Bin ...9.png => en-us_image_0000002218819094.png} | Bin docs/cce/umn/en-us_image_0000002218819126.png | Bin 0 -> 16103 bytes docs/cce/umn/en-us_image_0000002218819222.png | Bin 0 -> 109664 bytes ...9.png => en-us_image_0000002218819242.png} | Bin ...7.png => en-us_image_0000002218819650.png} | Bin ...3.png => en-us_image_0000002218819718.png} | Bin ...0.png => en-us_image_0000002218819774.png} | Bin ...2.png => en-us_image_0000002218819786.png} | Bin ...5.png => en-us_image_0000002218819838.png} | Bin docs/cce/umn/en-us_image_0000002218819854.png | Bin 0 -> 492 bytes docs/cce/umn/en-us_image_0000002218819982.png | Bin 0 -> 8985 bytes ...6.png => en-us_image_0000002218820018.png} | Bin ...8.png => en-us_image_0000002218820034.png} | Bin ...4.png => en-us_image_0000002218820038.png} | Bin ...6.png => en-us_image_0000002218820158.png} | Bin docs/cce/umn/en-us_image_0000002218820166.png | Bin 0 -> 125 bytes docs/cce/umn/en-us_image_0000002218820214.png | Bin 0 -> 3460 bytes docs/cce/umn/en-us_image_0000002218820226.png | Bin 0 -> 492 bytes docs/cce/umn/en-us_image_0000002218820242.png | Bin 0 -> 80016 bytes ...8.png => en-us_image_0000002218820382.png} | Bin ...7.png => en-us_image_0000002218820402.png} | Bin ...0.png => en-us_image_0000002218820410.png} | Bin docs/cce/umn/en-us_image_0000002218820434.png | Bin 0 -> 44580 bytes ...2.png => en-us_image_0000002218820458.png} | Bin ...2.png => en-us_image_0000002218820526.png} | Bin ...5.png => en-us_image_0000002218820570.png} | Bin docs/cce/umn/en-us_image_0000002218820586.png | Bin 0 -> 42320 bytes docs/cce/umn/en-us_image_0000002218820614.png | Bin 0 -> 12522 bytes ...0.png => en-us_image_0000002218820646.png} | Bin ...3.png => en-us_image_0000002218820650.png} | Bin docs/cce/umn/en-us_image_0000002218820658.png | Bin 0 -> 26098 bytes docs/cce/umn/en-us_image_0000002218820674.png | Bin 0 -> 36749 bytes docs/cce/umn/en-us_image_0000002218820702.png | Bin 0 -> 125 bytes ...8.png => en-us_image_0000002253617217.png} | Bin ...3.png => en-us_image_0000002253617941.png} | Bin ...9.png => en-us_image_0000002253618117.png} | Bin ...8.png => en-us_image_0000002253618121.png} | Bin ...0.png => en-us_image_0000002253618133.png} | Bin ...2.png => en-us_image_0000002253618137.png} | Bin docs/cce/umn/en-us_image_0000002253618289.png | Bin 0 -> 224439 bytes ...6.png => en-us_image_0000002253618329.png} | Bin ...0.png => en-us_image_0000002253618345.png} | Bin ...2.png => en-us_image_0000002253618457.png} | Bin ...9.png => en-us_image_0000002253618517.png} | Bin ...7.png => en-us_image_0000002253618529.png} | Bin ...7.png => en-us_image_0000002253618549.png} | Bin ...7.png => en-us_image_0000002253618569.png} | Bin ...3.png => en-us_image_0000002253618605.png} | Bin ...5.png => en-us_image_0000002253618649.png} | Bin docs/cce/umn/en-us_image_0000002253618813.png | Bin 0 -> 70330 bytes ...9.png => en-us_image_0000002253618817.png} | Bin ...7.png => en-us_image_0000002253618837.png} | Bin ...3.png => en-us_image_0000002253618841.png} | Bin ...8.png => en-us_image_0000002253618845.png} | Bin ...0.png => en-us_image_0000002253618897.png} | Bin ...1.png => en-us_image_0000002253619005.png} | Bin ...9.png => en-us_image_0000002253619089.png} | Bin docs/cce/umn/en-us_image_0000002253619117.png | Bin 0 -> 34602 bytes ...0.png => en-us_image_0000002253619133.png} | Bin ...9.png => en-us_image_0000002253619517.png} | Bin ...6.png => en-us_image_0000002253619521.png} | Bin ...9.png => en-us_image_0000002253619569.png} | Bin ...4.png => en-us_image_0000002253619601.png} | Bin ...5.png => en-us_image_0000002253619605.png} | Bin ...9.png => en-us_image_0000002253619613.png} | Bin ...6.png => en-us_image_0000002253619621.png} | Bin ...6.png => en-us_image_0000002253619653.png} | Bin ...4.png => en-us_image_0000002253619701.png} | Bin docs/cce/umn/en-us_image_0000002253619705.png | Bin 0 -> 30987 bytes ...8.png => en-us_image_0000002253619713.png} | Bin ...5.png => en-us_image_0000002253619725.png} | Bin ...3.png => en-us_image_0000002253619737.png} | Bin ...3.png => en-us_image_0000002253619765.png} | Bin docs/cce/umn/en-us_image_0000002253619901.png | Bin 0 -> 172415 bytes ...3.png => en-us_image_0000002253619909.png} | Bin ...9.png => en-us_image_0000002253619937.png} | Bin ...7.png => en-us_image_0000002253619977.png} | Bin ...3.png => en-us_image_0000002253619981.png} | Bin ...0.png => en-us_image_0000002253620001.png} | Bin ...6.png => en-us_image_0000002253620029.png} | Bin ...6.png => en-us_image_0000002253620033.png} | Bin ...3.png => en-us_image_0000002253620049.png} | Bin ...1.png => en-us_image_0000002253620097.png} | Bin ...1.png => en-us_image_0000002253620189.png} | Bin docs/cce/umn/en-us_image_0000002253620209.png | Bin 0 -> 310647 bytes docs/cce/umn/en-us_image_0000002253620213.png | Bin 0 -> 310647 bytes ...7.png => en-us_image_0000002253620305.png} | Bin ...7.png => en-us_image_0000002253620349.png} | Bin ...1.png => en-us_image_0000002253620361.png} | Bin ...9.png => en-us_image_0000002253620365.png} | Bin ...8.png => en-us_image_0000002253620397.png} | Bin ...7.png => en-us_image_0000002253620425.png} | Bin ...0.png => en-us_image_0000002253620433.png} | Bin ...7.png => en-us_image_0000002253620437.png} | Bin ...5.png => en-us_image_0000002253620477.png} | Bin ...4.png => en-us_image_0000002253620497.png} | Bin ...7.png => en-us_image_0000002253620533.png} | Bin docs/cce/umn/en-us_image_0000002253620537.png | Bin 0 -> 78033 bytes ...5.png => en-us_image_0000002253620541.png} | Bin ...8.png => en-us_image_0000002253620561.png} | Bin ...3.png => en-us_image_0000002253777129.png} | Bin ...9.png => en-us_image_0000002253777197.png} | Bin ...5.png => en-us_image_0000002253777225.png} | Bin ...3.png => en-us_image_0000002253777937.png} | Bin ...1.png => en-us_image_0000002253777941.png} | Bin ...8.png => en-us_image_0000002253777953.png} | Bin ...9.png => en-us_image_0000002253778017.png} | Bin ...6.png => en-us_image_0000002253778021.png} | Bin docs/cce/umn/en-us_image_0000002253778205.png | Bin 0 -> 22235 bytes ...7.png => en-us_image_0000002253778225.png} | Bin docs/cce/umn/en-us_image_0000002253778245.png | Bin 0 -> 144381 bytes ...7.png => en-us_image_0000002253778253.png} | Bin docs/cce/umn/en-us_image_0000002253778265.png | Bin 0 -> 55882 bytes ...8.png => en-us_image_0000002253778269.png} | Bin docs/cce/umn/en-us_image_0000002253778301.png | Bin 0 -> 134722 bytes ...7.png => en-us_image_0000002253778377.png} | Bin ...7.png => en-us_image_0000002253778437.png} | Bin ...8.png => en-us_image_0000002253778449.png} | Bin ...2.png => en-us_image_0000002253778453.png} | Bin ...2.png => en-us_image_0000002253778485.png} | Bin ...5.png => en-us_image_0000002253778493.png} | Bin ...9.png => en-us_image_0000002253778497.png} | Bin ...0.png => en-us_image_0000002253778541.png} | Bin docs/cce/umn/en-us_image_0000002253778733.png | Bin 0 -> 33648 bytes ...0.png => en-us_image_0000002253778737.png} | Bin ...6.png => en-us_image_0000002253778797.png} | Bin ...1.png => en-us_image_0000002253778813.png} | Bin ...1.png => en-us_image_0000002253778853.png} | Bin ...5.png => en-us_image_0000002253778885.png} | Bin ...9.png => en-us_image_0000002253778901.png} | Bin ...4.png => en-us_image_0000002253778965.png} | Bin docs/cce/umn/en-us_image_0000002253779013.png | Bin 0 -> 15929 bytes docs/cce/umn/en-us_image_0000002253779017.png | Bin 0 -> 108403 bytes ...3.png => en-us_image_0000002253779397.png} | Bin ...2.png => en-us_image_0000002253779469.png} | Bin ...2.png => en-us_image_0000002253779473.png} | Bin ...1.png => en-us_image_0000002253779501.png} | Bin ...1.png => en-us_image_0000002253779505.png} | Bin ...4.png => en-us_image_0000002253779605.png} | Bin ...2.png => en-us_image_0000002253779617.png} | Bin ...2.png => en-us_image_0000002253779625.png} | Bin ...7.png => en-us_image_0000002253779633.png} | Bin docs/cce/umn/en-us_image_0000002253779657.png | Bin 0 -> 4439 bytes ...8.png => en-us_image_0000002253779681.png} | Bin ...5.jpg => en-us_image_0000002253779773.jpg} | Bin ...5.png => en-us_image_0000002253779809.png} | Bin ...1.png => en-us_image_0000002253779825.png} | Bin docs/cce/umn/en-us_image_0000002253779849.png | Bin 0 -> 57912 bytes docs/cce/umn/en-us_image_0000002253779921.png | Bin 0 -> 190913 bytes ...0.png => en-us_image_0000002253779941.png} | Bin ...8.png => en-us_image_0000002253779949.png} | Bin ...1.png => en-us_image_0000002253779993.png} | Bin ...1.png => en-us_image_0000002253780085.png} | Bin ...2.png => en-us_image_0000002253780093.png} | Bin ...3.png => en-us_image_0000002253780145.png} | Bin ...9.png => en-us_image_0000002253780209.png} | Bin ...8.png => en-us_image_0000002253780305.png} | Bin ...8.png => en-us_image_0000002253780329.png} | Bin ...5.png => en-us_image_0000002253780361.png} | Bin ...7.png => en-us_image_0000002253780381.png} | Bin ...3.png => en-us_image_0000002253780433.png} | Bin ...9.png => en-us_image_0000002253780457.png} | Bin docs/cce/umn/en-us_image_0000002254877052.png | Bin 0 -> 30906 bytes docs/cce/umn/en-us_image_0000002254877428.png | Bin 0 -> 30769 bytes docs/cce/umn/en-us_image_0000002254879860.png | Bin 0 -> 28488 bytes docs/cce/umn/en-us_image_0000002254895070.png | Bin 0 -> 28621 bytes docs/cce/umn/en-us_image_0000002254895574.png | Bin 0 -> 14444 bytes docs/cce/umn/en-us_image_0000002254895914.png | Bin 0 -> 26346 bytes docs/cce/umn/en-us_image_0000002254978558.png | Bin 0 -> 28739 bytes docs/cce/umn/en-us_image_0000002255002834.png | Bin 0 -> 26389 bytes docs/cce/umn/en-us_image_0000002274473989.png | Bin 0 -> 11094 bytes docs/cce/umn/en-us_image_0000002289476265.png | Bin 0 -> 28576 bytes docs/cce/umn/en-us_image_0000002289589649.png | Bin 0 -> 17223 bytes docs/cce/umn/en-us_image_0000002289592109.png | Bin 0 -> 28041 bytes ...5638074.png => en-us_image_0261818867.png} | Bin 760 files changed, 13737 insertions(+), 8019 deletions(-) create mode 100644 docs/cce/umn/cce_10_0416.html create mode 100644 docs/cce/umn/cce_10_0527.html create mode 100644 docs/cce/umn/cce_10_0528.html create mode 100644 docs/cce/umn/cce_10_0529.html create mode 100644 docs/cce/umn/cce_10_0530.html create mode 100644 docs/cce/umn/cce_10_0531.html create mode 100644 docs/cce/umn/cce_10_0554.html create mode 100644 docs/cce/umn/cce_10_0555.html create mode 100644 docs/cce/umn/cce_10_0792.html create mode 100644 docs/cce/umn/cce_10_0793.html create mode 100644 docs/cce/umn/cce_10_0799.html create mode 100644 docs/cce/umn/cce_10_0809.html create mode 100644 docs/cce/umn/cce_10_0919.html create mode 100644 docs/cce/umn/cce_10_0945.html create mode 100644 docs/cce/umn/cce_10_0947.html create mode 100644 docs/cce/umn/cce_10_0949.html create mode 100644 docs/cce/umn/cce_10_0950.html create mode 100644 docs/cce/umn/cce_10_0954.html create mode 100644 docs/cce/umn/cce_10_0955.html create mode 100644 docs/cce/umn/cce_10_0957.html create mode 100644 docs/cce/umn/cce_10_0967.html create mode 100644 docs/cce/umn/cce_10_0968.html create mode 100644 docs/cce/umn/cce_bestpractice_10021.html delete mode 100644 docs/cce/umn/cce_bulletin_0033.html create mode 100644 docs/cce/umn/cce_bulletin_0099.html create mode 100644 docs/cce/umn/cce_faq_00404.html create mode 100644 docs/cce/umn/cce_faq_00418.html create mode 100644 docs/cce/umn/cce_faq_00455.html create mode 100644 docs/cce/umn/cce_faq_00468.html create mode 100644 docs/cce/umn/cce_faq_00484.html create mode 100644 docs/cce/umn/cce_faq_00487.html delete mode 100644 docs/cce/umn/en-us_image_0000001332989461.png delete mode 100644 docs/cce/umn/en-us_image_0000001751308190.png rename docs/cce/umn/{en-us_image_0000001751467114.png => en-us_image_0000001851742516.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001851742548.png rename docs/cce/umn/{en-us_image_0000001798266905.png => en-us_image_0000001851742596.png} (100%) rename docs/cce/umn/{en-us_image_0000001751467142.png => en-us_image_0000001851742644.png} (100%) rename docs/cce/umn/{en-us_image_0000001751308206.png => en-us_image_0000001851742664.png} (100%) rename docs/cce/umn/{en-us_image_0000001798266925.png => en-us_image_0000001851742724.png} (100%) rename docs/cce/umn/{en-us_image_0000001798307873.png => en-us_image_0000001898022705.png} (100%) rename docs/cce/umn/{en-us_image_0000001798307901.png => en-us_image_0000001898022793.png} (100%) rename docs/cce/umn/{en-us_image_0000001751467134.png => en-us_image_0000001898022857.png} (100%) delete mode 100644 docs/cce/umn/en-us_image_0000002065478774.gif delete mode 100644 docs/cce/umn/en-us_image_0000002065478874.png delete mode 100644 docs/cce/umn/en-us_image_0000002065479138.png delete mode 100644 docs/cce/umn/en-us_image_0000002065479674.png delete mode 100644 docs/cce/umn/en-us_image_0000002065480910.png delete mode 100644 docs/cce/umn/en-us_image_0000002065636318.png delete mode 100644 docs/cce/umn/en-us_image_0000002065636326.png delete mode 100644 docs/cce/umn/en-us_image_0000002065637230.png delete mode 100644 docs/cce/umn/en-us_image_0000002065637498.png delete mode 100644 docs/cce/umn/en-us_image_0000002065639022.png delete mode 100644 docs/cce/umn/en-us_image_0000002065639130.png delete mode 100644 docs/cce/umn/en-us_image_0000002065639146.png delete mode 100644 docs/cce/umn/en-us_image_0000002065639262.png delete mode 100644 docs/cce/umn/en-us_image_0000002101595681.gif delete mode 100644 docs/cce/umn/en-us_image_0000002101596485.png delete mode 100644 docs/cce/umn/en-us_image_0000002101596565.png delete mode 100644 docs/cce/umn/en-us_image_0000002101597089.png delete mode 100644 docs/cce/umn/en-us_image_0000002101597829.png delete mode 100644 docs/cce/umn/en-us_image_0000002101677169.gif delete mode 100644 docs/cce/umn/en-us_image_0000002101677565.png delete mode 100644 docs/cce/umn/en-us_image_0000002101678921.png delete mode 100644 docs/cce/umn/en-us_image_0000002101679293.png rename docs/cce/umn/{en-us_image_0000002101594869.png => en-us_image_0000002218657498.png} (100%) rename docs/cce/umn/{en-us_image_0000002101594885.png => en-us_image_0000002218657514.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637006.png => en-us_image_0000002218658206.png} (100%) rename docs/cce/umn/{en-us_image_0000002101677229.png => en-us_image_0000002218658310.png} (100%) rename docs/cce/umn/{en-us_image_0000002101677245.png => en-us_image_0000002218658322.png} (100%) rename docs/cce/umn/{en-us_image_0000002101595757.png => en-us_image_0000002218658326.png} (100%) rename docs/cce/umn/{en-us_image_0000002101595793.png => en-us_image_0000002218658406.png} (100%) rename docs/cce/umn/{en-us_image_0000002101595809.png => en-us_image_0000002218658418.png} (100%) rename docs/cce/umn/{en-us_image_0000002065478990.png => en-us_image_0000002218658506.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218658526.png rename docs/cce/umn/{en-us_image_0000002101596077.png => en-us_image_0000002218658606.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637534.png => en-us_image_0000002218658614.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218658654.png rename docs/cce/umn/{en-us_image_0000002065637710.png => en-us_image_0000002218658786.png} (100%) rename docs/cce/umn/{en-us_image_0000002101595749.png => en-us_image_0000002218658854.png} (100%) rename docs/cce/umn/{en-us_image_0000002101596661.png => en-us_image_0000002218658914.png} (100%) rename docs/cce/umn/{en-us_image_0000002101595797.jpg => en-us_image_0000002218658934.jpg} (100%) rename docs/cce/umn/{en-us_image_0000002101596405.png => en-us_image_0000002218658938.png} (100%) rename docs/cce/umn/{en-us_image_0000002065478954.png => en-us_image_0000002218659046.png} (100%) rename docs/cce/umn/{en-us_image_0000002101677485.png => en-us_image_0000002218659098.png} (100%) rename docs/cce/umn/{en-us_image_0000002065479098.png => en-us_image_0000002218659110.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637438.png => en-us_image_0000002218659118.png} (100%) rename docs/cce/umn/{en-us_image_0000002065479118.png => en-us_image_0000002218659142.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637614.png => en-us_image_0000002218659174.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637630.jpg => en-us_image_0000002218659182.jpg} (100%) rename docs/cce/umn/{en-us_image_0000002065637706.png => en-us_image_0000002218659242.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637662.png => en-us_image_0000002218659254.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480898.png => en-us_image_0000002218659274.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218659302.png create mode 100644 docs/cce/umn/en-us_image_0000002218659314.png rename docs/cce/umn/{en-us_image_0000002101678557.png => en-us_image_0000002218659818.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678525.png => en-us_image_0000002218659822.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638558.png => en-us_image_0000002218659866.png} (100%) rename docs/cce/umn/{en-us_image_0000002065479422.png => en-us_image_0000002218659906.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480278.png => en-us_image_0000002218659930.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480330.png => en-us_image_0000002218659938.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597289.png => en-us_image_0000002218660018.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218660022.png rename docs/cce/umn/{en-us_image_0000002101678833.png => en-us_image_0000002218660194.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480470.png => en-us_image_0000002218660226.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597409.png => en-us_image_0000002218660238.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678937.png => en-us_image_0000002218660286.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480554.png => en-us_image_0000002218660294.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480558.png => en-us_image_0000002218660298.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218660366.png rename docs/cce/umn/{en-us_image_0000002065480618.png => en-us_image_0000002218660418.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638938.png => en-us_image_0000002218660430.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638946.png => en-us_image_0000002218660438.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218660466.png create mode 100644 docs/cce/umn/en-us_image_0000002218660474.png create mode 100644 docs/cce/umn/en-us_image_0000002218660478.png rename docs/cce/umn/{en-us_image_0000002101597485.png => en-us_image_0000002218660486.png} (100%) rename docs/cce/umn/{en-us_image_0000002101679081.png => en-us_image_0000002218660514.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480610.png => en-us_image_0000002218660566.png} (100%) rename docs/cce/umn/{en-us_image_0000002101679273.png => en-us_image_0000002218660654.png} (100%) rename docs/cce/umn/{en-us_image_0000002101679233.png => en-us_image_0000002218660706.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597757.png => en-us_image_0000002218660710.png} (100%) rename docs/cce/umn/{en-us_image_0000002065479386.png => en-us_image_0000002218660718.png} (100%) rename docs/cce/umn/{en-us_image_0000002065639282.png => en-us_image_0000002218660734.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218660782.png rename docs/cce/umn/{en-us_image_0000002065480762.png => en-us_image_0000002218660810.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218817314.png create mode 100644 docs/cce/umn/en-us_image_0000002218817326.png rename docs/cce/umn/{en-us_image_0000002065478702.png => en-us_image_0000002218818034.png} (100%) rename docs/cce/umn/{en-us_image_0000002065478822.png => en-us_image_0000002218818126.png} (100%) rename docs/cce/umn/{en-us_image_0000002101595737.png => en-us_image_0000002218818142.png} (100%) rename docs/cce/umn/{en-us_image_0000002065478854.png => en-us_image_0000002218818146.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637194.png => en-us_image_0000002218818158.png} (100%) rename docs/cce/umn/{en-us_image_0000002101677309.png => en-us_image_0000002218818218.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218818222.png rename docs/cce/umn/{en-us_image_0000002101677301.png => en-us_image_0000002218818234.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637258.png => en-us_image_0000002218818246.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637342.png => en-us_image_0000002218818310.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218818366.png create mode 100644 docs/cce/umn/en-us_image_0000002218818382.png create mode 100644 docs/cce/umn/en-us_image_0000002218818386.png create mode 100644 docs/cce/umn/en-us_image_0000002218818398.png rename docs/cce/umn/{en-us_image_0000002101595761.jpg => en-us_image_0000002218818442.jpg} (100%) rename docs/cce/umn/{en-us_image_0000002101677605.png => en-us_image_0000002218818446.png} (100%) rename docs/cce/umn/{en-us_image_0000002065479222.png => en-us_image_0000002218818458.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218818490.png rename docs/cce/umn/{en-us_image_0000002101677281.png => en-us_image_0000002218818530.png} (100%) rename docs/cce/umn/{en-us_image_0000002065479338.png => en-us_image_0000002218818546.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480858.png => en-us_image_0000002218818590.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637794.png => en-us_image_0000002218818630.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638086.png => en-us_image_0000002218818686.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678157.png => en-us_image_0000002218818734.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638098.png => en-us_image_0000002218818738.png} (100%) rename docs/cce/umn/{en-us_image_0000002065478898.jpg => en-us_image_0000002218818770.jpg} (100%) rename docs/cce/umn/{en-us_image_0000002065637422.png => en-us_image_0000002218818914.png} (100%) rename docs/cce/umn/{en-us_image_0000002101677497.png => en-us_image_0000002218818934.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637450.png => en-us_image_0000002218818946.png} (100%) rename docs/cce/umn/{en-us_image_0000002101677421.png => en-us_image_0000002218818954.png} (100%) rename docs/cce/umn/{en-us_image_0000002065479622.png => en-us_image_0000002218818982.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637598.png => en-us_image_0000002218818994.png} (100%) rename docs/cce/umn/{en-us_image_0000002101596229.png => en-us_image_0000002218819094.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218819126.png create mode 100644 docs/cce/umn/en-us_image_0000002218819222.png rename docs/cce/umn/{en-us_image_0000002101596489.png => en-us_image_0000002218819242.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678517.png => en-us_image_0000002218819650.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678573.png => en-us_image_0000002218819718.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638630.png => en-us_image_0000002218819774.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480222.png => en-us_image_0000002218819786.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597285.png => en-us_image_0000002218819838.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218819854.png create mode 100644 docs/cce/umn/en-us_image_0000002218819982.png rename docs/cce/umn/{en-us_image_0000002065638766.png => en-us_image_0000002218820018.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638678.png => en-us_image_0000002218820034.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638794.png => en-us_image_0000002218820038.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638906.png => en-us_image_0000002218820158.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218820166.png create mode 100644 docs/cce/umn/en-us_image_0000002218820214.png create mode 100644 docs/cce/umn/en-us_image_0000002218820226.png create mode 100644 docs/cce/umn/en-us_image_0000002218820242.png rename docs/cce/umn/{en-us_image_0000002065639038.png => en-us_image_0000002218820382.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678997.png => en-us_image_0000002218820402.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638950.png => en-us_image_0000002218820410.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218820434.png rename docs/cce/umn/{en-us_image_0000002065639042.png => en-us_image_0000002218820458.png} (100%) rename docs/cce/umn/{en-us_image_0000002065639162.png => en-us_image_0000002218820526.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597765.png => en-us_image_0000002218820570.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218820586.png create mode 100644 docs/cce/umn/en-us_image_0000002218820614.png rename docs/cce/umn/{en-us_image_0000002065480750.png => en-us_image_0000002218820646.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597653.png => en-us_image_0000002218820650.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002218820658.png create mode 100644 docs/cce/umn/en-us_image_0000002218820674.png create mode 100644 docs/cce/umn/en-us_image_0000002218820702.png rename docs/cce/umn/{en-us_image_0000002065477978.png => en-us_image_0000002253617217.png} (100%) rename docs/cce/umn/{en-us_image_0000002101595573.png => en-us_image_0000002253617941.png} (100%) rename docs/cce/umn/{en-us_image_0000002101677269.png => en-us_image_0000002253618117.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637238.png => en-us_image_0000002253618121.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637250.png => en-us_image_0000002253618133.png} (100%) rename docs/cce/umn/{en-us_image_0000002065478942.png => en-us_image_0000002253618137.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253618289.png rename docs/cce/umn/{en-us_image_0000002065479186.png => en-us_image_0000002253618329.png} (100%) rename docs/cce/umn/{en-us_image_0000002065479210.png => en-us_image_0000002253618345.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637722.png => en-us_image_0000002253618457.png} (100%) rename docs/cce/umn/{en-us_image_0000002101596289.png => en-us_image_0000002253618517.png} (100%) rename docs/cce/umn/{en-us_image_0000002101596357.png => en-us_image_0000002253618529.png} (100%) rename docs/cce/umn/{en-us_image_0000002101596637.png => en-us_image_0000002253618549.png} (100%) rename docs/cce/umn/{en-us_image_0000002101677397.png => en-us_image_0000002253618569.png} (100%) rename docs/cce/umn/{en-us_image_0000002101596653.png => en-us_image_0000002253618605.png} (100%) rename docs/cce/umn/{en-us_image_0000002101596525.png => en-us_image_0000002253618649.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253618813.png rename docs/cce/umn/{en-us_image_0000002101595969.png => en-us_image_0000002253618817.png} (100%) rename docs/cce/umn/{en-us_image_0000002101595997.png => en-us_image_0000002253618837.png} (100%) rename docs/cce/umn/{en-us_image_0000002101677513.png => en-us_image_0000002253618841.png} (100%) rename docs/cce/umn/{en-us_image_0000002065479598.png => en-us_image_0000002253618845.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637590.png => en-us_image_0000002253618897.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597161.png => en-us_image_0000002253619005.png} (100%) rename docs/cce/umn/{en-us_image_0000002101596349.png => en-us_image_0000002253619089.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253619117.png rename docs/cce/umn/{en-us_image_0000002065479290.png => en-us_image_0000002253619133.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597009.png => en-us_image_0000002253619517.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638446.png => en-us_image_0000002253619521.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597069.png => en-us_image_0000002253619569.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480154.png => en-us_image_0000002253619601.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597065.png => en-us_image_0000002253619605.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678569.png => en-us_image_0000002253619613.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638526.png => en-us_image_0000002253619621.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638606.png => en-us_image_0000002253619653.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480234.png => en-us_image_0000002253619701.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253619705.png rename docs/cce/umn/{en-us_image_0000002065480238.png => en-us_image_0000002253619713.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678765.png => en-us_image_0000002253619725.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678773.png => en-us_image_0000002253619737.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597253.png => en-us_image_0000002253619765.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253619901.png rename docs/cce/umn/{en-us_image_0000002101597333.png => en-us_image_0000002253619909.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597349.png => en-us_image_0000002253619937.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597397.png => en-us_image_0000002253619977.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678893.png => en-us_image_0000002253619981.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638710.png => en-us_image_0000002253620001.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480366.png => en-us_image_0000002253620029.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638886.png => en-us_image_0000002253620033.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678953.png => en-us_image_0000002253620049.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597461.png => en-us_image_0000002253620097.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678961.png => en-us_image_0000002253620189.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253620209.png create mode 100644 docs/cce/umn/en-us_image_0000002253620213.png rename docs/cce/umn/{en-us_image_0000002101597577.png => en-us_image_0000002253620305.png} (100%) rename docs/cce/umn/{en-us_image_0000002101679217.png => en-us_image_0000002253620349.png} (100%) rename docs/cce/umn/{en-us_image_0000002101679261.png => en-us_image_0000002253620361.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597689.png => en-us_image_0000002253620365.png} (100%) rename docs/cce/umn/{en-us_image_0000002065639238.png => en-us_image_0000002253620397.png} (100%) rename docs/cce/umn/{en-us_image_0000002101679277.png => en-us_image_0000002253620425.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480670.png => en-us_image_0000002253620433.png} (100%) rename docs/cce/umn/{en-us_image_0000002101679237.png => en-us_image_0000002253620437.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597825.png => en-us_image_0000002253620477.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480794.png => en-us_image_0000002253620497.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597657.png => en-us_image_0000002253620533.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253620537.png rename docs/cce/umn/{en-us_image_0000002101597665.png => en-us_image_0000002253620541.png} (100%) rename docs/cce/umn/{en-us_image_0000002065639258.png => en-us_image_0000002253620561.png} (100%) rename docs/cce/umn/{en-us_image_0000002101676373.png => en-us_image_0000002253777129.png} (100%) rename docs/cce/umn/{en-us_image_0000002101594929.png => en-us_image_0000002253777197.png} (100%) rename docs/cce/umn/{en-us_image_0000002101594945.png => en-us_image_0000002253777225.png} (100%) rename docs/cce/umn/{en-us_image_0000002101595713.png => en-us_image_0000002253777937.png} (100%) rename docs/cce/umn/{en-us_image_0000002101677221.png => en-us_image_0000002253777941.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637178.png => en-us_image_0000002253777953.png} (100%) rename docs/cce/umn/{en-us_image_0000002101595789.png => en-us_image_0000002253778017.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637246.png => en-us_image_0000002253778021.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253778205.png rename docs/cce/umn/{en-us_image_0000002101677557.png => en-us_image_0000002253778225.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253778245.png rename docs/cce/umn/{en-us_image_0000002101596097.png => en-us_image_0000002253778253.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253778265.png rename docs/cce/umn/{en-us_image_0000002065479218.png => en-us_image_0000002253778269.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253778301.png rename docs/cce/umn/{en-us_image_0000002101677757.png => en-us_image_0000002253778377.png} (100%) rename docs/cce/umn/{en-us_image_0000002101596297.png => en-us_image_0000002253778437.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637318.png => en-us_image_0000002253778449.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637802.png => en-us_image_0000002253778453.png} (100%) rename docs/cce/umn/{en-us_image_0000002065479742.png => en-us_image_0000002253778485.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678145.png => en-us_image_0000002253778493.png} (100%) rename docs/cce/umn/{en-us_image_0000002101596649.png => en-us_image_0000002253778497.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637370.png => en-us_image_0000002253778541.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253778733.png rename docs/cce/umn/{en-us_image_0000002065479090.png => en-us_image_0000002253778737.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637606.png => en-us_image_0000002253778797.png} (100%) rename docs/cce/umn/{en-us_image_0000002101596161.png => en-us_image_0000002253778813.png} (100%) rename docs/cce/umn/{en-us_image_0000002101677721.png => en-us_image_0000002253778853.png} (100%) rename docs/cce/umn/{en-us_image_0000002101677725.png => en-us_image_0000002253778885.png} (100%) rename docs/cce/umn/{en-us_image_0000002101596309.png => en-us_image_0000002253778901.png} (100%) rename docs/cce/umn/{en-us_image_0000002065479494.png => en-us_image_0000002253778965.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253779013.png create mode 100644 docs/cce/umn/en-us_image_0000002253779017.png rename docs/cce/umn/{en-us_image_0000002101678473.png => en-us_image_0000002253779397.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638502.png => en-us_image_0000002253779469.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480162.png => en-us_image_0000002253779473.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597121.png => en-us_image_0000002253779501.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597061.png => en-us_image_0000002253779505.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638574.png => en-us_image_0000002253779605.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638582.png => en-us_image_0000002253779617.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480242.png => en-us_image_0000002253779625.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597157.png => en-us_image_0000002253779633.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253779657.png rename docs/cce/umn/{en-us_image_0000002065480398.png => en-us_image_0000002253779681.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678805.jpg => en-us_image_0000002253779773.jpg} (100%) rename docs/cce/umn/{en-us_image_0000002101678825.png => en-us_image_0000002253779809.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678821.png => en-us_image_0000002253779825.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002253779849.png create mode 100644 docs/cce/umn/en-us_image_0000002253779921.png rename docs/cce/umn/{en-us_image_0000002065638890.png => en-us_image_0000002253779941.png} (100%) rename docs/cce/umn/{en-us_image_0000002065638898.png => en-us_image_0000002253779949.png} (100%) rename docs/cce/umn/{en-us_image_0000002101678941.png => en-us_image_0000002253779993.png} (100%) rename docs/cce/umn/{en-us_image_0000002101679001.png => en-us_image_0000002253780085.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480682.png => en-us_image_0000002253780093.png} (100%) rename docs/cce/umn/{en-us_image_0000002101679193.png => en-us_image_0000002253780145.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597649.png => en-us_image_0000002253780209.png} (100%) rename docs/cce/umn/{en-us_image_0000002065637758.png => en-us_image_0000002253780305.png} (100%) rename docs/cce/umn/{en-us_image_0000002065480658.png => en-us_image_0000002253780329.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597645.png => en-us_image_0000002253780361.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597817.png => en-us_image_0000002253780381.png} (100%) rename docs/cce/umn/{en-us_image_0000002101597693.png => en-us_image_0000002253780433.png} (100%) rename docs/cce/umn/{en-us_image_0000002101679209.png => en-us_image_0000002253780457.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002254877052.png create mode 100644 docs/cce/umn/en-us_image_0000002254877428.png create mode 100644 docs/cce/umn/en-us_image_0000002254879860.png create mode 100644 docs/cce/umn/en-us_image_0000002254895070.png create mode 100644 docs/cce/umn/en-us_image_0000002254895574.png create mode 100644 docs/cce/umn/en-us_image_0000002254895914.png create mode 100644 docs/cce/umn/en-us_image_0000002254978558.png create mode 100644 docs/cce/umn/en-us_image_0000002255002834.png create mode 100644 docs/cce/umn/en-us_image_0000002274473989.png create mode 100644 docs/cce/umn/en-us_image_0000002289476265.png create mode 100644 docs/cce/umn/en-us_image_0000002289589649.png create mode 100644 docs/cce/umn/en-us_image_0000002289592109.png rename docs/cce/umn/{en-us_image_0000002065638074.png => en-us_image_0261818867.png} (100%) diff --git a/docs/cce/umn/ALL_META.TXT.json b/docs/cce/umn/ALL_META.TXT.json index 1d24509ed..2270b6fdc 100644 --- a/docs/cce/umn/ALL_META.TXT.json +++ b/docs/cce/umn/ALL_META.TXT.json @@ -27,14 +27,14 @@ "node_id":"cce_productdesc_0001.xml", "product_code":"cce", "code":"2", - "des":"Cloud Container Engine (CCE) is a Kubernetes cluster hosting service for enterprises. It manages the enter lifecycle of containerized applications and delivers scalable, ", + "des":"Cloud Container Engine (CCE) is a Kubernetes cluster hosting service for enterprises. It manages the entire lifecycle of containerized applications and delivers scalable,", "doc_type":"usermanual2", "kw":"What Is CCE?,Service Overview,User Guide", "search_title":"", "metedata":[ { - "documenttype":"usermanual", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"What Is CCE?", @@ -51,8 +51,8 @@ "search_title":"", "metedata":[ { - "documenttype":"usermanual", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Product Advantages", @@ -69,8 +69,8 @@ "search_title":"", "metedata":[ { - "documenttype":"usermanual", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Application Scenarios", @@ -87,8 +87,8 @@ "search_title":"", "metedata":[ { - "documenttype":"usermanual", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Containerized Application Management", @@ -105,8 +105,8 @@ "search_title":"", "metedata":[ { - "documenttype":"usermanual", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Auto Scaling in Seconds", @@ -123,8 +123,8 @@ "search_title":"", "metedata":[ { - "documenttype":"usermanual", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"DevOps and CI/CD", @@ -135,14 +135,14 @@ "node_id":"cce_productdesc_0018.xml", "product_code":"cce", "code":"8", - "des":"Multi-cloud deployment and disaster recoveryRunning apps in containers on different clouds can ensure high availability. When a cloud is down, other clouds respond and se", + "des":"Multi-cloud deployment and disaster recoveryTo ensure high service availability, services need to be deployed on container services of multiple clouds. When a cloud is fa", "doc_type":"usermanual2", "kw":"Hybrid Cloud,Application Scenarios,User Guide", "search_title":"", "metedata":[ { - "documenttype":"usermanual", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Hybrid Cloud", @@ -159,8 +159,8 @@ "search_title":"", "metedata":[ { - "documenttype":"usermanual", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Permissions", @@ -177,8 +177,8 @@ "search_title":"", "metedata":[ { - "documenttype":"usermanual", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Notes and Constraints", @@ -195,8 +195,8 @@ "search_title":"", "metedata":[ { - "documenttype":"usermanual", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Related Services", @@ -213,8 +213,8 @@ "search_title":"", "metedata":[ { - "documenttype":"usermanual", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Regions and AZs", @@ -240,30 +240,11 @@ "title":"Product Bulletin", "githuburl":"" }, - { - "uri":"cce_bulletin_0033.html", - "node_id":"cce_bulletin_0033.xml", - "product_code":"cce", - "code":"14", - "des":"CCE provides highly scalable, high-performance, enterprise-class Kubernetes clusters. This section describes the Kubernetes version policy of CCE clusters.The CCE console", - "doc_type":"usermanual2", - "kw":"Kubernetes Version Policy,Product Bulletin,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"cce", - "opensource":"true", - "documenttype":"usermanual" - } - ], - "title":"Kubernetes Version Policy", - "githuburl":"" - }, { "uri":"cce_bulletin_0098.html", "node_id":"cce_bulletin_0098.xml", "product_code":"cce", - "code":"15", + "code":"14", "des":"Released: Oct 23, 2024CentOS has reached its end of maintenance (EOM) date, which means it will no longer receive updates or support. The CentOS public images on CCE are ", "doc_type":"usermanual2", "kw":"EOM of CentOS,Product Bulletin,User Guide", @@ -280,7 +261,7 @@ "uri":"cce_bulletin_0169.html", "node_id":"cce_bulletin_0169.xml", "product_code":"cce", - "code":"16", + "code":"15", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Security Vulnerability Responses", @@ -300,7 +281,7 @@ "uri":"cce_bulletin_0011.html", "node_id":"cce_bulletin_0011.xml", "product_code":"cce", - "code":"17", + "code":"16", "des":"High-risk vulnerabilities:CCE fixes vulnerabilities as soon as possible after the Kubernetes community detects them and releases fixing solutions. The fixing policies are", "doc_type":"usermanual2", "kw":"Vulnerability Fixing Policies,Security Vulnerability Responses,User Guide", @@ -319,7 +300,7 @@ "uri":"CVE-2021-4034.html", "node_id":"cve-2021-4034.xml", "product_code":"cce", - "code":"18", + "code":"17", "des":"Recently, a security research team disclosed a privilege escalation vulnerability (CVE-2021-4034, also dubbed PwnKit) in PolKit's pkexec. Unprivileged users can gain full", "doc_type":"usermanual2", "kw":"Linux Polkit Privilege Escalation Vulnerability (CVE-2021-4034),Security Vulnerability Responses,Use", @@ -339,7 +320,7 @@ "uri":"cce_bulletin_0206.html", "node_id":"cce_bulletin_0206.xml", "product_code":"cce", - "code":"19", + "code":"18", "des":"The Linux Kernel SACK vulnerabilities have been fixed. This section describes the solution to these vulnerabilities.On June 18, 2019, Red Hat released a security notice, ", "doc_type":"usermanual2", "kw":"Notice on Fixing Linux Kernel SACK Vulnerabilities,Security Vulnerability Responses,User Guide", @@ -359,7 +340,7 @@ "uri":"cce_qs_0000.html", "node_id":"cce_qs_0000.xml", "product_code":"cce", - "code":"20", + "code":"19", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Getting Started", @@ -379,15 +360,15 @@ "uri":"cce_qs_0001.html", "node_id":"cce_qs_0001.xml", "product_code":"cce", - "code":"21", + "code":"20", "des":"This section describes how to use Cloud Container Engine (CCE) and provides frequently asked questions (FAQs) to help you quickly get started with CCE.Complete the follow", "doc_type":"usermanual2", "kw":"Introduction,Getting Started,User Guide", "search_title":"", "metedata":[ { - "documenttype":"usermanual2", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Introduction", @@ -397,15 +378,15 @@ "uri":"cce_qs_0006.html", "node_id":"cce_qs_0006.xml", "product_code":"cce", - "code":"22", + "code":"21", "des":"Before using CCE, make the following preparations:Creating an IAM userObtaining Resource Permissions(Optional) Creating a VPC(Optional) Creating a Key PairIf you want to ", "doc_type":"usermanual2", "kw":"VPC,Preparations,Getting Started,User Guide", "search_title":"", "metedata":[ { - "documenttype":"usermanual2", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Preparations", @@ -415,15 +396,15 @@ "uri":"cce_qs_0008.html", "node_id":"cce_qs_0008.xml", "product_code":"cce", - "code":"23", - "des":"This section describes how to quickly create a CCE cluster. In this example, the default or simple configurations are in use.If you have no clusters, click Create CCE Sta", + "code":"22", + "des":"This section describes how to quickly create a CCE cluster. In this example, the default or simple configurations are in use.If you have no clusters, click Create Cluster", "doc_type":"usermanual2", "kw":"Creating a Kubernetes Cluster,Getting Started,User Guide", "search_title":"", "metedata":[ { - "documenttype":"usermanual2", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Creating a Kubernetes Cluster", @@ -433,33 +414,33 @@ "uri":"cce_qs_0003.html", "node_id":"cce_qs_0003.xml", "product_code":"cce", - "code":"24", + "code":"23", "des":"You can use images to quickly create a single-pod workload that can be accessed from public networks. This section describes how to use CCE to quickly deploy an Nginx app", "doc_type":"usermanual2", - "kw":"Creating a Deployment (Nginx),Getting Started,User Guide", + "kw":"Deploying a Deployment (Nginx),Getting Started,User Guide", "search_title":"", "metedata":[ { - "documenttype":"usermanual2", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], - "title":"Creating a Deployment (Nginx)", + "title":"Deploying a Deployment (Nginx)", "githuburl":"" }, { "uri":"cce_qs_0007.html", "node_id":"cce_qs_0007.xml", "product_code":"cce", - "code":"25", + "code":"24", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Deploying WordPress and MySQL That Depend on Each Other", "search_title":"", "metedata":[ { - "documenttype":"usermanual2", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Deploying WordPress and MySQL That Depend on Each Other", @@ -469,15 +450,15 @@ "uri":"cce_qs_0009.html", "node_id":"cce_qs_0009.xml", "product_code":"cce", - "code":"26", + "code":"25", "des":"WordPress was originally a blog platform based on PHP and MySQL. It is gradually evolved into a content management system. You can set up your own blog website on any ser", "doc_type":"usermanual2", "kw":"Overview,Deploying WordPress and MySQL That Depend on Each Other,User Guide", "search_title":"", "metedata":[ { - "documenttype":"usermanual2", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], "title":"Overview", @@ -487,46 +468,46 @@ "uri":"cce_qs_0004.html", "node_id":"cce_qs_0004.xml", "product_code":"cce", - "code":"27", + "code":"26", "des":"WordPress must be used together with MySQL. WordPress runs the content management program while MySQL serves as a database to store data.You have created a CCE cluster th", "doc_type":"usermanual2", - "kw":"Creating a MySQL Workload,Deploying WordPress and MySQL That Depend on Each Other,User Guide", + "kw":"Step 1: Deploying MySQL,Deploying WordPress and MySQL That Depend on Each Other,User Guide", "search_title":"", "metedata":[ { - "documenttype":"usermanual2", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], - "title":"Creating a MySQL Workload", + "title":"Step 1: Deploying MySQL", "githuburl":"" }, { "uri":"cce_qs_0005.html", "node_id":"cce_qs_0005.xml", "product_code":"cce", - "code":"28", + "code":"27", "des":"WordPress was originally a blog platform based on PHP and MySQL. It is gradually evolved into a content management system. You can set up your own blog website on any ser", "doc_type":"usermanual2", - "kw":"Creating a WordPress Workload,Deploying WordPress and MySQL That Depend on Each Other,User Guide", + "kw":"Step 2: Deploying WordPress,Deploying WordPress and MySQL That Depend on Each Other,User Guide", "search_title":"", "metedata":[ { - "documenttype":"usermanual2", - "prodname":"cce" + "prodname":"cce", + "documenttype":"usermanual" } ], - "title":"Creating a WordPress Workload", + "title":"Step 2: Deploying WordPress", "githuburl":"" }, { "uri":"cce_10_0054.html", "node_id":"cce_10_0054.xml", "product_code":"cce", - "code":"29", + "code":"28", "des":"During service deployment or running, you may trigger high-risk operations at different levels, causing service faults or interruption. To help you better estimate and av", "doc_type":"usermanual2", - "kw":"High-Risk Operations,User Guide", + "kw":"network-attachment-definitions,High-Risk Operations,User Guide", "search_title":"", "metedata":[ { @@ -541,7 +522,7 @@ "uri":"cce_10_0091.html", "node_id":"cce_10_0091.xml", "product_code":"cce", - "code":"30", + "code":"29", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Clusters", @@ -556,13 +537,13 @@ "githuburl":"" }, { - "uri":"cce_10_0002.html", - "node_id":"cce_10_0002.xml", + "uri":"cce_10_0430.html", + "node_id":"cce_10_0430.xml", "product_code":"cce", - "code":"31", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "code":"30", + "des":"Cloud Container Engine (CCE) is a Kubernetes cluster hosting service for enterprises. It manages the entire lifecycle of containerized applications and delivers scalable,", "doc_type":"usermanual2", - "kw":"Cluster Overview", + "kw":"Number of Master Nodes in a Cluster,Cluster Overview,Clusters,User Guide", "search_title":"", "metedata":[ { @@ -574,13 +555,13 @@ "githuburl":"" }, { - "uri":"cce_10_0430.html", - "node_id":"cce_10_0430.xml", + "uri":"cce_10_0002.html", + "node_id":"cce_10_0002.xml", "product_code":"cce", - "code":"32", - "des":"Kubernetes is an open source container orchestration engine for automating deployment, scaling, and management of containerized applications.For developers, Kubernetes is", + "code":"31", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", - "kw":"Master Nodes,Basic Cluster Information,Cluster Overview,User Guide", + "kw":"Cluster Version Release Notes", "search_title":"", "metedata":[ { @@ -588,14 +569,14 @@ "documenttype":"usermanual" } ], - "title":"Basic Cluster Information", + "title":"Cluster Version Release Notes", "githuburl":"" }, { "uri":"cce_10_0068.html", "node_id":"cce_10_0068.xml", "product_code":"cce", - "code":"33", + "code":"32", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Kubernetes Version Release Notes", @@ -609,6 +590,24 @@ "title":"Kubernetes Version Release Notes", "githuburl":"" }, + { + "uri":"cce_bulletin_0099.html", + "node_id":"cce_bulletin_0099.xml", + "product_code":"cce", + "code":"33", + "des":"CCE allows you to create Kubernetes clusters 1.31. This section describes the changes made in Kubernetes 1.31.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku", + "doc_type":"usermanual2", + "kw":"Kubernetes 1.31 Release Notes,Kubernetes Version Release Notes,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Kubernetes 1.31 Release Notes", + "githuburl":"" + }, { "uri":"cce_bulletin_0095.html", "node_id":"cce_bulletin_0095.xml", @@ -668,7 +667,7 @@ "node_id":"cce_bulletin_0059.xml", "product_code":"cce", "code":"37", - "des":"CCE allows you to create clusters of Kubernetes 1.27. This section describes the changes made in Kubernetes 1.27 compared with Kubernetes 1.25.New FeaturesDeprecations an", + "des":"CCE allows you to create Kubernetes clusters 1.27. This section describes the changes made in Kubernetes 1.27 compared with Kubernetes 1.25.New FeaturesDeprecations and R", "doc_type":"usermanual2", "kw":"Kubernetes 1.27 Release Notes,Kubernetes Version Release Notes,User Guide", "search_title":"", @@ -704,7 +703,7 @@ "node_id":"cce_bulletin_0027.xml", "product_code":"cce", "code":"39", - "des":"This section describes the updates in CCE Kubernetes 1.23.Kubernetes 1.23 Release NotesFlexVolume is deprecated. Use CSI.HorizontalPodAutoscaler v2 is promoted to GA, and", + "des":"This section describes the updates in CCE Kubernetes 1.23.Kubernetes v1.23 Release NotesFlexVolume is deprecated. Use CSI.HorizontalPodAutoscaler v2 is promoted to GA, an", "doc_type":"usermanual2", "kw":"Kubernetes 1.23 Release Notes,Kubernetes Version Release Notes,User Guide", "search_title":"", @@ -722,7 +721,7 @@ "node_id":"cce_bulletin_0026.xml", "product_code":"cce", "code":"40", - "des":"This section describes the updates in CCE Kubernetes 1.21.Kubernetes 1.21 Release NotesCronJob is now in the stable state, and the version number changes to batch/v1.The ", + "des":"This section describes the updates in CCE Kubernetes 1.21.Kubernetes v1.21 Release NotesCronJob is now in the stable state, and the version number changes to batch/v1.The", "doc_type":"usermanual2", "kw":"Kubernetes 1.21 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide", "search_title":"", @@ -776,9 +775,9 @@ "node_id":"cce_10_0405.xml", "product_code":"cce", "code":"43", - "des":"dockershim has been removed since Kubernetes v1.24, and Docker is not supported in v1.24 and later versions by default. Use containerd.All nodes in the CCE clusters of ve", + "des":"In CCE clusters of v1.25, containerd is the default runtime for nodes, except for nodes running EulerOS 2.5. In addition, clusters of v1.25 or later no longer support Eul", "doc_type":"usermanual2", - "kw":"Patch Version Release Notes,Cluster Overview,User Guide", + "kw":"Patch Version Release Notes,Cluster Version Release Notes,User Guide", "search_title":"", "metedata":[ { @@ -884,9 +883,9 @@ "node_id":"cce_10_0107.xml", "product_code":"cce", "code":"49", - "des":"This section uses a CCE standard cluster as an example to describe how to access a CCE cluster using kubectl.When you access a cluster using kubectl, CCE uses kubeconfig ", + "des":"kubectl is a command-line tool provided by Kubernetes, enabling you to manage cluster resources, view cluster status, deploy applications, and debug issues through the CL", "doc_type":"usermanual2", - "kw":"kubectl,Intranet access,Two-Way Authentication for Domain Names,Error from server Forbidden,The conn", + "kw":"Intranet access,Internet access,kubectl,intranet access,Internet access,Two-Way Authentication for D", "search_title":"", "metedata":[ { @@ -894,7 +893,7 @@ "documenttype":"usermanual" } ], - "title":"Connecting to a Cluster Using kubectl", + "title":"Accessing a Cluster Using kubectl", "githuburl":"" }, { @@ -902,7 +901,7 @@ "node_id":"cce_10_0175.xml", "product_code":"cce", "code":"50", - "des":"This section describes how to obtain the cluster certificate from the console and use it to access Kubernetes clusters.The downloaded certificate contains three files: cl", + "des":"X.509 certificates are essential for verifying identities and encrypting communication within CCE clusters. These certificates enable authorized clients to access target ", "doc_type":"usermanual2", "kw":"X.509 certificate,Accessing a Cluster Using an X.509 Certificate,Connecting to a Cluster,User Guide", "search_title":"", @@ -920,7 +919,7 @@ "node_id":"cce_10_0367.xml", "product_code":"cce", "code":"51", - "des":"Subject Alternative Name (SAN) allows multiple values (including IP addresses, domain names, and so on) to be associated with certificates. A SAN is usually used by the c", + "des":"Subject Alternative Name (SAN) enables certificates to be associated with multiple values, including IP addresses and domain names. A SAN is usually used by the client to", "doc_type":"usermanual2", "kw":"SAN,X.509 certificate,Accessing a Cluster Using a Custom Domain Name,Connecting to a Cluster,User Gu", "search_title":"", @@ -956,7 +955,7 @@ "node_id":"cce_10_0744.xml", "product_code":"cce", "code":"53", - "des":"In multi-tenant scenarios, CCE generates a credential (kubeconfig or X.509 certificate) for you to access the corresponding cluster. The credential contains user identity", + "des":"In multi-tenant scenarios, CCE generates a unique credential (such as a kubeconfig file or an X.509 certificate) for each user to access their designated cluster. These c", "doc_type":"usermanual2", "kw":"Revoking a Cluster Access Credential,Connecting to a Cluster,User Guide", "search_title":"", @@ -992,9 +991,9 @@ "node_id":"cce_10_0213.xml", "product_code":"cce", "code":"55", - "des":"CCE allows you to manage cluster parameters, through which you can let core components work under your requirements.kube-apiserverkube-controller-managerkube-scheduler", + "des":"Cluster configuration parameters are underlying rules that define node behavior, resource allocation, communication rules, and scaling policies in a distributed system. T", "doc_type":"usermanual2", - "kw":"cluster parameters,kube-apiserver,kube-controller-manager,Modifying Cluster Configurations,Managing ", + "kw":"Cluster configuration parameters,cluster configuration parameters,Cluster configuration parameters,C", "search_title":"", "metedata":[ { @@ -1010,9 +1009,9 @@ "node_id":"cce_10_0602.xml", "product_code":"cce", "code":"56", - "des":"After overload control is enabled, the number of simultaneous requests is dynamically regulated according to the resource pressure on the master nodes. This ensures that ", + "des":"Cluster overload occurs when system load such as request volume or resource usage exceeds the system's processing capacity, leading to degraded performance or system fail", "doc_type":"usermanual2", - "kw":"overload control,Enabling Overload Control for a Cluster,Managing a Cluster,User Guide", + "kw":"Enabling Overload Control for a Cluster,Managing a Cluster,User Guide", "search_title":"", "metedata":[ { @@ -1028,9 +1027,9 @@ "node_id":"cce_10_0403.xml", "product_code":"cce", "code":"57", - "des":"CCE allows you to change the number of nodes managed in a cluster.A cluster that has only one master node supports fewer than 1000 worker nodes.The number of master nodes", + "des":"A cluster scale specifies the maximum number of nodes a cluster can manage. If the current cluster scale cannot meet your requirements, you can scale it out.A cluster tha", "doc_type":"usermanual2", - "kw":"Changing Cluster Scale,Managing a Cluster,User Guide", + "kw":"scale it out,Changing a Cluster Scale,Managing a Cluster,User Guide", "search_title":"", "metedata":[ { @@ -1038,7 +1037,7 @@ "documenttype":"usermanual" } ], - "title":"Changing Cluster Scale", + "title":"Changing a Cluster Scale", "githuburl":"" }, { @@ -1138,7 +1137,7 @@ "code":"63", "des":"CCE strictly complies with community consistency authentication. It releases three Kubernetes versions each year and offers a maintenance period of at least 24 months aft", "doc_type":"usermanual2", - "kw":"cluster upgrade process,Node Priority,In-place upgrade,Process and Method of Upgrading a Cluster,Upg", + "kw":"cluster upgrade process,Node Priority,In-place upgrade,Cluster Upgrade Overview,Upgrading a Cluster,", "search_title":"", "metedata":[ { @@ -1146,7 +1145,7 @@ "documenttype":"usermanual" } ], - "title":"Process and Method of Upgrading a Cluster", + "title":"Cluster Upgrade Overview", "githuburl":"" }, { @@ -1154,7 +1153,7 @@ "node_id":"cce_10_0302.xml", "product_code":"cce", "code":"64", - "des":"Before the upgrade, you can check whether your cluster can be upgraded and which versions are available on the CCE console. For details, see Process and Method of Upgradi", + "des":"Before the upgrade, you can check whether your cluster can be upgraded and which versions are available on the CCE console. For details, see Cluster Upgrade Overview.Befo", "doc_type":"usermanual2", "kw":"Deprecated APIs,Before You Start,Upgrading a Cluster,User Guide", "search_title":"", @@ -1460,7 +1459,7 @@ "node_id":"cce_10_0437.xml", "product_code":"cce", "code":"81", - "des":"Check whether the Protocol & Port of the worker node security groups is set to ICMP: All and whether the security group with the source IP address set to the master node ", + "des":"Check whether the Protocol & Port of the worker node security groups is set to ICMP: All and whether the security group rule with the source IP address set to the master ", "doc_type":"usermanual2", "kw":"Security Groups,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -1532,7 +1531,7 @@ "node_id":"cce_10_0442.xml", "product_code":"cce", "code":"85", - "des":"Check whether cce-agent on the current node is of the latest version.Scenario 1: The error message \"you cce-agent no update, please restart it\" is displayed.cce-agent doe", + "des":"Check whether cce-agent on the current node is of the latest version.Scenario 1: The error message \"you cce-agent no update, please restart it\" is displayed.This issue oc", "doc_type":"usermanual2", "kw":"CCE Agent Versions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -1640,7 +1639,7 @@ "node_id":"cce_10_0448.xml", "product_code":"cce", "code":"91", - "des":"Check whether the kubelet on the node is running properly.Scenario 1: The kubelet status is abnormal.If the kubelet malfunctions, the node is unavailable. Restore the nod", + "des":"Check whether the kubelet on the node is running properly.Scenario 1: The kubelet status is abnormal.If the kubelet malfunctions, the node will be unavailable. Restore th", "doc_type":"usermanual2", "kw":"kubelet,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -1712,7 +1711,7 @@ "node_id":"cce_10_0452.xml", "product_code":"cce", "code":"95", - "des":"Check and make sure that the master nodes in your cluster have more than 2 CPU cores.The number of CPU cores on the master nodes is 2, which may lead to a cluster upgrade", + "des":"Verify that the master nodes in your cluster have more than 2 CPU cores.The master nodes have only 2 CPU cores, which may lead to a cluster upgrade failure.Contact techni", "doc_type":"usermanual2", "kw":"Node CPU Cores,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -2252,9 +2251,9 @@ "node_id":"cce_10_0503.xml", "product_code":"cce", "code":"125", - "des":"The GPU add-on is involved in the upgrade, which may affect the GPU driver installation during the creation of a GPU node.The GPU add-on driver needs to be configured by ", + "des":"CCE AI Suite (NVIDIA GPU) is involved in the upgrade, which may affect the GPU driver installation during the creation of a GPU node.The driver of CCE AI Suite (NVIDIA GP", "doc_type":"usermanual2", - "kw":"GPU Add-on,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "kw":"CCE AI Suite (NVIDIA GPU),Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", "metedata":[ { @@ -2262,7 +2261,7 @@ "documenttype":"usermanual" } ], - "title":"GPU Add-on", + "title":"CCE AI Suite (NVIDIA GPU)", "githuburl":"" }, { @@ -2344,7 +2343,7 @@ "code":"130", "des":"Check item 1: Check whether there is an Nginx Ingress route whose ingress type is not specified (kubernetes.io/ingress.class: nginx is not added to annotations) in the cl", "doc_type":"usermanual2", - "kw":"nginx-ingress Upgrade,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "kw":"NGINX Ingress Controller,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", "metedata":[ { @@ -2352,7 +2351,7 @@ "documenttype":"usermanual" } ], - "title":"nginx-ingress Upgrade", + "title":"NGINX Ingress Controller", "githuburl":"" }, { @@ -2378,9 +2377,9 @@ "node_id":"cce_10_0511.xml", "product_code":"cce", "code":"132", - "des":"Check whether the configuration of the CCE AI Suite add-on in a cluster has been intrusively modified. If so, upgrading the cluster may fail.", + "des":"Check whether the configuration of CCE AI Suite (NVIDIA GPU) in a cluster has been intrusively modified. If so, upgrading the cluster may fail.", "doc_type":"usermanual2", - "kw":"Key GPU Add-on Parameters,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "kw":"Key CCE AI Suite (NVIDIA GPU) Parameters,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", "metedata":[ { @@ -2388,7 +2387,7 @@ "documenttype":"usermanual" } ], - "title":"Key GPU Add-on Parameters", + "title":"Key CCE AI Suite (NVIDIA GPU) Parameters", "githuburl":"" }, { @@ -2414,7 +2413,7 @@ "node_id":"cce_10_0513.xml", "product_code":"cce", "code":"134", - "des":"Check whether ELB listener access control has been configured for the Services in the current cluster using annotations.If so, check whether their configurations are corr", + "des":"Check whether ELB listener access control has been configured using annotations for the Services in the current cluster.If so, check whether their configurations are corr", "doc_type":"usermanual2", "kw":"ELB Listener Access Control,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -2540,7 +2539,7 @@ "node_id":"cce_10_0521.xml", "product_code":"cce", "code":"141", - "des":"Make sure that the GPU add-on and Ubuntu nodes are compatible before using them in a cluster. If the Ubuntu kernel is 5.15.0-113-generic, the driver of the GPU add-on mus", + "des":"Make sure that CCE AI Suite (NVIDIA GPU) and Ubuntu nodes are compatible before using them in a cluster. If the Ubuntu kernel is 5.15.0-113-generic, the driver of the GPU", "doc_type":"usermanual2", "kw":"Compatibility Between the Ubuntu Kernel and GPU Driver,Troubleshooting for Pre-upgrade Check Excepti", "search_title":"", @@ -2643,11 +2642,101 @@ "title":"Ingress and ELB Configuration Consistency", "githuburl":"" }, + { + "uri":"cce_10_0527.html", + "node_id":"cce_10_0527.xml", + "product_code":"cce", + "code":"147", + "des":"Check the network policy settings on the master nodes in your cluster. If any manual modifications have been made, they will be reset during the upgrade.Check whether net", + "doc_type":"usermanual2", + "kw":"Network Policies of Cluster Network Components,Troubleshooting for Pre-upgrade Check Exceptions,User", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Network Policies of Cluster Network Components", + "githuburl":"" + }, + { + "uri":"cce_10_0528.html", + "node_id":"cce_10_0528.xml", + "product_code":"cce", + "code":"148", + "des":"Check whether the nic-max-above-warm-target value configured for the network component of the current cluster exceeds the maximum value allowed.Determine the scope of imp", + "doc_type":"usermanual2", + "kw":"Cluster and Node Pool Configurations,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Cluster and Node Pool Configurations", + "githuburl":"" + }, + { + "uri":"cce_10_0529.html", + "node_id":"cce_10_0529.xml", + "product_code":"cce", + "code":"149", + "des":"Check whether the time zone of the master nodes matches the cluster's time zone. If they are different, the master nodes will be updated to match the cluster's time zone ", + "doc_type":"usermanual2", + "kw":"Time Zone of Master Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Time Zone of Master Nodes", + "githuburl":"" + }, + { + "uri":"cce_10_0530.html", + "node_id":"cce_10_0530.xml", + "product_code":"cce", + "code":"150", + "des":"Check whether the SNATIPRanges value has changed after the upgrade. This check is available only for CCE Turbo clusters.In a CCE Turbo cluster, the CIDR blocks in SNATIPR", + "doc_type":"usermanual2", + "kw":"SNATIPRanges,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"SNATIPRanges", + "githuburl":"" + }, + { + "uri":"cce_10_0531.html", + "node_id":"cce_10_0531.xml", + "product_code":"cce", + "code":"151", + "des":"Manual modifications to add-on configuration parameters (typically ConfigMaps), instead of modifications through the CCE console or APIs, may be overwritten after an upgr", + "doc_type":"usermanual2", + "kw":"Add-on Configuration Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Add-on Configuration Consistency", + "githuburl":"" + }, { "uri":"cce_10_0183.html", "node_id":"cce_10_0183.xml", "product_code":"cce", - "code":"147", + "code":"152", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Nodes", @@ -2665,7 +2754,7 @@ "uri":"cce_10_0180.html", "node_id":"cce_10_0180.xml", "product_code":"cce", - "code":"148", + "code":"153", "des":"A container cluster consists of a set of worker machines, called nodes, that run containerized applications. A node can be a virtual machine (VM) or a physical machine (P", "doc_type":"usermanual2", "kw":"paas,user group,Node Overview,Nodes,User Guide", @@ -2683,7 +2772,7 @@ "uri":"cce_10_0462.html", "node_id":"cce_10_0462.xml", "product_code":"cce", - "code":"149", + "code":"154", "des":"Container engines, one of the most important components of Kubernetes, manage the lifecycle of images and containers. The kubelet interacts with a container runtime throu", "doc_type":"usermanual2", "kw":"Container Engines,Nodes,User Guide", @@ -2701,7 +2790,7 @@ "uri":"cce_10_0476.html", "node_id":"cce_10_0476.xml", "product_code":"cce", - "code":"150", + "code":"155", "des":"This section describes the mappings between released cluster versions and OS versions.", "doc_type":"usermanual2", "kw":"Node OSs,Nodes,User Guide", @@ -2719,7 +2808,7 @@ "uri":"cce_10_0363.html", "node_id":"cce_10_0363.xml", "product_code":"cce", - "code":"151", + "code":"156", "des":"At least one cluster has been created.A key pair has been created for identity authentication upon remote node login.The DNS configuration of a subnet where a node is loc", "doc_type":"usermanual2", "kw":"Creating a Node,Nodes,User Guide", @@ -2737,7 +2826,7 @@ "uri":"cce_10_0198.html", "node_id":"cce_10_0198.xml", "product_code":"cce", - "code":"152", + "code":"157", "des":"In CCE, you can create a node (Creating a Node) or add existing nodes (ECSs) to your cluster for management.When accepting an ECS, you can reset the ECS OS to a standard ", "doc_type":"usermanual2", "kw":"Accepting Nodes for Management,Nodes,User Guide", @@ -2755,7 +2844,7 @@ "uri":"cce_10_0185.html", "node_id":"cce_10_0185.xml", "product_code":"cce", - "code":"153", + "code":"158", "des":"Before you log in to a node using SSH, ensure that the SSH port (22 by default) is enabled in the security group of the node.Before you log in to a node (an ECS) using SS", "doc_type":"usermanual2", "kw":"Logging In to a Node,Nodes,User Guide", @@ -2773,7 +2862,7 @@ "uri":"cce_10_0672.html", "node_id":"cce_10_0672.xml", "product_code":"cce", - "code":"154", + "code":"159", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"node labels", @@ -2791,7 +2880,7 @@ "uri":"cce_10_0004.html", "node_id":"cce_10_0004.xml", "product_code":"cce", - "code":"155", + "code":"160", "des":"You can add different labels to nodes and define different attributes for labels. By using these node labels, you can quickly understand the characteristics of each node.", "doc_type":"usermanual2", "kw":"node labels,Inherent Label of a Node,Managing Node Labels,Management Nodes,User Guide", @@ -2809,7 +2898,7 @@ "uri":"cce_10_0352.html", "node_id":"cce_10_0352.xml", "product_code":"cce", - "code":"156", + "code":"161", "des":"Taints enable a node to repel specific pods to prevent these pods from being scheduled to the node.On the CCE console, you can also batch manage nodes' taints.Enter the k", "doc_type":"usermanual2", "kw":"NoSchedule,PreferNoSchedule,NoExecute,System Taints,Managing Node Taints,Management Nodes,User Guide", @@ -2827,7 +2916,7 @@ "uri":"cce_10_0003.html", "node_id":"cce_10_0003.xml", "product_code":"cce", - "code":"157", + "code":"162", "des":"You can reset a node to modify the node configuration, such as the node OS and login mode.Resetting a node will reinstall the node OS and the Kubernetes software on the n", "doc_type":"usermanual2", "kw":"reset a node,Resetting a Node,Management Nodes,User Guide", @@ -2845,7 +2934,7 @@ "uri":"cce_10_0338.html", "node_id":"cce_10_0338.xml", "product_code":"cce", - "code":"158", + "code":"163", "des":"Removing a node from a cluster will re-install the node OS and clear CCE components on the node.Removing a node will not delete the server corresponding to the node. You ", "doc_type":"usermanual2", "kw":"Removing a Node,Management Nodes,User Guide", @@ -2863,7 +2952,7 @@ "uri":"cce_10_0184.html", "node_id":"cce_10_0184.xml", "product_code":"cce", - "code":"159", + "code":"164", "des":"Each node in a cluster is a cloud server or physical machine. After a cluster node is created, you can change the cloud server name or specifications as required. Modifyi", "doc_type":"usermanual2", "kw":"synchronize the ECS,Synchronizing the Data of Cloud Servers,Management Nodes,User Guide", @@ -2881,7 +2970,7 @@ "uri":"cce_10_0605.html", "node_id":"cce_10_0605.xml", "product_code":"cce", - "code":"160", + "code":"165", "des":"After you enable nodal drainage on the console, CCE configures the node to be non-schedulable and securely evicts all pods that comply with Rules for Draining Nodes on th", "doc_type":"usermanual2", "kw":"nodal drainage,nodal drainage,Draining a Node,Management Nodes,User Guide", @@ -2899,8 +2988,8 @@ "uri":"cce_10_0186.html", "node_id":"cce_10_0186.xml", "product_code":"cce", - "code":"161", - "des":"You can delete a pay-per-use node that is not needed from the node list.Deleting or unsubscribing from a node in a CCE cluster will release the node and services running ", + "code":"166", + "des":"If a node is no longer needed, delete it from the node list on the CCE console if the node is billed on a pay-per-use basis. Do not manually remove nodes using kubectl de", "doc_type":"usermanual2", "kw":"Deleting a Node,Management Nodes,User Guide", "search_title":"", @@ -2917,7 +3006,7 @@ "uri":"cce_10_0036.html", "node_id":"cce_10_0036.xml", "product_code":"cce", - "code":"162", + "code":"167", "des":"When a node in the cluster is stopped, all services on that node will also be stopped, and the node will no longer be available for scheduling. Check if your services wil", "doc_type":"usermanual2", "kw":"Stopping a Node,Management Nodes,User Guide", @@ -2935,7 +3024,7 @@ "uri":"cce_10_0276.html", "node_id":"cce_10_0276.xml", "product_code":"cce", - "code":"163", + "code":"168", "des":"In a rolling upgrade, a new node is created, existing workloads are migrated to the new node, and then the old node is deleted. Figure 1 shows the migration process.The o", "doc_type":"usermanual2", "kw":"Performing Rolling Upgrade for Nodes,Management Nodes,User Guide", @@ -2953,7 +3042,7 @@ "uri":"cce_10_0704.html", "node_id":"cce_10_0704.xml", "product_code":"cce", - "code":"164", + "code":"169", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Node O&M", @@ -2971,7 +3060,7 @@ "uri":"cce_10_0178.html", "node_id":"cce_10_0178.xml", "product_code":"cce", - "code":"165", + "code":"170", "des":"Some node resources are used to run mandatory Kubernetes system components and resources to make the node as part of your cluster. Therefore, the total number of node res", "doc_type":"usermanual2", "kw":"total number of node resources,Node Resource Reservation Policy,Node O&M,User Guide", @@ -2989,7 +3078,7 @@ "uri":"cce_10_0341.html", "node_id":"cce_10_0341.xml", "product_code":"cce", - "code":"166", + "code":"171", "des":"This section describes how to allocate data disk space to nodes so that you can configure the data disk space accordingly.In clusters of a version earlier than v1.23.18-r", "doc_type":"usermanual2", "kw":"Data Disk Space Allocation,Container engine and container image space,container engine and container", @@ -3007,8 +3096,8 @@ "uri":"cce_10_0348.html", "node_id":"cce_10_0348.xml", "product_code":"cce", - "code":"167", - "des":"The maximum number of pods that can be created on a node is calculated based on the cluster type:When creating a cluster in the VPC network model, specify the number of c", + "code":"172", + "des":"The maximum number of pods that can be created on a node is calculated based on the cluster type:When creating a cluster in the VPC network model, follow the and specify", "doc_type":"usermanual2", "kw":"Maximum Number of Pods on a Node,alpha.cce/fixPoolMask,maximum number of pods,Maximum Number of Pods", "search_title":"", @@ -3025,7 +3114,7 @@ "uri":"cce_10_0883.html", "node_id":"cce_10_0883.xml", "product_code":"cce", - "code":"168", + "code":"173", "des":"To maintain the stability of nodes, CCE stores Kubernetes and container runtime components on separate data disks. Kubernetes uses the /mnt/paas/kubernetes directory, and", "doc_type":"usermanual2", "kw":"Differences in kubelet and Runtime Component Configurations Between CCE and the Native Community,Nod", @@ -3043,8 +3132,8 @@ "uri":"cce_10_0601.html", "node_id":"cce_10_0601.xml", "product_code":"cce", - "code":"169", - "des":"Kubernetes has removed dockershim from v1.24 and does not support Docker by default. CCE is going to stop the support for Docker. Change the node container engine from Do", + "code":"174", + "des":"As of Kubernetes v1.24, dockershim has been deprecated. To maintain compatibility and ensure continued support for future Kubernetes releases, switch your node's containe", "doc_type":"usermanual2", "kw":"Migrating Nodes from Docker to containerd,Node O&M,User Guide", "search_title":"", @@ -3061,7 +3150,7 @@ "uri":"cce_10_0659.html", "node_id":"cce_10_0659.xml", "product_code":"cce", - "code":"170", + "code":"175", "des":"The node fault detection function depends on the NPD add-on. The add-on instances run on nodes and monitor nodes. This section describes how to enable node fault detectio", "doc_type":"usermanual2", "kw":"Node Fault Detection,Check Items,Configuring Node Fault Detection Policies,Node O&M,User Guide", @@ -3076,10 +3165,10 @@ "githuburl":"" }, { - "uri":"cce_bestpractice_10020_0.html", - "node_id":"cce_bestpractice_10020_0.xml", + "uri":"cce_bestpractice_10020.html", + "node_id":"cce_bestpractice_10020.xml", "product_code":"cce", - "code":"171", + "code":"176", "des":"When creating a node, use the pre- or -installation commands to install tools or perform security hardening on the node. This section provides guidance for you to correct", "doc_type":"usermanual2", "kw":"Executing the Pre- or Post-installation Commands During Node Creation,Node O&M,User Guide", @@ -3097,7 +3186,7 @@ "uri":"cce_10_0035.html", "node_id":"cce_10_0035.xml", "product_code":"cce", - "code":"172", + "code":"177", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Node Pools", @@ -3115,7 +3204,7 @@ "uri":"cce_10_0081.html", "node_id":"cce_10_0081.xml", "product_code":"cce", - "code":"173", + "code":"178", "des":"CCE introduces node pools to help you better manage nodes in Kubernetes clusters. A node pool contains one node or a group of nodes with identical configuration in a clus", "doc_type":"usermanual2", "kw":"DefaultPool,DefaultPool,Deploying a Workload in a Specified Node Pool,Node Pool Overview,Node Pools,", @@ -3133,8 +3222,8 @@ "uri":"cce_10_0012.html", "node_id":"cce_10_0012.xml", "product_code":"cce", - "code":"174", - "des":"This section describes how to create a node pool and perform operations on the node pool. For details about how a node pool works, see Node Pool Overview.Basic SettingsCo", + "code":"179", + "des":"This section describes how to create a node pool and perform operations on the node pool. For details about how a node pool works, see Node Pool Overview.Basic SettingsNo", "doc_type":"usermanual2", "kw":"Creating a Node Pool,Node Pools,User Guide", "search_title":"", @@ -3151,8 +3240,8 @@ "uri":"cce_10_0658.html", "node_id":"cce_10_0658.xml", "product_code":"cce", - "code":"175", - "des":"You can specify a specification in a node pool for scaling.The default node pool does not support scaling. Use Creating a Node to add a node.Add or reduce nodes for scali", + "code":"180", + "des":"You can specify a specification in a node pool for scaling.The default node pool does not support scaling. Use Creating a Node to add a node.Resize: Add or reduce nodes f", "doc_type":"usermanual2", "kw":"Scaling a Node Pool,Node Pools,User Guide", "search_title":"", @@ -3169,7 +3258,7 @@ "uri":"cce_10_0222.html", "node_id":"cce_10_0222.xml", "product_code":"cce", - "code":"176", + "code":"181", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Managing a Node Pool", @@ -3187,7 +3276,7 @@ "uri":"cce_10_0653.html", "node_id":"cce_10_0653.xml", "product_code":"cce", - "code":"177", + "code":"182", "des":"Changes to the container engine, OS, or pre-/post-installation script in a node pool take effect only on new nodes. To synchronize the modification onto existing nodes, m", "doc_type":"usermanual2", "kw":"base size,Updating a Node Pool,Managing a Node Pool,User Guide", @@ -3205,7 +3294,7 @@ "uri":"cce_10_0727.html", "node_id":"cce_10_0727.xml", "product_code":"cce", - "code":"178", + "code":"183", "des":"Auto Scaling (AS) enables elastic scaling of nodes in a node pool based on scaling policies. Without this function, you have to manually adjust the number of nodes in a n", "doc_type":"usermanual2", "kw":"Updating an AS Configuration,Managing a Node Pool,User Guide", @@ -3223,8 +3312,8 @@ "uri":"cce_10_0652.html", "node_id":"cce_10_0652.xml", "product_code":"cce", - "code":"179", - "des":"The default node pool does not support the following management operations.CCE allows you to highly customize Kubernetes parameter settings on core components in a cluste", + "code":"184", + "des":"The default node pool does not support the management operations described in this section.CCE allows you to highly customize Kubernetes parameter settings on core compon", "doc_type":"usermanual2", "kw":"Modifying Node Pool Configurations,Managing a Node Pool,User Guide", "search_title":"", @@ -3241,7 +3330,7 @@ "uri":"cce_10_0886.html", "node_id":"cce_10_0886.xml", "product_code":"cce", - "code":"180", + "code":"185", "des":"If you want to add a newly created ECS to a node pool in a cluster, or remove a node from a node pool and add it to the node pool again, accept the node.When an ECS is ac", "doc_type":"usermanual2", "kw":"Accepting Nodes in a Node Pool,Managing a Node Pool,User Guide", @@ -3259,7 +3348,7 @@ "uri":"cce_10_0655.html", "node_id":"cce_10_0655.xml", "product_code":"cce", - "code":"181", + "code":"186", "des":"You can copy the configuration of an existing node pool on the CCE console to create new node pools.", "doc_type":"usermanual2", "kw":"Copying a Node Pool,Managing a Node Pool,User Guide", @@ -3277,7 +3366,7 @@ "uri":"cce_10_0654.html", "node_id":"cce_10_0654.xml", "product_code":"cce", - "code":"182", + "code":"187", "des":"After the configuration of a node pool is updated, some configurations cannot be automatically synchronized for existing nodes. You can manually synchronize configuration", "doc_type":"usermanual2", "kw":"Synchronizing Node Pools,Managing a Node Pool,User Guide", @@ -3295,7 +3384,7 @@ "uri":"cce_10_0660.html", "node_id":"cce_10_0660.xml", "product_code":"cce", - "code":"183", + "code":"188", "des":"After CCE releases a new OS image, if existing nodes cannot be automatically upgraded, you can manually upgrade them in batches.This section describes how to upgrade an O", "doc_type":"usermanual2", "kw":"Upgrading an OS,Managing a Node Pool,User Guide", @@ -3313,7 +3402,7 @@ "uri":"cce_10_0656.html", "node_id":"cce_10_0656.xml", "product_code":"cce", - "code":"184", + "code":"189", "des":"You can migrate nodes between node pools within a cluster. Table 1 lists migration scenarios.Migration scenariosMigration ScenarioMigrationOperationSource Node PoolTarget", "doc_type":"usermanual2", "kw":"Migrating a Node,Managing a Node Pool,User Guide", @@ -3331,7 +3420,7 @@ "uri":"cce_10_0657.html", "node_id":"cce_10_0657.xml", "product_code":"cce", - "code":"185", + "code":"190", "des":"Deleting a node pool will delete nodes in the pool. Pods on these nodes will be automatically migrated to available nodes in other node pools.Deleting a node pool will de", "doc_type":"usermanual2", "kw":"Deleting a Node Pool,Managing a Node Pool,User Guide", @@ -3349,7 +3438,7 @@ "uri":"cce_10_0046.html", "node_id":"cce_10_0046.xml", "product_code":"cce", - "code":"186", + "code":"191", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Workloads", @@ -3367,7 +3456,7 @@ "uri":"cce_10_0006.html", "node_id":"cce_10_0006.xml", "product_code":"cce", - "code":"187", + "code":"192", "des":"A workload is an application running on Kubernetes. No matter how many components are there in your workload, you can run it in a group of Kubernetes pods. A workload is ", "doc_type":"usermanual2", "kw":"Deployments,StatefulSets,DaemonSets,jobs,cron jobs,Overview,Workloads,User Guide", @@ -3385,7 +3474,7 @@ "uri":"cce_10_0673.html", "node_id":"cce_10_0673.xml", "product_code":"cce", - "code":"188", + "code":"193", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Creating a Workload", @@ -3403,7 +3492,7 @@ "uri":"cce_10_0047.html", "node_id":"cce_10_0047.xml", "product_code":"cce", - "code":"189", + "code":"194", "des":"Deployments are workloads (for example, Nginx) that do not store any data or status. You can create Deployments on the CCE console or by running kubectl commands.Before c", "doc_type":"usermanual2", "kw":"create a workload using kubectl,Creating a Deployment,Creating a Workload,User Guide", @@ -3421,7 +3510,7 @@ "uri":"cce_10_0048.html", "node_id":"cce_10_0048.xml", "product_code":"cce", - "code":"190", + "code":"195", "des":"StatefulSets are a type of workloads whose data or status is stored while they are running. For example, MySQL is a StatefulSet because it needs to store new data.A conta", "doc_type":"usermanual2", "kw":"Using kubectl,Creating a StatefulSet,Creating a Workload,User Guide", @@ -3439,7 +3528,7 @@ "uri":"cce_10_0216.html", "node_id":"cce_10_0216.xml", "product_code":"cce", - "code":"191", + "code":"196", "des":"CCE provides deployment and management capabilities for multiple types of containers and supports features of container workloads, including creation, configuration, moni", "doc_type":"usermanual2", "kw":"create a workload using kubectl,Creating a DaemonSet,Creating a Workload,User Guide", @@ -3457,7 +3546,7 @@ "uri":"cce_10_0150.html", "node_id":"cce_10_0150.xml", "product_code":"cce", - "code":"192", + "code":"197", "des":"Jobs are short-lived and run for a certain time to completion. They can be executed immediately after being deployed. It is completed after it exits normally (exit 0).A j", "doc_type":"usermanual2", "kw":"Creating a Job,Creating a Workload,User Guide", @@ -3475,10 +3564,10 @@ "uri":"cce_10_0151.html", "node_id":"cce_10_0151.xml", "product_code":"cce", - "code":"193", - "des":"A cron job runs on a repeating schedule. You can perform time synchronization for all active nodes at a fixed time point.A cron job runs periodically at the specified tim", + "code":"198", + "des":"A CronJob runs on a repeating schedule. You can perform time synchronization for all active nodes at a fixed time point.A CronJob runs periodically at the specified time.", "doc_type":"usermanual2", - "kw":"time synchronization,Creating a Cron Job,Creating a Workload,User Guide", + "kw":"time synchronization,Creating a CronJob,Creating a Workload,User Guide", "search_title":"", "metedata":[ { @@ -3486,14 +3575,14 @@ "documenttype":"usermanual" } ], - "title":"Creating a Cron Job", + "title":"Creating a CronJob", "githuburl":"" }, { "uri":"cce_10_0130.html", "node_id":"cce_10_0130.xml", "product_code":"cce", - "code":"194", + "code":"199", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Configuring a Workload", @@ -3511,8 +3600,8 @@ "uri":"cce_10_0463.html", "node_id":"cce_10_0463.xml", "product_code":"cce", - "code":"195", - "des":"The most significant difference is that each Kata container (pod) runs on an independent micro-VM, has an independent OS kernel, and is securely isolated at the virtualiz", + "code":"200", + "des":"Compared with a common runtime, a secure runtime allows each container (pod) to run on its own micro-VM with a separate OS kernel. This ensures secure isolation at the vi", "doc_type":"usermanual2", "kw":"Secure Runtime and Common Runtime,Configuring a Workload,User Guide", "search_title":"", @@ -3529,7 +3618,7 @@ "uri":"cce_10_0354.html", "node_id":"cce_10_0354.xml", "product_code":"cce", - "code":"196", + "code":"201", "des":"When creating a workload, you can configure containers to use the same time zone as the node. You can enable time zone synchronization when creating a workload.The time z", "doc_type":"usermanual2", "kw":"Configuring Time Zone Synchronization,Configuring a Workload,User Guide", @@ -3547,7 +3636,7 @@ "uri":"cce_10_0353.html", "node_id":"cce_10_0353.xml", "product_code":"cce", - "code":"197", + "code":"202", "des":"When a workload is created, the container image is pulled from the image repository to the node. The image is also pulled when the workload is restarted or upgraded.By de", "doc_type":"usermanual2", "kw":"Configuring an Image Pull Policy,Configuring a Workload,User Guide", @@ -3565,7 +3654,7 @@ "uri":"cce_10_0009.html", "node_id":"cce_10_0009.xml", "product_code":"cce", - "code":"198", + "code":"203", "des":"CCE allows you to create workloads using images pulled from third-party image repositories.Generally, a third-party image repository can be accessed only after authentica", "doc_type":"usermanual2", "kw":"Using Third-Party Images,Configuring a Workload,User Guide", @@ -3583,7 +3672,7 @@ "uri":"cce_10_0163.html", "node_id":"cce_10_0163.xml", "product_code":"cce", - "code":"199", + "code":"204", "des":"CCE allows you to set resource requirements and limits, such as CPU and RAM, for added containers during workload creation. Kubernetes also allows using YAML to set requi", "doc_type":"usermanual2", "kw":"ephemeral storage,Configuring Container Specifications,Configuring a Workload,User Guide", @@ -3601,7 +3690,7 @@ "uri":"cce_10_0105.html", "node_id":"cce_10_0105.xml", "product_code":"cce", - "code":"200", + "code":"205", "des":"CCE provides callback functions for the lifecycle management of containerized applications. For example, if you want a container to perform a certain operation before sto", "doc_type":"usermanual2", "kw":"Startup Command,Post-Start,Pre-Stop,Configuring Container Lifecycle Parameters,Configuring a Workloa", @@ -3619,7 +3708,7 @@ "uri":"cce_10_0112.html", "node_id":"cce_10_0112.xml", "product_code":"cce", - "code":"201", + "code":"206", "des":"Health check regularly checks the health status of containers during container running. If the health check function is not configured, a pod cannot detect application ex", "doc_type":"usermanual2", "kw":"Health check,HTTP request,TCP port,CLI,Configuring Container Health Check,Configuring a Workload,Use", @@ -3637,7 +3726,7 @@ "uri":"cce_10_0113.html", "node_id":"cce_10_0113.xml", "product_code":"cce", - "code":"202", + "code":"207", "des":"An environment variable is a variable whose value can affect the way a running container will behave. You can modify environment variables even after workloads are deploy", "doc_type":"usermanual2", "kw":"Configuring Environment Variables,Configuring a Workload,User Guide", @@ -3655,7 +3744,7 @@ "uri":"cce_10_0397.html", "node_id":"cce_10_0397.xml", "product_code":"cce", - "code":"203", + "code":"208", "des":"In actual applications, upgrade is a common operation. A Deployment, StatefulSet, or DaemonSet can easily support application upgrade.You can set different upgrade polici", "doc_type":"usermanual2", "kw":"Configuring Workload Upgrade Policies,Configuring a Workload,User Guide", @@ -3673,7 +3762,7 @@ "uri":"cce_10_0728.html", "node_id":"cce_10_0728.xml", "product_code":"cce", - "code":"204", + "code":"209", "des":"Tolerations allow the scheduler to schedule pods to nodes with target taints. Tolerances work with node taints. Each node allows one or more taints. If no tolerance is co", "doc_type":"usermanual2", "kw":"Configuring Tolerance Policies,Configuring a Workload,User Guide", @@ -3691,7 +3780,7 @@ "uri":"cce_10_0386.html", "node_id":"cce_10_0386.xml", "product_code":"cce", - "code":"205", + "code":"210", "des":"CCE allows you to add annotations to a YAML file to realize some advanced pod functions. The following table describes the annotations you can add.When you create a workl", "doc_type":"usermanual2", "kw":"Configuring Labels and Annotations,Configuring a Workload,User Guide", @@ -3709,7 +3798,7 @@ "uri":"cce_10_0889.html", "node_id":"cce_10_0889.xml", "product_code":"cce", - "code":"206", + "code":"211", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Scheduling a Workload", @@ -3727,7 +3816,7 @@ "uri":"cce_10_0232.html", "node_id":"cce_10_0232.xml", "product_code":"cce", - "code":"207", + "code":"212", "des":"Kubernetes schedules workloads based on pods. After you create a workload, the scheduler automatically assigns pods. For example, the scheduler distributes pods to nodes ", "doc_type":"usermanual2", "kw":"Overview,Scheduling a Workload,User Guide", @@ -3745,7 +3834,7 @@ "uri":"cce_10_0891.html", "node_id":"cce_10_0891.xml", "product_code":"cce", - "code":"208", + "code":"213", "des":"To select a node for scheduling in Kubernetes, simply configure the nodeSelector field in the workload. This field allows you to configure the label of the desired node t", "doc_type":"usermanual2", "kw":"Configuring Specified Node Scheduling (nodeSelector),Scheduling a Workload,User Guide", @@ -3763,10 +3852,10 @@ "uri":"cce_10_0892.html", "node_id":"cce_10_0892.xml", "product_code":"cce", - "code":"209", + "code":"214", "des":"Kubernetes can schedule workload pods to affinity nodes based on their labels and label values. For example, some nodes support GPU computing, and node affinity schedulin", "doc_type":"usermanual2", - "kw":"Node Affinity,Specified Node Pool Scheduling,Configuring Node Affinity Scheduling (nodeAffinity),Sch", + "kw":"Specify node,Specify node pool,Configuring Node Affinity Scheduling (nodeAffinity),Scheduling a Work", "search_title":"", "metedata":[ { @@ -3781,7 +3870,7 @@ "uri":"cce_10_0893.html", "node_id":"cce_10_0893.xml", "product_code":"cce", - "code":"210", + "code":"215", "des":"Kubernetes offers workload affinity and anti-affinity scheduling, which allows for flexible scheduling of new workloads on either related or unrelated nodes. This results", "doc_type":"usermanual2", "kw":"Configuring Workload Affinity or Anti-affinity Scheduling (podAffinity or podAntiAffinity),Schedulin", @@ -3799,8 +3888,8 @@ "uri":"cce_10_00356.html", "node_id":"cce_10_00356.xml", "product_code":"cce", - "code":"211", - "des":"If you encounter unexpected problems when using a container, you can log in to the container to debug it.When using CloudShell to access a CCE cluster or container, you c", + "code":"216", + "des":"If you encounter unexpected problems when using a container, you can log in to the container to debug it.When kubectl is used in CloudShell, permissions are determined by", "doc_type":"usermanual2", "kw":"Logging In to a Container,Workloads,User Guide", "search_title":"", @@ -3817,7 +3906,7 @@ "uri":"cce_10_0007.html", "node_id":"cce_10_0007.xml", "product_code":"cce", - "code":"212", + "code":"217", "des":"After a workload is created, you can upgrade, log, monitor, roll back, or delete the workload, as well as edit its YAML file.Workload/Job managementOperationDescriptionMo", "doc_type":"usermanual2", "kw":"Managing Workloads,Workloads,User Guide", @@ -3835,7 +3924,7 @@ "uri":"cce_10_0833.html", "node_id":"cce_10_0833.xml", "product_code":"cce", - "code":"213", + "code":"218", "des":"Custom Resource Definition (CRD) is an extension of Kubernetes APIs. When default Kubernetes resources cannot meet service requirements, you can use CRDs to define new re", "doc_type":"usermanual2", "kw":"Managing Custom Resources,Workloads,User Guide", @@ -3853,7 +3942,7 @@ "uri":"cce_10_0465.html", "node_id":"cce_10_0465.xml", "product_code":"cce", - "code":"214", + "code":"219", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Pod Security", @@ -3871,7 +3960,7 @@ "uri":"cce_10_0275.html", "node_id":"cce_10_0275.xml", "product_code":"cce", - "code":"215", + "code":"220", "des":"A pod security policy (PSP) is a cluster-level resource that controls sensitive security aspects of the pod specification. The PodSecurityPolicy object in Kubernetes defi", "doc_type":"usermanual2", "kw":"Configuring a Pod Security Policy,Pod Security,User Guide", @@ -3889,7 +3978,7 @@ "uri":"cce_10_0466.html", "node_id":"cce_10_0466.xml", "product_code":"cce", - "code":"216", + "code":"221", "des":"Before using pod security admission, understand Kubernetes Pod Security Standards. These standards define different isolation levels for pods. They let you define how you", "doc_type":"usermanual2", "kw":"Configuring Pod Security Admission,Pod Security,User Guide", @@ -3907,7 +3996,7 @@ "uri":"cce_10_0674.html", "node_id":"cce_10_0674.xml", "product_code":"cce", - "code":"217", + "code":"222", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Scheduling", @@ -3925,7 +4014,7 @@ "uri":"cce_10_0702.html", "node_id":"cce_10_0702.xml", "product_code":"cce", - "code":"218", + "code":"223", "des":"CCE supports different types of resource scheduling and task scheduling, improving application performance and overall cluster resource utilization. This section describe", "doc_type":"usermanual2", "kw":"Overview,Scheduling,User Guide", @@ -3943,7 +4032,7 @@ "uri":"cce_10_0551.html", "node_id":"cce_10_0551.xml", "product_code":"cce", - "code":"219", + "code":"224", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"CPU Scheduling", @@ -3961,7 +4050,7 @@ "uri":"cce_10_0351.html", "node_id":"cce_10_0351.xml", "product_code":"cce", - "code":"220", + "code":"225", "des":"By default, kubelet uses CFS quotas to enforce pod CPU limits. When a node runs many CPU-bound pods, the workload can move to different CPU cores depending on whether the", "doc_type":"usermanual2", "kw":"CPU Policy,CPU Scheduling,User Guide", @@ -3979,7 +4068,7 @@ "uri":"cce_10_0552.html", "node_id":"cce_10_0552.xml", "product_code":"cce", - "code":"221", + "code":"226", "des":"Kubernetes provides two CPU policies: none and static.none: The CPU policy is disabled by default, indicating the existing scheduling behavior.static: The static CPU core", "doc_type":"usermanual2", "kw":"Enhanced CPU Policy,CPU Scheduling,User Guide", @@ -3997,7 +4086,7 @@ "uri":"cce_10_0720.html", "node_id":"cce_10_0720.xml", "product_code":"cce", - "code":"222", + "code":"227", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"GPU Scheduling", @@ -4015,8 +4104,8 @@ "uri":"cce_10_0345.html", "node_id":"cce_10_0345.xml", "product_code":"cce", - "code":"223", - "des":"You can use GPUs in CCE containers.A GPU node has been created. For details, see Creating a Node.The CCE AI Suite (NVIDIA GPU) add-on has been installed. During the insta", + "code":"228", + "des":"You can use GPUs in CCE containers.A GPU node has been created. For details, see Creating a Node.The CCE AI Suite (NVIDIA GPU) add-on has been installed, with the selecte", "doc_type":"usermanual2", "kw":"Default GPU Scheduling in Kubernetes,GPU Scheduling,User Guide", "search_title":"", @@ -4029,11 +4118,29 @@ "title":"Default GPU Scheduling in Kubernetes", "githuburl":"" }, + { + "uri":"cce_10_0955.html", + "node_id":"cce_10_0955.xml", + "product_code":"cce", + "code":"229", + "des":"The CCE AI Suite (NVIDIA GPU) add-on provides GPU monitoring metrics. This add-on offers additional GPU observability options. This section describes the metrics provided", + "doc_type":"usermanual2", + "kw":"GPU Metrics,GPU Scheduling,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"GPU Metrics", + "githuburl":"" + }, { "uri":"cce_10_0423.html", "node_id":"cce_10_0423.xml", "product_code":"cce", - "code":"224", + "code":"230", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Volcano Scheduling", @@ -4051,7 +4158,7 @@ "uri":"cce_10_0721.html", "node_id":"cce_10_0721.xml", "product_code":"cce", - "code":"225", + "code":"231", "des":"Volcano is a batch processing platform that runs on Kubernetes for machine learning, deep learning, bioinformatics, genomics, and other big data applications. It provides", "doc_type":"usermanual2", "kw":"Overview,Volcano Scheduling,User Guide", @@ -4069,7 +4176,7 @@ "uri":"cce_10_0722.html", "node_id":"cce_10_0722.xml", "product_code":"cce", - "code":"226", + "code":"232", "des":"Volcano is a Kubernetes-based batch processing platform with high-performance general computing capabilities like task scheduling engine, heterogeneous chip management, a", "doc_type":"usermanual2", "kw":"Scheduling Workloads,Volcano Scheduling,User Guide", @@ -4087,7 +4194,7 @@ "uri":"cce_10_0768.html", "node_id":"cce_10_0768.xml", "product_code":"cce", - "code":"227", + "code":"233", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Resource Usage-based Scheduling", @@ -4105,7 +4212,7 @@ "uri":"cce_10_0773.html", "node_id":"cce_10_0773.xml", "product_code":"cce", - "code":"228", + "code":"234", "des":"Bin packing is an optimization algorithm that aims to properly allocate resources to each job and get the jobs done using the minimum amount of resources. After bin packi", "doc_type":"usermanual2", "kw":"Bin Packing,Resource Usage-based Scheduling,User Guide", @@ -4123,7 +4230,7 @@ "uri":"cce_10_0766.html", "node_id":"cce_10_0766.xml", "product_code":"cce", - "code":"229", + "code":"235", "des":"Scheduling in a cluster is the process of binding pending pods to nodes, and is performed by a component called kube-scheduler or Volcano Scheduler. The scheduler uses a ", "doc_type":"usermanual2", "kw":"Descheduling,Resource Usage-based Scheduling,User Guide", @@ -4141,7 +4248,7 @@ "uri":"cce_10_0767.html", "node_id":"cce_10_0767.xml", "product_code":"cce", - "code":"230", + "code":"236", "des":"In scenarios such as node pool replacement and rolling node upgrade, an old resource pool needs to be replaced with a new one. To prevent the node pool replacement from a", "doc_type":"usermanual2", "kw":"Node Pool Affinity,Resource Usage-based Scheduling,User Guide", @@ -4159,7 +4266,7 @@ "uri":"cce_10_0789.html", "node_id":"cce_10_0789.xml", "product_code":"cce", - "code":"231", + "code":"237", "des":"Volcano Scheduler offers CPU and memory load-aware scheduling for pods and preferentially schedules pods to the node with the lightest load to balance node loads. This pr", "doc_type":"usermanual2", "kw":"Load-aware Scheduling,Resource Usage-based Scheduling,User Guide", @@ -4177,7 +4284,7 @@ "uri":"cce_10_0813.html", "node_id":"cce_10_0813.xml", "product_code":"cce", - "code":"232", + "code":"238", "des":"Volcano scheduling involves node filtering and scoring, which is used to filter the nodes meeting scheduling conditions and score the filtered nodes to find the one with ", "doc_type":"usermanual2", "kw":"Configuration Cases for Resource Usage-based Scheduling,Resource Usage-based Scheduling,User Guide", @@ -4195,7 +4302,7 @@ "uri":"cce_10_0774.html", "node_id":"cce_10_0774.xml", "product_code":"cce", - "code":"233", + "code":"239", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Priority-based Scheduling", @@ -4213,7 +4320,7 @@ "uri":"cce_10_0775.html", "node_id":"cce_10_0775.xml", "product_code":"cce", - "code":"234", + "code":"240", "des":"A pod priority indicates the importance of a pod relative to other pods. Volcano supports pod PriorityClasses in Kubernetes. After PriorityClasses are configured, the sch", "doc_type":"usermanual2", "kw":"Priority-based Scheduling,Priority-based Scheduling,User Guide", @@ -4231,7 +4338,7 @@ "uri":"cce_10_0776.html", "node_id":"cce_10_0776.xml", "product_code":"cce", - "code":"235", + "code":"241", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"AI Performance-based Scheduling", @@ -4249,7 +4356,7 @@ "uri":"cce_10_0777.html", "node_id":"cce_10_0777.xml", "product_code":"cce", - "code":"236", + "code":"242", "des":"Dominant Resource Fairness (DRF) is a scheduling algorithm based on the dominant resource of a container group. DRF scheduling can be used to enhance the service throughp", "doc_type":"usermanual2", "kw":"DRF,AI Performance-based Scheduling,User Guide", @@ -4267,7 +4374,7 @@ "uri":"cce_10_0778.html", "node_id":"cce_10_0778.xml", "product_code":"cce", - "code":"237", + "code":"243", "des":"Gang scheduling is a scheduling algorithm that schedules correlated processes or threads to run simultaneously on different processors. It meets the scheduling requiremen", "doc_type":"usermanual2", "kw":"Gang,AI Performance-based Scheduling,User Guide", @@ -4285,7 +4392,7 @@ "uri":"cce_10_0425.html", "node_id":"cce_10_0425.xml", "product_code":"cce", - "code":"238", + "code":"244", "des":"In non-uniform memory access (NUMA) architecture, a NUMA node is a fundamental component that includes a processor and local memory. These nodes are physically separate b", "doc_type":"usermanual2", "kw":"NUMA Affinity Scheduling,Volcano Scheduling,User Guide", @@ -4303,7 +4410,7 @@ "uri":"cce_10_0709.html", "node_id":"cce_10_0709.xml", "product_code":"cce", - "code":"239", + "code":"245", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Cloud Native Hybrid Deployment", @@ -4321,7 +4428,7 @@ "uri":"cce_10_0384.html", "node_id":"cce_10_0384.xml", "product_code":"cce", - "code":"240", + "code":"246", "des":"Many services see surges in traffic. To ensure performance and stability, resources are often requested at the maximum needed. However, the surges may ebb very shortly an", "doc_type":"usermanual2", "kw":"Dynamic Resource Oversubscription,Cloud Native Hybrid Deployment,User Guide", @@ -4339,7 +4446,7 @@ "uri":"cce_10_0020.html", "node_id":"cce_10_0020.xml", "product_code":"cce", - "code":"241", + "code":"247", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Network", @@ -4357,7 +4464,7 @@ "uri":"cce_10_0010.html", "node_id":"cce_10_0010.xml", "product_code":"cce", - "code":"242", + "code":"248", "des":"You can learn about a cluster network from the following two aspects:What is a cluster network like? A cluster consists of multiple nodes, and pods (or containers) are ru", "doc_type":"usermanual2", "kw":"Overview,Network,User Guide", @@ -4375,7 +4482,7 @@ "uri":"cce_10_0280.html", "node_id":"cce_10_0280.xml", "product_code":"cce", - "code":"243", + "code":"249", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Container Network", @@ -4393,7 +4500,7 @@ "uri":"cce_10_0281.html", "node_id":"cce_10_0281.xml", "product_code":"cce", - "code":"244", + "code":"250", "des":"The container network assigns IP addresses to pods in a cluster and provides networking services. In CCE, you can select the following network models for your cluster:Clo", "doc_type":"usermanual2", "kw":"Overview,Container Network,User Guide", @@ -4411,7 +4518,7 @@ "uri":"cce_10_0678.html", "node_id":"cce_10_0678.xml", "product_code":"cce", - "code":"245", + "code":"251", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Cloud Native Network 2.0 Settings", @@ -4429,10 +4536,10 @@ "uri":"cce_10_0284.html", "node_id":"cce_10_0284.xml", "product_code":"cce", - "code":"246", - "des":"Cloud Native 2.0 network model is a proprietary, next-generation container network model that combines the elastic network interfaces (ENIs) and supplementary network int", + "code":"252", + "des":"Cloud Native Network 2.0 is a proprietary, next-generation container network model that combines the elastic network interfaces (ENIs) and supplementary network interface", "doc_type":"usermanual2", - "kw":"Cloud Native 2.0 Network Model,Cloud Native Network 2.0 Settings,User Guide", + "kw":"Cloud Native Network 2.0,Cloud Native Network 2.0 Settings,User Guide", "search_title":"", "metedata":[ { @@ -4440,17 +4547,17 @@ "documenttype":"usermanual" } ], - "title":"Cloud Native 2.0 Network Model", + "title":"Cloud Native Network 2.0", "githuburl":"" }, { "uri":"cce_10_0906.html", "node_id":"cce_10_0906.xml", "product_code":"cce", - "code":"247", + "code":"253", "des":"If the pod subnet configured during CCE Turbo cluster creation cannot meet service expansion requirements, you can add a pod subnet for the cluster.This function is avail", "doc_type":"usermanual2", - "kw":"Configuring Pod Subnets of a Cluster,Cloud Native Network 2.0 Settings,User Guide", + "kw":"Configuring a Default Container Subnet for a CCE Turbo Cluster,Cloud Native Network 2.0 Settings,Use", "search_title":"", "metedata":[ { @@ -4458,15 +4565,15 @@ "documenttype":"usermanual" } ], - "title":"Configuring Pod Subnets of a Cluster", + "title":"Configuring a Default Container Subnet for a CCE Turbo Cluster", "githuburl":"" }, { "uri":"cce_10_0897.html", "node_id":"cce_10_0897.xml", "product_code":"cce", - "code":"248", - "des":"In Cloud Native 2.0 network mode, pods use ENIs or sub-ENIs of the VPC. You can configure a security group for a pod using a pod's annotation.Configure a security group i", + "code":"254", + "des":"In Cloud Native Network 2.0, pods use ENIs or sub-ENIs of the VPC. You can configure a security group for a pod using a pod's annotation.Configure a security group in eit", "doc_type":"usermanual2", "kw":"Binding a Security Group to a Pod Using an Annotation,Cloud Native Network 2.0 Settings,User Guide", "search_title":"", @@ -4483,7 +4590,7 @@ "uri":"cce_10_0288.html", "node_id":"cce_10_0288.xml", "product_code":"cce", - "code":"249", + "code":"255", "des":"In Cloud Native Network 2.0, pods use VPC ENIs or sub-ENIs for networking. You can directly bind security groups and EIPs to pods. To bind CCE pods with security groups, ", "doc_type":"usermanual2", "kw":"Binding a Security Group to a Workload Using a Security Group Policy,Cloud Native Network 2.0 Settin", @@ -4501,7 +4608,7 @@ "uri":"cce_10_0196.html", "node_id":"cce_10_0196.xml", "product_code":"cce", - "code":"250", + "code":"256", "des":"In a CCE Turbo cluster, you can configure subnets and security groups for containers by namespace or workload using NetworkAttachmentDefinition CRDs. To configure a parti", "doc_type":"usermanual2", "kw":"Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configurati", @@ -4519,7 +4626,7 @@ "uri":"cce_10_0603.html", "node_id":"cce_10_0603.xml", "product_code":"cce", - "code":"251", + "code":"257", "des":"In Cloud Native Network 2.0, each pod is associated with an ENI, providing a static IP address to the StatefulSet pods (container ENI). This is a common practice in acces", "doc_type":"usermanual2", "kw":"Configuring a Static IP Address for a Pod,Cloud Native Network 2.0 Settings,User Guide", @@ -4537,7 +4644,7 @@ "uri":"cce_10_0734.html", "node_id":"cce_10_0734.xml", "product_code":"cce", - "code":"252", + "code":"258", "des":"In Cloud Native Network 2.0, pods use VPC ENIs or sub-ENIs for networking. You can directly bind EIPs to pods.To associate an EIP with a pod, simply set the value of the ", "doc_type":"usermanual2", "kw":"Configuring an EIP for a Pod,Cloud Native Network 2.0 Settings,User Guide", @@ -4555,7 +4662,7 @@ "uri":"cce_10_0651.html", "node_id":"cce_10_0651.xml", "product_code":"cce", - "code":"253", + "code":"259", "des":"In Cloud Native Network 2.0, static public IP addresses (EIPs) can be assigned to StatefulSets or pods created directly.You can configure a static EIP for a pod only in C", "doc_type":"usermanual2", "kw":"static EIPs,Configuring a Static EIP for a Pod,Cloud Native Network 2.0 Settings,User Guide", @@ -4573,7 +4680,7 @@ "uri":"cce_10_0604.html", "node_id":"cce_10_0604.xml", "product_code":"cce", - "code":"254", + "code":"260", "des":"By default, pods with IPv6 dual-stack ENIs can access only the IPv6 private network. To access the public network, configure shared bandwidth for such pods.Only CCE Turbo", "doc_type":"usermanual2", "kw":"Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack ENIs,Cloud Native Network 2.0 Settings,U", @@ -4591,7 +4698,7 @@ "uri":"cce_10_0904.html", "node_id":"cce_10_0904.xml", "product_code":"cce", - "code":"255", + "code":"261", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"VPC Network Settings", @@ -4609,7 +4716,7 @@ "uri":"cce_10_0283.html", "node_id":"cce_10_0283.xml", "product_code":"cce", - "code":"256", + "code":"262", "des":"The VPC network model seamlessly combines VPC routing with the underlying network, making it ideal for high-performance scenarios. However, the maximum number of nodes al", "doc_type":"usermanual2", "kw":"VPC Network Model,VPC Network Settings,User Guide", @@ -4627,7 +4734,7 @@ "uri":"cce_10_0680.html", "node_id":"cce_10_0680.xml", "product_code":"cce", - "code":"257", + "code":"263", "des":"If the container CIDR block configured during CCE cluster creation cannot meet service expansion requirements, you can add a container CIDR block for the cluster.This fun", "doc_type":"usermanual2", "kw":"Adding a Container CIDR Block for a Cluster,VPC Network Settings,User Guide", @@ -4645,7 +4752,7 @@ "uri":"cce_10_0677.html", "node_id":"cce_10_0677.xml", "product_code":"cce", - "code":"258", + "code":"264", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Tunnel Network Settings", @@ -4663,7 +4770,7 @@ "uri":"cce_10_0282.html", "node_id":"cce_10_0282.xml", "product_code":"cce", - "code":"259", + "code":"265", "des":"A container tunnel network creates a separate network plane for containers by using tunnel encapsulation on the host network plane. The container tunnel network of a CCE ", "doc_type":"usermanual2", "kw":"Tunnel Network Model,Tunnel Network Settings,User Guide", @@ -4681,7 +4788,7 @@ "uri":"cce_10_0675.html", "node_id":"cce_10_0675.xml", "product_code":"cce", - "code":"260", + "code":"266", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Pod Network Settings", @@ -4699,7 +4806,7 @@ "uri":"cce_10_0402.html", "node_id":"cce_10_0402.xml", "product_code":"cce", - "code":"261", + "code":"267", "des":"Kubernetes allows pods to directly use the host/node network. When a pod is configured with hostNetwork: true, applications running in the pod can directly view the netwo", "doc_type":"usermanual2", "kw":"Configuring hostNetwork for Pods,Pod Network Settings,User Guide", @@ -4717,8 +4824,8 @@ "uri":"cce_10_0382.html", "node_id":"cce_10_0382.xml", "product_code":"cce", - "code":"262", - "des":"Bandwidth preemption occurs between different containers deployed on the same node, which may cause service jitter. You can configure QoS rate limiting for inter-pod acce", + "code":"268", + "des":"Bandwidth preemption occurs between different containers deployed on the same node, which may cause service jitter. You can configure bandwidth limitation for the pod to ", "doc_type":"usermanual2", "kw":"Configuring QoS for a Pod,Pod Network Settings,User Guide", "search_title":"", @@ -4735,7 +4842,7 @@ "uri":"cce_10_0059.html", "node_id":"cce_10_0059.xml", "product_code":"cce", - "code":"263", + "code":"269", "des":"Network policies are designed by Kubernetes to restrict pod access. It is equivalent to a firewall at the application layer to enhance network security. The capabilities ", "doc_type":"usermanual2", "kw":"Configuring Network Policies to Restrict Pod Access,Pod Network Settings,User Guide", @@ -4749,11 +4856,29 @@ "title":"Configuring Network Policies to Restrict Pod Access", "githuburl":"" }, + { + "uri":"cce_10_0945.html", + "node_id":"cce_10_0945.xml", + "product_code":"cce", + "code":"270", + "des":"DataPlane V2 can be enabled for clusters that use Cloud Native 2.0 networks. After this function is enabled, eBPF redirection will be enabled for the capability of networ", + "doc_type":"usermanual2", + "kw":"DataPlane V2 Network Acceleration,Pod Network Settings,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"DataPlane V2 Network Acceleration", + "githuburl":"" + }, { "uri":"cce_10_0247.html", "node_id":"cce_10_0247.xml", "product_code":"cce", - "code":"264", + "code":"271", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Service", @@ -4771,7 +4896,7 @@ "uri":"cce_10_0249.html", "node_id":"cce_10_0249.xml", "product_code":"cce", - "code":"265", + "code":"272", "des":"After a pod is created, the following problems may occur if you directly access the pod:The pod can be deleted and recreated at any time by a controller such as a Deploym", "doc_type":"usermanual2", "kw":"Overview,Service,User Guide", @@ -4789,7 +4914,7 @@ "uri":"cce_10_0011.html", "node_id":"cce_10_0011.xml", "product_code":"cce", - "code":"266", + "code":"273", "des":"ClusterIP Services allow workloads in the same cluster to use their cluster-internal domain names to access each other.The cluster-internal domain name format is -

2025-02-10

+

2025-05-23

+ +

Update:

+ + + +

2025-05-12

+ +

Add:

+ +

Update:

+ + + +

2025-04-28

+ +

Updated Overview.

+ + +

2025-03-31

+ +

Update:

+ + + +

2025-03-10

+ +

Add:

+ +

Update:

+ +

Delete:

+
  • Deleted "Kubernetes Version Policy".
+ + +

2025-02-28

+ +

Update:

+ + + +

2025-02-10

Add:

@@ -21,7 +62,7 @@

Add:

Update:

- +

Delete:

  • Deleted "CCE Console Upgrade".
  • Deleted "Scheduling Policies (Affinity/Anti-affinity)".
@@ -78,7 +119,7 @@

2024-06-26

- +

2024-05-30

diff --git a/docs/cce/umn/cce_10_0002.html b/docs/cce/umn/cce_10_0002.html index 5da4fd1c2..606c27a4c 100644 --- a/docs/cce/umn/cce_10_0002.html +++ b/docs/cce/umn/cce_10_0002.html @@ -1,11 +1,9 @@ -

Cluster Overview

+

Cluster Version Release Notes

Notes and Constraints

  • To enable node resetting in CCE standard clusters or CCE Turbo clusters, the version must be v1.13 or later.
-

Precautions

  • Only worker nodes can be reset. If the node is still unavailable after the resetting, delete the node and create a new one.
  • After a node is reset, the node OS will be reinstalled. Before resetting a node, drain the node to gracefully evict the pods running on the node to other available nodes. Perform this operation during off-peak hours.
  • After a node is reset, its system disk and data disks will be cleared. Back up important data before resetting a node.
  • If you reset a worker node that has an additional data disk attached on the ECS console, the attachment will be removed. To keep the data, you need to reattach the disk.
  • The IP addresses of the workload pods on the node will change, but the container network access is not affected.
  • There is remaining EVS disk quota.
  • When a node is reset, the backend will make it unschedulable.
  • Resetting a node will clear the Kubernetes labels and taints you added (those added by editing a node pool will not be lost). As a result, node-specific resources (such as local storage and workloads scheduled to this node) may be unavailable.
  • Resetting a node will cause PVC/PV data loss for the local PV associated with the node. These PVCs and PVs cannot be restored or used again. In this scenario, the pod that uses the local PV is evicted from the reset node. A new pod is created and stays in the pending state. This is because the PVC used by the pod has a node label, due to which the pod cannot be scheduled. After the node is reset, the pod may be scheduled to the reset node. In this case, the pod remains in the creating state because the underlying logical volume corresponding to the PVC does not exist.
+

Precautions

  • Only worker nodes can be reset. If the node is still unavailable after the resetting, delete the node and create a new one.
  • After a node is reset, the node OS will be reinstalled. Before resetting a node, drain the node to gracefully evict the pods running on the node to other available nodes. Perform this operation during off-peak hours.
  • After a node is reset, its system disk and data disks will be cleared. Back up important data before resetting a node.
  • If you reset a worker node that has an additional data disk attached on the ECS console, the attachment will be removed. To keep the data, you need to reattach the disk.
  • The IP addresses of the workload pods on the node will change, but the container network access is not affected.
  • There is remaining EVS disk quota.
  • When a node is reset, the backend will make it unschedulable.
  • Resetting a node will clear the Kubernetes labels and taints you added (those added by editing a node pool will not be lost). As a result, node-specific resources (such as local storage and workloads scheduled to this node) may be unavailable.
  • Resetting a node will cause PVC/PV data loss for the local PV associated with the node. These PVCs and PVs cannot be restored or used again. In this scenario, the pod that uses the local PV is evicted from the node. A new pod is created and stays in the pending state. This is because the PVC used by the pod has a node label, due to which the pod cannot be scheduled. After the node is reset, the pod may be scheduled to the reset node. In this case, the pod remains in the creating state because the underlying logical volume corresponding to the PVC does not exist.

Resetting Nodes in the Default Pool

  1. Log in to the CCE console and click the cluster name to access the cluster console.
  2. In the navigation pane, choose Nodes. On the displayed page, click the Nodes tab.
  3. In the node list of the default pool, select one or more nodes to be reset and choose More > Reset Node in the Operation column.
  4. In the displayed dialog box, click Next.
  5. Specify node parameters.

    Compute Settings
    - @@ -87,7 +86,7 @@ @@ -107,7 +106,7 @@ - @@ -151,9 +150,9 @@ diff --git a/docs/cce/umn/cce_10_0007.html b/docs/cce/umn/cce_10_0007.html index d6606322a..58a09e8bc 100644 --- a/docs/cce/umn/cce_10_0007.html +++ b/docs/cce/umn/cce_10_0007.html @@ -105,7 +105,7 @@
    1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
    2. Click the Deployments tab and choose More > Disable/Enable Upgrade in the Operation column of the workload.
    3. In the dialog box that is displayed, click Yes.

    Managing Labels

    Labels are key-value pairs and can be attached to workloads. You can manage and select workloads by labels. You can add labels to multiple workloads or a specified workload.

    -
    1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
    2. Click the Deployments tab and choose More > Manage Label in the Operation column of the target workload.
    3. Click , enter a key and a value, and click OK.

      A key-value pair must contain 1 to 63 characters starting and ending with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.

      +
      1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
      2. Click the Deployments tab and choose More > Manage Label in the Operation column of the target workload.
      3. Click , enter a key and a value, and click OK.

        A key-value pair must contain 1 to 63 characters starting and ending with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.

      diff --git a/docs/cce/umn/cce_10_0009.html b/docs/cce/umn/cce_10_0009.html index 6caddac75..a6e865329 100644 --- a/docs/cce/umn/cce_10_0009.html +++ b/docs/cce/umn/cce_10_0009.html @@ -10,7 +10,7 @@

      Enter the username and password used to access the third-party image repository.

    4. When creating a workload, enter a private image path in the format of domainname/namespace/imagename:tag in Image Name and select the key created in 1.
    5. Set other parameters and click Create Workload.
    -

    Using kubectl

    1. Use kubectl to access the cluster. For details, see Connecting to a Cluster Using kubectl.
    2. Use kubectl to create a secret of the kubernetes.io/dockerconfigjson.

      kubectl create secret docker-registry myregistrykey  -n default --docker-server=DOCKER_REGISTRY_SERVER --docker-username=DOCKER_USER --docker-password=DOCKER_PASSWORD --docker-email=DOCKER_EMAIL
      +

      Using kubectl

      1. Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
      2. Use kubectl to create a secret of the kubernetes.io/dockerconfigjson.

        kubectl create secret docker-registry myregistrykey  -n default --docker-server=DOCKER_REGISTRY_SERVER --docker-username=DOCKER_USER --docker-password=DOCKER_PASSWORD --docker-email=DOCKER_EMAIL

        In the preceding command, myregistrykey indicates the key name, default indicates the namespace where the key is located, and other parameters are as follows:

        • DOCKER_REGISTRY_SERVER: address of a third-party image repository, for example, www.3rdregistry.com or 10.10.10.10:443
        • DOCKER_USER: account used for logging in to a third-party image repository
        • DOCKER_PASSWORD: password used for logging in to a third-party image repository
        • DOCKER_EMAIL: email of a third-party image repository

      3. Use a third-party image to create a workload.

        A kubernetes.io/dockerconfigjson secret is used for authentication when you obtain a private image. The following is an example of using the myregistrykey for authentication.
        apiVersion: v1
diff --git a/docs/cce/umn/cce_10_0010.html b/docs/cce/umn/cce_10_0010.html
index 4625ee7f8..956fe1d6c 100644
--- a/docs/cce/umn/cce_10_0010.html
+++ b/docs/cce/umn/cce_10_0010.html
@@ -4,11 +4,11 @@
 
        You can learn about a cluster network from the following two aspects:
        
 
        • What is a cluster network like? A cluster consists of multiple nodes, and pods (or containers) are running on the nodes. Nodes and containers need to communicate with each other. For details about the cluster network types and their functions, see Cluster Network Structure.
        • How is pod access implemented in a cluster? Accessing a pod or container is a process of accessing services of a user. Kubernetes provides Service and Ingress to address pod access issues. This section summarizes common network access scenarios. You can select the proper scenario based on site requirements. For details about the network access scenarios, see Access Scenarios.
        
 
        Cluster Network Structure
        All nodes in the cluster are located in a VPC and use the VPC network. The container network is managed by dedicated network add-ons.
        
-
        
-
        • Node Network
          A node network assigns IP addresses to hosts (nodes in the figure above) in a cluster. Select a VPC subnet as the node network of the CCE cluster. The number of available IP addresses in a subnet determines the maximum number of nodes (including master nodes and worker nodes) that can be created in a cluster. This quantity is also affected by the container network. For details, see the container network model.
          
+
          
+
          • Node Network
            A node network assigns IP addresses to hosts (nodes in the figure above) in a cluster. Select a VPC subnet as the node network of the CCE cluster. The number of available IP addresses in a subnet determines the maximum number of nodes (including master nodes and worker nodes) that can be created in a cluster. This number is also affected by the container network. For details, see the container network model.
            
 
          • Container Network
            A container network assigns IP addresses to pods in a cluster. CCE inherits the IP-Per-Pod-Per-Network network model of Kubernetes. That is, each pod has an independent IP address on a network plane and all containers in a pod share the same network namespace. All pods in a cluster exist in a directly connected flat network. They can access each other through their IP addresses without using NAT. Kubernetes only provides a network mechanism for pods, but does not directly configure pod networks. The configuration of pod networks is implemented by specific container network add-ons. The container network add-ons are responsible for configuring networks for pods and managing container IP addresses.
            
 
            Currently, CCE supports the following container network models:
            
-
            • Container tunnel network: The container tunnel network is constructed on but independent of the node network through tunnel encapsulation. This network model uses VXLAN to encapsulate Ethernet packets into UDP packets and transmits them in tunnels. Open vSwitch serves as the backend virtual switch.
            • VPC network: The VPC network model seamlessly combines VPC routing with the underlying network, making it ideal for high-performance scenarios. However, the maximum number of nodes allowed in a cluster is determined by the VPC route quota. Each node is assigned a CIDR block of a fixed size. The VPC network model outperforms the container tunnel network model in terms of performance because it does not have tunnel encapsulation overhead. In addition, as VPC routing includes routes to node IP addresses and the container CIDR block, container pods in a cluster can be directly accessed from outside the cluster.
            • Developed by CCE, Cloud Native 2.0 network deeply integrates Elastic Network Interfaces (ENIs) and Sub Network Interfaces (sub-ENIs) of VPC. Container IP addresses are allocated from the VPC CIDR block. ELB passthrough networking is supported to direct access requests to containers. Security groups and EIPs are bound to deliver high performance.
            
+
            • Container tunnel network: The container tunnel network is constructed on but independent of the node network through tunnel encapsulation. This network model uses VXLAN to encapsulate Ethernet packets into UDP packets and transmits them in tunnels. Open vSwitch serves as the backend virtual switch.
            • VPC network: The VPC network model seamlessly combines VPC routing with the underlying network, making it ideal for high-performance scenarios. However, the maximum number of nodes allowed in a cluster is determined by the VPC route quota. Each node is assigned a CIDR block of a fixed size. The VPC network model outperforms the container tunnel network model in terms of performance because it does not have tunnel encapsulation overhead. In addition, as VPC routing includes routes to node IP addresses and the container CIDR block, container pods in a cluster can be directly accessed from outside the cluster.
            • Developed by CCE, Cloud Native Network 2.0 deeply integrates Elastic Network Interfaces (ENIs) and Sub Network Interfaces (sub-ENIs) of VPC. Container IP addresses are allocated from the VPC CIDR block. ELB passthrough networking is supported to direct access requests to containers. Security groups and EIPs are bound to deliver high performance.
            
 
            The performance, networking scale, and application scenarios of a container network vary according to the container network model. For details about the functions and features of different container network models, see Overview.
            
 
          • Service Network
            Service is also a Kubernetes object. Each Service has a static IP address. When creating a cluster on CCE, you can specify the Service CIDR block. The Service CIDR block cannot overlap with the node or container CIDR block. The Service CIDR block can be used only within a cluster.
            
 
          
@@ -25,9 +25,9 @@
 
        
 
        Access Scenarios
        Workload access scenarios can be categorized as follows:
        
 
        • Intra-cluster access: A ClusterIP Service is used for workloads in the same cluster to access each other.
        • Access from outside a cluster: A Service (NodePort or LoadBalancer type) or an ingress is recommended for a workload outside a cluster to access workloads in the cluster.
          • Access through the public network: An EIP should be bound to the node or load balancer.
          • Access through the private network: The workload can be accessed through the internal IP address of the node or load balancer. If workloads are located in different VPCs, a peering connection is required to enable communication between different VPCs.
          
-
        • The workload can access the external network as follows:
          • Accessing an intranet: The workload accesses the intranet address, but the implementation method varies depending on container network models. Ensure that the peer security group allows the access requests from the container CIDR block.
          • Accessing a public network: Assign an EIP to the node where the workload runs (when the VPC network or tunnel network model is used), bind an EIP to the pod IP address (when the Cloud Native Network 2.0 model is used), or configure SNAT rules through the NAT gateway. For details, see Accessing the Internet from a Container.
          
+
        • The workload can access the external network as follows:
          • Accessing an intranet: The workload accesses the intranet address, but the implementation method varies depending on container network models. Ensure that the peer security group allows the access requests from the container CIDR block.
          • Accessing a public network: Assign an EIP to the node where the workload runs (when a VPC network or tunnel network is used), bind an EIP to the pod IP address (when Cloud Native Network 2.0 is used), or configure SNAT rules through the NAT gateway. For details, see Accessing the Internet from a Container.
          
 
        
-
        Figure 3 Network access diagram
        
+
        Figure 3 Network access diagram
        
 
        
 
        
 
        
diff --git a/docs/cce/umn/cce_10_0011.html b/docs/cce/umn/cce_10_0011.html
index 2399fdf9e..ec6803eb6 100644
--- a/docs/cce/umn/cce_10_0011.html
+++ b/docs/cce/umn/cce_10_0011.html
@@ -4,15 +4,15 @@
 
        Scenario
        ClusterIP Services allow workloads in the same cluster to use their cluster-internal domain names to access each other.
        
 
        The cluster-internal domain name format is <Service name>.<Namespace of the workload>.svc.cluster.local:<Port>, for example, nginx.default.svc.cluster.local:80.
        
 
        Figure 1 shows the mapping relationships between access channels, container ports, and access ports.
        
-
        Figure 1 Intra-cluster access (ClusterIP)
        
+
        Figure 1 Intra-cluster access (ClusterIP)
        
 
        
-
        Creating a ClusterIP Service
        1. Log in to the CCE console and click the cluster name to access the cluster console.
        2. In the navigation pane, choose Services & Ingresses. In the upper right corner, click Create Service.
        3. Configure intra-cluster access parameters.
          • Service Name: Specify a Service name, which can be the same as the workload name.
          • Service Type: Select ClusterIP.
          • Namespace: namespace that the workload belongs to.
          • Selector: Add a label and click Confirm. The Service will use this label to select pods. You can also click Reference Workload Label to use the label of an existing workload. In the dialog box that is displayed, select a workload and click OK.
          • Protocol Version: Select the IP address of different versions based on service requirements. This parameter is available only in clusters of v1.15 or later with IPv6 enabled (set during cluster creation).
          • Ports
            • Protocol: protocol used by the Service.
            • Service Port: port used by the Service. The port number ranges from 1 to 65535.
            • Container Port: listener port of the workload. For example, Nginx uses port 80 by default.
            
+
            Creating a ClusterIP Service
            1. Log in to the CCE console and click the cluster name to access the cluster console.
            2. In the navigation pane, choose Services & Ingresses. In the upper right corner, click Create Service.
            3. Configure intra-cluster access parameters.
              • Service Name: Specify a Service name, which can be the same as the workload name.
              • Service Type: Select ClusterIP.
              • Namespace: namespace that the workload belongs to.
              • Selector: Add a label and click Confirm. The Service will use this label to select pods. You can also click Reference Workload Label to use the label of an existing workload. In the dialog box that is displayed, select a workload and click OK.
              • Protocol Version: Select the IP address of different versions based on service requirements.  This parameter is available only in clusters of v1.15 or later with IPv6 enabled (set during cluster creation).
              • Ports
                • Protocol: protocol used by the Service.
                • Service Port: port used by the Service. The port number ranges from 1 to 65535.
                • Container Port: listener port of the workload. For example, Nginx uses port 80 by default.
                
 
              
 
            4. Click OK.
            
 
            
 
            Setting the Access Type Using kubectl
            You can configure Service access using kubectl. This section uses an Nginx workload as an example to describe how to implement intra-cluster access using kubectl.
            
-
            1. Use kubectl to access the cluster. For details, see Connecting to a Cluster Using kubectl.
            2. Create and edit the nginx-deployment.yaml and nginx-clusterip-svc.yaml files.
              The file names are user-defined. nginx-deployment.yaml and nginx-clusterip-svc.yaml are merely example file names.
              
-
              vi nginx-deployment.yaml
              apiVersion: apps/v1
+
              1. Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
              2. Create and edit the nginx-deployment.yaml file to configure the sample workload. For details, see Creating a Deployment. nginx-deployment.yaml is an example file name. You can rename it as needed.
                vi nginx-deployment.yaml
                
+
                File content:
                apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: nginx
@@ -32,7 +32,8 @@ spec:
       imagePullSecrets:
       - name: default-secret
                
 
                
-
                vi nginx-clusterip-svc.yaml
                apiVersion: v1
+
              3. Create and edit the nginx-clusterip-svc.yaml file to configure Service parameters. nginx-clusterip-svc.yaml is an example file name. You can rename it as needed.
                vi nginx-clusterip-svc.yaml
                
+
                File content:
                apiVersion: v1
 kind: Service
 metadata:
   labels:
@@ -41,36 +42,39 @@ metadata:
 spec:
   ports:
   - name: service0
-    port: 8080                # Port for accessing a Service.
+    port: 8080                # Port for accessing a Service
     protocol: TCP             # Protocol used for accessing a Service. The value can be TCP or UDP.
     targetPort: 80            # Port used by a Service to access the target container. This port is closely related to the applications running in a container. In this example, the Nginx image uses port 80 by default.
   selector:                   # Label selector. A Service selects a pod based on the label and forwards the requests for accessing the Service to the pod. In this example, select the pod with the app:nginx label.
     app: nginx
   type: ClusterIP             # Type of a Service. ClusterIP indicates that a Service is only reachable from within the cluster.
                
 
                
-
              4. Create a workload.
                kubectl create -f nginx-deployment.yaml
                
-
                If information similar to the following is displayed, the workload has been created.
                
-
                deployment "nginx" created
                
-
                kubectl get po
                
-
                If information similar to the following is displayed, the workload is running.
                
+
              5. Create a workload.
                kubectl create -f nginx-deployment.yaml
                
+
                If information similar to the following is displayed, the workload has been created:
                
+
                deployment/nginx created
                
+
                Check the created workload.
                
+
                kubectl get pod
                
+
                If information similar to the following is displayed, the workload is running:
                
 
                NAME                     READY     STATUS             RESTARTS   AGE
 nginx-2601814895-znhbr   1/1       Running            0          15s
                
-
              6. Create a Service.
                kubectl create -f nginx-clusterip-svc.yaml
                
+
              7. Create a Service.
                kubectl create -f nginx-clusterip-svc.yaml
                
 
                If information similar to the following is displayed, the Service is being created:
                
-
                service "nginx-clusterip" created
                
-
                kubectl get svc
                
+
                service/nginx-clusterip created
                
+
                Check the created Service.
                
+
                kubectl get svc
                
 
                If information similar to the following is displayed, the Service has been created, and a cluster-internal IP address has been assigned to the Service.
                
 
                # kubectl get svc
 NAME              TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE
 kubernetes        ClusterIP   10.247.0.1     <none>        443/TCP    4d6h
 nginx-clusterip   ClusterIP   10.247.74.52   <none>        8080/TCP   14m
                
-
              8. Access the Service.
                A Service can be accessed from containers or nodes in a cluster.
                
-
                Create a pod, access the pod, and run the curl command to access IP address:Port or the domain name of the Service, as shown in the following figure.
                
-
                The domain name suffix can be omitted. In the same namespace, you can directly use nginx-clusterip:8080 for access. In other namespaces, you can use nginx-clusterip.default:8080 for access.
                
-
                # kubectl run -i --tty --image nginx:alpine test --rm /bin/sh
-If you do not see a command prompt, try pressing Enter.
-/ # curl 10.247.74.52:8080
-<!DOCTYPE html>
+
              9. Access the Service from a container or node in the cluster.
                1. Create a pod and access its container.
                  kubectl run -i --tty --image nginx:alpine test --rm /bin/sh
                  
+
                2. Run the curl command to access the Service.
                  • Access through IP:Port:
                    curl 10.247.74.52:8080
                    
+
                  • Access through Domain-name:Port:
                    curl nginx-clusterip.default.svc.cluster.local:8080
                    
+
                    nginx-clusterip is the Service name, default is the namespace where the Service is located, and svc.cluster.local is the DNS domain for the ClusterIP Service.
                    
+
                    You can simplify the domain name based on your requirements. For example, if the Service and the accessing pod are in the same namespace, you can use nginx-clusterip:8080 to access it. If they are in different namespaces, you can use nginx-clusterip.default:8080 to access it.
                    
+
                  
+
                  If the access is successful, the following information will be displayed:
                  
+
                  <!DOCTYPE html>
 <html>
 <head>
 <title>Welcome to nginx!</title>
@@ -94,19 +98,8 @@ Commercial support is available at
 
 <p><em>Thank you for using nginx.</em></p>
 </body>
-</html>
-/ # curl nginx-clusterip.default.svc.cluster.local:8080
-...
-<h1>Welcome to nginx!</h1>
-...
-/ # curl nginx-clusterip.default:8080
-...
-<h1>Welcome to nginx!</h1>
-...
-/ # curl nginx-clusterip:8080
-...
-<h1>Welcome to nginx!</h1>
-...
                  
+</html>
              
+
            
 
        
 
        
 
        
diff --git a/docs/cce/umn/cce_10_0012.html b/docs/cce/umn/cce_10_0012.html
index 935ed1c66..956534554 100644
--- a/docs/cce/umn/cce_10_0012.html
+++ b/docs/cce/umn/cce_10_0012.html
@@ -5,21 +5,21 @@
 
        
 
        Procedure
        1. Log in to the CCE console.
        2. Click the cluster name to access the cluster console. Choose Nodes in the navigation pane. In the right pane, click the Node Pools tab.
        3. In the upper right corner of the page, click Create Node Pool.
          Basic Settings
          
 
-
    Table 1 Configuration parameters

    Parameter

    @@ -67,10 +67,9 @@

    Data Disk

    At least one data disk is required 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. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.

    -

    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 System Component Storage is set to System Disk, you have the option not to add the default data disk.

    -

    Click Expand to configure Data Disk Space Allocation, 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 Space Allocation of a Data Disk.

    -

    For other data disks, a raw disk is created without any processing by default. You can also click Expand and select Mount Disk to mount the data disk to a specified directory.

    +
    • At least one default data disk must be added for storing container runtime and kubelet components if System Component Storage is set to Data Disk. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable. This function is available for 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.
    • If System Component Storage is set to System Disk, you do not need to add a 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. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.
    +

    Click Expand to configure Data Disk Space Allocation. This allocates space for container engines, images, and ephemeral storage to ensure their proper running. For details about how to allocate data disk space, see Space Allocation of a Data Disk.

    +

    For other data disks, a raw disk is created without any processing by default. You can also click Expand and select Mount Disk to mount the data disk to a specified directory. Data disks can also be used as local PVs or local EVs.

    Resource Tag

    You can add resource tags to classify resources. A maximum of eight resource tags can be added.

    -

    You can create predefined tags 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.

    +

    You can create predefined tags on the TMS console. These tags are available to all resources that support tags. You can use these tags to improve the tag creation and resource migration efficiency.

    CCE will automatically create the CCE-Dynamic-Provisioning-Node=Node ID tag.

    Max. Pods

    Maximum number of pods that can run on the node, including the default system pods.

    +

    Maximum number of pods that can run on the node, including the default system pods.

    This limit prevents the node from being overloaded with pods.

    Data Disk

    Configure advanced settings for each data disk.

    -

    For the default data disk, click Expand to configure Data Disk Space Allocation, 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 Space Allocation of a Data Disk.

    -

    For a common data disk, click Expand and select attachment settings.

    -
    • Default: The data disk is attached as a raw disk without any settings.
    • Mount Disk: The data disk is attached to the service directory path. This parameter cannot be left blank or set to a key OS path such as the root directory.
    • Use as PV: The data disk is used as persistent storage volumes for PVCs. For details, see Local PVs.
    • Use as ephemeral volume: The data disk is used as ephemeral storage volumes for PVCs. For details, see Using a Local EV.
    +

    For the default data disk, click Expand to configure Data Disk Space Allocation. This allocates space for container engines, images, and ephemeral storage to ensure their proper running. For details about how to allocate data disk space, see Space Allocation of a Data Disk.

    +

    For a common data disk, click Expand and configure mount options.

    +
    • Default: The data disk is attached as a raw disk without any settings.
    • Mount Disk: The data disk is attached to the service directory path. This parameter cannot be left blank or set to a key OS path such as the root directory.
    • Use as PV: The data disk is used as persistent storage volumes for PVCs. For details, see Local PVs.
    • Use as ephemeral volume: The data disk is used as ephemeral storage volumes for PVCs. For details, see Local EV.
    - @@ -189,7 +189,7 @@ spec: 
    Hello

    Using kubectl

    -
    1. Use kubectl to access the cluster. For details, see Connecting to a Cluster Using kubectl.
    2. Create a file named nginx-configmap.yaml and edit it.

      vi nginx-configmap.yaml

      +
      1. Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
      2. Create a file named nginx-configmap.yaml and edit it.

        vi nginx-configmap.yaml

        As shown in the following example, after the ConfigMap volume is mounted, a configuration file with the key as the file name and value as the file content is generated in the /etc/config directory of the container.

        apiVersion: apps/v1
 kind: Deployment
@@ -216,7 +216,7 @@ spec:
     - name: config-volume
       configMap:
         name: cce-configmap                 # Name of the referenced ConfigMap.
        -

      3. Create a workload.

        kubectl apply -f nginx-configmap.yaml

        +

      4. Create a workload.

        kubectl apply -f nginx-configmap.yaml

      5. After the workload runs properly, the SPECIAL_LEVEL and SPECIAL_TYPE files will be generated in the /etc/config directory. The contents of the files are Hello and CCE, respectively.

        1. Run the following command to view the created pod:
          kubectl get pod | grep nginx-configmap
          Expected output:
          nginx-configmap-***   1/1     Running   0              2m18s
          diff --git a/docs/cce/umn/cce_10_0016.html b/docs/cce/umn/cce_10_0016.html index 9710f1821..a3e802071 100644 --- a/docs/cce/umn/cce_10_0016.html +++ b/docs/cce/umn/cce_10_0016.html @@ -28,7 +28,7 @@ data:

          If the output is the same as the content in the secret, the secret has been set as an environment variable of the workload.

        Using kubectl

        -
        1. Use kubectl to access the cluster. For details, see Connecting to a Cluster Using kubectl.
        2. Create a file named nginx-secret.yaml and edit it.

          vi nginx-secret.yaml

          +
          1. Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
          2. Create a file named nginx-secret.yaml and edit it.

            vi nginx-secret.yaml

            Content of the YAML file:

            • Added from secret: To add all data in a secret to environment variables, use the envFrom parameter. The keys in the secret will become names of environment variables in a workload.
              apiVersion: apps/v1
 kind: Deployment
@@ -83,7 +83,7 @@ spec:
       imagePullSecrets:
       - name: default-secret
            -

          3. Create a workload.

            kubectl apply -f nginx-secret.yaml

            +

          4. Create a workload.

            kubectl apply -f nginx-secret.yaml

          5. View the environment variables in the pod.

            1. Run the following command to view the created pod:
              kubectl get pod | grep nginx-secret
              Expected output:
              nginx-secret-***   1/1     Running   0              2m18s
              @@ -119,7 +119,7 @@ spec:
    Table 1 Basic settings

    Parameter

    +
    - - -
    Table 1 Basic settings

    Parameter

    Description

    +

    Description

    Node Pool Name

    +

    Node Pool Name

    Name of a node pool. By default, the name is in the format of Cluster name-nodepool-Random number. If you do not want to use the default name format, you can customize the name.

    +

    Name of a node pool. By default, the name is in the format of Cluster name-nodepool-Random number. If you do not want to use the default name format, you can customize the name.
    -

    Configurations

    +

    Node Configuration

    You can configure the flavor and OS of a cloud server, on which your containerized applications run.
    @@ -30,15 +30,15 @@ - @@ -78,7 +78,7 @@ @@ -92,22 +92,21 @@ - @@ -122,7 +121,7 @@ - @@ -162,7 +161,7 @@ @@ -240,7 +239,7 @@
    Table 2 Node configuration parameters

    Parameter

    Node Type

    Select a node type based on service requirements. Then, you can select a proper flavor from the node flavor list.

    -
    CCE standard clusters support the following node types:
    • ECS (VM): A virtualized ECS is used as a cluster node.
    +
    CCE standard clusters support the following node types:
    • ECS (VM): A virtualized ECS is used as a cluster node.
    -
    CCE Turbo clusters support the following node types:
    • ECS (VM): A virtualized ECS is used as a cluster node. A CCE Turbo cluster supports only the cloud servers that allow multiple ENIs. Select a server type displayed on the CCE console.
    +
    CCE Turbo clusters support the following node types:
    • ECS (VM): A VM ECS is used as a cluster node. A CCE Turbo cluster supports only the cloud servers that allow multiple ENIs. Select a server type displayed on the CCE console.

    Specifications

    Select a node flavor based on service requirements. The available node flavors vary depending on regions or AZs. For details, see the CCE console. For the supported node flavors, see Node Flavor Description.
    NOTE:
    • If a node pool is configured with multiple node flavors, only the flavors (which can be located in different AZs) of the same node type are supported. For example, a node pool consisting of general computing-plus nodes supports only general computing-plus node flavors, but not the flavors of general computing nodes.
    • A maximum of 10 node flavors can be added to a node pool (the flavors in different AZs are counted separately). When adding a node flavor, you can choose multiple AZs, but you need to specify them.
    • Nodes in a newly created node pool are created using the default flavor. If the resources for the default flavor are insufficient, node creation will fail.
    • After a node pool is created, the flavors of existing nodes cannot be deleted.
    +
    Select a node flavor based on service requirements. The available node flavors vary depending on regions. For details, see the CCE console. For the supported node flavors, see Node Flavor Description.
    NOTE:
    • If a node pool is configured with multiple node flavors, only the flavors (which can be located in different AZs) of the same node type are supported. For example, a node pool consisting of general computing-plus nodes supports only general computing-plus node flavors, but not the flavors of general computing nodes.
    • A maximum of 10 node flavors can be added to a node pool (the flavors in different AZs are counted separately). When adding a node flavor, you can choose multiple AZs, but you need to specify them.
    • Nodes in a newly created node pool are created using the default flavor. If the resources for the default flavor are insufficient, node creation will fail.
    • After a node pool is created, the flavors of existing nodes cannot be deleted.

    System Disk

    System disk used by the node OS. The value ranges from 40 GiB to 1024 GiB. The default value is 50 GiB.

    -
    System Disk Encryption: System disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. Only the nodes of the Elastic Cloud Server (VM) type in certain regions support system disk encryption. For details, see the console.
    • Not encrypted is selected by default.
    • If you select Enabled (key) for System Disk Encryption, choose an existing key. If no key is available, click View Key List and create a key. After the key is created, click the refresh icon next to the text box.
    • If you select Enabled (KMS key ID) for System Disk Encryption, enter a KMS key (which can be shared by others) in the current region.
    +
    System Disk Encryption: System disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. Only the nodes of the Elastic Cloud Server (VM) type in certain regions support system disk encryption. For details, see the console.
    • Not encrypted is selected by default.
    • If you select Enabled (key) for System Disk Encryption, choose an existing key. If no key is available, click View Key List and create a key. After the key is created, click the refresh icon next to the text box.
    • If you select Enabled (KMS key ID) for System Disk Encryption, enter a KMS key (which can be shared by others) in the current region.

    Data Disk

    At least one data disk is required 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. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.
    • 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.
    • 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.
    -
    -

    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 System Component Storage is set to System Disk, 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.

    +
    • At least one default data disk must be added for storing container runtime and kubelet components if System Component Storage is set to Data Disk. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable. This function is available for 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.
      • 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.
      • 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.
      +
    • If System Component Storage is set to System Disk, you do not need to add a 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. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.
    NOTE:
    • If the node flavor is disk-intensive or ultra-high I/O, one data disk can be a local disk.
    • 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.

    Advanced Settings

    -

    Expand the area and configure the following parameters:

    -
    • Data Disk Space Allocation: allocates space for container engines, images, and ephemeral storage for them to run properly. For details about how to allocate data disk space, see Space Allocation of a Data Disk.
    • Data Disk Encryption: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting.
      • Not encrypted is selected by default.
      • If you select Enabled (key) for Data Disk Encryption, choose an existing key. If no key is available, click View Key List and create a key. After the key is created, click the refresh icon next to the text box.
      • If you select Enabled (KMS key ID) for Data Disk Encryption, enter a KMS key (which can be shared by others) in the current region.
      +

      Expand the area and configure the following parameters:

      +
      • Data Disk Space Allocation: allocates space for container engines, images, and ephemeral storage for them to run properly. For details about how to allocate data disk space, see Space Allocation of a Data Disk.
      • Data Disk Encryption: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting.
        • Not encrypted is selected by default.
        • If you select Enabled (key) for Data Disk Encryption, choose an existing key. If no key is available, click View Key List and create a key. After the key is created, click the refresh icon next to the text box.
        • If you select Enabled (KMS key ID) for Data Disk Encryption, enter a KMS key (which can be shared by others) in the current region.
      -

      Adding data disks

      +

      Adding data disks

      A maximum of 16 data disks can be attached to an ECS. By default, a raw disk is created without any processing. You can also click Expand and select any of the following options:

      • Default: By default, a raw disk is created without any processing.
      • Mount Disk: The data disk is attached to a specified directory.
      • Use as PV: applicable when there is a high performance requirement on PVs. The node.kubernetes.io/local-storage-persistent label is added to the node with PV configured. The value is linear or striped.
      • Use as ephemeral volume: applicable when there is a high performance requirement on emptyDir.
      -
      NOTE:
      • Local PVs are supported only when the cluster version is v1.21.2-r0 or later and the Everest add-on version is 2.1.23 or later. Version 2.1.23 or later is recommended.
      • Local EVs are supported only when the cluster version is v1.21.2-r0 or later and the Everest add-on version is 1.2.29 or later.
      +

      PVs and EVs support the following write modes:

      +
      • Linear: 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.
      • Striped: 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. This option can be selected only when there are multiple volumes.
      +
      NOTE:
      • Local PVs are supported only when the cluster version is v1.21.2-r0 or later and the Everest add-on version is 2.1.23 or later. Version 2.1.23 or later is recommended.
      • Local EVs are supported only when the cluster version is v1.21.2-r0 or later and the Everest add-on version is 1.2.29 or later.
      -
      Local PVs and local EVs can be written in the following modes:
      • Linear: 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.
      • Striped: 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. This option can be selected only when multiple volumes exist.
      -

    Virtual Private Cloud

    +

    VPC

    The VPC to which the cluster belongs by default, which cannot be changed.

    Resource Tag

    You can add resource tags to classify resources.

    -

    You can create predefined tags 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.

    +

    You can create predefined tags on the TMS console. These tags are available to all resources that support tags. You can use these tags to improve the tag creation and resource migration efficiency.

    CCE will automatically create the "CCE-Dynamic-Provisioning-Node=Node ID" tag.
    -

  6. Click Next: Confirm.
  7. Click Submit.
    8. +

  8. Click Next: Confirm.
  9. Click Submit.
    10. diff --git a/docs/cce/umn/cce_10_0014.html b/docs/cce/umn/cce_10_0014.html index 411149513..9166892a1 100644 --- a/docs/cce/umn/cce_10_0014.html +++ b/docs/cce/umn/cce_10_0014.html @@ -18,13 +18,13 @@
  10. Configuring a Blocklist/Trustlist Access Policy for a LoadBalancer Service
    11. -
  11. Configuring Health Check on Multiple Ports of a LoadBalancer Service
    +
  12. Configuring Health Check on Multiple LoadBalancer Service Ports
  13. Configuring Passthrough Networking for a LoadBalancer Service
  14. Enabling a LoadBalancer Service to Obtain the Client IP Address
    15. -
  15. Configuring a Custom EIP for a LoadBalancer Service
    +
  16. Changing a Custom EIP for a LoadBalancer Service
  17. Setting the Pod Ready Status Through the ELB Health Check
    18. diff --git a/docs/cce/umn/cce_10_0015.html b/docs/cce/umn/cce_10_0015.html index 58fd588c4..9bb53d52f 100644 --- a/docs/cce/umn/cce_10_0015.html +++ b/docs/cce/umn/cce_10_0015.html @@ -2,7 +2,7 @@

    Using a ConfigMap

    After a ConfigMap is created, it can be used in three workload scenarios: environment variables, command line parameters, and data volumes.

    - +

    The following example shows how to use a ConfigMap.

    apiVersion: v1
 kind: ConfigMap
@@ -15,17 +15,17 @@ data:
 
  18. When a ConfigMap is used as an environment variable, data is not automatically updated when the ConfigMap is updated. To update the data, restart the pod.
    19.

    Configuring Environment Variables of a Workload

    Using the CCE console

    -
    1. Log in to the CCE console and click the cluster name to access the cluster console.
    2. In the navigation pane, choose Workloads. Then, click Create Workload in the upper right corner.

      When creating a workload, click Environment Variables in the Container Settings area, and click Add Variable.

      +
      1. Log in to the CCE console and click the cluster name to access the cluster console.
      2. In the navigation pane, choose Workloads. In the dialog box displayed, click Create Workload in the upper right corner.

        When creating a workload, click Environment Variables in the Container Settings area, and click Add Variable.

        • Added from ConfigMap: Select a ConfigMap to import all of its keys as environment variables.
        • Added from ConfigMap key: Import a key in a ConfigMap as the value of an environment variable.
          • Variable Name: name of an environment variable in the workload. The name can be customized and is set to the key name selected in the ConfigMap by default.
          • Variable Value/Reference: Select a ConfigMap and the key to be imported. The corresponding value is imported as a workload environment variable.

          For example, after you import the value Hello of SPECIAL_LEVEL in ConfigMap cce-configmap as the value of workload environment variable SPECIAL_LEVEL, an environment variable named SPECIAL_LEVEL with its value Hello exists in the container.

      3. Configure other workload parameters and click Create Workload.

        After the workload runs properly, log in to the container and run the following statement to check whether the ConfigMap has been set as an environment variable of the workload:

        printenv SPECIAL_LEVEL
        -

        The example output is as follows:

        +

        Example output:

        Hello

      Using kubectl

      -
      1. Use kubectl to access the cluster. For details, see Connecting to a Cluster Using kubectl.
      2. Create a file named nginx-configmap.yaml and edit it.

        vi nginx-configmap.yaml

        +
        1. Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
        2. Create a file named nginx-configmap.yaml and edit it.

          vi nginx-configmap.yaml

          Content of the YAML file:

          • Added from ConfigMap: To add all data in a ConfigMap to environment variables, use the envFrom parameter. The keys in the ConfigMap will become names of environment variables in the workload.
            apiVersion: apps/v1
 kind: Deployment
@@ -68,7 +68,7 @@ spec:
         image: nginx:latest
         env:                             # Set the environment variable in the workload.
         - name: SPECIAL_LEVEL           # Name of the environment variable in the workload.
-          valueFrom:                    # Specify a ConfigMap to be referenced by the environment variable.
+          valueFrom:                    # Use valueFrom to specify a ConfigMap to be referenced by environment variables.
             configMapKeyRef:
               name: cce-configmap       # Name of the referenced ConfigMap.
               key: SPECIAL_LEVEL        # Key in the referenced ConfigMap.
@@ -80,7 +80,7 @@ spec:
       imagePullSecrets:
       - name: default-secret
          -

        3. Create a workload.

          kubectl apply -f nginx-configmap.yaml

          +

        4. Create a workload.

          kubectl apply -f nginx-configmap.yaml

        5. View the environment variables in the pod.

          1. Run the following command to view the created pod:
            kubectl get pod | grep nginx-configmap
            Expected output:
            nginx-configmap-***   1/1     Running   0              2m18s
            @@ -102,11 +102,11 @@ echo $SPECIAL_LEVEL $SPECIAL_TYPE > /usr/share/nginx/html/index.html

          2. Configure other workload parameters and click Create Workload.

            After the workload runs properly, log in to the container and run the following statement to check whether the ConfigMap has been set as an environment variable of the workload:

            cat /usr/share/nginx/html/index.html
            -

            The example output is as follows:

            +

            Example output:

            Hello CCE

          Using kubectl

          -
          1. Use kubectl to access the cluster. For details, see Connecting to a Cluster Using kubectl.
          2. Create a file named nginx-configmap.yaml and edit it.

            vi nginx-configmap.yaml

            +
            1. Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
            2. Create a file named nginx-configmap.yaml and edit it.

              vi nginx-configmap.yaml
              In the following example, the cce-configmap ConfigMap is imported to the workload. SPECIAL_LEVEL and SPECIAL_TYPE are the environment variable names in the workload, which are key names in the cce-configmap ConfigMap.
              apiVersion: apps/v1
 kind: Deployment
 metadata:
@@ -134,7 +134,7 @@ spec:
       imagePullSecrets:
         - name: default-secret
              -

            3. Create a workload.

              kubectl apply -f nginx-configmap.yaml

              +

            4. Create a workload.

              kubectl apply -f nginx-configmap.yaml

            5. Wait until the workload runs properly. Then, data will be added the /usr/share/nginx/html/index.html file in the container.

              1. Run the following command to view the created pod:
                kubectl get pod | grep nginx-configmap
                Expected output:
                nginx-configmap-***   1/1     Running   0              2m18s
                @@ -144,7 +144,7 @@ spec:

    -

    Mounting a ConfigMap to the Workload Data Volume

    The data stored in a ConfigMap can be referenced in a volume of type ConfigMap. You can mount such a volume to a specified container path. The platform supports the separation of workload codes and configuration files. ConfigMap volumes are used to store workload configuration parameters. Before that, create ConfigMaps in advance. For details, see Creating a ConfigMap.

    +

    Mounting a ConfigMap to a Workload Data Volume

    The data stored in a ConfigMap can be referenced in a volume of type ConfigMap. You can mount such a volume to a specified container path. The platform supports the separation of workload codes and configuration files. ConfigMap volumes are used to store workload configuration parameters. Before that, create ConfigMaps in advance. For details, see Creating a ConfigMap.

    Using the CCE console

    1. Log in to the CCE console and click the cluster name to access the cluster console.
    2. In the navigation pane, choose Workloads. In the dialog box displayed, click Create Workload in the upper right corner.

      When creating a workload, click Data Storage in the Container Settings area. Click Add Volume and select ConfigMap from the drop-down list.

    3. Select parameters for mounting a ConfigMap volume, as shown in Table 1.

      @@ -163,14 +163,14 @@ spec:

    Mount Path

    Enter a mount path. After the ConfigMap volume is mounted, a configuration file with the key as the file name and value as the file content is generated in the mount path of the container.

    -
    This parameter specifies a container path to which a data volume will be mounted. Do not mount the volume to a system directory such as / or /var/run. This may lead to container errors. Mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. Otherwise, the files will be replaced, leading to container startup failures or workload creation failures.
    NOTICE:

    If the container is mounted to a high-risk directory, use an account with minimum permissions to start the container. Otherwise, high-risk files on the host may be damaged.

    +
    This parameter specifies a container path to which a data volume will be mounted. Do not mount the volume to a system directory such as / or /var/run. This may lead to container errors. Mount the volume to an empty directory. If the directory is not empty, ensure that there are no files that affect container startup. Otherwise, the files will be replaced, leading to container startup failures or workload creation failures.
    NOTICE:

    If a volume is mounted to a high-risk directory, use an account with minimum permissions to start the container. Otherwise, high-risk files on the host may be damaged.

    Subpath

    Enter a subpath of the mount path.
    • A subpath is used to mount a local volume so that the same data volume is used in a single pod. If this parameter is left blank, the root path will be used by default.
    • The subpath can be the key and value of a ConfigMap or secret. If the subpath is a key-value pair that does not exist, the data import does not take effect.
    • The data imported by specifying a subpath will not be updated along with the ConfigMap/secret updates.
    +
    Enter a subpath of the mount path.
    • A subpath is used to mount a local volume so that the same data volume is used in a single pod. If this parameter is left blank, the root path will be used by default.
    • The subpath can be the key and value of a ConfigMap. If the subpath is a key-value pair that does not exist, the data import does not take effect.
    • The data imported by specifying a subpath will not be updated along with the ConfigMap updates.

    Subpath

    Enter a subpath of the mount path.

    -
    • A subpath is used to mount a local volume so that the same data volume is used in a single pod. If this parameter is left blank, the root path will be used by default.
    • The subpath can be the key and value of a ConfigMap or secret. If the subpath is a key-value pair that does not exist, the data import does not take effect.
    • The data imported by specifying a subpath will not be updated along with the ConfigMap/secret updates.
    +
    • A subpath is used to mount a local volume so that the same data volume is used in a single pod. If this parameter is left blank, the root path will be used by default.
    • The subpath can be the key and value of a secret. If the subpath is a key-value pair that does not exist, the data import does not take effect.
    • The data imported by specifying a subpath will not be updated along with the secret updates.

    Permission

    @@ -136,7 +136,7 @@ spec:

    The expected output is the same as the content in the secret.

    Using kubectl

    -
    1. Use kubectl to access the cluster. For details, see Connecting to a Cluster Using kubectl.
    2. Create a file named nginx-secret.yaml and edit it.

      vi nginx-secret.yaml

      +
      1. Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
      2. Create a file named nginx-secret.yaml and edit it.

        vi nginx-secret.yaml
        In the following example, the username and password in the mysecret secret are saved in the /etc/foo directory as files.
        apiVersion: apps/v1
 kind: Deployment
 metadata:
@@ -155,15 +155,15 @@ spec:
       - name: container-1
         image: nginx:latest
         volumeMounts:
-       - name: foo
+        - name: foo
          mountPath: /etc/foo          # Mount to the /etc/foo directory.
-         readOnly: true
+          readOnly: true
     volumes:
     - name: foo
       secret:
         secretName: mysecret      # Name of the referenced secret.
        -
        You can also use the items field to control the mapping path of secret keys. For example, store username in the /etc/foo/my-group/my-username directory in the container.
        • If you use the items field to specify the mapping path of the secret keys, the keys that are not specified will not be created as files. For example, if the password key in the following example is not specified, the file will not be created.
        • If you want to use all keys in a secret, you must list all keys in the items field.
        • All keys listed in the items field must exist in the corresponding secret. Otherwise, the volume is not created.
        +
        You can also use the items field to control the mapping path of secret keys. For example, store username in the /etc/foo/my-group/my-username directory in the container.
        • If you use the items field to specify the mapping path of the secret keys, the keys that are not specified will not be created as files. For example, if the password key in the following example is not specified, the file will not be created.
        • If you want to use all keys in a secret, you must list all keys in the items field.
        • All keys listed in items must exist in target secrets. Otherwise, the volume is not created.
        apiVersion: apps/v1
 kind: Deployment
@@ -183,9 +183,9 @@ spec:
       - name: container-1
         image: nginx:latest
         volumeMounts:
-       - name: foo
+        - name: foo
          mountPath: /etc/foo          # Mount to the /etc/foo directory.
-         readOnly: true
+          readOnly: true
     volumes:
     - name: foo
       secret:
@@ -194,8 +194,8 @@ spec:
         - key: username      # Name of the referenced key.
           path: my-group/my-username    # Mapping path of the secret key
        -

      3. Create a workload.

        kubectl apply -f nginx-secret.yaml

        -

      4. After the workload runs properly, the username and password files are generated in the /etc/foo directory.

        1. Run the following command to view the created pod:
          kubectl get pod | grep nginx-secret
          +

        2. Create a workload.

          kubectl apply -f nginx-secret.yaml
          +

        3. After the workload runs properly, the username and password files will be generated in the /etc/foo directory.

          1. Run the following command to view the created pod:
            kubectl get pod | grep nginx-secret
            Expected output:
            nginx-secret-***   1/1     Running   0              2m18s
          2. Run the following command to view the username or password file in the pod:
            kubectl exec nginx-secret-*** -- cat /etc/foo/username
            diff --git a/docs/cce/umn/cce_10_0018.html b/docs/cce/umn/cce_10_0018.html index 823f4216d..a74b5b756 100644 --- a/docs/cce/umn/cce_10_0018.html +++ b/docs/cce/umn/cce_10_0018.html @@ -4,7 +4,7 @@

            CCE works with AOM to collect workload logs. When a node is created, ICAgent (a DaemonSet named icagent in the kube-system namespace of a cluster) of AOM is installed by default. ICAgent collects workload logs and reports them to AOM. You can view workload logs on the CCE or AOM console.

            Constraints

            ICAgent only collects text logs in .log, .trace, and .out formats.

            -

            Using ICAgent to Collect Logs

            1. When creating a workload, set logging for the container.
            2. Click to add a log policy.

              The following uses Nginx as an example. Log policies vary depending on workloads.

              +

              Using ICAgent to Collect Logs

              1. When creating a workload, set logging for the container.
              2. Click to add a log policy.

                The following uses Nginx as an example. Log policies vary depending on workloads.

              3. Set Volume Type to hostPath or emptyDir.

                @@ -42,7 +42,7 @@ @@ -154,8 +154,8 @@ spec: @@ -173,9 +173,9 @@ spec: diff --git a/docs/cce/umn/cce_10_0024.html b/docs/cce/umn/cce_10_0024.html index ca7e88caf..02f5f7fc4 100644 --- a/docs/cce/umn/cce_10_0024.html +++ b/docs/cce/umn/cce_10_0024.html @@ -11,7 +11,7 @@
                -
                Parent topic: Observability
                +
                Parent topic: O&M
                diff --git a/docs/cce/umn/cce_10_0026.html b/docs/cce/umn/cce_10_0026.html index 5605aa3ac..4ce73e548 100644 --- a/docs/cce/umn/cce_10_0026.html +++ b/docs/cce/umn/cce_10_0026.html @@ -1,13 +1,11 @@

                Viewing CTS Traces in the Trace List

                -

                Scenarios

                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.

                -

                These operation records are retained for seven days on the CTS console and are automatically deleted upon expiration. Manual deletion is not supported.

                -
                +

                Scenarios

                After you enable Cloud Trace Service (CTS) and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records (traces) generated in the last seven days.

                -

                Viewing Real-Time Traces

                1. Log in to the management console.
                2. Click in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
                3. Choose Trace List in the navigation pane on the left.
                4. Set filters to search for your desired traces, as shown in Figure 1. The following filters are available.
                  Figure 1 Filters
                  +

                  Viewing Real-Time Traces in the Trace List

                  1. Log in to the management console.
                  2. Click in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
                  3. Choose Trace List in the navigation pane on the left.
                  4. Set filters to search for your desired traces, as shown in Figure 1. The following filters are available.
                    Figure 1 Filters
                    • Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
                      • If you select Resource ID for Search By, specify a resource ID.
                      • If you select Trace name for Search By, specify a trace name.
                      • If you select Resource name for Search By, specify a resource name.
                      -
                    • Operator: Select a user.
                    • Trace Status: Select All trace statuses, Normal, Warning, or Incident.
                    • Time range: Select Last 1 hour, Last 1 day, or Last 1 week, or specify a custom time range within the last seven days.
                    +
                  5. Operator: Select a user.
                  6. Trace Status: Select All trace statuses, Normal, Warning, or Incident.
                  7. Time range: Select Last 1 hour, Last 1 day, or Last 1 week, or specify a custom time range within the last seven days.
                5. Click Query.
                6. On the Trace List page, you can also export and refresh the trace list.
                  • Click Export to export all traces in the query result as a CSV file. The file can contain up to 5,000 records.
                  • Click to view the latest information about traces.
                7. Click on the left of a trace to expand its details.

                  @@ -16,7 +14,7 @@

                8. Click View Trace in the Operation column. The trace details are displayed.

                  -
                9. For details about key fields in the trace structure, see section "Trace References" > "Trace Structure" and section "Trace References" > "Example Traces" in the CTS User Guide.
                +
              4. For details about key fields in the trace structure, see Trace Structure and Example Traces in the CTS User Guide.
                5. diff --git a/docs/cce/umn/cce_10_0028.html b/docs/cce/umn/cce_10_0028.html index 400b47ffd..cf61cb744 100644 --- a/docs/cce/umn/cce_10_0028.html +++ b/docs/cce/umn/cce_10_0028.html @@ -5,43 +5,44 @@

                Precautions

                • After a cluster is created, the following items cannot be changed:
                  • Cluster type
                  • Number of master nodes in the cluster
                  • AZ of a master node
                  • Network configurations of the cluster, such as the VPC, subnet, Service CIDR block, IPv6 settings, and kube-proxy settings
                  • Network model. For example, change Tunnel network to VPC network.
                -

                Step 1: Log In to the CCE Console

                1. Log in to the CCE console.
                2. On the Clusters page, click Create Cluster in the upper right corner.
                +

                Step 1: Log In to the CCE Console

                1. Log in to the CCE console.
                2. On the Clusters page, click Create Cluster.
                -

                Step 2: Configure the Cluster

                On the Create Cluster page, configure the parameters.

                +

                Step 2: Configure the Cluster

                On the Create Cluster page, configure the parameters.

                Basic Settings

                +

                -
                Table 1 Configuring log policies

                Parameter

                A collection path narrows down the scope of collection to specified logs.

                • If no collection path is specified, log files in .log, .trace, and .out formats will be collected from the specified path.
                • /Path/**/ indicates that all log files in .log, .trace, and .out formats will be recursively collected from the specified path and all subdirectories at 5 levels deep.
                • * in log file names indicates a fuzzy match.

                Example: The collection path /tmp/**/test*.log indicates that all .log files prefixed with test will be collected from /tmp and subdirectories at 5 levels deep.

                -
                CAUTION:

                Ensure that ICAgent is of v5.12.22 or later.

                +
                CAUTION:

                Ensure that ICAgent is of version 5.12.22 or later.

                Extended host path

                Extended host paths contain pod IDs or container names to distinguish different containers into which the host path is mounted.

                -

                A level-3 directory is added to the original volume directory/subdirectory. You can easily obtain the files output by a single Pod.

                -
                • None: No extended path is configured.
                • PodUID: ID of a pod.
                • PodName: name of a pod.
                • PodUID/ContainerName: ID of a pod or name of a container.
                • PodName/ContainerName: name of a pod or container.
                +

                A level-3 directory is added to the original volume directory/subdirectory. You can easily obtain the files output by a single Pod.

                +
                • None: No extended path is configured.
                • PodUID: ID of a pod.
                • PodName: name of a pod.
                • PodUID/ContainerName: ID of a pod or name of a container.
                • PodName/ContainerName: name of a pod or container.

                policy.logs.rotate

                @@ -163,7 +163,7 @@ spec:

                Log dump

                Log dump refers to rotating log files on a local host.

                -
                • Enabled: AOM scans log files every minute. When a log file exceeds 50 MB, it is dumped immediately. A new .zip file is generated in the directory where the log file locates. For a log file, AOM stores only the latest 20 .zip files. When the number of .zip files exceeds 20, earlier .zip files will be deleted. After the dump is complete, the log file in AOM will be cleared.
                • Disabled: AOM does not dump log files.
                +
                • Enabled: AOM scans log files every minute. When a log file exceeds 50 MB, it is dumped immediately. A new .zip file is generated in the directory where the log file locates. For a log file, AOM stores only the latest 20 .zip files. When the number of .zip files exceeds 20, earlier .zip files will be deleted. After the dump is complete, the log file in AOM will be cleared.
                • Disabled: AOM does not dump log files.
                NOTE:
                • AOM rotates log files using copytruncate. Before enabling log dumping, ensure that log files are written in the append mode. Otherwise, file holes may occur.
                • Currently, mainstream log components such as Log4j and Logback support log file rotation. If you have already set rotation for log files, skip the configuration. Otherwise, conflicts may occur.
                • You are advised to configure log file rotation for your own services to flexibly control the size and number of rolled files.

                Collection path

                A collection path narrows down the scope of collection to specified logs.

                -
                • If no collection path is specified, log files in .log, .trace, and .out formats will be collected from the specified path.
                • /Path/**/ indicates that all log files in .log, .trace, and .out formats will be recursively collected from the specified path and all subdirectories at 5 levels deep.
                • * in log file names indicates a fuzzy match.
                +
                • If no collection path is specified, log files in .log, .trace, and .out formats will be collected from the specified path.
                • /Path/**/ indicates that all log files in .log, .trace, and .out formats will be recursively collected from the specified path and all subdirectories at 5 levels deep.
                • * in log file names indicates a fuzzy match.

                Example: The collection path /tmp/**/test*.log indicates that all .log files prefixed with test will be collected from /tmp and subdirectories at 5 levels deep.

                -
                CAUTION:

                Ensure that ICAgent is of v5.12.22 or later.

                +
                CAUTION:

                Ensure that ICAgent is of version 5.12.22 or later.

                Parameter

                +
                - - - - - - - - - - -

                Parameter

                Description

                +

                Description

                Type

                +

                Type

                Select CCE Standard Cluster or CCE Turbo Cluster as required.

                +

                Select CCE Standard Cluster or CCE Turbo Cluster as required.

                • CCE standard clusters provide highly reliable and secure containers for commercial use.
                • CCE Turbo clusters use the high-performance cloud native network. Such clusters provide cloud native hybrid scheduling, achieving higher resource utilization and wider scenario coverage.

                For more details, see cluster types.

                Cluster Name

                +

                Cluster Name

                Enter a cluster name. Cluster names under the same account must be unique.

                +

                Enter a cluster name. Cluster names under the same account must be unique.

                Cluster Version

                +

                Cluster Version

                Select the Kubernetes version used by the cluster.

                +

                Select the Kubernetes version used by the cluster.

                Cluster Scale

                +

                Cluster Scale

                Select a cluster scale for your cluster as required. These values specify the maximum number of nodes that can be managed by the cluster.

                +

                Select a cluster scale for your cluster as required. These values specify the maximum number of nodes that can be managed by the cluster.

                Master Nodes

                +

                Master Nodes

                Select the number of master nodes. The master nodes are automatically hosted by CCE and deployed with Kubernetes cluster management components such as kube-apiserver, kube-controller-manager, and kube-scheduler.

                -
                • Multiple: Three master nodes will be created for high cluster availability.
                • Single: Only one master node will be created in your cluster.
                  NOTE:
                  • If more than half of the master nodes in a cluster are faulty, the cluster will not run properly.
                  +

                Select the number of master nodes. The master nodes are automatically hosted by CCE and deployed with Kubernetes cluster management components such as kube-apiserver, kube-controller-manager, and kube-scheduler.

                +
                • 3 Masters: Three master nodes will be created for high cluster availability.
                • Single: Only one master node will be created in your cluster.
                  NOTE:
                  • If more than half of the master nodes in a CCE cluster are faulty, the cluster cannot function properly.
                You can also select AZs for deploying the master nodes of a specific cluster. By default, AZs are allocated automatically for the master nodes.