From 86fb05065f4039b2576fb876b8d1fb220a1b0ecf Mon Sep 17 00:00:00 2001 From: "Dong, Qiu Jian" Date: Mon, 10 Jun 2024 08:19:07 +0000 Subject: [PATCH] CCE UMN for 24.2.0 version -20240428 Reviewed-by: Eotvos, Oliver Co-authored-by: Dong, Qiu Jian Co-committed-by: Dong, Qiu Jian --- docs/cce/umn/ALL_META.TXT.json | 3744 +++++++---------- docs/cce/umn/CLASS.TXT.json | 2353 ++++++----- docs/cce/umn/cce_01_0300.html | 22 +- docs/cce/umn/cce_10_0002.html | 4 +- docs/cce/umn/cce_10_0003.html | 35 +- docs/cce/umn/cce_10_0004.html | 3 +- docs/cce/umn/cce_10_0007.html | 2 +- docs/cce/umn/cce_10_0010.html | 8 +- docs/cce/umn/cce_10_0011.html | 4 +- docs/cce/umn/cce_10_0012.html | 85 +- docs/cce/umn/cce_10_0014.html | 10 +- docs/cce/umn/cce_10_0018.html | 18 +- docs/cce/umn/cce_10_0020.html | 2 +- docs/cce/umn/cce_10_0026.html | 2 +- docs/cce/umn/cce_10_0028.html | 45 +- docs/cce/umn/cce_10_0036.html | 2 +- docs/cce/umn/cce_10_0046.html | 2 + docs/cce/umn/cce_10_0047.html | 12 +- docs/cce/umn/cce_10_0048.html | 16 +- docs/cce/umn/cce_10_0054.html | 36 +- docs/cce/umn/cce_10_0059.html | 32 +- docs/cce/umn/cce_10_0063.html | 8 +- docs/cce/umn/cce_10_0064.html | 2 +- docs/cce/umn/cce_10_0066.html | 22 +- docs/cce/umn/cce_10_0068.html | 4 +- docs/cce/umn/cce_10_0081.html | 4 +- docs/cce/umn/cce_10_0083.html | 4 +- docs/cce/umn/cce_10_0084.html | 66 +- docs/cce/umn/cce_10_0094.html | 16 +- docs/cce/umn/cce_10_0105.html | 2 +- docs/cce/umn/cce_10_0107.html | 16 +- docs/cce/umn/cce_10_0112.html | 32 +- docs/cce/umn/cce_10_0113.html | 8 +- docs/cce/umn/cce_10_0125.html | 2 +- docs/cce/umn/cce_10_0127.html | 4 +- docs/cce/umn/cce_10_0129.html | 8 +- docs/cce/umn/cce_10_0132.html | 92 +- docs/cce/umn/cce_10_0141.html | 10 +- docs/cce/umn/cce_10_0142.html | 6 +- docs/cce/umn/cce_10_0144.html | 14 +- docs/cce/umn/cce_10_0146.html | 4 +- docs/cce/umn/cce_10_0150.html | 6 +- docs/cce/umn/cce_10_0151.html | 4 +- docs/cce/umn/cce_10_0152.html | 4 +- docs/cce/umn/cce_10_0153.html | 10 +- docs/cce/umn/cce_10_0154.html | 6 +- docs/cce/umn/cce_10_0163.html | 38 +- docs/cce/umn/cce_10_0175.html | 4 +- docs/cce/umn/cce_10_0180.html | 9 +- docs/cce/umn/cce_10_0182.html | 4 +- docs/cce/umn/cce_10_0183.html | 4 +- docs/cce/umn/cce_10_0184.html | 4 +- docs/cce/umn/cce_10_0186.html | 2 +- docs/cce/umn/cce_10_0187.html | 2 +- docs/cce/umn/cce_10_0188.html | 6 +- docs/cce/umn/cce_10_0189.html | 6 +- docs/cce/umn/cce_10_0190.html | 17 +- docs/cce/umn/cce_10_0191.html | 2 +- docs/cce/umn/cce_10_0193.html | 351 +- docs/cce/umn/cce_10_0196.html | 56 +- docs/cce/umn/cce_10_0197.html | 160 +- docs/cce/umn/cce_10_0198.html | 41 +- docs/cce/umn/cce_10_0201.html | 8 +- docs/cce/umn/cce_10_0205.html | 8 +- docs/cce/umn/cce_10_0208.html | 2 +- docs/cce/umn/cce_10_0209.html | 174 +- docs/cce/umn/cce_10_0210.html | 2 +- docs/cce/umn/cce_10_0212.html | 4 +- docs/cce/umn/cce_10_0213.html | 124 +- docs/cce/umn/cce_10_0214.html | 2 +- docs/cce/umn/cce_10_0215.html | 2 - docs/cce/umn/cce_10_0216.html | 12 +- docs/cce/umn/cce_10_0232.html | 22 +- docs/cce/umn/cce_10_0240.html | 8 +- docs/cce/umn/cce_10_0245.html | 2 +- docs/cce/umn/cce_10_0247.html | 2 +- docs/cce/umn/cce_10_0248.html | 2 +- docs/cce/umn/cce_10_0249.html | 4 +- docs/cce/umn/cce_10_0251.html | 59 +- docs/cce/umn/cce_10_0252.html | 100 +- docs/cce/umn/cce_10_0276.html | 2 +- docs/cce/umn/cce_10_0277.html | 241 +- docs/cce/umn/cce_10_0279.html | 16 +- docs/cce/umn/cce_10_0282.html | 4 +- docs/cce/umn/cce_10_0283.html | 4 +- docs/cce/umn/cce_10_0284.html | 101 +- docs/cce/umn/cce_10_0285.html | 8 +- docs/cce/umn/cce_10_0288.html | 78 +- docs/cce/umn/cce_10_0296.html | 18 +- docs/cce/umn/cce_10_0298.html | 4 +- docs/cce/umn/cce_10_0300.html | 6 +- docs/cce/umn/cce_10_0301.html | 74 - docs/cce/umn/cce_10_0302.html | 87 +- docs/cce/umn/cce_10_0307.html | 253 +- docs/cce/umn/cce_10_0336.html | 5 +- docs/cce/umn/cce_10_0337.html | 23 +- docs/cce/umn/cce_10_0341.html | 40 +- docs/cce/umn/cce_10_0342.html | 64 +- docs/cce/umn/cce_10_0345.html | 6 +- docs/cce/umn/cce_10_0349.html | 4 +- docs/cce/umn/cce_10_0351.html | 2 + docs/cce/umn/cce_10_0352.html | 28 +- docs/cce/umn/cce_10_0353.html | 1 - docs/cce/umn/cce_10_0355.html | 14 +- docs/cce/umn/cce_10_0360.html | 4 +- docs/cce/umn/cce_10_0361.html | 8 +- docs/cce/umn/cce_10_0363.html | 77 +- docs/cce/umn/cce_10_0365.html | 2 +- docs/cce/umn/cce_10_0367.html | 18 +- docs/cce/umn/cce_10_0378.html | 28 +- docs/cce/umn/cce_10_0379.html | 186 +- docs/cce/umn/cce_10_0380.html | 206 +- docs/cce/umn/cce_10_0381.html | 6 +- docs/cce/umn/cce_10_0384.html | 60 +- docs/cce/umn/cce_10_0385.html | 160 +- docs/cce/umn/cce_10_0386.html | 33 +- docs/cce/umn/cce_10_0397.html | 2 +- docs/cce/umn/cce_10_0398.html | 4 +- docs/cce/umn/cce_10_0400.html | 18 +- docs/cce/umn/cce_10_0402.html | 2 +- docs/cce/umn/cce_10_0405.html | 482 ++- docs/cce/umn/cce_10_0415.html | 24 +- docs/cce/umn/cce_10_0423.html | 2 +- docs/cce/umn/cce_10_0425.html | 195 +- docs/cce/umn/cce_10_0430.html | 7 +- docs/cce/umn/cce_10_0431.html | 21 +- docs/cce/umn/cce_10_0433.html | 8 +- docs/cce/umn/cce_10_0436.html | 5 +- docs/cce/umn/cce_10_0437.html | 1 - docs/cce/umn/cce_10_0441.html | 10 +- docs/cce/umn/cce_10_0442.html | 4 +- docs/cce/umn/cce_10_0445.html | 2 +- docs/cce/umn/cce_10_0448.html | 2 +- docs/cce/umn/cce_10_0450.html | 4 +- docs/cce/umn/cce_10_0451.html | 8 +- docs/cce/umn/cce_10_0456.html | 2 +- docs/cce/umn/cce_10_0459.html | 2 +- docs/cce/umn/cce_10_0460.html | 2 +- docs/cce/umn/cce_10_0462.html | 312 +- docs/cce/umn/cce_10_0463.html | 5 +- docs/cce/umn/cce_10_0476.html | 221 + docs/cce/umn/cce_10_0477.html | 2 +- docs/cce/umn/cce_10_0487.html | 2 +- docs/cce/umn/cce_10_0493.html | 2 +- docs/cce/umn/cce_10_0495.html | 6 +- docs/cce/umn/cce_10_0497.html | 8 +- docs/cce/umn/cce_10_0498.html | 2 +- docs/cce/umn/cce_10_0500.html | 2 +- docs/cce/umn/cce_10_0510.html | 6 +- docs/cce/umn/cce_10_0511.html | 10 +- docs/cce/umn/cce_10_0512.html | 6 +- docs/cce/umn/cce_10_0513.html | 14 + docs/cce/umn/cce_10_0514.html | 14 + docs/cce/umn/cce_10_0515.html | 14 + docs/cce/umn/cce_10_0516.html | 14 + docs/cce/umn/cce_10_0517.html | 14 + docs/cce/umn/cce_10_0518.html | 14 + docs/cce/umn/cce_10_0549.html | 60 +- docs/cce/umn/cce_10_0550.html | 20 +- docs/cce/umn/cce_10_0552.html | 15 +- docs/cce/umn/cce_10_0553.html | 2 +- docs/cce/umn/cce_10_0557.html | 4 +- docs/cce/umn/cce_10_0560.html | 6 - docs/cce/umn/cce_10_0562.html | 16 - docs/cce/umn/cce_10_0563.html | 133 - docs/cce/umn/cce_10_0564.html | 18 - docs/cce/umn/cce_10_0566.html | 2 +- docs/cce/umn/cce_10_0601.html | 4 +- docs/cce/umn/cce_10_0602.html | 2 +- docs/cce/umn/cce_10_0603.html | 96 + docs/cce/umn/cce_10_0604.html | 32 + docs/cce/umn/cce_10_0605.html | 4 +- docs/cce/umn/cce_10_0614.html | 46 +- docs/cce/umn/cce_10_0615.html | 40 +- docs/cce/umn/cce_10_0616.html | 80 +- docs/cce/umn/cce_10_0619.html | 22 +- docs/cce/umn/cce_10_0620.html | 109 +- docs/cce/umn/cce_10_0624.html | 2 +- docs/cce/umn/cce_10_0625.html | 74 +- docs/cce/umn/cce_10_0626.html | 17 +- docs/cce/umn/cce_10_0630.html | 70 +- docs/cce/umn/cce_10_0631.html | 103 +- docs/cce/umn/cce_10_0634.html | 14 +- docs/cce/umn/cce_10_0635.html | 12 +- docs/cce/umn/cce_10_0637.html | 2 +- docs/cce/umn/cce_10_0638.html | 2 +- docs/cce/umn/cce_10_0652.html | 623 +-- docs/cce/umn/cce_10_0653.html | 34 +- docs/cce/umn/cce_10_0654.html | 2 +- docs/cce/umn/cce_10_0655.html | 3 +- docs/cce/umn/cce_10_0657.html | 2 +- docs/cce/umn/cce_10_0659.html | 68 +- docs/cce/umn/cce_10_0660.html | 6 +- docs/cce/umn/cce_10_0672.html | 2 +- docs/cce/umn/cce_10_0678.html | 8 +- docs/cce/umn/cce_10_0680.html | 2 +- docs/cce/umn/cce_10_0681.html | 171 +- docs/cce/umn/cce_10_0683.html | 64 +- docs/cce/umn/cce_10_0684.html | 71 +- docs/cce/umn/cce_10_0685.html | 2 +- docs/cce/umn/cce_10_0686.html | 20 +- docs/cce/umn/cce_10_0687.html | 43 +- docs/cce/umn/cce_10_0688.html | 11 +- docs/cce/umn/cce_10_0689.html | 9 +- docs/cce/umn/cce_10_0691.html | 10 +- docs/cce/umn/cce_10_0694.html | 52 +- docs/cce/umn/cce_10_0695.html | 301 +- docs/cce/umn/cce_10_0702.html | 21 + docs/cce/umn/cce_10_0721.html | 6 +- docs/cce/umn/cce_10_0722.html | 2 +- docs/cce/umn/cce_10_0727.html | 28 +- docs/cce/umn/cce_10_0729.html | 34 +- docs/cce/umn/cce_10_0730.html | 54 +- docs/cce/umn/cce_10_0766.html | 144 +- docs/cce/umn/cce_10_0767.html | 8 +- docs/cce/umn/cce_10_0768.html | 6 +- docs/cce/umn/cce_10_0773.html | 62 +- docs/cce/umn/cce_10_0775.html | 10 +- docs/cce/umn/cce_10_0777.html | 12 +- docs/cce/umn/cce_10_0778.html | 14 +- docs/cce/umn/cce_10_0833.html | 19 + docs/cce/umn/cce_bestpractice_00004.html | 27 +- docs/cce/umn/cce_bestpractice_00006.html | 4 +- docs/cce/umn/cce_bestpractice_0003.html | 2 +- docs/cce/umn/cce_bestpractice_00035.html | 16 +- docs/cce/umn/cce_bestpractice_0004.html | 2 +- docs/cce/umn/cce_bestpractice_0006.html | 2 +- docs/cce/umn/cce_bestpractice_0008.html | 2 +- docs/cce/umn/cce_bestpractice_0009.html | 2 +- docs/cce/umn/cce_bestpractice_0010.html | 8 +- docs/cce/umn/cce_bestpractice_0013.html | 19 + ...e_0308.html => cce_bestpractice_0014.html} | 62 +- docs/cce/umn/cce_bestpractice_00162.html | 80 +- docs/cce/umn/cce_bestpractice_00198.html | 18 +- docs/cce/umn/cce_bestpractice_00199.html | 6 +- docs/cce/umn/cce_bestpractice_00221.html | 57 +- docs/cce/umn/cce_bestpractice_00226.html | 2 +- docs/cce/umn/cce_bestpractice_00228.html | 2 +- docs/cce/umn/cce_bestpractice_00231.html | 421 +- docs/cce/umn/cce_bestpractice_00237.html | 2 +- docs/cce/umn/cce_bestpractice_0024.html | 68 + docs/cce/umn/cce_bestpractice_00253.html | 53 +- docs/cce/umn/cce_bestpractice_00253_0.html | 53 +- docs/cce/umn/cce_bestpractice_00254.html | 6 +- docs/cce/umn/cce_bestpractice_00281.html | 249 +- docs/cce/umn/cce_bestpractice_00282.html | 6 +- docs/cce/umn/cce_bestpractice_00284.html | 4 +- docs/cce/umn/cce_bestpractice_0053.html | 2 +- docs/cce/umn/cce_bestpractice_0059.html | 25 + docs/cce/umn/cce_bestpractice_0107.html | 2 +- docs/cce/umn/cce_bestpractice_0307.html | 18 +- docs/cce/umn/cce_bestpractice_0309.html | 25 - docs/cce/umn/cce_bestpractice_0310.html | 72 +- docs/cce/umn/cce_bestpractice_0311.html | 67 - docs/cce/umn/cce_bestpractice_0312.html | 8 +- docs/cce/umn/cce_bestpractice_0313.html | 4 +- docs/cce/umn/cce_bestpractice_0314.html | 16 +- docs/cce/umn/cce_bestpractice_0323.html | 2 + docs/cce/umn/cce_bestpractice_0324.html | 24 +- docs/cce/umn/cce_bestpractice_0326.html | 18 +- docs/cce/umn/cce_bestpractice_10001.html | 6 +- docs/cce/umn/cce_bestpractice_10002.html | 6 +- docs/cce/umn/cce_bestpractice_10009.html | 12 +- docs/cce/umn/cce_bestpractice_10010.html | 21 +- docs/cce/umn/cce_bestpractice_10012.html | 2 +- docs/cce/umn/cce_bestpractice_10016.html | 58 +- docs/cce/umn/cce_bestpractice_10017.html | 34 +- docs/cce/umn/cce_bestpractice_10020.html | 4 +- docs/cce/umn/cce_bestpractice_10027.html | 23 + docs/cce/umn/cce_bulletin_0000.html | 2 - docs/cce/umn/cce_bulletin_0003.html | 6 +- docs/cce/umn/cce_bulletin_0026.html | 2 +- docs/cce/umn/cce_bulletin_0027.html | 2 +- docs/cce/umn/cce_bulletin_0058.html | 68 +- docs/cce/umn/cce_bulletin_0059.html | 100 +- docs/cce/umn/cce_bulletin_0068.html | 46 + docs/cce/umn/cce_bulletin_0301.html | 255 -- docs/cce/umn/cce_faq_00006.html | 2 +- docs/cce/umn/cce_faq_00012.html | 2 +- docs/cce/umn/cce_faq_00015.html | 4 +- docs/cce/umn/cce_faq_00018.html | 36 +- docs/cce/umn/cce_faq_00020.html | 2 +- docs/cce/umn/cce_faq_00025.html | 2 +- docs/cce/umn/cce_faq_00027.html | 10 +- docs/cce/umn/cce_faq_00030.html | 2 +- docs/cce/umn/cce_faq_00039.html | 9 +- docs/cce/umn/cce_faq_00041.html | 2 +- docs/cce/umn/cce_faq_00090.html | 2 +- docs/cce/umn/cce_faq_00095.html | 2 - docs/cce/umn/cce_faq_00097.html | 2 +- docs/cce/umn/cce_faq_00098.html | 2 +- docs/cce/umn/cce_faq_00107.html | 4 +- docs/cce/umn/cce_faq_00120.html | 11 +- docs/cce/umn/cce_faq_00134.html | 156 +- docs/cce/umn/cce_faq_00146.html | 4 +- docs/cce/umn/cce_faq_00152.html | 19 - docs/cce/umn/cce_faq_00195.html | 2 +- docs/cce/umn/cce_faq_00197.html | 2 +- docs/cce/umn/cce_faq_00200.html | 2 +- docs/cce/umn/cce_faq_00201.html | 5 + docs/cce/umn/cce_faq_00202.html | 6 +- docs/cce/umn/cce_faq_00203.html | 4 +- docs/cce/umn/cce_faq_00204.html | 8 +- docs/cce/umn/cce_faq_00209.html | 8 +- docs/cce/umn/cce_faq_00218.html | 4 +- docs/cce/umn/cce_faq_00224.html | 12 +- docs/cce/umn/cce_faq_00263.html | 2 +- docs/cce/umn/cce_faq_00264.html | 2 + docs/cce/umn/cce_faq_00265.html | 50 +- docs/cce/umn/cce_faq_00266.html | 2 +- docs/cce/umn/cce_faq_00279.html | 2 +- docs/cce/umn/cce_faq_00286.html | 2 +- docs/cce/umn/cce_faq_00296.html | 2 +- docs/cce/umn/cce_faq_00307.html | 4 +- docs/cce/umn/cce_faq_00309.html | 4 +- docs/cce/umn/cce_faq_00319.html | 2 +- docs/cce/umn/cce_faq_00321.html | 2 +- docs/cce/umn/cce_faq_00322.html | 12 +- docs/cce/umn/cce_faq_00325.html | 2 +- docs/cce/umn/cce_faq_00394.html | 17 +- docs/cce/umn/cce_faq_00406.html | 119 + docs/cce/umn/cce_faq_00407.html | 2 +- docs/cce/umn/cce_faq_00409.html | 22 +- docs/cce/umn/cce_faq_00413.html | 14 +- docs/cce/umn/cce_faq_00417.html | 16 + docs/cce/umn/cce_faq_00429.html | 80 +- docs/cce/umn/cce_faq_00432.html | 10 +- docs/cce/umn/cce_productdesc_0005.html | 8 +- docs/cce/umn/cce_whsnew_0007.html | 2 +- docs/cce/umn/cce_whsnew_0010.html | 4 +- docs/cce/umn/en-us_image_0000001461224886.png | Bin 16828 -> 17878 bytes docs/cce/umn/en-us_image_0000001750790124.png | Bin 4394 -> 0 bytes docs/cce/umn/en-us_image_0000001750790372.png | Bin 1370 -> 0 bytes docs/cce/umn/en-us_image_0000001750791044.png | Bin 41021 -> 0 bytes docs/cce/umn/en-us_image_0000001750791064.png | Bin 867 -> 0 bytes docs/cce/umn/en-us_image_0000001750791628.png | Bin 41419 -> 0 bytes docs/cce/umn/en-us_image_0000001750949488.png | Bin 58823 -> 0 bytes docs/cce/umn/en-us_image_0000001750950264.png | Bin 5848 -> 0 bytes docs/cce/umn/en-us_image_0000001750950284.png | Bin 80598 -> 0 bytes docs/cce/umn/en-us_image_0000001750950508.png | Bin 49269 -> 0 bytes docs/cce/umn/en-us_image_0000001797870901.png | Bin 16198 -> 0 bytes docs/cce/umn/en-us_image_0000001797871017.png | Bin 25122 -> 0 bytes docs/cce/umn/en-us_image_0000001797871357.png | Bin 14592 -> 0 bytes docs/cce/umn/en-us_image_0000001797908941.png | Bin 173544 -> 0 bytes docs/cce/umn/en-us_image_0000001797909113.png | Bin 15212 -> 0 bytes docs/cce/umn/en-us_image_0000001797909141.png | Bin 158873 -> 0 bytes docs/cce/umn/en-us_image_0000001797909393.png | Bin 49502 -> 0 bytes docs/cce/umn/en-us_image_0000001797909897.png | Bin 3760 -> 0 bytes docs/cce/umn/en-us_image_0000001797910133.png | Bin 42468 -> 0 bytes ...7.png => en-us_image_0000001851584908.png} | Bin ...5.gif => en-us_image_0000001851585000.gif} | Bin ...2.jpg => en-us_image_0000001851585004.jpg} | Bin ...9.png => en-us_image_0000001851585032.png} | Bin ...6.png => en-us_image_0000001851585064.png} | Bin ...0.png => en-us_image_0000001851585068.png} | Bin ...4.png => en-us_image_0000001851585080.png} | Bin ...3.png => en-us_image_0000001851585104.png} | Bin ...7.png => en-us_image_0000001851585112.png} | Bin ...4.png => en-us_image_0000001851585136.png} | Bin ...5.png => en-us_image_0000001851585148.png} | Bin ...2.png => en-us_image_0000001851585156.png} | Bin ...6.png => en-us_image_0000001851585168.png} | Bin ...2.png => en-us_image_0000001851585188.png} | Bin ...0.png => en-us_image_0000001851585200.png} | Bin ...1.png => en-us_image_0000001851585204.png} | Bin ...1.jpg => en-us_image_0000001851585232.jpg} | Bin ...4.png => en-us_image_0000001851585272.png} | Bin ...9.png => en-us_image_0000001851585280.png} | Bin ...8.png => en-us_image_0000001851585384.png} | Bin ...3.png => en-us_image_0000001851585416.png} | Bin ...5.png => en-us_image_0000001851585432.png} | Bin ...4.png => en-us_image_0000001851585440.png} | Bin ...7.png => en-us_image_0000001851585464.png} | Bin ...3.png => en-us_image_0000001851585496.png} | Bin ...6.png => en-us_image_0000001851585500.png} | Bin ...9.png => en-us_image_0000001851585668.png} | Bin ...7.png => en-us_image_0000001851585672.png} | Bin ...1.png => en-us_image_0000001851585684.png} | Bin ...7.png => en-us_image_0000001851585700.png} | Bin ...7.png => en-us_image_0000001851585808.png} | Bin ...8.png => en-us_image_0000001851585812.png} | Bin docs/cce/umn/en-us_image_0000001851586224.png | Bin 0 -> 44668 bytes docs/cce/umn/en-us_image_0000001851586240.png | Bin 0 -> 568 bytes ...8.png => en-us_image_0000001851586264.png} | Bin ...9.png => en-us_image_0000001851586336.png} | Bin ...5.png => en-us_image_0000001851586420.png} | Bin ...5.png => en-us_image_0000001851586460.png} | Bin ...0.png => en-us_image_0000001851586476.png} | Bin ...2.png => en-us_image_0000001851586516.png} | Bin docs/cce/umn/en-us_image_0000001851586520.png | Bin 0 -> 473 bytes ...1.png => en-us_image_0000001851586648.png} | Bin ...9.png => en-us_image_0000001851586668.png} | Bin ...6.png => en-us_image_0000001851586680.png} | Bin ...8.png => en-us_image_0000001851586708.png} | Bin ...1.png => en-us_image_0000001851586944.png} | Bin ...2.png => en-us_image_0000001851586988.png} | Bin ...3.png => en-us_image_0000001851586992.png} | Bin ...7.png => en-us_image_0000001851587044.png} | Bin ...1.png => en-us_image_0000001851587144.png} | Bin ...1.png => en-us_image_0000001851587156.png} | Bin docs/cce/umn/en-us_image_0000001851587336.png | Bin 0 -> 31597 bytes ...4.png => en-us_image_0000001851587340.png} | Bin docs/cce/umn/en-us_image_0000001851587344.png | Bin 0 -> 41251 bytes ...2.png => en-us_image_0000001851587348.png} | Bin ...2.png => en-us_image_0000001851587784.png} | Bin ...0.png => en-us_image_0000001851587788.png} | Bin ...5.png => en-us_image_0000001851587796.png} | Bin ...4.png => en-us_image_0000001851587804.png} | Bin ...1.png => en-us_image_0000001851743660.png} | Bin ...6.png => en-us_image_0000001851743664.png} | Bin ...2.png => en-us_image_0000001851743708.png} | Bin ...6.jpg => en-us_image_0000001851743732.jpg} | Bin ...0.gif => en-us_image_0000001851743740.gif} | Bin ...8.png => en-us_image_0000001851743812.png} | Bin ...8.png => en-us_image_0000001851743816.png} | Bin ...5.png => en-us_image_0000001851743820.png} | Bin ...1.png => en-us_image_0000001851743828.png} | Bin ...4.png => en-us_image_0000001851743836.png} | Bin ...9.png => en-us_image_0000001851743848.png} | Bin ...3.png => en-us_image_0000001851743860.png} | Bin ...2.png => en-us_image_0000001851743868.png} | Bin ...3.png => en-us_image_0000001851743880.png} | Bin ...9.png => en-us_image_0000001851743884.png} | Bin ...9.png => en-us_image_0000001851743900.png} | Bin ...0.png => en-us_image_0000001851743916.png} | Bin ...5.png => en-us_image_0000001851743956.png} | Bin ...8.png => en-us_image_0000001851744000.png} | Bin ...4.png => en-us_image_0000001851744004.png} | Bin ...1.png => en-us_image_0000001851744076.png} | Bin ...4.png => en-us_image_0000001851744088.png} | Bin ...6.png => en-us_image_0000001851744104.png} | Bin ...9.png => en-us_image_0000001851744112.png} | Bin ...8.png => en-us_image_0000001851744176.png} | Bin ...8.png => en-us_image_0000001851744224.png} | Bin ...0.png => en-us_image_0000001851744368.png} | Bin ...3.png => en-us_image_0000001851744412.png} | Bin ...6.png => en-us_image_0000001851744500.png} | Bin ...9.png => en-us_image_0000001851744516.png} | Bin ...7.png => en-us_image_0000001851744964.png} | Bin ...5.png => en-us_image_0000001851745096.png} | Bin ...2.png => en-us_image_0000001851745196.png} | Bin ...1.png => en-us_image_0000001851745204.png} | Bin ...1.png => en-us_image_0000001851745256.png} | Bin ...2.png => en-us_image_0000001851745260.png} | Bin docs/cce/umn/en-us_image_0000001851745380.png | Bin 0 -> 16295 bytes ...8.png => en-us_image_0000001851745400.png} | Bin ...8.png => en-us_image_0000001851745436.png} | Bin ...4.png => en-us_image_0000001851745492.png} | Bin ...4.png => en-us_image_0000001851745496.png} | Bin ...0.png => en-us_image_0000001851745504.png} | Bin ...0.png => en-us_image_0000001851745528.png} | Bin ...6.png => en-us_image_0000001851745568.png} | Bin ...7.png => en-us_image_0000001851745580.png} | Bin ...1.png => en-us_image_0000001851745612.png} | Bin ...7.png => en-us_image_0000001851745632.png} | Bin ...2.png => en-us_image_0000001851745716.png} | Bin ...5.png => en-us_image_0000001851745744.png} | Bin ...2.png => en-us_image_0000001851745764.png} | Bin ...7.png => en-us_image_0000001851745808.png} | Bin ...7.png => en-us_image_0000001851745844.png} | Bin ...4.png => en-us_image_0000001851745852.png} | Bin ...6.png => en-us_image_0000001851745864.png} | Bin ...5.png => en-us_image_0000001851746056.png} | Bin docs/cce/umn/en-us_image_0000001851746060.png | Bin 0 -> 29113 bytes ...0.png => en-us_image_0000001851746444.png} | Bin ...7.png => en-us_image_0000001851746504.png} | Bin ...4.png => en-us_image_0000001851746508.png} | Bin ...3.png => en-us_image_0000001851746544.png} | Bin ...9.png => en-us_image_0000001852319184.png} | Bin docs/cce/umn/en-us_image_0000001863378970.png | Bin 0 -> 10385 bytes docs/cce/umn/en-us_image_0000001864147989.png | Bin 21024 -> 0 bytes docs/cce/umn/en-us_image_0000001865760133.png | Bin 67959 -> 0 bytes docs/cce/umn/en-us_image_0000001867802022.png | Bin 0 -> 27013 bytes ...9.jpg => en-us_image_0000001897904309.jpg} | Bin ...6.png => en-us_image_0000001897904393.png} | Bin ...9.png => en-us_image_0000001897904433.png} | Bin ...6.png => en-us_image_0000001897904509.png} | Bin ...3.png => en-us_image_0000001897904517.png} | Bin ...9.png => en-us_image_0000001897904533.png} | Bin ...2.png => en-us_image_0000001897904561.png} | Bin ...2.png => en-us_image_0000001897904609.png} | Bin ...4.png => en-us_image_0000001897904725.png} | Bin ...9.png => en-us_image_0000001897904773.png} | Bin ...7.png => en-us_image_0000001897904777.png} | Bin ...0.png => en-us_image_0000001897905025.png} | Bin ...6.png => en-us_image_0000001897905033.png} | Bin ...3.png => en-us_image_0000001897905069.png} | Bin ...7.png => en-us_image_0000001897905113.png} | Bin ...2.png => en-us_image_0000001897905125.png} | Bin ...9.png => en-us_image_0000001897905169.png} | Bin ...6.png => en-us_image_0000001897905209.png} | Bin ...0.png => en-us_image_0000001897905601.png} | Bin ...8.png => en-us_image_0000001897905605.png} | Bin ...3.png => en-us_image_0000001897905733.png} | Bin ...6.png => en-us_image_0000001897905793.png} | Bin ...1.png => en-us_image_0000001897905921.png} | Bin ...4.png => en-us_image_0000001897906037.png} | Bin ...4.png => en-us_image_0000001897906049.png} | Bin ...4.png => en-us_image_0000001897906057.png} | Bin ...7.png => en-us_image_0000001897906097.png} | Bin ...5.png => en-us_image_0000001897906125.png} | Bin ...0.png => en-us_image_0000001897906145.png} | Bin ...6.png => en-us_image_0000001897906149.png} | Bin ...6.jpg => en-us_image_0000001897906165.jpg} | Bin ...6.png => en-us_image_0000001897906185.png} | Bin docs/cce/umn/en-us_image_0000001897906197.png | Bin 0 -> 22353 bytes ...8.png => en-us_image_0000001897906213.png} | Bin ...5.png => en-us_image_0000001897906225.png} | Bin ...9.png => en-us_image_0000001897906233.png} | Bin ...4.png => en-us_image_0000001897906237.png} | Bin ...9.png => en-us_image_0000001897906253.png} | Bin ...3.png => en-us_image_0000001897906289.png} | Bin ...8.png => en-us_image_0000001897906293.png} | Bin ...8.png => en-us_image_0000001897906365.png} | Bin ...1.png => en-us_image_0000001897906417.png} | Bin ...4.png => en-us_image_0000001897906445.png} | Bin docs/cce/umn/en-us_image_0000001897906717.png | Bin 0 -> 38608 bytes docs/cce/umn/en-us_image_0000001897906729.png | Bin 0 -> 29220 bytes ...2.png => en-us_image_0000001897907185.png} | Bin ...1.png => en-us_image_0000001898023829.png} | Bin ...8.png => en-us_image_0000001898023841.png} | Bin ...5.png => en-us_image_0000001898023873.png} | Bin ...9.gif => en-us_image_0000001898023913.gif} | Bin ...3.png => en-us_image_0000001898023989.png} | Bin ...6.png => en-us_image_0000001898024017.png} | Bin ...2.png => en-us_image_0000001898024033.png} | Bin ...8.png => en-us_image_0000001898024041.png} | Bin ...5.png => en-us_image_0000001898024049.png} | Bin ...9.png => en-us_image_0000001898024061.png} | Bin ...3.png => en-us_image_0000001898024113.png} | Bin ...3.png => en-us_image_0000001898024121.png} | Bin docs/cce/umn/en-us_image_0000001898024145.png | Bin 0 -> 41567 bytes ...1.png => en-us_image_0000001898024157.png} | Bin ...1.png => en-us_image_0000001898024237.png} | Bin ...1.png => en-us_image_0000001898024249.png} | Bin ...2.png => en-us_image_0000001898024285.png} | Bin ...6.png => en-us_image_0000001898024289.png} | Bin ...7.png => en-us_image_0000001898024333.png} | Bin docs/cce/umn/en-us_image_0000001898024381.png | Bin 0 -> 210 bytes ...1.png => en-us_image_0000001898024541.png} | Bin ...2.png => en-us_image_0000001898024545.png} | Bin ...9.png => en-us_image_0000001898024565.png} | Bin ...4.png => en-us_image_0000001898024613.png} | Bin ...1.png => en-us_image_0000001898024625.png} | Bin ...6.png => en-us_image_0000001898024709.png} | Bin docs/cce/umn/en-us_image_0000001898025121.png | Bin 0 -> 22306 bytes ...6.png => en-us_image_0000001898025173.png} | Bin ...9.png => en-us_image_0000001898025401.png} | Bin ...5.png => en-us_image_0000001898025441.png} | Bin ...0.png => en-us_image_0000001898025573.png} | Bin ...9.png => en-us_image_0000001898025577.png} | Bin ...4.png => en-us_image_0000001898025669.png} | Bin ...0.png => en-us_image_0000001898025681.png} | Bin ...5.png => en-us_image_0000001898025705.png} | Bin ...2.png => en-us_image_0000001898025749.png} | Bin ...2.png => en-us_image_0000001898025781.png} | Bin ...9.png => en-us_image_0000001898025869.png} | Bin ...6.png => en-us_image_0000001898025885.png} | Bin ...4.png => en-us_image_0000001898025961.png} | Bin ...0.png => en-us_image_0000001898026001.png} | Bin ...1.png => en-us_image_0000001898026021.png} | Bin ...4.png => en-us_image_0000001898026057.png} | Bin docs/cce/umn/en-us_image_0000001898026645.png | Bin 0 -> 53292 bytes ...6.png => en-us_image_0000001898026669.png} | Bin docs/cce/umn/en-us_image_0000001898026693.png | Bin 0 -> 14949 bytes ...6.png => en-us_image_0000001898026705.png} | Bin ...2.png => en-us_image_0000001902829161.png} | Bin docs/cce/umn/en-us_image_0000001909237081.png | Bin 0 -> 62540 bytes docs/cce/umn/en-us_image_0000001911555737.png | Bin 0 -> 173094 bytes 569 files changed, 9251 insertions(+), 7871 deletions(-) delete mode 100644 docs/cce/umn/cce_10_0301.html create mode 100644 docs/cce/umn/cce_10_0476.html create mode 100644 docs/cce/umn/cce_10_0513.html create mode 100644 docs/cce/umn/cce_10_0514.html create mode 100644 docs/cce/umn/cce_10_0515.html create mode 100644 docs/cce/umn/cce_10_0516.html create mode 100644 docs/cce/umn/cce_10_0517.html create mode 100644 docs/cce/umn/cce_10_0518.html delete mode 100644 docs/cce/umn/cce_10_0562.html delete mode 100644 docs/cce/umn/cce_10_0563.html delete mode 100644 docs/cce/umn/cce_10_0564.html create mode 100644 docs/cce/umn/cce_10_0603.html create mode 100644 docs/cce/umn/cce_10_0604.html create mode 100644 docs/cce/umn/cce_10_0833.html create mode 100644 docs/cce/umn/cce_bestpractice_0013.html rename docs/cce/umn/{cce_bestpractice_0308.html => cce_bestpractice_0014.html} (55%) create mode 100644 docs/cce/umn/cce_bestpractice_0024.html create mode 100644 docs/cce/umn/cce_bestpractice_0059.html delete mode 100644 docs/cce/umn/cce_bestpractice_0309.html delete mode 100644 docs/cce/umn/cce_bestpractice_0311.html create mode 100644 docs/cce/umn/cce_bestpractice_10027.html create mode 100644 docs/cce/umn/cce_bulletin_0068.html delete mode 100644 docs/cce/umn/cce_bulletin_0301.html delete mode 100644 docs/cce/umn/cce_faq_00152.html create mode 100644 docs/cce/umn/cce_faq_00406.html create mode 100644 docs/cce/umn/cce_faq_00417.html delete mode 100644 docs/cce/umn/en-us_image_0000001750790124.png delete mode 100644 docs/cce/umn/en-us_image_0000001750790372.png delete mode 100644 docs/cce/umn/en-us_image_0000001750791044.png delete mode 100644 docs/cce/umn/en-us_image_0000001750791064.png delete mode 100644 docs/cce/umn/en-us_image_0000001750791628.png delete mode 100644 docs/cce/umn/en-us_image_0000001750949488.png delete mode 100644 docs/cce/umn/en-us_image_0000001750950264.png delete mode 100644 docs/cce/umn/en-us_image_0000001750950284.png delete mode 100644 docs/cce/umn/en-us_image_0000001750950508.png delete mode 100644 docs/cce/umn/en-us_image_0000001797870901.png delete mode 100644 docs/cce/umn/en-us_image_0000001797871017.png delete mode 100644 docs/cce/umn/en-us_image_0000001797871357.png delete mode 100644 docs/cce/umn/en-us_image_0000001797908941.png delete mode 100644 docs/cce/umn/en-us_image_0000001797909113.png delete mode 100644 docs/cce/umn/en-us_image_0000001797909141.png delete mode 100644 docs/cce/umn/en-us_image_0000001797909393.png delete mode 100644 docs/cce/umn/en-us_image_0000001797909897.png delete mode 100644 docs/cce/umn/en-us_image_0000001797910133.png rename docs/cce/umn/{en-us_image_0000001870542157.png => en-us_image_0000001851584908.png} (100%) rename docs/cce/umn/{en-us_image_0000001797869765.gif => en-us_image_0000001851585000.gif} (100%) rename docs/cce/umn/{en-us_image_0000001750949172.jpg => en-us_image_0000001851585004.jpg} (100%) rename docs/cce/umn/{en-us_image_0000001797908969.png => en-us_image_0000001851585032.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949056.png => en-us_image_0000001851585064.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790140.png => en-us_image_0000001851585068.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949064.png => en-us_image_0000001851585080.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909093.png => en-us_image_0000001851585104.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870097.png => en-us_image_0000001851585112.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949264.png => en-us_image_0000001851585136.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870045.png => en-us_image_0000001851585148.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790092.png => en-us_image_0000001851585156.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949016.png => en-us_image_0000001851585168.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949032.png => en-us_image_0000001851585188.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949040.png => en-us_image_0000001851585200.png} (100%) rename docs/cce/umn/{en-us_image_0000001844691101.png => en-us_image_0000001851585204.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870021.jpg => en-us_image_0000001851585232.jpg} (100%) rename docs/cce/umn/{en-us_image_0000001823625674.png => en-us_image_0000001851585272.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909429.png => en-us_image_0000001851585280.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949308.png => en-us_image_0000001851585384.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909133.png => en-us_image_0000001851585416.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909145.png => en-us_image_0000001851585432.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790604.png => en-us_image_0000001851585440.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870037.png => en-us_image_0000001851585464.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909213.png => en-us_image_0000001851585496.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790516.png => en-us_image_0000001851585500.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870429.png => en-us_image_0000001851585668.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909457.png => en-us_image_0000001851585672.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870441.png => en-us_image_0000001851585684.png} (100%) rename docs/cce/umn/{en-us_image_0000001826752857.png => en-us_image_0000001851585700.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870437.png => en-us_image_0000001851585808.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790768.png => en-us_image_0000001851585812.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001851586224.png create mode 100644 docs/cce/umn/en-us_image_0000001851586240.png rename docs/cce/umn/{en-us_image_0000001750790788.png => en-us_image_0000001851586264.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909749.png => en-us_image_0000001851586336.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870765.png => en-us_image_0000001851586420.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909805.png => en-us_image_0000001851586460.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791100.png => en-us_image_0000001851586476.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791112.png => en-us_image_0000001851586516.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001851586520.png rename docs/cce/umn/{en-us_image_0000001797870861.png => en-us_image_0000001851586648.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909889.png => en-us_image_0000001851586668.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791236.png => en-us_image_0000001851586680.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950248.png => en-us_image_0000001851586708.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871181.png => en-us_image_0000001851586944.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950352.png => en-us_image_0000001851586988.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871133.png => en-us_image_0000001851586992.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871377.png => en-us_image_0000001851587044.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871201.png => en-us_image_0000001851587144.png} (100%) rename docs/cce/umn/{en-us_image_0000001865613281.png => en-us_image_0000001851587156.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001851587336.png rename docs/cce/umn/{en-us_image_0000001750791624.png => en-us_image_0000001851587340.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001851587344.png rename docs/cce/umn/{en-us_image_0000001750950532.png => en-us_image_0000001851587348.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791732.png => en-us_image_0000001851587784.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950660.png => en-us_image_0000001851587788.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871425.png => en-us_image_0000001851587796.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791664.png => en-us_image_0000001851587804.png} (100%) rename docs/cce/umn/{en-us_image_0000001797869741.png => en-us_image_0000001851743660.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790176.png => en-us_image_0000001851743664.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790172.png => en-us_image_0000001851743708.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949156.jpg => en-us_image_0000001851743732.jpg} (100%) rename docs/cce/umn/{en-us_image_0000001750949000.gif => en-us_image_0000001851743740.gif} (100%) rename docs/cce/umn/{en-us_image_0000001750949408.png => en-us_image_0000001851743812.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949068.png => en-us_image_0000001851743816.png} (100%) rename docs/cce/umn/{en-us_image_0000001797908865.png => en-us_image_0000001851743820.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909221.png => en-us_image_0000001851743828.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949364.png => en-us_image_0000001851743836.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909249.png => en-us_image_0000001851743848.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870253.png => en-us_image_0000001851743860.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790572.png => en-us_image_0000001851743868.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870093.png => en-us_image_0000001851743880.png} (100%) rename docs/cce/umn/{en-us_image_0000001797869789.png => en-us_image_0000001851743884.png} (100%) rename docs/cce/umn/{en-us_image_0000001797908809.png => en-us_image_0000001851743900.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790120.png => en-us_image_0000001851743916.png} (100%) rename docs/cce/umn/{en-us_image_0000001797869825.png => en-us_image_0000001851743956.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949248.png => en-us_image_0000001851744000.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790564.png => en-us_image_0000001851744004.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909241.png => en-us_image_0000001851744076.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949444.png => en-us_image_0000001851744088.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790396.png => en-us_image_0000001851744104.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870089.png => en-us_image_0000001851744112.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790328.png => en-us_image_0000001851744176.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949428.png => en-us_image_0000001851744224.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790640.png => en-us_image_0000001851744368.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909473.png => en-us_image_0000001851744412.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790716.png => en-us_image_0000001851744500.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870469.png => en-us_image_0000001851744516.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909777.png => en-us_image_0000001851744964.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909785.png => en-us_image_0000001851745096.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949232.png => en-us_image_0000001851745196.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909801.png => en-us_image_0000001851745204.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870801.png => en-us_image_0000001851745256.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950032.png => en-us_image_0000001851745260.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001851745380.png rename docs/cce/umn/{en-us_image_0000001750791228.png => en-us_image_0000001851745400.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791328.png => en-us_image_0000001851745436.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950204.png => en-us_image_0000001851745492.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791444.png => en-us_image_0000001851745496.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950360.png => en-us_image_0000001851745504.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950380.png => en-us_image_0000001851745528.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950236.png => en-us_image_0000001851745568.png} (100%) rename docs/cce/umn/{en-us_image_0000001797910037.png => en-us_image_0000001851745580.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871061.png => en-us_image_0000001851745612.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871157.png => en-us_image_0000001851745632.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791672.png => en-us_image_0000001851745716.png} (100%) rename docs/cce/umn/{en-us_image_0000001797910405.png => en-us_image_0000001851745744.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950592.png => en-us_image_0000001851745764.png} (100%) rename docs/cce/umn/{en-us_image_0000001865334477.png => en-us_image_0000001851745808.png} (100%) rename docs/cce/umn/{en-us_image_0000001797910077.png => en-us_image_0000001851745844.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950404.png => en-us_image_0000001851745852.png} (100%) rename docs/cce/umn/{en-us_image_0000001817324166.png => en-us_image_0000001851745864.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871305.png => en-us_image_0000001851746056.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001851746060.png rename docs/cce/umn/{en-us_image_0000001750950640.png => en-us_image_0000001851746444.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871437.png => en-us_image_0000001851746504.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791744.png => en-us_image_0000001851746508.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871433.png => en-us_image_0000001851746544.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870849.png => en-us_image_0000001852319184.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001863378970.png delete mode 100644 docs/cce/umn/en-us_image_0000001864147989.png delete mode 100644 docs/cce/umn/en-us_image_0000001865760133.png create mode 100644 docs/cce/umn/en-us_image_0000001867802022.png rename docs/cce/umn/{en-us_image_0000001797869869.jpg => en-us_image_0000001897904309.jpg} (100%) rename docs/cce/umn/{en-us_image_0000001750790256.png => en-us_image_0000001897904393.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909149.png => en-us_image_0000001897904433.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790556.png => en-us_image_0000001897904509.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909273.png => en-us_image_0000001897904517.png} (100%) rename docs/cce/umn/{en-us_image_0000001797908909.png => en-us_image_0000001897904533.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790112.png => en-us_image_0000001897904561.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790212.png => en-us_image_0000001897904609.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790504.png => en-us_image_0000001897904725.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909109.png => en-us_image_0000001897904773.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909117.png => en-us_image_0000001897904777.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790740.png => en-us_image_0000001897905025.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949656.png => en-us_image_0000001897905033.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870453.png => en-us_image_0000001897905069.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909497.png => en-us_image_0000001897905113.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790672.png => en-us_image_0000001897905125.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909489.png => en-us_image_0000001897905169.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790816.png => en-us_image_0000001897905209.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949980.png => en-us_image_0000001897905601.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949988.png => en-us_image_0000001897905605.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870753.png => en-us_image_0000001897905733.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950176.png => en-us_image_0000001897905793.png} (100%) rename docs/cce/umn/{en-us_image_0000001797910061.png => en-us_image_0000001897905921.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791424.png => en-us_image_0000001897906037.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950104.png => en-us_image_0000001897906049.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950144.png => en-us_image_0000001897906057.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909977.png => en-us_image_0000001897906097.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870965.png => en-us_image_0000001897906125.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791280.png => en-us_image_0000001897906145.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791276.png => en-us_image_0000001897906149.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950196.jpg => en-us_image_0000001897906165.jpg} (100%) rename docs/cce/umn/{en-us_image_0000001750950376.png => en-us_image_0000001897906185.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001897906197.png rename docs/cce/umn/{en-us_image_0000001750791308.png => en-us_image_0000001897906213.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871005.png => en-us_image_0000001897906225.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871009.png => en-us_image_0000001897906233.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791324.png => en-us_image_0000001897906237.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871049.png => en-us_image_0000001897906253.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871313.png => en-us_image_0000001897906289.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791468.png => en-us_image_0000001897906293.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791508.png => en-us_image_0000001897906365.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871421.png => en-us_image_0000001897906417.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950604.png => en-us_image_0000001897906445.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001897906717.png create mode 100644 docs/cce/umn/en-us_image_0000001897906729.png rename docs/cce/umn/{en-us_image_0000001750950652.png => en-us_image_0000001897907185.png} (100%) rename docs/cce/umn/{en-us_image_0000001797908741.png => en-us_image_0000001898023829.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790208.png => en-us_image_0000001898023841.png} (100%) rename docs/cce/umn/{en-us_image_0000001797908765.png => en-us_image_0000001898023873.png} (100%) rename docs/cce/umn/{en-us_image_0000001797869769.gif => en-us_image_0000001898023913.gif} (100%) rename docs/cce/umn/{en-us_image_0000001797908853.png => en-us_image_0000001898023989.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790376.png => en-us_image_0000001898024017.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949452.png => en-us_image_0000001898024033.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949468.png => en-us_image_0000001898024041.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909005.png => en-us_image_0000001898024049.png} (100%) rename docs/cce/umn/{en-us_image_0000001797869889.png => en-us_image_0000001898024061.png} (100%) rename docs/cce/umn/{en-us_image_0000001797908833.png => en-us_image_0000001898024113.png} (100%) rename docs/cce/umn/{en-us_image_0000001797908933.png => en-us_image_0000001898024121.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001898024145.png rename docs/cce/umn/{en-us_image_0000001797870781.png => en-us_image_0000001898024157.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870281.png => en-us_image_0000001898024237.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870201.png => en-us_image_0000001898024249.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790392.png => en-us_image_0000001898024285.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949476.png => en-us_image_0000001898024289.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909137.png => en-us_image_0000001898024333.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001898024381.png rename docs/cce/umn/{en-us_image_0000001797870321.png => en-us_image_0000001898024541.png} (100%) rename docs/cce/umn/{en-us_image_0000001750949552.png => en-us_image_0000001898024545.png} (100%) rename docs/cce/umn/{en-us_image_0000001797909449.png => en-us_image_0000001898024565.png} (100%) rename docs/cce/umn/{en-us_image_0000001750790684.png => en-us_image_0000001898024613.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870461.png => en-us_image_0000001898024625.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950096.png => en-us_image_0000001898024709.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001898025121.png rename docs/cce/umn/{en-us_image_0000001750791196.png => en-us_image_0000001898025173.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870789.png => en-us_image_0000001898025401.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870805.png => en-us_image_0000001898025441.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791220.png => en-us_image_0000001898025573.png} (100%) rename docs/cce/umn/{en-us_image_0000001797870909.png => en-us_image_0000001898025577.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791284.png => en-us_image_0000001898025669.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791360.png => en-us_image_0000001898025681.png} (100%) rename docs/cce/umn/{en-us_image_0000001797910165.png => en-us_image_0000001898025705.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950232.png => en-us_image_0000001898025749.png} (100%) rename docs/cce/umn/{en-us_image_0000001750950272.png => en-us_image_0000001898025781.png} (100%) rename docs/cce/umn/{en-us_image_0000001797910209.png => en-us_image_0000001898025869.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791656.png => en-us_image_0000001898025885.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791684.png => en-us_image_0000001898025961.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791480.png => en-us_image_0000001898026001.png} (100%) rename docs/cce/umn/{en-us_image_0000001797871321.png => en-us_image_0000001898026021.png} (100%) rename docs/cce/umn/{en-us_image_0000001750791484.png => en-us_image_0000001898026057.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001898026645.png rename docs/cce/umn/{en-us_image_0000001750791636.png => en-us_image_0000001898026669.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001898026693.png rename docs/cce/umn/{en-us_image_0000001750950646.png => en-us_image_0000001898026705.png} (100%) rename docs/cce/umn/{en-us_image_0000001817482742.png => en-us_image_0000001902829161.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000001909237081.png create mode 100644 docs/cce/umn/en-us_image_0000001911555737.png diff --git a/docs/cce/umn/ALL_META.TXT.json b/docs/cce/umn/ALL_META.TXT.json index 1f489ef2..e00f7a4d 100644 --- a/docs/cce/umn/ALL_META.TXT.json +++ b/docs/cce/umn/ALL_META.TXT.json @@ -260,31 +260,11 @@ "title":"Kubernetes Version Support Mechanism", "githuburl":"" }, - { - "uri":"cce_bulletin_0301.html", - "node_id":"cce_bulletin_0301.xml", - "product_code":"cce", - "code":"15", - "des":"CCE nodes in Hybrid clusters can run on EulerOS 2.5, EulerOS 2.9 , HCE OS 2.0 and Ubuntu 22.04. You are not advised to use the CentOS 7.7 image to create nodes because th", - "doc_type":"usermanual2", - "kw":"OS Patch Notes for Cluster Nodes,Product Bulletin,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"cce", - "opensource":"true", - "documenttype":"usermanual2", - "IsMulti":"Yes" - } - ], - "title":"OS Patch Notes for Cluster Nodes", - "githuburl":"" - }, { "uri":"cce_bulletin_0061.html", "node_id":"cce_bulletin_0061.xml", "product_code":"cce", - "code":"16", + "code":"15", "des":"Dear users,We are pleased to announce that a brand-new CCE console is available. The new console is modern, visually appealing, and concise, providing a more comfortable ", "doc_type":"usermanual2", "kw":"CCE Console Upgrade,Product Bulletin,User Guide", @@ -301,7 +281,7 @@ "uri":"cce_bulletin_0169.html", "node_id":"cce_bulletin_0169.xml", "product_code":"cce", - "code":"17", + "code":"16", "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", @@ -321,7 +301,7 @@ "uri":"cce_bulletin_0011.html", "node_id":"cce_bulletin_0011.xml", "product_code":"cce", - "code":"18", + "code":"17", "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", @@ -340,7 +320,7 @@ "uri":"CVE-2021-4034.html", "node_id":"cve-2021-4034.xml", "product_code":"cce", - "code":"19", + "code":"18", "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", @@ -360,7 +340,7 @@ "uri":"cce_bulletin_0206.html", "node_id":"cce_bulletin_0206.xml", "product_code":"cce", - "code":"20", + "code":"19", "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", @@ -380,7 +360,7 @@ "uri":"cce_qs_0000.html", "node_id":"cce_qs_0000.xml", "product_code":"cce", - "code":"21", + "code":"20", "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", @@ -400,7 +380,7 @@ "uri":"cce_qs_0001.html", "node_id":"cce_qs_0001.xml", "product_code":"cce", - "code":"22", + "code":"21", "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", @@ -408,7 +388,7 @@ "metedata":[ { "prodname":"cce", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Introduction", @@ -418,7 +398,7 @@ "uri":"cce_qs_0006.html", "node_id":"cce_qs_0006.xml", "product_code":"cce", - "code":"23", + "code":"22", "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", @@ -426,7 +406,7 @@ "metedata":[ { "prodname":"cce", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Preparations", @@ -436,7 +416,7 @@ "uri":"cce_qs_0008.html", "node_id":"cce_qs_0008.xml", "product_code":"cce", - "code":"24", + "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", "doc_type":"usermanual2", "kw":"Creating a Kubernetes Cluster,Getting Started,User Guide", @@ -444,7 +424,7 @@ "metedata":[ { "prodname":"cce", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Creating a Kubernetes Cluster", @@ -454,7 +434,7 @@ "uri":"cce_qs_0003.html", "node_id":"cce_qs_0003.xml", "product_code":"cce", - "code":"25", + "code":"24", "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", @@ -462,7 +442,7 @@ "metedata":[ { "prodname":"cce", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Creating a Deployment (Nginx)", @@ -472,7 +452,7 @@ "uri":"cce_qs_0007.html", "node_id":"cce_qs_0007.xml", "product_code":"cce", - "code":"26", + "code":"25", "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", @@ -480,7 +460,7 @@ "metedata":[ { "prodname":"cce", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Deploying WordPress and MySQL That Depend on Each Other", @@ -490,7 +470,7 @@ "uri":"cce_qs_0009.html", "node_id":"cce_qs_0009.xml", "product_code":"cce", - "code":"27", + "code":"26", "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", @@ -498,7 +478,7 @@ "metedata":[ { "prodname":"cce", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Overview", @@ -508,7 +488,7 @@ "uri":"cce_qs_0004.html", "node_id":"cce_qs_0004.xml", "product_code":"cce", - "code":"28", + "code":"27", "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", @@ -516,7 +496,7 @@ "metedata":[ { "prodname":"cce", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Creating a MySQL Workload", @@ -526,7 +506,7 @@ "uri":"cce_qs_0005.html", "node_id":"cce_qs_0005.xml", "product_code":"cce", - "code":"29", + "code":"28", "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", @@ -534,7 +514,7 @@ "metedata":[ { "prodname":"cce", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Creating a WordPress Workload", @@ -544,7 +524,7 @@ "uri":"cce_10_0054.html", "node_id":"cce_10_0054.xml", "product_code":"cce", - "code":"30", + "code":"29", "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 and Solutions,User Guide", @@ -552,9 +532,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"High-Risk Operations and Solutions", @@ -564,7 +542,7 @@ "uri":"cce_10_0091.html", "node_id":"cce_10_0091.xml", "product_code":"cce", - "code":"31", + "code":"30", "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", @@ -572,9 +550,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Clusters", @@ -584,7 +560,7 @@ "uri":"cce_10_0002.html", "node_id":"cce_10_0002.xml", "product_code":"cce", - "code":"32", + "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":"Cluster Overview", @@ -592,9 +568,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Cluster Overview", @@ -604,7 +578,7 @@ "uri":"cce_10_0430.html", "node_id":"cce_10_0430.xml", "product_code":"cce", - "code":"33", + "code":"32", "des":"Kubernetes is an open source container orchestration engine for automating deployment, scaling, and management of containerized applications.For developers, Kubernetes is", "doc_type":"usermanual2", "kw":"Master Nodes,Basic Cluster Information,Cluster Overview,User Guide", @@ -612,9 +586,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Basic Cluster Information", @@ -624,20 +596,36 @@ "uri":"cce_10_0068.html", "node_id":"cce_10_0068.xml", "product_code":"cce", - "code":"34", + "code":"33", "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 Release Notes", + "kw":"Kubernetes Version Release Notes", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], - "title":"Kubernetes Release Notes", + "title":"Kubernetes Version Release Notes", + "githuburl":"" + }, + { + "uri":"cce_bulletin_0068.html", + "node_id":"cce_bulletin_0068.xml", + "product_code":"cce", + "code":"34", + "des":"CCE allows you to create Kubernetes clusters 1.28. This section describes the changes made in Kubernetes 1.28.Important NotesNew and Enhanced FeaturesAPI Changes and Remo", + "doc_type":"usermanual2", + "kw":"Kubernetes 1.28 Release Notes,Kubernetes Version Release Notes,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual2" + } + ], + "title":"Kubernetes 1.28 Release Notes", "githuburl":"" }, { @@ -647,14 +635,12 @@ "code":"35", "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", "doc_type":"usermanual2", - "kw":"Kubernetes 1.27 Release Notes,Kubernetes Release Notes,User Guide", + "kw":"Kubernetes 1.27 Release Notes,Kubernetes Version Release Notes,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Kubernetes 1.27 Release Notes", @@ -667,14 +653,12 @@ "code":"36", "des":"CCE has passed the Certified Kubernetes Conformance Program and is a certified Kubernetes offering. This section describes the changes made in Kubernetes 1.25 compared wi", "doc_type":"usermanual2", - "kw":"Kubernetes 1.25 Release Notes,Kubernetes Release Notes,User Guide", + "kw":"Kubernetes 1.25 Release Notes,Kubernetes Version Release Notes,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Kubernetes 1.25 Release Notes", @@ -687,14 +671,12 @@ "code":"37", "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", "doc_type":"usermanual2", - "kw":"Kubernetes 1.23 Release Notes,Kubernetes Release Notes,User Guide", + "kw":"Kubernetes 1.23 Release Notes,Kubernetes Version Release Notes,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Kubernetes 1.23 Release Notes", @@ -707,14 +689,12 @@ "code":"38", "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 ", "doc_type":"usermanual2", - "kw":"Kubernetes 1.21 Release Notes,Kubernetes Release Notes,User Guide", + "kw":"Kubernetes 1.21 Release Notes,Kubernetes Version Release Notes,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Kubernetes 1.21 Release Notes", @@ -727,14 +707,12 @@ "code":"39", "des":"CCE has passed the Certified Kubernetes Conformance Program and is a certified Kubernetes offering. This section describes the updates in CCE Kubernetes 1.19.Kubernetes v", "doc_type":"usermanual2", - "kw":"Kubernetes 1.19 (EOM) Release Notes,Kubernetes Release Notes,User Guide", + "kw":"Kubernetes 1.19 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Kubernetes 1.19 (EOM) Release Notes", @@ -747,14 +725,12 @@ "code":"40", "des":"CCE has passed the Certified Kubernetes Conformance Program and is a certified Kubernetes offering. This section describes the updates in CCE Kubernetes 1.17.All resource", "doc_type":"usermanual2", - "kw":"Kubernetes 1.17 (EOM) Release Notes,Kubernetes Release Notes,User Guide", + "kw":"Kubernetes 1.17 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Kubernetes 1.17 (EOM) Release Notes", @@ -767,17 +743,15 @@ "code":"41", "des":"In CCE v1.27 and later versions, all nodes support only the containerd container engine.All nodes in the CCE clusters of version 1.25, except the ones running EulerOS 2.5", "doc_type":"usermanual2", - "kw":"Release Notes for CCE Cluster Versions,Cluster Overview,User Guide", + "kw":"Patch Version Release Notes,Cluster Overview,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], - "title":"Release Notes for CCE Cluster Versions", + "title":"Patch Version Release Notes", "githuburl":"" }, { @@ -792,9 +766,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Creating a Cluster", @@ -805,19 +777,17 @@ "node_id":"cce_10_0342.xml", "product_code":"cce", "code":"43", - "des":"The following table lists the differences between CCE Turbo clusters and CCE standard clusters.", + "des":"CCE provides different types of clusters for you to select. The following table lists the differences between them.", "doc_type":"usermanual2", - "kw":"CCE Turbo Clusters and CCE Standard Clusters,Creating a Cluster,User Guide", + "kw":"Comparison Between Cluster Types,Creating a Cluster,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], - "title":"CCE Turbo Clusters and CCE Standard Clusters", + "title":"Comparison Between Cluster Types", "githuburl":"" }, { @@ -827,17 +797,15 @@ "code":"44", "des":"On the CCE console, you can easily create Kubernetes clusters. After a cluster is created, the master node is hosted by CCE. You only need to create worker nodes. In this", "doc_type":"usermanual2", - "kw":"Creating a CCE Cluster,Creating a Cluster,User Guide", + "kw":"Creating a CCE Standard/Turbo Cluster,Creating a Cluster,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], - "title":"Creating a CCE Cluster", + "title":"Creating a CCE Standard/Turbo Cluster", "githuburl":"" }, { @@ -852,9 +820,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Comparing iptables and IPVS", @@ -872,9 +838,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Connecting to a Cluster", @@ -885,16 +849,14 @@ "node_id":"cce_10_0107.xml", "product_code":"cce", "code":"47", - "des":"This section uses a CCE standard cluster as an example to describe how to connect to a CCE cluster using kubectl.When you access a cluster using kubectl, CCE uses kubecon", + "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 ", "doc_type":"usermanual2", - "kw":"kubectl,kubeconfig,Intranet access,Two-Way Authentication for Domain Names,Error from server Forbidd", + "kw":"kubectl,Intranet access,Two-Way Authentication for Domain Names,Error from server Forbidden,The conn", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Connecting to a Cluster Using kubectl", @@ -905,16 +867,14 @@ "node_id":"cce_10_0175.xml", "product_code":"cce", "code":"48", - "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":"This section describes how to obtain the cluster certificate from the console and use it access Kubernetes clusters.The downloaded certificate contains three files: clien", "doc_type":"usermanual2", "kw":"X.509 certificate,Connecting to a Cluster Using an X.509 Certificate,Connecting to a Cluster,User Gu", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Connecting to a Cluster Using an X.509 Certificate", @@ -927,14 +887,12 @@ "code":"49", "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", "doc_type":"usermanual2", - "kw":"SAN,Accessing a Cluster Using a Custom Domain Name,Connecting to a Cluster,User Guide", + "kw":"SAN,X.509 certificate,Accessing a Cluster Using a Custom Domain Name,Connecting to a Cluster,User Gu", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Accessing a Cluster Using a Custom Domain Name", @@ -952,9 +910,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Upgrading a Cluster", @@ -965,16 +921,14 @@ "node_id":"cce_10_0197.xml", "product_code":"cce", "code":"51", - "des":"To enable interoperability from one Kubernetes installation to the next, you must upgrade your Kubernetes clusters before the maintenance period ends.After the latest Kub", + "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,Upgrade,In-place upgrade,Upgrade Overview,Upgrading a Cluster,User Guide", + "kw":"cluster upgrade process,Node Priority,In-place upgrade,Upgrade Overview,Upgrading a Cluster,User Gui", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Upgrade Overview", @@ -992,39 +946,17 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Before You Start", "githuburl":"" }, - { - "uri":"cce_10_0301.html", - "node_id":"cce_10_0301.xml", - "product_code":"cce", - "code":"53", - "des":"You can upgrade your clusters to a newer version on the CCE console.Before the upgrade, learn about the target version to which each CCE cluster can be upgraded in what w", - "doc_type":"usermanual2", - "kw":"Node Priority,Performing an In-place Upgrade,Upgrading a Cluster,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" - } - ], - "title":"Performing an In-place Upgrade", - "githuburl":"" - }, { "uri":"cce_10_0560.html", "node_id":"cce_10_0560.xml", "product_code":"cce", - "code":"54", + "code":"53", "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":"Performing Post-Upgrade Verification", @@ -1032,79 +964,17 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Performing Post-Upgrade Verification", "githuburl":"" }, - { - "uri":"cce_10_0562.html", - "node_id":"cce_10_0562.xml", - "product_code":"cce", - "code":"55", - "des":"Check whether there are unexpected pods in the cluster.Check whether there are any pods that ran properly originally in the cluster restart unexpectedly.If there are abno", - "doc_type":"usermanual2", - "kw":"Pod Check,Performing Post-Upgrade Verification,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" - } - ], - "title":"Pod Check", - "githuburl":"" - }, - { - "uri":"cce_10_0563.html", - "node_id":"cce_10_0563.xml", - "product_code":"cce", - "code":"56", - "des":"Check whether nodes are running properly.Check whether the node network is functional.Check whether the container network is functional.If the container network malfuncti", - "doc_type":"usermanual2", - "kw":"Node and Container Network Check,Performing Post-Upgrade Verification,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" - } - ], - "title":"Node and Container Network Check", - "githuburl":"" - }, - { - "uri":"cce_10_0564.html", - "node_id":"cce_10_0564.xml", - "product_code":"cce", - "code":"57", - "des":"Check whether custom node labels are lost.Check whether there are any unexpected taints newly added on the node, which will affect workload scheduling.Custom labels will ", - "doc_type":"usermanual2", - "kw":"Node Label and Taint Check,Performing Post-Upgrade Verification,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" - } - ], - "title":"Node Label and Taint Check", - "githuburl":"" - }, { "uri":"cce_10_0568.html", "node_id":"cce_10_0568.xml", "product_code":"cce", - "code":"58", + "code":"54", "des":"After a cluster is upgraded, check whether the cluster is in the Running state.CCE automatically checks your cluster status. Go to the cluster list page and confirm the c", "doc_type":"usermanual2", "kw":"Cluster Status Check,Performing Post-Upgrade Verification,User Guide", @@ -1112,9 +982,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Cluster Status Check", @@ -1124,7 +992,7 @@ "uri":"cce_10_0569.html", "node_id":"cce_10_0569.xml", "product_code":"cce", - "code":"59", + "code":"55", "des":"After a cluster is upgraded, check whether nodes in the cluster are in the Running state.CCE automatically checks your node statuses. Go to the node list page and confirm", "doc_type":"usermanual2", "kw":"Node Status Check,Performing Post-Upgrade Verification,User Guide", @@ -1132,9 +1000,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Status Check", @@ -1144,7 +1010,7 @@ "uri":"cce_10_0567.html", "node_id":"cce_10_0567.xml", "product_code":"cce", - "code":"60", + "code":"56", "des":"After a cluster is upgraded, check whether there are any nodes that skip the upgrade in the cluster. These nodes may affect the proper running of the cluster.CCE automati", "doc_type":"usermanual2", "kw":"Node Skipping Check,Performing Post-Upgrade Verification,User Guide", @@ -1152,9 +1018,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Skipping Check", @@ -1164,7 +1028,7 @@ "uri":"cce_10_0561.html", "node_id":"cce_10_0561.xml", "product_code":"cce", - "code":"61", + "code":"57", "des":"After a cluster is upgraded, check whether its services are running properly.Different services have different verification mode. Select a suitable one and verify the ser", "doc_type":"usermanual2", "kw":"Service Check,Performing Post-Upgrade Verification,User Guide", @@ -1172,9 +1036,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Service Check", @@ -1184,7 +1046,7 @@ "uri":"cce_10_0565.html", "node_id":"cce_10_0565.xml", "product_code":"cce", - "code":"62", + "code":"58", "des":"Check whether nodes can be created in the cluster.If nodes cannot be created in your cluster after the cluster is upgraded, contact technical support.", "doc_type":"usermanual2", "kw":"New Node Check,Performing Post-Upgrade Verification,User Guide", @@ -1192,9 +1054,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"New Node Check", @@ -1204,7 +1064,7 @@ "uri":"cce_10_0566.html", "node_id":"cce_10_0566.xml", "product_code":"cce", - "code":"63", + "code":"59", "des":"Check whether pods can be created on the existing nodes after the cluster is upgraded.Check whether pods can be created on new nodes after the cluster is upgraded.After c", "doc_type":"usermanual2", "kw":"New Pod Check,Performing Post-Upgrade Verification,User Guide", @@ -1212,9 +1072,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"New Pod Check", @@ -1224,7 +1082,7 @@ "uri":"cce_10_0210.html", "node_id":"cce_10_0210.xml", "product_code":"cce", - "code":"64", + "code":"60", "des":"This section describes how to migrate services from a cluster of an earlier version to a cluster of a later version in CCE.This operation is applicable when a cross-versi", "doc_type":"usermanual2", "kw":"Migrating Services Across Clusters of Different Versions,Upgrading a Cluster,User Guide", @@ -1232,9 +1090,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Migrating Services Across Clusters of Different Versions", @@ -1244,7 +1100,7 @@ "uri":"cce_10_0550.html", "node_id":"cce_10_0550.xml", "product_code":"cce", - "code":"65", + "code":"61", "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":"Troubleshooting for Pre-upgrade Check Exceptions", @@ -1252,9 +1108,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Troubleshooting for Pre-upgrade Check Exceptions", @@ -1264,7 +1118,7 @@ "uri":"cce_10_0549.html", "node_id":"cce_10_0549.xml", "product_code":"cce", - "code":"66", + "code":"62", "des":"The system automatically checks a cluster before its upgrade. If the cluster does not meet the pre-upgrade check conditions, the upgrade cannot continue. To avoid risks, ", "doc_type":"usermanual2", "kw":"Pre-upgrade Check,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1272,9 +1126,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Pre-upgrade Check", @@ -1284,7 +1136,7 @@ "uri":"cce_10_0431.html", "node_id":"cce_10_0431.xml", "product_code":"cce", - "code":"67", + "code":"63", "des":"Check the following items:Check whether the node is available.Check whether the node OS supports the upgrade.Check whether the node is marked with unexpected node pool la", "doc_type":"usermanual2", "kw":"Node Restrictions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1292,9 +1144,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Restrictions", @@ -1304,7 +1154,7 @@ "uri":"cce_10_0432.html", "node_id":"cce_10_0432.xml", "product_code":"cce", - "code":"68", + "code":"64", "des":"Check whether the target cluster is under upgrade management.CCE may temporarily restrict the cluster upgrade due to the following reasons:The cluster is identified as th", "doc_type":"usermanual2", "kw":"Upgrade Management,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1312,9 +1162,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Upgrade Management", @@ -1324,7 +1172,7 @@ "uri":"cce_10_0433.html", "node_id":"cce_10_0433.xml", "product_code":"cce", - "code":"69", + "code":"65", "des":"Check the following items:Check whether the add-on status is normal.Check whether the add-on support the target version.Scenario 1: The add-on malfunctions.Log in to the ", "doc_type":"usermanual2", "kw":"Add-ons,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1332,9 +1180,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Add-ons", @@ -1344,7 +1190,7 @@ "uri":"cce_10_0434.html", "node_id":"cce_10_0434.xml", "product_code":"cce", - "code":"70", + "code":"66", "des":"Check whether the current HelmRelease record contains discarded Kubernetes APIs that are not supported by the target cluster version. If yes, the Helm chart may be unavai", "doc_type":"usermanual2", "kw":"Helm Charts,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1352,9 +1198,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Helm Charts", @@ -1364,7 +1208,7 @@ "uri":"cce_10_0435.html", "node_id":"cce_10_0435.xml", "product_code":"cce", - "code":"71", + "code":"67", "des":"Check whether CCE can connect to your master nodes.Contact technical support.", "doc_type":"usermanual2", "kw":"SSH Connectivity of Master Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1372,9 +1216,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"SSH Connectivity of Master Nodes", @@ -1384,7 +1226,7 @@ "uri":"cce_10_0436.html", "node_id":"cce_10_0436.xml", "product_code":"cce", - "code":"72", + "code":"68", "des":"Check the node pool status.Check whether the node pool OS or container runtime is supported after the upgrade.Scenario: The node pool malfunctions.Log in to the CCE conso", "doc_type":"usermanual2", "kw":"Node Pools,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1392,9 +1234,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Pools", @@ -1404,7 +1244,7 @@ "uri":"cce_10_0437.html", "node_id":"cce_10_0437.xml", "product_code":"cce", - "code":"73", + "code":"69", "des":"Check whether the Protocol & Port of the worker node security groups are set to ICMP: All and whether the security group with the source IP address set to the master node", "doc_type":"usermanual2", "kw":"Security Groups,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1412,9 +1252,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Security Groups", @@ -1424,7 +1262,7 @@ "uri":"cce_10_0439.html", "node_id":"cce_10_0439.xml", "product_code":"cce", - "code":"74", + "code":"70", "des":"Check whether the node needs to be migrated.For the 1.15 cluster that is upgraded from 1.13 in rolling mode, migrate (reset or create and replace) all nodes before perfor", "doc_type":"usermanual2", "kw":"To-Be-Migrated Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1432,9 +1270,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"To-Be-Migrated Nodes", @@ -1444,7 +1280,7 @@ "uri":"cce_10_0440.html", "node_id":"cce_10_0440.xml", "product_code":"cce", - "code":"75", + "code":"71", "des":"Check whether there are discarded resources in the clusters.Scenario: The Service in the clusters of v1.25 or later has discarded annotation: tolerate-unready-endpoints.E", "doc_type":"usermanual2", "kw":"Discarded Kubernetes Resources,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1452,9 +1288,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Discarded Kubernetes Resources", @@ -1464,7 +1298,7 @@ "uri":"cce_10_0441.html", "node_id":"cce_10_0441.xml", "product_code":"cce", - "code":"76", + "code":"72", "des":"Read the version compatibility differences and ensure that they are not affected. The patch upgrade does not involve version compatibility differences.", "doc_type":"usermanual2", "kw":"Compatibility Risks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1472,9 +1306,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Compatibility Risks", @@ -1484,27 +1316,25 @@ "uri":"cce_10_0442.html", "node_id":"cce_10_0442.xml", "product_code":"cce", - "code":"77", + "code":"73", "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", "doc_type":"usermanual2", - "kw":"Node CCE Agent Versions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "kw":"CCE Agent Versions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], - "title":"Node CCE Agent Versions", + "title":"CCE Agent Versions", "githuburl":"" }, { "uri":"cce_10_0443.html", "node_id":"cce_10_0443.xml", "product_code":"cce", - "code":"78", + "code":"74", "des":"Check whether the CPU usage of the node exceeds 90%.Upgrade the cluster during off-peak hours.Check whether too many pods are deployed on the node. If yes, reschedule pod", "doc_type":"usermanual2", "kw":"Node CPU Usage,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1512,9 +1342,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node CPU Usage", @@ -1524,7 +1352,7 @@ "uri":"cce_10_0444.html", "node_id":"cce_10_0444.xml", "product_code":"cce", - "code":"79", + "code":"75", "des":"Check the following items:Check whether the key CRD packageversions.version.cce.io of the cluster is deleted.Check whether the cluster key CRD network-attachment-definiti", "doc_type":"usermanual2", "kw":"CRDs,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1532,9 +1360,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"CRDs", @@ -1544,7 +1370,7 @@ "uri":"cce_10_0445.html", "node_id":"cce_10_0445.xml", "product_code":"cce", - "code":"80", + "code":"76", "des":"Check the following items:Check whether the key data disks on the node meet the upgrade requirements.Check whether the /tmp directory has 500 MB available space.During th", "doc_type":"usermanual2", "kw":"Node Disks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1552,9 +1378,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Disks", @@ -1564,7 +1388,7 @@ "uri":"cce_10_0446.html", "node_id":"cce_10_0446.xml", "product_code":"cce", - "code":"81", + "code":"77", "des":"Check the following items:Check whether the DNS configuration of the current node can resolve the OBS address.Check whether the current node can access the OBS address of", "doc_type":"usermanual2", "kw":"Node DNS,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1572,9 +1396,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node DNS", @@ -1584,7 +1406,7 @@ "uri":"cce_10_0447.html", "node_id":"cce_10_0447.xml", "product_code":"cce", - "code":"82", + "code":"78", "des":"Check whether the owner and owner group of the files in the /var/paas directory used by the CCE are both paas.Scenario 1: The error message \"xx file permission has been c", "doc_type":"usermanual2", "kw":"Node Key Directory File Permissions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1592,9 +1414,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Key Directory File Permissions", @@ -1604,7 +1424,7 @@ "uri":"cce_10_0448.html", "node_id":"cce_10_0448.xml", "product_code":"cce", - "code":"83", + "code":"79", "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", "doc_type":"usermanual2", "kw":"Kubelet,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1612,9 +1432,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Kubelet", @@ -1624,7 +1442,7 @@ "uri":"cce_10_0449.html", "node_id":"cce_10_0449.xml", "product_code":"cce", - "code":"84", + "code":"80", "des":"Check whether the memory usage of the node exceeds 90%.Upgrade the cluster during off-peak hours.Check whether too many pods are deployed on the node. If yes, reschedule ", "doc_type":"usermanual2", "kw":"Node Memory,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1632,9 +1450,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Memory", @@ -1644,7 +1460,7 @@ "uri":"cce_10_0450.html", "node_id":"cce_10_0450.xml", "product_code":"cce", - "code":"85", + "code":"81", "des":"Check whether the clock synchronization server ntpd or chronyd of the node is running properly.Scenario 1: ntpd is running abnormally.Log in to the node and run the syste", "doc_type":"usermanual2", "kw":"Node Clock Synchronization Server,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1652,9 +1468,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Clock Synchronization Server", @@ -1664,17 +1478,15 @@ "uri":"cce_10_0451.html", "node_id":"cce_10_0451.xml", "product_code":"cce", - "code":"86", - "des":"Check whether the OS kernel version of the node is supported by CCE.CCE nodes run depending on the initial standard kernel version when they are created. CCE has performe", + "code":"82", + "des":"Check whether the OS kernel version of the node is supported by CCE.Case 1: The node image is not a standard CCE image.CCE nodes run depending on the initial standard ker", "doc_type":"usermanual2", "kw":"Node OS,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node OS", @@ -1684,7 +1496,7 @@ "uri":"cce_10_0452.html", "node_id":"cce_10_0452.xml", "product_code":"cce", - "code":"87", + "code":"83", "des":"Check whether the number of CPUs on the master node is greater than 2.If the number of CPUs on the master node is 2, contact technical support to expand the number to 4 o", "doc_type":"usermanual2", "kw":"Node CPUs,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1692,9 +1504,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node CPUs", @@ -1704,7 +1514,7 @@ "uri":"cce_10_0453.html", "node_id":"cce_10_0453.xml", "product_code":"cce", - "code":"88", + "code":"84", "des":"Check whether the Python commands are available on a node.If the command output is not 0, the check fails.Install Python before the upgrade.", "doc_type":"usermanual2", "kw":"Node Python Commands,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1712,9 +1522,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Python Commands", @@ -1724,7 +1532,7 @@ "uri":"cce_10_0455.html", "node_id":"cce_10_0455.xml", "product_code":"cce", - "code":"89", + "code":"85", "des":"Check whether the nodes in the cluster are ready.Scenario 1: The nodes are in the unavailable status.Log in to the CCE console and click the cluster name to access the cl", "doc_type":"usermanual2", "kw":"Node Readiness,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1732,9 +1540,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Readiness", @@ -1744,7 +1550,7 @@ "uri":"cce_10_0456.html", "node_id":"cce_10_0456.xml", "product_code":"cce", - "code":"90", + "code":"86", "des":"Check whether journald of a node is normal.Log in to the node and run the systemctl is-active systemd-journald command to obtain the running status of journald. If the co", "doc_type":"usermanual2", "kw":"Node journald,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1752,9 +1558,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node journald", @@ -1764,7 +1568,7 @@ "uri":"cce_10_0457.html", "node_id":"cce_10_0457.xml", "product_code":"cce", - "code":"91", + "code":"87", "des":"Check whether the containerd.sock file exists on the node. This file affects the startup of container runtime in the Euler OS.Scenario: The Docker used by the node is the", "doc_type":"usermanual2", "kw":"containerd.sock,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1772,9 +1576,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"containerd.sock", @@ -1784,7 +1586,7 @@ "uri":"cce_10_0458.html", "node_id":"cce_10_0458.xml", "product_code":"cce", - "code":"92", + "code":"88", "des":"Before the upgrade, check whether an internal error occurs.If this check fails, contact technical support.", "doc_type":"usermanual2", "kw":"Internal Errors,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1792,9 +1594,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Internal Errors", @@ -1804,17 +1604,15 @@ "uri":"cce_10_0459.html", "node_id":"cce_10_0459.xml", "product_code":"cce", - "code":"93", - "des":"Check whether inaccessible mount points exist on the node.Scenario: There are inaccessible mount points on the node.If NFS (such as OBS parallel file systems and SFS) is ", + "code":"89", + "des":"Check whether inaccessible mount points exist on the node.Scenario: There are inaccessible mount points on the node.If NFS (such as obsfs or SFS) is used by the node and ", "doc_type":"usermanual2", "kw":"Node Mount Points,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Mount Points", @@ -1824,7 +1622,7 @@ "uri":"cce_10_0460.html", "node_id":"cce_10_0460.xml", "product_code":"cce", - "code":"94", + "code":"90", "des":"Check whether the taint needed for cluster upgrade exists on the node.Scenario 1: The node is skipped during the cluster upgrade.If the version of the node is different f", "doc_type":"usermanual2", "kw":"Kubernetes Node Taints,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1832,9 +1630,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Kubernetes Node Taints", @@ -1844,7 +1640,7 @@ "uri":"cce_10_0478.html", "node_id":"cce_10_0478.xml", "product_code":"cce", - "code":"95", + "code":"91", "des":"Check whether there are any compatibility restrictions on the current Everest add-on.There are compatibility restrictions on the current Everest add-on and it cannot be u", "doc_type":"usermanual2", "kw":"Everest Restrictions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1852,9 +1648,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Everest Restrictions", @@ -1864,7 +1658,7 @@ "uri":"cce_10_0479.html", "node_id":"cce_10_0479.xml", "product_code":"cce", - "code":"96", + "code":"92", "des":"Check whether the current cce-controller-hpa add-on has compatibility restrictions.The current cce-controller-hpa add-on has compatibility restrictions. An add-on that ca", "doc_type":"usermanual2", "kw":"cce-hpa-controller Restrictions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1872,9 +1666,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"cce-hpa-controller Restrictions", @@ -1884,7 +1676,7 @@ "uri":"cce_10_0480.html", "node_id":"cce_10_0480.xml", "product_code":"cce", - "code":"97", + "code":"93", "des":"Check whether the current cluster version and the target version support enhanced CPU policy.Scenario: Only the current cluster version supports the enhanced CPU policy f", "doc_type":"usermanual2", "kw":"Enhanced CPU Policies,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1892,9 +1684,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Enhanced CPU Policies", @@ -1904,7 +1694,7 @@ "uri":"cce_10_0484.html", "node_id":"cce_10_0484.xml", "product_code":"cce", - "code":"98", + "code":"94", "des":"Check whether the container runtime and network components on the worker nodes are healthy.If a worker node component malfunctions, log in to the node to check the status", "doc_type":"usermanual2", "kw":"Health of Worker Node Components,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1912,9 +1702,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Health of Worker Node Components", @@ -1924,7 +1712,7 @@ "uri":"cce_10_0485.html", "node_id":"cce_10_0485.xml", "product_code":"cce", - "code":"99", + "code":"95", "des":"Check whether the Kubernetes, container runtime, and network components of the master nodes are healthy.If a master node component malfunctions, contact technical support", "doc_type":"usermanual2", "kw":"Health of Master Node Components,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1932,9 +1720,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Health of Master Node Components", @@ -1944,7 +1730,7 @@ "uri":"cce_10_0486.html", "node_id":"cce_10_0486.xml", "product_code":"cce", - "code":"100", + "code":"96", "des":"Check whether the resources of Kubernetes components, such as etcd and kube-controller-manager, exceed the upper limit.Solution 1: Reduce Kubernetes resources that are ne", "doc_type":"usermanual2", "kw":"Memory Resource Limit of Kubernetes Components,Troubleshooting for Pre-upgrade Check Exceptions,User", @@ -1952,9 +1738,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Memory Resource Limit of Kubernetes Components", @@ -1964,7 +1748,7 @@ "uri":"cce_10_0487.html", "node_id":"cce_10_0487.xml", "product_code":"cce", - "code":"101", + "code":"97", "des":"The system scans the audit logs of the past day to check whether the user calls the deprecated APIs of the target Kubernetes version.Due to the limited time range of audi", "doc_type":"usermanual2", "kw":"Discarded Kubernetes APIs,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1972,9 +1756,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Discarded Kubernetes APIs", @@ -1984,7 +1766,7 @@ "uri":"cce_10_0488.html", "node_id":"cce_10_0488.xml", "product_code":"cce", - "code":"102", + "code":"98", "des":"If IPv6 is enabled for a CCE Turbo cluster, check whether the target cluster version supports IPv6.CCE Turbo clusters support IPv6 since v1.23. This feature is available ", "doc_type":"usermanual2", "kw":"IPv6 Capabilities of a CCE Turbo Cluster,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1992,9 +1774,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"IPv6 Capabilities of a CCE Turbo Cluster", @@ -2004,7 +1784,7 @@ "uri":"cce_10_0489.html", "node_id":"cce_10_0489.xml", "product_code":"cce", - "code":"103", + "code":"99", "des":"Check whether NetworkManager of a node is normal.Log in to the node and run the systemctl is-active NetworkManager command to obtain the running status of NetworkManager.", "doc_type":"usermanual2", "kw":"Node NetworkManager,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2012,9 +1792,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node NetworkManager", @@ -2024,7 +1802,7 @@ "uri":"cce_10_0490.html", "node_id":"cce_10_0490.xml", "product_code":"cce", - "code":"104", + "code":"100", "des":"Check the ID file format.", "doc_type":"usermanual2", "kw":"Node ID File,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2032,9 +1810,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node ID File", @@ -2044,7 +1820,7 @@ "uri":"cce_10_0491.html", "node_id":"cce_10_0491.xml", "product_code":"cce", - "code":"105", + "code":"101", "des":"When you upgrade a cluster to v1.19 or later, the system checks whether the following configuration files have been modified on the backend:/opt/cloud/cce/kubernetes/kube", "doc_type":"usermanual2", "kw":"Node Configuration Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2052,9 +1828,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Configuration Consistency", @@ -2064,7 +1838,7 @@ "uri":"cce_10_0492.html", "node_id":"cce_10_0492.xml", "product_code":"cce", - "code":"106", + "code":"102", "des":"Check whether the configuration files of key components exist on the node.The following table lists the files to be checked.Contact technical support to restore the confi", "doc_type":"usermanual2", "kw":"Node Configuration File,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2072,9 +1846,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Configuration File", @@ -2084,7 +1856,7 @@ "uri":"cce_10_0493.html", "node_id":"cce_10_0493.xml", "product_code":"cce", - "code":"107", + "code":"103", "des":"Check whether the current CoreDNS key configuration Corefile is different from the Helm release record. The difference may be overwritten during the add-on upgrade, affec", "doc_type":"usermanual2", "kw":"CoreDNS Configuration Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2092,9 +1864,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"CoreDNS Configuration Consistency", @@ -2104,7 +1874,7 @@ "uri":"cce_10_0494.html", "node_id":"cce_10_0494.xml", "product_code":"cce", - "code":"108", + "code":"104", "des":"Whether the sudo commands and sudo-related files of the node are workingScenario 1: The sudo command fails to be executed.During the in-place cluster upgrade, the sudo co", "doc_type":"usermanual2", "kw":"sudo Commands of a Node,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2112,9 +1882,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"sudo Commands of a Node", @@ -2124,17 +1892,15 @@ "uri":"cce_10_0495.html", "node_id":"cce_10_0495.xml", "product_code":"cce", - "code":"109", - "des":"Whether some key commands that the node upgrade depends on are workingScenario 1: The package manager command fails to be executed.The rpm or dpkg command fails to be exe", + "code":"105", + "des":"Whether some key commands that the node upgrade depends on are workingScenario 1: Executing the package manager command failed.Executing the rpm or dpkg command failed. I", "doc_type":"usermanual2", "kw":"Key Commands of Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Key Commands of Nodes", @@ -2144,7 +1910,7 @@ "uri":"cce_10_0496.html", "node_id":"cce_10_0496.xml", "product_code":"cce", - "code":"110", + "code":"106", "des":"Check whether the docker/containerd.sock file is directly mounted to the pods on a node. During an upgrade, Docker or containerd restarts and the sock file on the host ch", "doc_type":"usermanual2", "kw":"Mounting of a Sock File on a Node,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2152,9 +1918,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Mounting of a Sock File on a Node", @@ -2164,17 +1928,15 @@ "uri":"cce_10_0497.html", "node_id":"cce_10_0497.xml", "product_code":"cce", - "code":"111", - "des":"Check whether the certificate used by an HTTPS load balancer has been modified on ELB.The certificate referenced by an HTTPS Ingress created on CCE is modified on the ELB", + "code":"107", + "des":"Check whether the certificate used by an HTTPS load balancer has been modified on ELB.The certificate referenced by an HTTPS ingress created on CCE is modified on the ELB", "doc_type":"usermanual2", "kw":"HTTPS Load Balancer Certificate Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Gu", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"HTTPS Load Balancer Certificate Consistency", @@ -2184,7 +1946,7 @@ "uri":"cce_10_0498.html", "node_id":"cce_10_0498.xml", "product_code":"cce", - "code":"112", + "code":"108", "des":"Check whether the default mount directory and soft link on the node have been manually mounted or modified.Non-shared diskBy default, /var/lib/docker, containerd, or /mnt", "doc_type":"usermanual2", "kw":"Node Mounting,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2192,9 +1954,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Mounting", @@ -2204,7 +1964,7 @@ "uri":"cce_10_0499.html", "node_id":"cce_10_0499.xml", "product_code":"cce", - "code":"113", + "code":"109", "des":"Check whether user paas is allowed to log in to a node.Run the following command to check whether user paas is allowed to log in to a node:If the permissions assigned to ", "doc_type":"usermanual2", "kw":"Login Permissions of User paas on a Node,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2212,9 +1972,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Login Permissions of User paas on a Node", @@ -2224,7 +1982,7 @@ "uri":"cce_10_0500.html", "node_id":"cce_10_0500.xml", "product_code":"cce", - "code":"114", + "code":"110", "des":"Check whether the load balancer associated with a Service is allocated with a private IPv4 address.Solution 1: Delete the Service that is associated with a load balancer ", "doc_type":"usermanual2", "kw":"Private IPv4 Addresses of Load Balancers,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2232,9 +1990,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Private IPv4 Addresses of Load Balancers", @@ -2244,7 +2000,7 @@ "uri":"cce_10_0501.html", "node_id":"cce_10_0501.xml", "product_code":"cce", - "code":"115", + "code":"111", "des":"Check whether the source version of the cluster is earlier than v1.11 and the target version is later than v1.23.If the source version of the cluster is earlier than v1.1", "doc_type":"usermanual2", "kw":"Historical Upgrade Records,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2252,9 +2008,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Historical Upgrade Records", @@ -2264,7 +2018,7 @@ "uri":"cce_10_0502.html", "node_id":"cce_10_0502.xml", "product_code":"cce", - "code":"116", + "code":"112", "des":"Check whether the CIDR block of the cluster management plane is the same as that configured on the backbone network.If the CIDR block of the cluster management plane is d", "doc_type":"usermanual2", "kw":"CIDR Block of the Cluster Management Plane,Troubleshooting for Pre-upgrade Check Exceptions,User Gui", @@ -2272,9 +2026,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"CIDR Block of the Cluster Management Plane", @@ -2284,7 +2036,7 @@ "uri":"cce_10_0503.html", "node_id":"cce_10_0503.xml", "product_code":"cce", - "code":"117", + "code":"113", "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 ", "doc_type":"usermanual2", "kw":"GPU Add-on,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2292,9 +2044,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"GPU Add-on", @@ -2304,7 +2054,7 @@ "uri":"cce_10_0504.html", "node_id":"cce_10_0504.xml", "product_code":"cce", - "code":"118", + "code":"114", "des":"Check whether the default system parameter settings on your nodes are modified.If the MTU value of the bond0 network on your BMS node is not the default value 1500, this ", "doc_type":"usermanual2", "kw":"Nodes' System Parameter Settings,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2312,9 +2062,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Nodes' System Parameter Settings", @@ -2324,7 +2072,7 @@ "uri":"cce_10_0505.html", "node_id":"cce_10_0505.xml", "product_code":"cce", - "code":"119", + "code":"115", "des":"Check whether there are residual package version data in the current cluster.A message is displayed indicating that there are residual 10.12.1.109 CRD resources in your c", "doc_type":"usermanual2", "kw":"Residual Package Versions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2332,9 +2080,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Residual Package Versions", @@ -2344,7 +2090,7 @@ "uri":"cce_10_0506.html", "node_id":"cce_10_0506.xml", "product_code":"cce", - "code":"120", + "code":"116", "des":"Check whether the commands required for the upgrade are available on the node.The cluster upgrade failure is typically caused by the lack of key node commands that are re", "doc_type":"usermanual2", "kw":"Node Commands,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2352,9 +2098,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Commands", @@ -2364,7 +2108,7 @@ "uri":"cce_10_0507.html", "node_id":"cce_10_0507.xml", "product_code":"cce", - "code":"121", + "code":"117", "des":"Check whether swap has been enabled on cluster nodes.By default, swap is disabled on CCE nodes. Check the necessity of enabling swap manually and determine the impact of ", "doc_type":"usermanual2", "kw":"Node Swap,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2372,9 +2116,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Swap", @@ -2384,67 +2126,169 @@ "uri":"cce_10_0510.html", "node_id":"cce_10_0510.xml", "product_code":"cce", - "code":"122", - "des":"Check whether the service containers running on a node that uses containerd are restart when the node's containerd is upgraded.Upgrade the cluster when the impact on serv", + "code":"118", + "des":"Check whether the service container running on the node may restart when the containerd component is upgraded on the node that uses containerd in the current cluster.Ensu", "doc_type":"usermanual2", - "kw":"containerd Pod Restart Risk,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "kw":"Check containerd pod restart risk,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], - "title":"containerd Pod Restart Risk", + "title":"Check containerd pod restart risk", "githuburl":"" }, { "uri":"cce_10_0511.html", "node_id":"cce_10_0511.xml", "product_code":"cce", - "code":"123", - "des":"Check whether some configurations of the CCE AI Suite add-on installed in a cluster are intrusively modified. If yes, the upgrade may fail.", + "code":"119", + "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.", "doc_type":"usermanual2", - "kw":"Key Parameters of the GPU Add-on,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "kw":"Key GPU Add-on Parameters,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], - "title":"Key Parameters of the GPU Add-on", + "title":"Key GPU Add-on Parameters", "githuburl":"" }, { "uri":"cce_10_0512.html", "node_id":"cce_10_0512.xml", "product_code":"cce", - "code":"124", - "des":"Check whether the node on which GPU/NPU service containers run is rebuilt when kubelet is restarted during the upgrade of the current cluster. If yes, the services will b", + "code":"120", + "des":"Check whether GPU or NPU service pods are rebuilt in a cluster when kubelet is restarted during the upgrade of the cluster.Upgrade the cluster when the impact on services", "doc_type":"usermanual2", - "kw":"GPU/NPU Pod Rebuilding Risk,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "kw":"GPU or NPU Pod Rebuild Risks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], - "title":"GPU/NPU Pod Rebuilding Risk", + "title":"GPU or NPU Pod Rebuild Risks", + "githuburl":"" + }, + { + "uri":"cce_10_0513.html", + "node_id":"cce_10_0513.xml", + "product_code":"cce", + "code":"121", + "des":"Check whether the access control of the ELB listener has been configured for the Service in the current cluster using annotations and whether the configurations are corre", + "doc_type":"usermanual2", + "kw":"ELB Listener Access Control,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual2" + } + ], + "title":"ELB Listener Access Control", + "githuburl":"" + }, + { + "uri":"cce_10_0514.html", + "node_id":"cce_10_0514.xml", + "product_code":"cce", + "code":"122", + "des":"Check whether the flavor of the master nodes in the cluster is the same as the actual flavor of these nodes.Flavor inconsistency is typically due to a modification made o", + "doc_type":"usermanual2", + "kw":"Master Node Flavor,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual2" + } + ], + "title":"Master Node Flavor", + "githuburl":"" + }, + { + "uri":"cce_10_0515.html", + "node_id":"cce_10_0515.xml", + "product_code":"cce", + "code":"123", + "des":"Check whether the number of available IP addresses in the cluster subnet supports rolling upgrade.If the number of IP addresses in the selected cluster subnet is insuffic", + "doc_type":"usermanual2", + "kw":"Subnet Quota of Master Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual2" + } + ], + "title":"Subnet Quota of Master Nodes", + "githuburl":"" + }, + { + "uri":"cce_10_0516.html", + "node_id":"cce_10_0516.xml", + "product_code":"cce", + "code":"124", + "des":"Check whether an alarm is generated when a cluster is upgraded to v1.27 or later. Do not use Docker in clusters of versions later than 1.27.If the runtime on your node is", + "doc_type":"usermanual2", + "kw":"Node Runtime,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual2" + } + ], + "title":"Node Runtime", + "githuburl":"" + }, + { + "uri":"cce_10_0517.html", + "node_id":"cce_10_0517.xml", + "product_code":"cce", + "code":"125", + "des":"Check whether an alarm is generated when a cluster is upgraded to v1.27 or later. Do not use Docker in clusters of versions later than 1.27.If the runtime on your node po", + "doc_type":"usermanual2", + "kw":"Node Pool Runtime,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual2" + } + ], + "title":"Node Pool Runtime", + "githuburl":"" + }, + { + "uri":"cce_10_0518.html", + "node_id":"cce_10_0518.xml", + "product_code":"cce", + "code":"126", + "des":"Check the number of images on your node. If the number is greater than 1000, Docker startup may be slow.Contact O&M personnel to check whether this issue affects the upgr", + "doc_type":"usermanual2", + "kw":"Number of Node Images,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual2" + } + ], + "title":"Number of Node Images", "githuburl":"" }, { "uri":"cce_10_0031.html", "node_id":"cce_10_0031.xml", "product_code":"cce", - "code":"125", + "code":"127", "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 Cluster", @@ -2452,9 +2296,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Managing a Cluster", @@ -2464,17 +2306,15 @@ "uri":"cce_10_0213.html", "node_id":"cce_10_0213.xml", "product_code":"cce", - "code":"126", - "des":"CCE allows you to manage cluster parameters, through which you can let core components work under your very requirements.This function is supported only in clusters of v1", + "code":"128", + "des":"CCE allows you to manage cluster parameters, through which you can let core components work under your requirements.This function is supported only in clusters of v1.15 a", "doc_type":"usermanual2", "kw":"cluster parameters,kube-apiserver,kube-controller-manager,Cluster Configuration Management,Managing ", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Cluster Configuration Management", @@ -2484,7 +2324,7 @@ "uri":"cce_10_0602.html", "node_id":"cce_10_0602.xml", "product_code":"cce", - "code":"127", + "code":"129", "des":"If enabled, concurrent requests are dynamically controlled based on the resource pressure of master nodes to keep them and the cluster available.The cluster version must ", "doc_type":"usermanual2", "kw":"Cluster Overload Control,Managing a Cluster,User Guide", @@ -2492,9 +2332,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Cluster Overload Control", @@ -2504,7 +2342,7 @@ "uri":"cce_10_0403.html", "node_id":"cce_10_0403.xml", "product_code":"cce", - "code":"128", + "code":"130", "des":"CCE allows you to change the number of nodes managed in a cluster.This function is supported for clusters of v1.15 and later versions.Starting from v1.15.11, the number o", "doc_type":"usermanual2", "kw":"Changing Cluster Scale,Managing a Cluster,User Guide", @@ -2512,9 +2350,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Changing Cluster Scale", @@ -2524,7 +2360,7 @@ "uri":"cce_10_0212.html", "node_id":"cce_10_0212.xml", "product_code":"cce", - "code":"129", + "code":"131", "des":"Deleting a cluster will delete the nodes in the cluster (excluding accepted nodes), data disks attached to the nodes, workloads, and Services. Related services cannot be ", "doc_type":"usermanual2", "kw":"Deleting a Cluster,Managing a Cluster,User Guide", @@ -2532,9 +2368,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Deleting a Cluster", @@ -2544,7 +2378,7 @@ "uri":"cce_10_0214.html", "node_id":"cce_10_0214.xml", "product_code":"cce", - "code":"130", + "code":"132", "des":"If you do not need to use a cluster temporarily, hibernate the cluster.After a cluster is hibernated, resources such as workloads cannot be created or managed in the clus", "doc_type":"usermanual2", "kw":"Hibernating and Waking Up a Cluster,Managing a Cluster,User Guide", @@ -2552,9 +2386,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Hibernating and Waking Up a Cluster", @@ -2564,7 +2396,7 @@ "uri":"cce_10_0183.html", "node_id":"cce_10_0183.xml", "product_code":"cce", - "code":"131", + "code":"133", "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", @@ -2572,9 +2404,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Nodes", @@ -2584,7 +2414,7 @@ "uri":"cce_10_0180.html", "node_id":"cce_10_0180.xml", "product_code":"cce", - "code":"132", + "code":"134", "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", @@ -2592,9 +2422,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Overview", @@ -2604,7 +2432,7 @@ "uri":"cce_10_0462.html", "node_id":"cce_10_0462.xml", "product_code":"cce", - "code":"133", + "code":"135", "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 Engine,Nodes,User Guide", @@ -2612,19 +2440,35 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Container Engine", "githuburl":"" }, + { + "uri":"cce_10_0476.html", + "node_id":"cce_10_0476.xml", + "product_code":"cce", + "code":"136", + "des":"This section describes the mappings between released cluster versions and OS versions.", + "doc_type":"usermanual2", + "kw":"Node OS,Nodes,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual2" + } + ], + "title":"Node OS", + "githuburl":"" + }, { "uri":"cce_10_0363.html", "node_id":"cce_10_0363.xml", "product_code":"cce", - "code":"134", + "code":"137", "des":"At least one cluster has been created.A key pair has been created for identity authentication upon remote node login.The node has at least 2 vCPUs and 4 GiB of memory.To ", "doc_type":"usermanual2", "kw":"Creating a Node,Nodes,User Guide", @@ -2632,9 +2476,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Creating a Node", @@ -2644,27 +2486,25 @@ "uri":"cce_10_0198.html", "node_id":"cce_10_0198.xml", "product_code":"cce", - "code":"135", - "des":"In CCE, you can create a node (Creating a Node) or add existing nodes (ECSs or) to your cluster.While an ECS is being accepted into a cluster, the operating system of the", + "code":"138", + "des":"In CCE, you can create a node (Creating a Node) or add existing nodes (ECSs) to your cluster for management.While an ECS is being accepted into a cluster, the operating s", "doc_type":"usermanual2", - "kw":"Adding Nodes for Management,Nodes,User Guide", + "kw":"Accepting Nodes for Management,Nodes,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], - "title":"Adding Nodes for Management", + "title":"Accepting Nodes for Management", "githuburl":"" }, { "uri":"cce_10_0185.html", "node_id":"cce_10_0185.xml", "product_code":"cce", - "code":"136", + "code":"139", "des":"If you use SSH to log in to a node (an ECS), ensure that the ECS already has an EIP (a public IP address).Only login to a running ECS is allowed.Only the user linux can l", "doc_type":"usermanual2", "kw":"Logging In to a Node,Nodes,User Guide", @@ -2672,9 +2512,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Logging In to a Node", @@ -2684,7 +2522,7 @@ "uri":"cce_10_0672.html", "node_id":"cce_10_0672.xml", "product_code":"cce", - "code":"137", + "code":"140", "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", @@ -2692,9 +2530,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Management Nodes", @@ -2704,7 +2540,7 @@ "uri":"cce_10_0004.html", "node_id":"cce_10_0004.xml", "product_code":"cce", - "code":"138", + "code":"141", "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", @@ -2712,9 +2548,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Managing Node Labels", @@ -2724,17 +2558,15 @@ "uri":"cce_10_0352.html", "node_id":"cce_10_0352.xml", "product_code":"cce", - "code":"139", - "des":"Taints enable a node to repel specific pods to prevent these pods from being scheduled to the node.A taint is a key-value pair associated with an effect. The following ef", + "code":"142", + "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", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Managing Node Taints", @@ -2744,7 +2576,7 @@ "uri":"cce_10_0003.html", "node_id":"cce_10_0003.xml", "product_code":"cce", - "code":"140", + "code":"143", "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", @@ -2752,9 +2584,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Resetting a Node", @@ -2764,7 +2594,7 @@ "uri":"cce_10_0338.html", "node_id":"cce_10_0338.xml", "product_code":"cce", - "code":"141", + "code":"144", "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", @@ -2772,9 +2602,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Removing a Node", @@ -2784,37 +2612,33 @@ "uri":"cce_10_0184.html", "node_id":"cce_10_0184.xml", "product_code":"cce", - "code":"142", + "code":"145", "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 Data with Cloud Servers,Management Nodes,User Guide", + "kw":"synchronize the ECS,Synchronizing the Data of Cloud Servers,Management Nodes,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], - "title":"Synchronizing Data with Cloud Servers", + "title":"Synchronizing the Data of Cloud Servers", "githuburl":"" }, { "uri":"cce_10_0605.html", "node_id":"cce_10_0605.xml", "product_code":"cce", - "code":"143", - "des":"After you enable the nodal drainage function on the console, the system sets the node to be non-schedulable and securely evicts all pods that comply with Nodal Drainage R", + "code":"146", + "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 Nodal Drainage Rules on the no", "doc_type":"usermanual2", - "kw":"nodal drainage,Draining a Node,Management Nodes,User Guide", + "kw":"nodal drainage,nodal drainage,Draining a Node,Management Nodes,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Draining a Node", @@ -2824,7 +2648,7 @@ "uri":"cce_10_0186.html", "node_id":"cce_10_0186.xml", "product_code":"cce", - "code":"144", + "code":"147", "des":"When a node in a CCE cluster is deleted, services running on the node will also be deleted. Exercise caution when performing this operation.VM nodes that are being used b", "doc_type":"usermanual2", "kw":"Deleting a Node,Management Nodes,User Guide", @@ -2832,9 +2656,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Deleting a Node", @@ -2844,7 +2666,7 @@ "uri":"cce_10_0036.html", "node_id":"cce_10_0036.xml", "product_code":"cce", - "code":"145", + "code":"148", "des":"After a node in the cluster is stopped, services on the node are also stopped. Before stopping a node, ensure that discontinuity of the services on the node will not resu", "doc_type":"usermanual2", "kw":"Stopping a Node,Management Nodes,User Guide", @@ -2852,9 +2674,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Stopping a Node", @@ -2864,7 +2684,7 @@ "uri":"cce_10_0276.html", "node_id":"cce_10_0276.xml", "product_code":"cce", - "code":"146", + "code":"149", "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", @@ -2872,9 +2692,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Performing Rolling Upgrade for Nodes", @@ -2884,7 +2702,7 @@ "uri":"cce_10_0704.html", "node_id":"cce_10_0704.xml", "product_code":"cce", - "code":"147", + "code":"150", "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", @@ -2892,9 +2710,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node O&M", @@ -2904,7 +2720,7 @@ "uri":"cce_10_0178.html", "node_id":"cce_10_0178.xml", "product_code":"cce", - "code":"148", + "code":"151", "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", @@ -2912,9 +2728,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Resource Reservation Policy", @@ -2924,7 +2738,7 @@ "uri":"cce_10_0341.html", "node_id":"cce_10_0341.xml", "product_code":"cce", - "code":"149", + "code":"152", "des":"This section describes how to allocate data disk space to nodes so that you can configure the data disk space accordingly.When creating a node, configure data disks for t", "doc_type":"usermanual2", "kw":"data disk space allocation,Container engine and container image space,basesize,basesize,Container St", @@ -2932,9 +2746,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Data Disk Space Allocation", @@ -2944,7 +2756,7 @@ "uri":"cce_10_0348.html", "node_id":"cce_10_0348.xml", "product_code":"cce", - "code":"150", + "code":"153", "des":"The maximum number of pods that can be created on a node is calculated based on the cluster type:For a cluster using the container tunnel network model, the value depends", "doc_type":"usermanual2", "kw":"Maximum Number of Pods on a Node,alpha.cce/fixPoolMask,maximum number of pods,Maximum Number of Pods", @@ -2952,9 +2764,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Maximum Number of Pods That Can Be Created on a Node", @@ -2964,17 +2774,15 @@ "uri":"cce_10_0601.html", "node_id":"cce_10_0601.xml", "product_code":"cce", - "code":"151", - "des":"Kubernetes has removed dockershim from v1.24 and does not support Docker by default. CCE will continue to support Docker in v1.25 but just till v1.27. The following steps", + "code":"154", + "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", "doc_type":"usermanual2", "kw":"Migrating Nodes from Docker to containerd,Node O&M,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Migrating Nodes from Docker to containerd", @@ -2984,7 +2792,7 @@ "uri":"cce_10_0659.html", "node_id":"cce_10_0659.xml", "product_code":"cce", - "code":"152", + "code":"155", "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,Node Fault Detection Policy,Node O&M,User Guide", @@ -2992,9 +2800,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Fault Detection Policy", @@ -3004,7 +2810,7 @@ "uri":"cce_10_0035.html", "node_id":"cce_10_0035.xml", "product_code":"cce", - "code":"153", + "code":"156", "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", @@ -3012,9 +2818,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Pools", @@ -3024,7 +2828,7 @@ "uri":"cce_10_0081.html", "node_id":"cce_10_0081.xml", "product_code":"cce", - "code":"154", + "code":"157", "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,", @@ -3032,9 +2836,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Pool Overview", @@ -3044,7 +2846,7 @@ "uri":"cce_10_0012.html", "node_id":"cce_10_0012.xml", "product_code":"cce", - "code":"155", + "code":"158", "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.The Autoscaler a", "doc_type":"usermanual2", "kw":"Creating a Node Pool,Node Pools,User Guide", @@ -3052,9 +2854,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Creating a Node Pool", @@ -3064,7 +2864,7 @@ "uri":"cce_10_0222.html", "node_id":"cce_10_0222.xml", "product_code":"cce", - "code":"156", + "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":"Managing a Node Pool", @@ -3072,9 +2872,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Managing a Node Pool", @@ -3084,17 +2882,15 @@ "uri":"cce_10_0653.html", "node_id":"cce_10_0653.xml", "product_code":"cce", - "code":"157", - "des":"When editing the resource tags of the node pool. The modified configuration takes effect only for new nodes. To synchronize the configuration to the existing nodes, manua", + "code":"160", + "des":"The modification of resource tags of a node pool takes effect only on new nodes. To synchronize the modification onto existing nodes, manually reset the existing nodes.Ch", "doc_type":"usermanual2", "kw":"Updating a Node Pool,Managing a Node Pool,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Updating a Node Pool", @@ -3104,7 +2900,7 @@ "uri":"cce_10_0727.html", "node_id":"cce_10_0727.xml", "product_code":"cce", - "code":"158", + "code":"161", "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", @@ -3112,9 +2908,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Updating an AS Configuration", @@ -3124,17 +2918,15 @@ "uri":"cce_10_0652.html", "node_id":"cce_10_0652.xml", "product_code":"cce", - "code":"159", + "code":"162", "des":"The default node pool DefaultPool does not support the following management operations.CCE allows you to highly customize Kubernetes parameter settings on core components", "doc_type":"usermanual2", - "kw":"PIDs,Configuring a Node Pool,Managing a Node Pool,User Guide", + "kw":"Configuring a Node Pool,Managing a Node Pool,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Configuring a Node Pool", @@ -3144,7 +2936,7 @@ "uri":"cce_10_0655.html", "node_id":"cce_10_0655.xml", "product_code":"cce", - "code":"160", + "code":"163", "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", @@ -3152,9 +2944,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Copying a Node Pool", @@ -3164,7 +2954,7 @@ "uri":"cce_10_0654.html", "node_id":"cce_10_0654.xml", "product_code":"cce", - "code":"161", + "code":"164", "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", @@ -3172,9 +2962,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Synchronizing Node Pools", @@ -3184,7 +2972,7 @@ "uri":"cce_10_0660.html", "node_id":"cce_10_0660.xml", "product_code":"cce", - "code":"162", + "code":"165", "des":"When CCE releases a new OS image, existing nodes cannot be automatically upgraded. You can manually upgrade them in batches.This section describes how to upgrade an OS by", "doc_type":"usermanual2", "kw":"Upgrading an OS,Managing a Node Pool,User Guide", @@ -3192,9 +2980,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Upgrading an OS", @@ -3204,7 +2990,7 @@ "uri":"cce_10_0656.html", "node_id":"cce_10_0656.xml", "product_code":"cce", - "code":"163", + "code":"166", "des":"Nodes in a node pool can be migrated to the default node pool. Nodes in the default node pool or a custom node pool cannot be migrated to other custom node pools.The migr", "doc_type":"usermanual2", "kw":"Migrating a Node,Managing a Node Pool,User Guide", @@ -3212,9 +2998,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Migrating a Node", @@ -3224,7 +3008,7 @@ "uri":"cce_10_0657.html", "node_id":"cce_10_0657.xml", "product_code":"cce", - "code":"164", + "code":"167", "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", @@ -3232,9 +3016,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Deleting a Node Pool", @@ -3244,7 +3026,7 @@ "uri":"cce_10_0046.html", "node_id":"cce_10_0046.xml", "product_code":"cce", - "code":"165", + "code":"168", "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":"Deployments,StatefulSets,DaemonSets,jobs,cron jobs", @@ -3252,9 +3034,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Workloads", @@ -3264,7 +3044,7 @@ "uri":"cce_10_0006.html", "node_id":"cce_10_0006.xml", "product_code":"cce", - "code":"166", + "code":"169", "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", @@ -3272,9 +3052,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Overview", @@ -3284,7 +3062,7 @@ "uri":"cce_10_0673.html", "node_id":"cce_10_0673.xml", "product_code":"cce", - "code":"167", + "code":"170", "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", @@ -3292,9 +3070,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Creating a Workload", @@ -3304,7 +3080,7 @@ "uri":"cce_10_0047.html", "node_id":"cce_10_0047.xml", "product_code":"cce", - "code":"168", + "code":"171", "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", @@ -3312,9 +3088,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Creating a Deployment", @@ -3324,7 +3098,7 @@ "uri":"cce_10_0048.html", "node_id":"cce_10_0048.xml", "product_code":"cce", - "code":"169", + "code":"172", "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", @@ -3332,9 +3106,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Creating a StatefulSet", @@ -3344,7 +3116,7 @@ "uri":"cce_10_0216.html", "node_id":"cce_10_0216.xml", "product_code":"cce", - "code":"170", + "code":"173", "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", @@ -3352,9 +3124,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Creating a DaemonSet", @@ -3364,7 +3134,7 @@ "uri":"cce_10_0150.html", "node_id":"cce_10_0150.xml", "product_code":"cce", - "code":"171", + "code":"174", "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", @@ -3372,9 +3142,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Creating a Job", @@ -3384,7 +3152,7 @@ "uri":"cce_10_0151.html", "node_id":"cce_10_0151.xml", "product_code":"cce", - "code":"172", + "code":"175", "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", "doc_type":"usermanual2", "kw":"time synchronization,Creating a Cron Job,Creating a Workload,User Guide", @@ -3392,9 +3160,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Creating a Cron Job", @@ -3404,7 +3170,7 @@ "uri":"cce_10_0130.html", "node_id":"cce_10_0130.xml", "product_code":"cce", - "code":"173", + "code":"176", "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 Container", @@ -3412,9 +3178,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Configuring a Container", @@ -3424,7 +3188,7 @@ "uri":"cce_10_0354.html", "node_id":"cce_10_0354.xml", "product_code":"cce", - "code":"174", + "code":"177", "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 Container,User Guide", @@ -3432,9 +3196,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Configuring Time Zone Synchronization", @@ -3444,7 +3206,7 @@ "uri":"cce_10_0353.html", "node_id":"cce_10_0353.xml", "product_code":"cce", - "code":"175", + "code":"178", "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 Container,User Guide", @@ -3452,9 +3214,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Configuring an Image Pull Policy", @@ -3464,7 +3224,7 @@ "uri":"cce_10_0009.html", "node_id":"cce_10_0009.xml", "product_code":"cce", - "code":"176", + "code":"179", "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 Container,User Guide", @@ -3472,9 +3232,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Using Third-Party Images", @@ -3484,17 +3242,15 @@ "uri":"cce_10_0163.html", "node_id":"cce_10_0163.xml", "product_code":"cce", - "code":"177", + "code":"180", "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":"Configuring Container Specifications,Configuring a Container,User Guide", + "kw":"ephemeral storage,Configuring Container Specifications,Configuring a Container,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Configuring Container Specifications", @@ -3504,7 +3260,7 @@ "uri":"cce_10_0105.html", "node_id":"cce_10_0105.xml", "product_code":"cce", - "code":"178", + "code":"181", "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 Contain", @@ -3512,9 +3268,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Configuring Container Lifecycle Parameters", @@ -3524,7 +3278,7 @@ "uri":"cce_10_0112.html", "node_id":"cce_10_0112.xml", "product_code":"cce", - "code":"179", + "code":"182", "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 Container,Us", @@ -3532,9 +3286,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Configuring Container Health Check", @@ -3544,7 +3296,7 @@ "uri":"cce_10_0113.html", "node_id":"cce_10_0113.xml", "product_code":"cce", - "code":"180", + "code":"183", "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 Container,User Guide", @@ -3552,9 +3304,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Configuring Environment Variables", @@ -3564,7 +3314,7 @@ "uri":"cce_10_0397.html", "node_id":"cce_10_0397.xml", "product_code":"cce", - "code":"181", + "code":"184", "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":"Workload Upgrade Policies,Configuring a Container,User Guide", @@ -3572,9 +3322,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Workload Upgrade Policies", @@ -3584,7 +3332,7 @@ "uri":"cce_10_0232.html", "node_id":"cce_10_0232.xml", "product_code":"cce", - "code":"182", + "code":"185", "des":"Kubernetes supports node affinity and pod affinity/anti-affinity. You can configure custom rules to achieve affinity and anti-affinity scheduling. For example, you can de", "doc_type":"usermanual2", "kw":"Scheduling Policies (Affinity/Anti-affinity),Configuring a Container,User Guide", @@ -3592,9 +3340,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Scheduling Policies (Affinity/Anti-affinity)", @@ -3604,7 +3350,7 @@ "uri":"cce_10_0728.html", "node_id":"cce_10_0728.xml", "product_code":"cce", - "code":"183", + "code":"186", "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":"Taints and Tolerations,Configuring a Container,User Guide", @@ -3612,9 +3358,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Taints and Tolerations", @@ -3624,7 +3368,7 @@ "uri":"cce_10_0386.html", "node_id":"cce_10_0386.xml", "product_code":"cce", - "code":"184", + "code":"187", "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":"Labels and Annotations,Configuring a Container,User Guide", @@ -3632,9 +3376,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Labels and Annotations", @@ -3644,7 +3386,7 @@ "uri":"cce_10_00356.html", "node_id":"cce_10_00356.xml", "product_code":"cce", - "code":"185", + "code":"188", "des":"If you encounter unexpected problems when using a container, you can log in to the container to debug it.The example output is as follows:NAME ", "doc_type":"usermanual2", "kw":"Accessing a Container,Workloads,User Guide", @@ -3652,9 +3394,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Accessing a Container", @@ -3664,7 +3404,7 @@ "uri":"cce_10_0007.html", "node_id":"cce_10_0007.xml", "product_code":"cce", - "code":"186", + "code":"189", "des":"After a workload is created, you can upgrade, monitor, roll back, or delete the workload, as well as edit its YAML file.Workload/Job managementOperationDescriptionMonitor", "doc_type":"usermanual2", "kw":"Managing Workloads and Jobs,Workloads,User Guide", @@ -3672,19 +3412,35 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Managing Workloads and Jobs", "githuburl":"" }, + { + "uri":"cce_10_0833.html", + "node_id":"cce_10_0833.xml", + "product_code":"cce", + "code":"190", + "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", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual2" + } + ], + "title":"Managing Custom Resources", + "githuburl":"" + }, { "uri":"cce_10_0463.html", "node_id":"cce_10_0463.xml", "product_code":"cce", - "code":"187", + "code":"191", "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", "doc_type":"usermanual2", "kw":"Kata Runtime and Common Runtime,Workloads,User Guide", @@ -3692,9 +3448,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Kata Runtime and Common Runtime", @@ -3704,7 +3458,7 @@ "uri":"cce_10_0674.html", "node_id":"cce_10_0674.xml", "product_code":"cce", - "code":"188", + "code":"192", "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", @@ -3712,9 +3466,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Scheduling", @@ -3724,7 +3476,7 @@ "uri":"cce_10_0702.html", "node_id":"cce_10_0702.xml", "product_code":"cce", - "code":"189", + "code":"193", "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", @@ -3732,9 +3484,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Overview", @@ -3744,7 +3494,7 @@ "uri":"cce_10_0551.html", "node_id":"cce_10_0551.xml", "product_code":"cce", - "code":"190", + "code":"194", "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", @@ -3752,9 +3502,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"CPU Scheduling", @@ -3764,7 +3512,7 @@ "uri":"cce_10_0351.html", "node_id":"cce_10_0351.xml", "product_code":"cce", - "code":"191", + "code":"195", "des":"By default, kubelet uses CFS quotas to enforce pod CPU limits. When the node runs many CPU-bound pods, the workload can move to different CPU cores depending on whether t", "doc_type":"usermanual2", "kw":"CPU Policy,CPU Scheduling,User Guide", @@ -3772,9 +3520,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"CPU Policy", @@ -3784,7 +3530,7 @@ "uri":"cce_10_0552.html", "node_id":"cce_10_0552.xml", "product_code":"cce", - "code":"192", + "code":"196", "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", @@ -3792,9 +3538,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Enhanced CPU Policy", @@ -3804,7 +3548,7 @@ "uri":"cce_10_0720.html", "node_id":"cce_10_0720.xml", "product_code":"cce", - "code":"193", + "code":"197", "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", @@ -3812,9 +3556,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"GPU Scheduling", @@ -3824,7 +3566,7 @@ "uri":"cce_10_0345.html", "node_id":"cce_10_0345.xml", "product_code":"cce", - "code":"194", + "code":"198", "des":"You can use GPUs in CCE containers.A GPU node has been created. For details, see Creating a Node.The gpu-device-plugin (previously gpu-beta add-on) has been installed. Du", "doc_type":"usermanual2", "kw":"Default GPU Scheduling in Kubernetes,GPU Scheduling,User Guide", @@ -3832,9 +3574,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Default GPU Scheduling in Kubernetes", @@ -3844,7 +3584,7 @@ "uri":"cce_10_0423.html", "node_id":"cce_10_0423.xml", "product_code":"cce", - "code":"195", + "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":"Volcano Scheduling", @@ -3852,9 +3592,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Volcano Scheduling", @@ -3864,17 +3602,15 @@ "uri":"cce_10_0721.html", "node_id":"cce_10_0721.xml", "product_code":"cce", - "code":"196", - "des":"Volcano Scheduler is a pod scheduling component, which consists of a series of actions and plugins. Actions should be executed in every step. Plugins provide the action a", + "code":"200", + "des":"Volcano is a Kubernetes-based batch processing platform that supports machine learning, deep learning, bioinformatics, genomics, and other big data applications. It provi", "doc_type":"usermanual2", "kw":"Overview,Volcano Scheduling,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Overview", @@ -3884,7 +3620,7 @@ "uri":"cce_10_0722.html", "node_id":"cce_10_0722.xml", "product_code":"cce", - "code":"197", + "code":"201", "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", @@ -3892,9 +3628,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Scheduling Workloads", @@ -3904,77 +3638,69 @@ "uri":"cce_10_0768.html", "node_id":"cce_10_0768.xml", "product_code":"cce", - "code":"198", + "code":"202", "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 Utilization-based Scheduling", + "kw":"Resource Usage-based Scheduling", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], - "title":"Resource Utilization-based Scheduling", + "title":"Resource Usage-based Scheduling", "githuburl":"" }, { "uri":"cce_10_0773.html", "node_id":"cce_10_0773.xml", "product_code":"cce", - "code":"199", - "des":"Binpack is a pod scheduling add-on that enables the scheduler to preferentially schedule pods to nodes with high resource allocation. This reduces resource fragments on e", + "code":"203", + "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":"Binpack,Resource Utilization-based Scheduling,User Guide", + "kw":"Bin Packing,Resource Usage-based Scheduling,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], - "title":"Binpack", + "title":"Bin Packing", "githuburl":"" }, { "uri":"cce_10_0766.html", "node_id":"cce_10_0766.xml", "product_code":"cce", - "code":"200", - "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 ", + "code":"204", + "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":"Descheduler,Resource Utilization-based Scheduling,User Guide", + "kw":"Descheduling,Resource Usage-based Scheduling,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], - "title":"Descheduler", + "title":"Descheduling", "githuburl":"" }, { "uri":"cce_10_0767.html", "node_id":"cce_10_0767.xml", "product_code":"cce", - "code":"201", + "code":"205", "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 Utilization-based Scheduling,User Guide", + "kw":"Node Pool Affinity,Resource Usage-based Scheduling,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Node Pool Affinity", @@ -3984,7 +3710,7 @@ "uri":"cce_10_0774.html", "node_id":"cce_10_0774.xml", "product_code":"cce", - "code":"202", + "code":"206", "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", @@ -3992,9 +3718,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Priority-based Scheduling", @@ -4004,7 +3728,7 @@ "uri":"cce_10_0775.html", "node_id":"cce_10_0775.xml", "product_code":"cce", - "code":"203", + "code":"207", "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", @@ -4012,9 +3736,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Priority-based Scheduling", @@ -4024,7 +3746,7 @@ "uri":"cce_10_0776.html", "node_id":"cce_10_0776.xml", "product_code":"cce", - "code":"204", + "code":"208", "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", @@ -4032,9 +3754,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"AI Performance-based Scheduling", @@ -4044,7 +3764,7 @@ "uri":"cce_10_0777.html", "node_id":"cce_10_0777.xml", "product_code":"cce", - "code":"205", + "code":"209", "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", @@ -4052,9 +3772,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"DRF", @@ -4064,7 +3782,7 @@ "uri":"cce_10_0778.html", "node_id":"cce_10_0778.xml", "product_code":"cce", - "code":"206", + "code":"210", "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", @@ -4072,9 +3790,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Gang", @@ -4084,17 +3800,15 @@ "uri":"cce_10_0425.html", "node_id":"cce_10_0425.xml", "product_code":"cce", - "code":"207", - "des":"When the node runs many CPU-bound pods, the workload can move to different CPU cores depending on whether the pod is throttled and which CPU cores are available at schedu", + "code":"211", + "des":"When a node runs many CPU-bound pods, the workload can move to different CPU cores depending on whether the pod is throttled and which CPU cores are available at scheduli", "doc_type":"usermanual2", "kw":"NUMA Affinity Scheduling,Volcano Scheduling,User Guide", "search_title":"", "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"NUMA Affinity Scheduling", @@ -4104,7 +3818,7 @@ "uri":"cce_10_0709.html", "node_id":"cce_10_0709.xml", "product_code":"cce", - "code":"208", + "code":"212", "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", @@ -4112,9 +3826,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Cloud Native Hybrid Deployment", @@ -4124,7 +3836,7 @@ "uri":"cce_10_0384.html", "node_id":"cce_10_0384.xml", "product_code":"cce", - "code":"209", + "code":"213", "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", @@ -4132,9 +3844,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Dynamic Resource Oversubscription", @@ -4144,7 +3854,7 @@ "uri":"cce_10_0020.html", "node_id":"cce_10_0020.xml", "product_code":"cce", - "code":"210", + "code":"214", "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", @@ -4152,9 +3862,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Network", @@ -4164,7 +3872,7 @@ "uri":"cce_10_0010.html", "node_id":"cce_10_0010.xml", "product_code":"cce", - "code":"211", + "code":"215", "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", @@ -4172,9 +3880,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Overview", @@ -4184,7 +3890,7 @@ "uri":"cce_10_0280.html", "node_id":"cce_10_0280.xml", "product_code":"cce", - "code":"212", + "code":"216", "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 Models", @@ -4192,9 +3898,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Container Network Models", @@ -4204,7 +3908,7 @@ "uri":"cce_10_0281.html", "node_id":"cce_10_0281.xml", "product_code":"cce", - "code":"213", + "code":"217", "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:Tun", "doc_type":"usermanual2", "kw":"Overview,Container Network Models,User Guide", @@ -4212,9 +3916,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Overview", @@ -4224,7 +3926,7 @@ "uri":"cce_10_0282.html", "node_id":"cce_10_0282.xml", "product_code":"cce", - "code":"214", + "code":"218", "des":"The container tunnel network is constructed on but independent of the node network through tunnel encapsulation. This network model uses VXLAN to encapsulate Ethernet pac", "doc_type":"usermanual2", "kw":"Container Tunnel Network,Container Network Models,User Guide", @@ -4232,9 +3934,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Container Tunnel Network", @@ -4244,7 +3944,7 @@ "uri":"cce_10_0283.html", "node_id":"cce_10_0283.xml", "product_code":"cce", - "code":"215", + "code":"219", "des":"The VPC network uses VPC routing to integrate with the underlying network. This network model is suitable for performance-intensive scenarios. The maximum number of nodes", "doc_type":"usermanual2", "kw":"VPC Network,Container Network Models,User Guide", @@ -4252,9 +3952,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"VPC Network", @@ -4264,7 +3962,7 @@ "uri":"cce_10_0284.html", "node_id":"cce_10_0284.xml", "product_code":"cce", - "code":"216", + "code":"220", "des":"Developed by CCE, Cloud Native 2.0 network deeply integrates Elastic Network Interfaces (ENIs) and sub-ENIs of Virtual Private Cloud (VPC). Container IP addresses are all", "doc_type":"usermanual2", "kw":"Cloud Native 2.0 Network,Container Network Models,User Guide", @@ -4272,9 +3970,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Cloud Native 2.0 Network", @@ -4284,7 +3980,7 @@ "uri":"cce_10_0247.html", "node_id":"cce_10_0247.xml", "product_code":"cce", - "code":"217", + "code":"221", "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", @@ -4292,9 +3988,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Service", @@ -4304,7 +3998,7 @@ "uri":"cce_10_0249.html", "node_id":"cce_10_0249.xml", "product_code":"cce", - "code":"218", + "code":"222", "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", @@ -4312,9 +4006,7 @@ "metedata":[ { "prodname":"cce", - "IsBot":"Yes", - "opensource":"true", - "documenttype":"usermanual" + "documenttype":"usermanual2" } ], "title":"Overview", @@ -4324,7 +4016,7 @@ "uri":"cce_10_0011.html", "node_id":"cce_10_0011.xml", "product_code":"cce", - "code":"219", + "code":"223", "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 -

2024-03-29

+

2024-05-30

- +
  • Deleted section "OS Patch Notes for Cluster Nodes".
  • Added Node OS.
  • Describes how to obtain the value of the available_zone, l4_flavor_name and l7_flavor_name.
+ + +

2024-04-28

+ +
  • Supported the creation of clusters of v1.28.
  • Supported IPv6.
  • Clusters of version 1.27 or later do not support nodes running EulerOS 2.5 or CentOS 7.7. For details, see Before You Start.
+ + +

2024-03-29

+ +

2024-01-29

@@ -30,7 +40,7 @@

2023-05-30

- +

2023-02-10

@@ -40,7 +50,7 @@

2022-12-20

- +

2022-11-21

@@ -50,7 +60,7 @@

2022-08-27

-

EulerOS 2.9 is supported. For details, see OS Patch Notes for Cluster Nodes.

+

EulerOS 2.9 is supported.

2022-07-13

@@ -70,7 +80,7 @@

2022-04-14

-

Allowed cluster upgrade from v1.19 to v1.21. For details, see Performing In-place Upgrade.

+

Allowed cluster upgrade from v1.19 to v1.21.

2022-03-24

diff --git a/docs/cce/umn/cce_10_0002.html b/docs/cce/umn/cce_10_0002.html index bd79eafb..5da4fd1c 100644 --- a/docs/cce/umn/cce_10_0002.html +++ b/docs/cce/umn/cce_10_0002.html @@ -6,9 +6,9 @@ diff --git a/docs/cce/umn/cce_10_0003.html b/docs/cce/umn/cce_10_0003.html index 3b3d3c65..a39d3d97 100644 --- a/docs/cce/umn/cce_10_0003.html +++ b/docs/cce/umn/cce_10_0003.html @@ -6,9 +6,9 @@

Constraints

  • For CCE standard clusters and CCE Turbo clusters to support node resetting, 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.
  • Resetting a node will reinstall the node OS and interrupt workload services running on the node. Therefore, perform this operation during off-peak hours.
  • Data in the system disk and Docker data disks will be cleared. Back up important data before resetting the node.
  • When an extra data disk is mounted to a node, data in this disk will be cleared if the disk has not been unmounted before the node reset. To prevent data loss, back up data in advance and mount the data disk again after the node reset is complete.
  • 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.
  • While the node is being deleted, the backend will set the node to the unschedulable state.
  • 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 is always 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.
  • After a worker node with an extra data disk attached is reset, the attachment will be cleared. In this case, attach the disk again and data will be retained.
  • 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.
  • While the node is being deleted, the backend will set the node to the unschedulable state.
  • 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.
-

Procedure

The new console allows you to reset nodes in batches. You can also use a private image to reset nodes in batches.

+

Procedure

You can batch reset nodes using private images.

  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, 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.

    • For nodes in the DefaultPool node pool, the parameter setting page is displayed. Set the parameters by referring to 5.
    • For a node you create in a node pool, resetting the node does not support parameter configuration. You can directly use the configuration image of the node pool to reset the node.

  5. Specify node parameters.

    Compute Settings
    - @@ -63,7 +62,7 @@ @@ -78,22 +77,22 @@ - - - - + + + - - - - diff --git a/docs/cce/umn/cce_10_0004.html b/docs/cce/umn/cce_10_0004.html index 4412480d..4a2ed4e0 100644 --- a/docs/cce/umn/cce_10_0004.html +++ b/docs/cce/umn/cce_10_0004.html @@ -2,8 +2,7 @@

    Managing Node Labels

    Node Label Usage Scenario

    Node labels are mainly used in the following scenarios:

    -
    • Node management: Node labels are used to classify nodes.
    • Affinity and anti-affinity between a workload and node:
      • Different workloads have different resource requirements such as CPU, memory, and I/O. If a workload consumes too many resources in a cluster, other workloads in the same cluster may fail to run properly. In this case, you are advised to add different labels to nodes. When deploying a workload, you can select nodes with specified labels for affinity deployment to ensure the normal operation of the system. Otherwise, node anti-affinity deployment can be used.
      • A system can be divided into multiple modules. Each module consists of multiple microservices. To ensure efficient O&M, you can add a module label to each node so that each module can be deployed on the corresponding node. In this way, modules do not interfere with each other and microservices can be easily maintained on their nodes.
      -
    +
    • Node management: Node labels are used to classify nodes.
    • Node affinity or anti-affinity for workloads: By adding labels to nodes, you can schedule pods to specific nodes through node affinity or prevent pods from being scheduled to specific nodes through node anti-affinity. For details, see Scheduling Policies (Affinity/Anti-affinity).

    Inherent Label of a Node

    After a node is created, some fixed labels exist and cannot be deleted. For details about these labels, see Table 1.

    Do not manually change the inherent labels that are automatically added to a node. If the manually changed value conflicts with the system value, the system value is used.

    diff --git a/docs/cce/umn/cce_10_0007.html b/docs/cce/umn/cce_10_0007.html index c6dba1f1..22595b6d 100644 --- a/docs/cce/umn/cce_10_0007.html +++ b/docs/cce/umn/cce_10_0007.html @@ -77,7 +77,7 @@

    Before viewing logs, ensure that the time of the browser is the same as that on the backend server.

    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 click the View Log of the target workload.

      In the displayed View Log window, you can view logs.

      -

      The displayed logs are standard output logs of containers and do not have persistence and advanced O&M capabilities. To use more comprehensive log capabilities, see Logs. If the function of collecting standard output is enabled for the workload (enabled by default), you can go to AOM to view more workload logs. For details, see Connecting CCE to AOM.

      +

      The displayed logs are standard output logs of containers and do not have persistence and advanced O&M capabilities. To use more comprehensive log capabilities, see Logs. If the function of collecting standard output is enabled for the workload (enabled by default), you can go to AOM to view more workload logs. For details, see Collecting Container Logs Using ICAgent.

    diff --git a/docs/cce/umn/cce_10_0010.html b/docs/cce/umn/cce_10_0010.html index d8a3c6e3..dbbe0ae1 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.

    • Container Network

      A container network assigns IP addresses to containers 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 uses VPC routing to integrate with the underlying network. This network model applies to performance-intensive scenarios. The maximum number of nodes allowed in a cluster depends on the route quota in a VPC network. Each node is assigned a CIDR block of a fixed size. This networking model is free from tunnel encapsulation overhead and outperforms the container tunnel network model. 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 elastic IPs (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 uses VPC routing to integrate with the underlying network. This network model applies to performance-intensive scenarios. The maximum number of nodes allowed in a cluster depends on the route quota in a VPC network. Each node is assigned a CIDR block of a fixed size. This networking model is free from tunnel encapsulation overhead and outperforms the container tunnel network model. 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.

      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 Public Networks 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 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.
    -
    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 cfdf722f..54cfdbfd 100644 --- a/docs/cce/umn/cce_10_0011.html +++ b/docs/cce/umn/cce_10_0011.html @@ -4,9 +4,9 @@

    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. Set intra-cluster access parameters.

      • Service Name: Service name, which can be the same as the workload name.
      • Service Type: Select ClusterIP.
      • Namespace: Namespace to which the workload belongs.
      • Selector: Add a label and click Confirm. A Service selects a pod based on the added label. You can also click Reference Workload Label to reference the label of an existing workload. In the dialog box that is displayed, select a workload and click OK.
      • Port Settings
        • Protocol: protocol used by the Service.
        • Service Port: port used by the Service. The port number ranges from 1 to 65535.
        • Container Port: port on which the workload listens. 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 to which the workload belongs.
          • Selector: Add a label and click Confirm. A Service selects a pod based on the added label. 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.
          • IPv6: This function is disabled by default. After this function is enabled, the cluster IP address of the Service changes to an IPv6 address. This parameter is available only in clusters of v1.15 or later with IPv6 enabled (set during cluster creation).
          • Port Settings
            • Protocol: protocol used by the Service.
            • Service Port: port used by the Service. The port number ranges from 1 to 65535.
            • Container Port: port on which the workload listens. For example, Nginx uses port 80 by default.

        4. Click OK.
        diff --git a/docs/cce/umn/cce_10_0012.html b/docs/cce/umn/cce_10_0012.html index c733270a..59f8bd58 100644 --- a/docs/cce/umn/cce_10_0012.html +++ b/docs/cce/umn/cce_10_0012.html @@ -18,7 +18,7 @@
    - @@ -26,9 +26,9 @@
    Table 1 Configuration parameters

    Parameter

    @@ -24,14 +24,13 @@

    Container Engine

    CCE clusters support Docker and containerd in some scenarios.
    • VPC network clusters of v1.23 and later versions support containerd. Tunnel network clusters of v1.23.2-r0 and later versions support containerd.
    • For a CCE Turbo cluster, both Docker and containerd are supported. For details, see Mapping between Node OSs and Container Engines.
    -
    +

    The container engines supported by CCE include Docker and containerd, which may vary depending on cluster types, cluster versions, and OSs. Select a container engine based on the information displayed on the CCE console. For details, see Mapping between Node OSs and Container Engines.

    OS
    Select an OS type. Different types of nodes support different OSs.
    • Public image: Select a public image for the node.
    • Private image: Select a private image for the node.
    -
    NOTE:
    • Service container runtimes share the kernel and underlying calls of nodes. To ensure compatibility, select a Linux distribution version that is the same as or close to that of the final service container image for the node OS.
    +
    NOTE:

    Service container runtimes share the kernel and underlying calls of nodes. To ensure compatibility, select a Linux distribution version that is the same as or close to that of the final service container image for the node OS.

    Data Disk

    At least one data disk is required for the container runtime and kubelet. The data disk cannot be deleted or uninstalled. Otherwise, the node will be unavailable.

    -

    Click Expand and select Allocate Disk Space to define the disk space occupied by the container runtime to store the working directories, container image data, and image metadata. For details about how to allocate data disk space, see Data Disk Space Allocation.

    +

    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 Data Disk Space Allocation.

    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.

    Kubernetes Label

    -

    Click Add to set the key-value pair attached to the Kubernetes objects (such as pods). A maximum of 20 labels can be added.

    -

    Labels can be used to distinguish nodes. With workload affinity settings, container pods can be scheduled to a specified node. For more information, see Labels and Selectors.

    -

    Resource Tag

    +

    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 predefined tags to improve the tag creation and resource migration efficiency.

    +

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

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

    Kubernetes Label

    +

    Click Add Label to set the key-value pair attached to the Kubernetes objects (such as pods). A maximum of 20 labels can be added.

    +

    Labels can be used to distinguish nodes. With workload affinity settings, container pods can be scheduled to a specified node. For more information, see Labels and Selectors.

    +

    Taint

    This parameter is left blank by default. You can add taints to configure anti-affinity for the node. A maximum of 20 taints are allowed for each node. Each taint contains the following parameters:
    • Key: A key must contain 1 to 63 characters, starting with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. A DNS subdomain name can be used as the prefix of a key.
    • Value: A value must start with a letter or digit and can contain a maximum of 63 characters, including letters, digits, hyphens (-), underscores (_), and periods (.).
    • Effect: Available options are NoSchedule, PreferNoSchedule, and NoExecute.
    +
    This parameter is left blank by default. You can add taints to configure node anti-affinity. A maximum of 20 taints are allowed for each node. Each taint contains the following parameters:
    • Key: A key must contain 1 to 63 characters, starting with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. A DNS subdomain name can be used as the prefix of a key.
    • Value: A value must start with a letter or digit and can contain a maximum of 63 characters, including letters, digits, hyphens (-), underscores (_), and periods (.).
    • Effect: Available options are NoSchedule, PreferNoSchedule, and NoExecute.
    NOTICE:
    • If taints are used, you must configure tolerations in the YAML files of pods. Otherwise, scale-up may fail or pods cannot be scheduled onto the added nodes.
    • After a node pool is created, you can click Edit to modify its configuration. The modification will be synchronized to all nodes in the node pool.
    @@ -101,19 +100,19 @@

    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.

    Pre-installation Command

    Enter commands. A maximum of 1000 characters are allowed.

    +

    Pre-installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded.

    The script will be executed before Kubernetes software is installed. Note that if the script is incorrect, Kubernetes software may fail to be installed.

    Post-installation Command

    Enter commands. A maximum of 1000 characters are allowed.

    +

    Pre-installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded.

    The script will be executed after Kubernetes software is installed, which does not affect the installation.

    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.

    Nodes

    +

    Expected Initial Nodes

    Number of nodes to be created in this node pool. A maximum of 50 nodes that can be created at a time.
    -

    Compute Settings

    +

    Configurations

    You can configure the flavor and OS of a cloud server, on which your containerized applications run. -
    Table 2 Compute parameters

    Parameter

    +
    @@ -37,33 +37,33 @@ - - - - - + + + @@ -80,7 +80,7 @@

    Storage Settings

    -
    Configure storage resources on a node for the containers running on it. Set the disk size according to site requirements. +
    Configure storage resources on a node for the containers running on it. Select a disk type and configure its size based on service requirements.
    Table 2 Node configuration parameters

    Parameter

    Description

    AZ

    AZ where the node is located. Nodes in a cluster can be created in different AZs for higher reliability. The value cannot be changed after the node is created.

    -

    You are advised to select Random to deploy your node in a random AZ based on the selected node flavor.

    +

    Select Random to deploy your node in a random AZ based on the selected node flavor.

    An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network. To enhance workload availability, create nodes in different AZs.

    Node Type

    CCE standard cluster:
    • ECS (VM): Containers run on ECSs.
    +

    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 Turbo cluster:
    • ECS (VM): Containers run on ECSs. Only the ECSs that can be bound with multiple NICs are supported.
    -
    -

    Container Engine

    -
    CCE clusters support Docker and containerd in some scenarios.
    • VPC network clusters of v1.23 and later versions support containerd. Tunnel network clusters of v1.23.2-r0 and later versions support containerd.
    • For a CCE Turbo cluster, both Docker and containerd are supported. For details, see Mapping between Node OSs and Container Engines.
    +
    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.

    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.

    +

    Select a node flavor based on service requirements. The available node flavors vary depending on regions or AZs. For details, see the CCE console.

    +

    Container Engine

    +

    The container engines supported by CCE include Docker and containerd, which may vary depending on cluster types, cluster versions, and OSs. Select a container engine based on the information displayed on the CCE console. For details, see Mapping between Node OSs and Container Engines.

    OS
    Select an OS type. Different types of nodes support different OSs.
    • Public image: Select a public image for the node.
    • Private image: Select a private image for the node.
    -
    NOTE:
    • Service container runtimes share the kernel and underlying calls of nodes. To ensure compatibility, select a Linux distribution version that is the same as or close to that of the final service container image for the node OS.
    +
    NOTE:

    Service container runtimes share the kernel and underlying calls of nodes. To ensure compatibility, select a Linux distribution version that is the same as or close to that of the final service container image for the node OS.
    - - - + + + @@ -141,6 +146,8 @@ @@ -155,25 +162,25 @@ - - - - + + + - @@ -193,13 +200,13 @@ - - diff --git a/docs/cce/umn/cce_10_0014.html b/docs/cce/umn/cce_10_0014.html index 7b5f47fe..4604a94b 100644 --- a/docs/cce/umn/cce_10_0014.html +++ b/docs/cce/umn/cce_10_0014.html @@ -6,16 +6,16 @@
    Table 3 Configuration parameters

    Parameter

    Description

    @@ -90,24 +90,23 @@

    System Disk

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

    -
    Encryption: System disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. This function is available only in certain regions.
    • Encryption is not selected by default.
    • After selecting Encryption, you can select an existing key in the displayed dialog box. 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 Encryption text box.
    +
    Encryption: System disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. This function is available only in certain regions.
    • Encryption is not selected by default.
    • After setting System Disk Encryption to 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 Encryption text box.

    Data Disk

    At least one data disk is required for the container runtime and kubelet. The data disk cannot be deleted or uninstalled. Otherwise, the node will be unavailable.

    -
    • First data disk: used for container runtime and kubelet components. The value ranges from 20 GiB to 32,768 GiB. The default value is 100 GiB.
    • Other data disks: You can set the data disk size to a value ranging from 10 GiB to 32,768 GiB. The default value is 100 GiB.
    -
    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.

    +
    • First data disk: used for container runtime and kubelet components. The value ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.
    • Other 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.
    +
    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

    -

    Click Expand to configure the following parameters:

    -
    • Data Disk Space Allocation: After selecting Set Container Engine Space, you can specify the proportion of the space for the container engine, image, and temporary storage on the data disk. The container engine space is used to store the working directory, container image data, and image metadata for the container runtime. The remaining space of the data disk is used for pod configuration files, keys, and EmptyDir. For details about how to allocate data disk space, see Data Disk Space Allocation.
    • Encryption: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. This function is available only in certain regions.
      • Encryption is not selected by default.
      • After selecting Encryption, you can select an existing key in the displayed dialog box. 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 Encryption text box.
      +

      Click Expand 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 Data Disk Space Allocation.
      • Encryption: Data disk encryption safeguards your data. Snapshots generated from encrypted disks and disks created using these snapshots automatically inherit the encryption setting. This function is available only in certain regions.
        • Encryption is not selected by default.
        • After selecting Encryption, you can select an existing key in the displayed dialog box. 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 Encryption text box.
      -

      Adding Multiple Data Disks

      +

      Adding data disks

      A maximum of four data disks can be added. By default, raw disks are 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 to scenarios in which 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 to scenarios in which there is a high performance requirement on EmptyDir.
      +
      • 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.
      Local Persistent Volumes and Local 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, allowing 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.
      @@ -126,12 +125,18 @@

    Node Subnet

    +

    Virtual Private Cloud

    The node subnet selected during cluster creation is used by default. You can choose another subnet instead.

    +

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

    Node IP

    +

    Node Subnet

    +

    The node subnet selected during cluster creation is used by default. You can choose another subnet instead.

    +
    • Multiple subnets: You can select multiple subnets in the same VPC for your node pool. Newly added nodes for a scale-out will preferentially consume the IP addresses of the subnets in the top order.
    • Single subnet: Only one subnet is configured for your node pool. If the IP addresses of a single subnet are insufficient, configure multiple subnets. Otherwise, a node pool scale-out may fail.
    +

    Node IP Address

    Random allocation is supported.

    Security group used by the nodes created in the node pool. A maximum of five security groups can be selected.

    When a cluster is created, a node security group named {Cluster name}-cce-node-{Random ID} is created and used by default.

    Traffic needs to pass through certain ports in the node security group to ensure node communications. Ensure that you have enabled these ports if you select another security group.

    +
    NOTE:

    After a node pool is created, its associated security group cannot be modified.

    +

    Kubernetes Label

    -

    A Kubernetes label is a key-value pair added to a Kubernetes object (such as a pod). After specifying a label, click Add. A maximum of 20 labels can be added.

    -

    Labels can be used to distinguish nodes. With workload affinity settings, container pods can be scheduled to a specified node. For more information, see Labels and Selectors.

    -

    Resource Tag

    +

    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 predefined tags to improve the tag creation and resource migration efficiency.

    +

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

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

    Kubernetes Label

    +

    A Kubernetes label is a key-value pair added to a Kubernetes object (such as a pod). After specifying a label, click Add. A maximum of 20 labels can be added.

    +

    Labels can be used to distinguish nodes. With workload affinity settings, container pods can be scheduled to a specified node. For more information, see Labels and Selectors.

    +

    Taint

    This parameter is left blank by default. You can add taints to configure node anti-affinity. A maximum of 20 taints are allowed for each node. Each taint contains the following parameters:
    • Key: A key must contain 1 to 63 characters starting with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. A DNS subdomain name can be used as the prefix of a key.
    • Value: A value must start with a letter or digit and can contain a maximum of 63 characters, including letters, digits, hyphens (-), underscores (_), and periods (.).
    • Effect: Available options are NoSchedule, PreferNoSchedule, and NoExecute.
    +
    This parameter is left blank by default. You can add taints to configure anti-affinity for the node. A maximum of 20 taints are allowed for each node. Each taint contains the following parameters:
    • Key: A key must contain 1 to 63 characters, starting with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. A DNS subdomain name can be used as the prefix of a key.
    • Value: A value must start with a letter or digit and can contain a maximum of 63 characters, including letters, digits, hyphens (-), underscores (_), and periods (.).
    • Effect: Available options are NoSchedule, PreferNoSchedule, and NoExecute.

    For details, see Managing Node Taints.

    -
    NOTE:

    For a cluster of v1.19 or earlier, the workload may have been scheduled to a node before the taint is added. To avoid such a situation, select a cluster of a version later than v1.19.

    +
    NOTE:

    For a cluster of v1.19 or earlier, the workload may have been scheduled to a node before the taint is added. To avoid such a situation, select a cluster of v1.19 or later.

    Pre-installation Command

    Enter commands. A maximum of 1000 characters are allowed.

    +

    Pre-installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded.

    The script will be executed before Kubernetes software is installed. Note that if the script is incorrect, Kubernetes software may fail to be installed.

    Post-installation Command

    Enter commands. A maximum of 1000 characters are allowed.

    +

    Pre-installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded.

    The script will be executed after Kubernetes software is installed, which does not affect the installation.

    NOTE:

    Do not run the reboot command in the post-installation script to restart the system immediately. To restart the system, run the shutdown -r 1 command to restart with a delay of one minute.

    @@ -208,7 +215,7 @@

    Agency

    An agency is created by the account administrator on the IAM console. By creating an agency, you can share your cloud server resources with another account, or entrust a more professional person or team to manage your resources.

    -

    If no agency is available, click Create Agency to create one.

    +

    If no agency is available, click Create Agency on the right to create one.
    - @@ -98,7 +98,7 @@ spec: name: vol-log imagePullSecrets: - name: default-secret -

    The following shows how to use a hostPath volume. Compared with emptyDir, the type of volumes is changed to hostPath, and the path on the host needs to be configured for this hostPath volume. In the following example, /tmp/log on the host is mounted to /var/log/nginx. In this way, the ICAgent can collects logs in /var/log/nginx, without deleting the logs from /tmp/log.

    +

    The following shows how to use a hostPath volume. Compared with emptyDir, the type of volumes is changed to hostPath, and the path on the host needs to be configured for this hostPath volume. In the following example, /tmp/log on the host is mounted to /var/log/nginx. In this way, the ICAgent can collects logs in /var/log/nginx, without deleting the logs from /tmp/log.

    apiVersion: apps/v1
 kind: Deployment
 metadata:
@@ -155,8 +155,8 @@ spec:
    @@ -174,7 +174,7 @@ spec:
    Table 1 Configuring log policies

    Parameter

    @@ -25,7 +25,7 @@

    Mount Path

    Container path (for example, /tmp) to which the storage resources will be mounted.
    NOTICE:
    • Do not mount a volume to a system directory such as / or /var/run. Otherwise, an exception occurs. 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, which leads to a container startup failure or workload creation failure.
    • 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 machine may be damaged.
    • AOM collects only the first 20 logs that have been modified recently. It collects logs from 2 levels of subdirectories by default.
    • AOM only collects .log, .trace, and .out text logs in mounting paths.
    • For details about how to set permissions for mount points in a container, see Configure a Security Context for a Pod or Container.
    +
    Container path (for example, /tmp) to which the storage resources will be mounted.
    NOTICE:
    • Do not mount storage to a system directory such as / or /var/run; this action may cause a container error to occur. You are advised to mount the container to an empty directory. If the directory is not empty, ensure that there are no files affecting container startup in the directory. Otherwise, such files will be replaced, resulting in failures to start the container and create the workload.
    • If the container is mounted to a high-risk directory, you are advised to use an account with minimum permissions to start the container; otherwise, high-risk files on the host may be damaged.
    • AOM collects only the first 20 logs that have been modified recently. It collects logs from 2 levels of subdirectories by default.
    • AOM only collects .log, .trace, and .out text logs in mounting paths.
    • For details about how to set permissions for mount points in a container, see Configure a Security Context for a Pod or Container.

    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

    @@ -164,7 +164,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.

    @@ -217,7 +217,7 @@ kubectl logs -f <pod_name> -n namespace (real-time query in tail -f mode)< diff --git a/docs/cce/umn/cce_10_0020.html b/docs/cce/umn/cce_10_0020.html index 1ceefb94..cfb96256 100644 --- a/docs/cce/umn/cce_10_0020.html +++ b/docs/cce/umn/cce_10_0020.html @@ -20,7 +20,7 @@
  6. Configuring Intra-VPC Access
    7. -
  7. Accessing Public Networks from a Container
    +
  8. Accessing the Internet from a Container
    9. diff --git a/docs/cce/umn/cce_10_0026.html b/docs/cce/umn/cce_10_0026.html index fb1c412f..25c74537 100644 --- a/docs/cce/umn/cce_10_0026.html +++ b/docs/cce/umn/cce_10_0026.html @@ -14,7 +14,7 @@

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

    -
  10. For details about key fields in the trace structure, see section "Trace References" > "Trace Structure" and section "Trace References" > "Example Traces".
    11. +
  11. 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.
    12. diff --git a/docs/cce/umn/cce_10_0028.html b/docs/cce/umn/cce_10_0028.html index 7f608e38..2a60f7d5 100644 --- a/docs/cce/umn/cce_10_0028.html +++ b/docs/cce/umn/cce_10_0028.html @@ -1,8 +1,8 @@ -

    Creating a CCE Cluster

    +

    Creating a CCE Standard/Turbo Cluster

    On the CCE console, you can easily create Kubernetes clusters. After a cluster is created, the master node is hosted by CCE. You only need to create worker nodes. In this way, you can implement cost-effective O&M and efficient service deployment.

    -

    Constraints

    • During the node creation, software packages are downloaded from OBS using the domain name. A private DNS server must be used to resolve the OBS domain name. Therefore, the DNS server address of the subnet where the node resides must be set to the private DNS server address so that the node can access the private DNS server. When you create a subnet, the private DNS server is used by default. If you change the subnet DNS, ensure that the DNS server in use can resolve the OBS domain name.
    • You can create a maximum of 50 clusters in a single region.
    • 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, container CIDR block, Service CIDR block, and kube-proxy settings.
      • Network model. For example, change Tunnel network to VPC network.
      +

      Constraints

      • During the node creation, software packages are downloaded from OBS using the domain name. A private DNS server must be used to resolve the OBS domain name. Therefore, the DNS server address of the subnet where the node resides must be set to the private DNS server address so that the node can access the private DNS server. When you create a subnet, the private DNS server is used by default. If you change the subnet DNS, ensure that the DNS server in use can resolve the OBS domain name.
      • You can create a maximum of 50 clusters in a single region.
      • 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.
      @@ -20,7 +20,7 @@

    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 details about the differences between CCE standard clusters and CCE Turbo clusters, see CCE Turbo Clusters and CCE Standard Clusters.

    +

    For more details, see cluster types.

    Cluster Name

    @@ -41,8 +41,8 @@

    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 to ensure cluster reliability.
    • Single: Only one master node will be created in your cluster.
    -
    You can also select AZs for the master nodes. By default, AZs are allocated automatically for the master nodes.