From 6d480dcc2099fd426404c7d47136adb1c9546e09 Mon Sep 17 00:00:00 2001 From: qiujiandong1 Date: Wed, 29 Oct 2025 10:20:57 +0000 Subject: [PATCH] CCE UMN update 20250912 version Reviewed-by: Eotvos, Oliver Co-authored-by: qiujiandong1 Co-committed-by: qiujiandong1 --- docs/cce/umn/ALL_META.TXT.json | 2801 ++++++++------ docs/cce/umn/CLASS.TXT.json | 3262 +++++++++-------- docs/cce/umn/CVE-2025-23266.html | 2 +- docs/cce/umn/cce_01_0300.html | 13 +- docs/cce/umn/cce_10_0003.html | 20 +- docs/cce/umn/cce_10_0004.html | 4 +- docs/cce/umn/cce_10_0006.html | 2 +- docs/cce/umn/cce_10_0007.html | 28 +- docs/cce/umn/cce_10_0009.html | 151 +- docs/cce/umn/cce_10_0010.html | 43 +- docs/cce/umn/cce_10_0011.html | 64 +- docs/cce/umn/cce_10_0012.html | 26 +- docs/cce/umn/cce_10_0014.html | 4 +- docs/cce/umn/cce_10_0015.html | 8 +- docs/cce/umn/cce_10_0016.html | 4 +- docs/cce/umn/cce_10_0018.html | 46 +- docs/cce/umn/cce_10_0019.html | 4 +- docs/cce/umn/cce_10_0020.html | 8 +- docs/cce/umn/cce_10_0024.html | 2 +- docs/cce/umn/cce_10_0025.html | 1393 +++++-- docs/cce/umn/cce_10_0026.html | 68 +- docs/cce/umn/cce_10_0028.html | 673 ++-- docs/cce/umn/cce_10_0031.html | 4 +- docs/cce/umn/cce_10_0034.html | 233 +- docs/cce/umn/cce_10_0035.html | 2 +- docs/cce/umn/cce_10_0036.html | 2 +- docs/cce/umn/cce_10_0044.html | 6 +- docs/cce/umn/cce_10_0046.html | 2 +- docs/cce/umn/cce_10_0047.html | 298 +- docs/cce/umn/cce_10_0048.html | 190 +- docs/cce/umn/cce_10_0054.html | 94 +- docs/cce/umn/cce_10_0059.html | 194 +- docs/cce/umn/cce_10_0063.html | 6 +- docs/cce/umn/cce_10_0064.html | 2 +- docs/cce/umn/cce_10_0066.html | 255 +- docs/cce/umn/cce_10_0068.html | 4 +- docs/cce/umn/cce_10_0081.html | 6 +- docs/cce/umn/cce_10_0083.html | 18 +- docs/cce/umn/cce_10_0084.html | 2 +- docs/cce/umn/cce_10_0091.html | 4 +- docs/cce/umn/cce_10_0094.html | 16 +- docs/cce/umn/cce_10_0105.html | 254 +- docs/cce/umn/cce_10_0107.html | 73 +- docs/cce/umn/cce_10_0111.html | 4 +- docs/cce/umn/cce_10_0112.html | 236 +- docs/cce/umn/cce_10_0113.html | 126 +- docs/cce/umn/cce_10_0125.html | 4 +- docs/cce/umn/cce_10_0127.html | 2 +- docs/cce/umn/cce_10_0129.html | 235 +- docs/cce/umn/cce_10_0130.html | 4 +- docs/cce/umn/cce_10_0132.html | 55 +- docs/cce/umn/cce_10_0140.html | 4 +- docs/cce/umn/cce_10_0141.html | 333 +- docs/cce/umn/cce_10_0142.html | 67 +- docs/cce/umn/cce_10_0144.html | 10 +- docs/cce/umn/cce_10_0146.html | 14 +- docs/cce/umn/cce_10_0150.html | 197 +- docs/cce/umn/cce_10_0151.html | 194 +- docs/cce/umn/cce_10_0152.html | 8 +- docs/cce/umn/cce_10_0153.html | 82 +- docs/cce/umn/cce_10_0154.html | 817 +++-- docs/cce/umn/cce_10_0160.html | 6 +- docs/cce/umn/cce_10_0163.html | 8 +- docs/cce/umn/cce_10_0164.html | 2 + docs/cce/umn/cce_10_0175.html | 6 +- docs/cce/umn/cce_10_0178.html | 235 +- docs/cce/umn/cce_10_0180.html | 2 +- docs/cce/umn/cce_10_0184.html | 4 +- docs/cce/umn/cce_10_0185.html | 8 +- docs/cce/umn/cce_10_0186.html | 6 +- docs/cce/umn/cce_10_0187.html | 4 +- docs/cce/umn/cce_10_0188.html | 8 +- docs/cce/umn/cce_10_0189.html | 9 +- docs/cce/umn/cce_10_0190.html | 4 +- docs/cce/umn/cce_10_0191.html | 8 +- docs/cce/umn/cce_10_0193.html | 426 +-- docs/cce/umn/cce_10_0196.html | 40 +- docs/cce/umn/cce_10_0197.html | 66 +- docs/cce/umn/cce_10_0198.html | 22 +- docs/cce/umn/cce_10_0201.html | 20 +- docs/cce/umn/cce_10_0205.html | 39 +- docs/cce/umn/cce_10_0207.html | 6 +- docs/cce/umn/cce_10_0208.html | 39 +- docs/cce/umn/cce_10_0209.html | 190 +- docs/cce/umn/cce_10_0210.html | 2 +- docs/cce/umn/cce_10_0212.html | 6 +- docs/cce/umn/cce_10_0213.html | 761 ++-- docs/cce/umn/cce_10_0214.html | 8 +- docs/cce/umn/cce_10_0216.html | 167 +- docs/cce/umn/cce_10_0222.html | 2 +- docs/cce/umn/cce_10_0240.html | 39 +- docs/cce/umn/cce_10_0245.html | 6 +- docs/cce/umn/cce_10_0247.html | 8 +- docs/cce/umn/cce_10_0248.html | 4 +- docs/cce/umn/cce_10_0249.html | 375 +- docs/cce/umn/cce_10_0251.html | 34 +- docs/cce/umn/cce_10_0252.html | 288 +- docs/cce/umn/cce_10_0275.html | 3 +- docs/cce/umn/cce_10_0276.html | 2 +- docs/cce/umn/cce_10_0277.html | 203 +- docs/cce/umn/cce_10_0278.html | 4 +- docs/cce/umn/cce_10_0279.html | 65 +- docs/cce/umn/cce_10_0280.html | 4 +- docs/cce/umn/cce_10_0281.html | 41 +- docs/cce/umn/cce_10_0282.html | 24 +- docs/cce/umn/cce_10_0283.html | 24 +- docs/cce/umn/cce_10_0284.html | 244 +- docs/cce/umn/cce_10_0285.html | 10 +- docs/cce/umn/cce_10_0287.html | 7 +- docs/cce/umn/cce_10_0288.html | 10 +- docs/cce/umn/cce_10_0290.html | 59 +- docs/cce/umn/cce_10_0291.html | 4 +- docs/cce/umn/cce_10_0293.html | 2 +- docs/cce/umn/cce_10_0296.html | 30 +- docs/cce/umn/cce_10_0300.html | 21 +- docs/cce/umn/cce_10_0302.html | 318 +- docs/cce/umn/cce_10_0307.html | 26 +- docs/cce/umn/cce_10_0336.html | 28 +- docs/cce/umn/cce_10_0337.html | 16 +- docs/cce/umn/cce_10_0338.html | 6 +- docs/cce/umn/cce_10_0341.html | 4 +- docs/cce/umn/cce_10_0342.html | 64 +- docs/cce/umn/cce_10_0345.html | 91 +- docs/cce/umn/cce_10_0348.html | 18 +- docs/cce/umn/cce_10_0349.html | 3 +- docs/cce/umn/cce_10_0351.html | 8 +- docs/cce/umn/cce_10_0352.html | 4 +- docs/cce/umn/cce_10_0353.html | 2 +- docs/cce/umn/cce_10_0354.html | 47 +- docs/cce/umn/cce_10_0355.html | 11 +- docs/cce/umn/cce_10_0359.html | 8 +- docs/cce/umn/cce_10_0360.html | 10 +- docs/cce/umn/cce_10_0361.html | 10 +- docs/cce/umn/cce_10_0362.html | 143 + docs/cce/umn/cce_10_0363.html | 37 +- docs/cce/umn/cce_10_0364.html | 70 +- docs/cce/umn/cce_10_0365.html | 20 +- docs/cce/umn/cce_10_0367.html | 10 +- docs/cce/umn/cce_10_0373.html | 12 +- docs/cce/umn/cce_10_0374.html | 12 +- docs/cce/umn/cce_10_0377.html | 6 +- docs/cce/umn/cce_10_0378.html | 117 +- docs/cce/umn/cce_10_0379.html | 26 +- docs/cce/umn/cce_10_0380.html | 819 +++-- docs/cce/umn/cce_10_0381.html | 108 +- docs/cce/umn/cce_10_0382.html | 70 +- docs/cce/umn/cce_10_0384.html | 23 +- docs/cce/umn/cce_10_0385.html | 83 +- docs/cce/umn/cce_10_0386.html | 209 +- docs/cce/umn/cce_10_0390.html | 4 +- docs/cce/umn/cce_10_0391.html | 2 +- docs/cce/umn/cce_10_0397.html | 210 +- docs/cce/umn/cce_10_0398.html | 97 +- docs/cce/umn/cce_10_0399.html | 14 +- docs/cce/umn/cce_10_0400.html | 14 +- docs/cce/umn/cce_10_0402.html | 43 +- docs/cce/umn/cce_10_0403.html | 8 +- docs/cce/umn/cce_10_0404.html | 145 + docs/cce/umn/cce_10_0405.html | 862 +++-- docs/cce/umn/cce_10_0406.html | 59 +- docs/cce/umn/cce_10_0415.html | 22 +- docs/cce/umn/cce_10_0416.html | 123 +- docs/cce/umn/cce_10_0420.html | 10 +- docs/cce/umn/cce_10_0421.html | 2 +- docs/cce/umn/cce_10_0422.html | 4 +- docs/cce/umn/cce_10_0423.html | 2 +- docs/cce/umn/cce_10_0425.html | 64 +- docs/cce/umn/cce_10_0426.html | 5 +- docs/cce/umn/cce_10_0430.html | 2 +- docs/cce/umn/cce_10_0431.html | 4 +- docs/cce/umn/cce_10_0433.html | 7 +- docs/cce/umn/cce_10_0436.html | 4 +- docs/cce/umn/cce_10_0437.html | 10 +- docs/cce/umn/cce_10_0439.html | 2 +- docs/cce/umn/cce_10_0440.html | 20 +- docs/cce/umn/cce_10_0441.html | 11 +- docs/cce/umn/cce_10_0442.html | 9 +- docs/cce/umn/cce_10_0445.html | 2 +- docs/cce/umn/cce_10_0447.html | 8 +- docs/cce/umn/cce_10_0448.html | 3 +- docs/cce/umn/cce_10_0449.html | 2 +- docs/cce/umn/cce_10_0450.html | 4 +- docs/cce/umn/cce_10_0455.html | 2 +- docs/cce/umn/cce_10_0456.html | 2 +- docs/cce/umn/cce_10_0459.html | 6 +- docs/cce/umn/cce_10_0460.html | 2 +- docs/cce/umn/cce_10_0462.html | 26 +- docs/cce/umn/cce_10_0463.html | 2 +- docs/cce/umn/cce_10_0465.html | 2 + docs/cce/umn/cce_10_0476.html | 87 +- docs/cce/umn/cce_10_0477.html | 4 +- docs/cce/umn/cce_10_0486.html | 2 +- docs/cce/umn/cce_10_0487.html | 3 + docs/cce/umn/cce_10_0490.html | 4 +- docs/cce/umn/cce_10_0491.html | 2 +- docs/cce/umn/cce_10_0493.html | 8 +- docs/cce/umn/cce_10_0495.html | 8 +- docs/cce/umn/cce_10_0497.html | 6 +- docs/cce/umn/cce_10_0498.html | 29 +- docs/cce/umn/cce_10_0500.html | 4 +- docs/cce/umn/cce_10_0503.html | 6 +- docs/cce/umn/cce_10_0504.html | 12 +- docs/cce/umn/cce_10_0505.html | 2 +- docs/cce/umn/cce_10_0508.html | 27 +- docs/cce/umn/cce_10_0518.html | 10 +- docs/cce/umn/cce_10_0520.html | 8 +- docs/cce/umn/cce_10_0522.html | 4 +- docs/cce/umn/cce_10_0528.html | 4 +- docs/cce/umn/cce_10_0530.html | 2 +- docs/cce/umn/cce_10_0531.html | 7 +- docs/cce/umn/cce_10_0549.html | 342 +- docs/cce/umn/cce_10_0550.html | 4 +- docs/cce/umn/cce_10_0552.html | 12 +- docs/cce/umn/cce_10_0554.html | 52 +- docs/cce/umn/cce_10_0555.html | 30 +- docs/cce/umn/cce_10_0557.html | 2 +- docs/cce/umn/cce_10_0565.html | 2 +- docs/cce/umn/cce_10_0566.html | 2 +- docs/cce/umn/cce_10_0601.html | 4 +- docs/cce/umn/cce_10_0602.html | 12 +- docs/cce/umn/cce_10_0603.html | 12 +- docs/cce/umn/cce_10_0604.html | 10 +- docs/cce/umn/cce_10_0605.html | 4 +- docs/cce/umn/cce_10_0613.html | 132 +- docs/cce/umn/cce_10_0614.html | 48 +- docs/cce/umn/cce_10_0615.html | 40 +- docs/cce/umn/cce_10_0616.html | 38 +- docs/cce/umn/cce_10_0617.html | 4 +- docs/cce/umn/cce_10_0619.html | 46 +- docs/cce/umn/cce_10_0620.html | 22 +- docs/cce/umn/cce_10_0624.html | 4 +- docs/cce/umn/cce_10_0625.html | 186 +- docs/cce/umn/cce_10_0626.html | 6 +- docs/cce/umn/cce_10_0628.html | 12 +- docs/cce/umn/cce_10_0630.html | 20 +- docs/cce/umn/cce_10_0631.html | 16 +- docs/cce/umn/cce_10_0633.html | 2 +- docs/cce/umn/cce_10_0634.html | 14 +- docs/cce/umn/cce_10_0635.html | 8 +- docs/cce/umn/cce_10_0636.html | 4 +- docs/cce/umn/cce_10_0637.html | 4 +- docs/cce/umn/cce_10_0638.html | 4 +- docs/cce/umn/cce_10_0642.html | 4 +- docs/cce/umn/cce_10_0643.html | 24 + docs/cce/umn/cce_10_0644.html | 65 + docs/cce/umn/cce_10_0645.html | 69 + docs/cce/umn/cce_10_0646.html | 202 + docs/cce/umn/cce_10_0649.html | 4 +- docs/cce/umn/cce_10_0651.html | 8 +- docs/cce/umn/cce_10_0652.html | 871 +++-- docs/cce/umn/cce_10_0653.html | 63 +- docs/cce/umn/cce_10_0654.html | 9 +- docs/cce/umn/cce_10_0655.html | 4 +- docs/cce/umn/cce_10_0656.html | 8 +- docs/cce/umn/cce_10_0657.html | 6 +- docs/cce/umn/cce_10_0658.html | 3 +- docs/cce/umn/cce_10_0659.html | 33 +- docs/cce/umn/cce_10_0660.html | 16 +- docs/cce/umn/cce_10_0674.html | 2 +- docs/cce/umn/cce_10_0675.html | 2 +- docs/cce/umn/cce_10_0677.html | 2 +- docs/cce/umn/cce_10_0678.html | 14 +- docs/cce/umn/cce_10_0680.html | 6 +- docs/cce/umn/cce_10_0681.html | 466 +-- docs/cce/umn/cce_10_0683.html | 99 +- docs/cce/umn/cce_10_0684.html | 2 +- docs/cce/umn/cce_10_0685.html | 2 +- docs/cce/umn/cce_10_0686.html | 10 +- docs/cce/umn/cce_10_0687.html | 160 +- docs/cce/umn/cce_10_0688.html | 173 +- docs/cce/umn/cce_10_0689.html | 22 +- docs/cce/umn/cce_10_0691.html | 8 +- docs/cce/umn/cce_10_0692.html | 2 +- docs/cce/umn/cce_10_0693.html | 2 +- docs/cce/umn/cce_10_0694.html | 12 +- docs/cce/umn/cce_10_0695.html | 58 +- docs/cce/umn/cce_10_0698.html | 2 +- docs/cce/umn/cce_10_0699.html | 8 +- docs/cce/umn/cce_10_0702.html | 59 +- docs/cce/umn/cce_10_0704.html | 4 +- docs/cce/umn/cce_10_0720.html | 10 +- docs/cce/umn/cce_10_0721.html | 4 +- docs/cce/umn/cce_10_0722.html | 2 +- docs/cce/umn/cce_10_0725.html | 6 +- docs/cce/umn/cce_10_0726.html | 6 +- docs/cce/umn/cce_10_0727.html | 32 +- docs/cce/umn/cce_10_0728.html | 8 +- docs/cce/umn/cce_10_0729.html | 28 +- docs/cce/umn/cce_10_0730.html | 16 +- docs/cce/umn/cce_10_0734.html | 12 +- docs/cce/umn/cce_10_0735.html | 4 +- docs/cce/umn/cce_10_0741.html | 83 + docs/cce/umn/cce_10_0742.html | 76 + docs/cce/umn/cce_10_0744.html | 8 +- docs/cce/umn/cce_10_0766.html | 68 +- docs/cce/umn/cce_10_0767.html | 4 +- docs/cce/umn/cce_10_0773.html | 15 +- docs/cce/umn/cce_10_0775.html | 4 +- docs/cce/umn/cce_10_0777.html | 4 +- docs/cce/umn/cce_10_0778.html | 4 +- docs/cce/umn/cce_10_0779.html | 304 ++ docs/cce/umn/cce_10_0782.html | 6 +- docs/cce/umn/cce_10_0783.html | 78 +- docs/cce/umn/cce_10_0784.html | 28 +- docs/cce/umn/cce_10_0785.html | 2 +- docs/cce/umn/cce_10_0786.html | 21 +- docs/cce/umn/cce_10_0787.html | 2 +- docs/cce/umn/cce_10_0788.html | 2 +- docs/cce/umn/cce_10_0789.html | 190 +- docs/cce/umn/cce_10_0792.html | 18 +- docs/cce/umn/cce_10_0793.html | 4 +- docs/cce/umn/cce_10_0809.html | 20 +- docs/cce/umn/cce_10_0811.html | 2 + docs/cce/umn/cce_10_0828.html | 148 + docs/cce/umn/cce_10_0831.html | 34 +- docs/cce/umn/cce_10_0832.html | 34 +- docs/cce/umn/cce_10_0833.html | 4 +- docs/cce/umn/cce_10_0836.html | 2 +- docs/cce/umn/cce_10_0839.html | 22 +- docs/cce/umn/cce_10_0841.html | 40 +- docs/cce/umn/cce_10_0842.html | 14 +- docs/cce/umn/cce_10_0844.html | 39 + docs/cce/umn/cce_10_0845.html | 25 + docs/cce/umn/cce_10_0846.html | 54 + docs/cce/umn/cce_10_0847.html | 78 + docs/cce/umn/cce_10_0848.html | 123 + docs/cce/umn/cce_10_0849.html | 35 + docs/cce/umn/cce_10_0857.html | 49 + docs/cce/umn/cce_10_0859.html | 29 +- docs/cce/umn/cce_10_0860.html | 4 +- docs/cce/umn/cce_10_0864.html | 6 +- docs/cce/umn/cce_10_0883.html | 4 +- docs/cce/umn/cce_10_0886.html | 8 +- docs/cce/umn/cce_10_0891.html | 2 +- docs/cce/umn/cce_10_0892.html | 6 +- docs/cce/umn/cce_10_0893.html | 8 +- docs/cce/umn/cce_10_0896.html | 2 +- docs/cce/umn/cce_10_0897.html | 57 +- docs/cce/umn/cce_10_0904.html | 4 +- docs/cce/umn/cce_10_0906.html | 25 +- docs/cce/umn/cce_10_0908.html | 2 + docs/cce/umn/cce_10_0909.html | 7 +- docs/cce/umn/cce_10_0910.html | 2 + docs/cce/umn/cce_10_0919.html | 6 +- docs/cce/umn/cce_10_0927.html | 4 +- docs/cce/umn/cce_10_0930.html | 4 +- docs/cce/umn/cce_10_0934.html | 70 +- docs/cce/umn/cce_10_0935.html | 4 - docs/cce/umn/cce_10_0936.html | 2 + docs/cce/umn/cce_10_0939.html | 257 +- docs/cce/umn/cce_10_0940.html | 242 -- docs/cce/umn/cce_10_0944.html | 12 +- docs/cce/umn/cce_10_0945.html | 61 +- docs/cce/umn/cce_10_0947.html | 40 +- docs/cce/umn/cce_10_0949.html | 843 ++++- docs/cce/umn/cce_10_0950.html | 85 +- docs/cce/umn/cce_10_0954.html | 76 +- docs/cce/umn/cce_10_0955.html | 158 +- docs/cce/umn/cce_10_0959.html | 21 + docs/cce/umn/cce_10_0960.html | 26 + docs/cce/umn/cce_10_0961.html | 65 + docs/cce/umn/cce_10_0962.html | 41 + docs/cce/umn/cce_10_0965.html | 131 + docs/cce/umn/cce_10_0966.html | 57 + docs/cce/umn/cce_10_0967.html | 48 +- docs/cce/umn/cce_10_0968.html | 49 +- docs/cce/umn/cce_10_0997.html | 240 ++ docs/cce/umn/cce_10_1006.html | 139 + docs/cce/umn/cce_10_1012.html | 104 + docs/cce/umn/cce_10_1016.html | 21 + docs/cce/umn/cce_10_1017.html | 19 + docs/cce/umn/cce_10_1077.html | 27 + docs/cce/umn/cce_10_1078.html | 72 + docs/cce/umn/cce_10_1079.html | 20 + docs/cce/umn/cce_bestpractice_0000.html | 2 +- docs/cce/umn/cce_bestpractice_00002.html | 4 +- docs/cce/umn/cce_bestpractice_00004.html | 59 +- docs/cce/umn/cce_bestpractice_00006.html | 2 +- docs/cce/umn/cce_bestpractice_0002.html | 2 +- docs/cce/umn/cce_bestpractice_0003.html | 4 +- docs/cce/umn/cce_bestpractice_00035.html | 8 +- docs/cce/umn/cce_bestpractice_0004.html | 2 +- docs/cce/umn/cce_bestpractice_0007.html | 2 +- docs/cce/umn/cce_bestpractice_0009.html | 2 +- docs/cce/umn/cce_bestpractice_0010.html | 12 +- docs/cce/umn/cce_bestpractice_0013.html | 4 +- docs/cce/umn/cce_bestpractice_0014.html | 48 +- docs/cce/umn/cce_bestpractice_00162.html | 104 +- docs/cce/umn/cce_bestpractice_00199.html | 14 +- docs/cce/umn/cce_bestpractice_00220.html | 4 +- docs/cce/umn/cce_bestpractice_00221.html | 18 +- docs/cce/umn/cce_bestpractice_00222.html | 29 +- docs/cce/umn/cce_bestpractice_00226.html | 2 +- docs/cce/umn/cce_bestpractice_00227.html | 44 +- docs/cce/umn/cce_bestpractice_00228.html | 28 +- docs/cce/umn/cce_bestpractice_00231.html | 4 +- docs/cce/umn/cce_bestpractice_00237.html | 4 +- docs/cce/umn/cce_bestpractice_0024.html | 45 +- docs/cce/umn/cce_bestpractice_00253.html | 74 +- docs/cce/umn/cce_bestpractice_00253_0.html | 74 +- docs/cce/umn/cce_bestpractice_00254.html | 4 +- docs/cce/umn/cce_bestpractice_00281.html | 263 +- docs/cce/umn/cce_bestpractice_00282.html | 21 +- docs/cce/umn/cce_bestpractice_00284.html | 4 +- docs/cce/umn/cce_bestpractice_0050.html | 2 +- docs/cce/umn/cce_bestpractice_0052.html | 4 +- docs/cce/umn/cce_bestpractice_0053.html | 2 +- docs/cce/umn/cce_bestpractice_0059.html | 2 +- docs/cce/umn/cce_bestpractice_0107.html | 2 +- docs/cce/umn/cce_bestpractice_0300.html | 2 +- docs/cce/umn/cce_bestpractice_0307.html | 6 +- docs/cce/umn/cce_bestpractice_0310.html | 109 +- docs/cce/umn/cce_bestpractice_0312.html | 32 +- docs/cce/umn/cce_bestpractice_0313.html | 2 +- docs/cce/umn/cce_bestpractice_0324.html | 22 +- docs/cce/umn/cce_bestpractice_0325.html | 28 +- docs/cce/umn/cce_bestpractice_0326.html | 2 +- docs/cce/umn/cce_bestpractice_0333.html | 20 +- docs/cce/umn/cce_bestpractice_0346.html | 4 +- docs/cce/umn/cce_bestpractice_0347.html | 2 + docs/cce/umn/cce_bestpractice_0348.html | 4 +- docs/cce/umn/cce_bestpractice_0350.html | 2 +- docs/cce/umn/cce_bestpractice_0351.html | 16 + docs/cce/umn/cce_bestpractice_0356.html | 2 +- docs/cce/umn/cce_bestpractice_0357.html | 38 +- docs/cce/umn/cce_bestpractice_10001.html | 22 +- docs/cce/umn/cce_bestpractice_10002.html | 8 +- docs/cce/umn/cce_bestpractice_10009.html | 12 +- docs/cce/umn/cce_bestpractice_10010.html | 36 +- docs/cce/umn/cce_bestpractice_10012.html | 4 +- docs/cce/umn/cce_bestpractice_10016.html | 171 +- docs/cce/umn/cce_bestpractice_10017.html | 4 +- docs/cce/umn/cce_bestpractice_10020.html | 22 +- docs/cce/umn/cce_bestpractice_10020_0.html | 22 +- docs/cce/umn/cce_bestpractice_10021.html | 8 +- docs/cce/umn/cce_bestpractice_10024.html | 167 +- docs/cce/umn/cce_bestpractice_10041.html | 4 +- docs/cce/umn/cce_bestpractice_10069.html | 19 + docs/cce/umn/cce_bulletin_0027.html | 6 +- docs/cce/umn/cce_bulletin_0058.html | 2 +- docs/cce/umn/cce_bulletin_0104.html | 31 + docs/cce/umn/cce_faq_00006.html | 6 +- docs/cce/umn/cce_faq_00012.html | 2 +- docs/cce/umn/cce_faq_00015.html | 15 +- docs/cce/umn/cce_faq_00018.html | 168 +- docs/cce/umn/cce_faq_00020.html | 6 +- docs/cce/umn/cce_faq_00022.html | 4 +- docs/cce/umn/cce_faq_00025.html | 2 +- docs/cce/umn/cce_faq_00027.html | 24 +- docs/cce/umn/cce_faq_00029.html | 2 +- docs/cce/umn/cce_faq_00030.html | 2 +- docs/cce/umn/cce_faq_00039.html | 8 +- docs/cce/umn/cce_faq_00041.html | 2 +- docs/cce/umn/cce_faq_00089.html | 2 +- docs/cce/umn/cce_faq_00097.html | 4 +- docs/cce/umn/cce_faq_00107.html | 4 +- docs/cce/umn/cce_faq_00109.html | 12 +- docs/cce/umn/cce_faq_00111.html | 2 +- docs/cce/umn/cce_faq_00120.html | 39 +- docs/cce/umn/cce_faq_00127.html | 2 +- docs/cce/umn/cce_faq_00130.html | 20 + docs/cce/umn/cce_faq_00134.html | 4 +- docs/cce/umn/cce_faq_00140.html | 8 +- docs/cce/umn/cce_faq_00154.html | 6 +- docs/cce/umn/cce_faq_00163.html | 4 +- docs/cce/umn/cce_faq_00189.html | 2 +- docs/cce/umn/cce_faq_00195.html | 2 +- docs/cce/umn/cce_faq_00197.html | 6 +- docs/cce/umn/cce_faq_00200.html | 7 +- docs/cce/umn/cce_faq_00202.html | 14 +- docs/cce/umn/cce_faq_00203.html | 4 +- docs/cce/umn/cce_faq_00205.html | 2 +- docs/cce/umn/cce_faq_00215.html | 4 + docs/cce/umn/cce_faq_00218.html | 2 +- docs/cce/umn/cce_faq_00263.html | 2 +- docs/cce/umn/cce_faq_00265.html | 98 +- docs/cce/umn/cce_faq_00266.html | 6 +- docs/cce/umn/cce_faq_00277.html | 100 + docs/cce/umn/cce_faq_00278.html | 2 +- docs/cce/umn/cce_faq_00281.html | 2 + docs/cce/umn/cce_faq_00286.html | 2 +- docs/cce/umn/cce_faq_00296.html | 4 +- docs/cce/umn/cce_faq_00307.html | 2 +- docs/cce/umn/cce_faq_00311.html | 2 +- docs/cce/umn/cce_faq_00319.html | 2 +- docs/cce/umn/cce_faq_00321.html | 2 +- docs/cce/umn/cce_faq_00322.html | 8 +- docs/cce/umn/cce_faq_00324.html | 2 + docs/cce/umn/cce_faq_00325.html | 2 +- docs/cce/umn/cce_faq_00394.html | 4 +- docs/cce/umn/cce_faq_00401.html | 4 +- docs/cce/umn/cce_faq_00402.html | 2 +- docs/cce/umn/cce_faq_00409.html | 3 +- docs/cce/umn/cce_faq_00417.html | 2 +- docs/cce/umn/cce_faq_00432.html | 6 +- docs/cce/umn/cce_faq_00440.html | 12 +- docs/cce/umn/cce_faq_00443.html | 6 +- docs/cce/umn/cce_faq_00447.html | 4 +- docs/cce/umn/cce_faq_00460.html | 4 +- docs/cce/umn/cce_faq_00468.html | 62 +- docs/cce/umn/cce_faq_00484.html | 4 +- docs/cce/umn/cce_faq_00487.html | 6 +- docs/cce/umn/cce_faq_00488.html | 19 + docs/cce/umn/cce_faq_00493.html | 246 ++ docs/cce/umn/cce_faq_00501.html | 76 + docs/cce/umn/cce_productdesc_0000.html | 2 +- docs/cce/umn/cce_productdesc_0001.html | 66 +- docs/cce/umn/cce_productdesc_0002.html | 4 +- docs/cce/umn/cce_productdesc_0003.html | 72 +- docs/cce/umn/cce_productdesc_0004.html | 2 +- docs/cce/umn/cce_productdesc_0005.html | 142 +- docs/cce/umn/cce_productdesc_0007.html | 14 +- docs/cce/umn/cce_productdesc_0008.html | 8 +- docs/cce/umn/cce_productdesc_0012.html | 2 +- docs/cce/umn/cce_productdesc_0017.html | 2 +- docs/cce/umn/cce_productdesc_0018.html | 22 +- docs/cce/umn/cce_productdesc_0021.html | 2 +- docs/cce/umn/en-us_image_0000002101396665.png | Bin 105943 -> 31093 bytes docs/cce/umn/en-us_image_0000002218659242.png | Bin 60086 -> 0 bytes docs/cce/umn/en-us_image_0000002218660418.png | Bin 5498 -> 0 bytes docs/cce/umn/en-us_image_0000002218660566.png | Bin 8145 -> 0 bytes docs/cce/umn/en-us_image_0000002218660782.png | Bin 50716 -> 0 bytes docs/cce/umn/en-us_image_0000002218818218.png | Bin 225679 -> 0 bytes docs/cce/umn/en-us_image_0000002218818934.png | Bin 114117 -> 0 bytes docs/cce/umn/en-us_image_0000002218819838.png | Bin 19210 -> 0 bytes docs/cce/umn/en-us_image_0000002218820402.png | Bin 101668 -> 0 bytes docs/cce/umn/en-us_image_0000002218820434.png | Bin 44580 -> 0 bytes docs/cce/umn/en-us_image_0000002253618649.png | Bin 32091 -> 0 bytes docs/cce/umn/en-us_image_0000002253618837.png | Bin 63511 -> 0 bytes docs/cce/umn/en-us_image_0000002253619653.png | Bin 62540 -> 0 bytes docs/cce/umn/en-us_image_0000002253619705.png | Bin 30987 -> 0 bytes docs/cce/umn/en-us_image_0000002253620097.png | Bin 311 -> 0 bytes docs/cce/umn/en-us_image_0000002253620365.png | Bin 311 -> 0 bytes docs/cce/umn/en-us_image_0000002253620433.png | Bin 321 -> 0 bytes docs/cce/umn/en-us_image_0000002253620437.png | Bin 158 -> 0 bytes docs/cce/umn/en-us_image_0000002253778377.png | Bin 1004 -> 0 bytes docs/cce/umn/en-us_image_0000002253779501.png | Bin 5713 -> 0 bytes docs/cce/umn/en-us_image_0000002253779921.png | Bin 190913 -> 0 bytes ...0.png => en-us_image_0000002359774578.png} | Bin ...4.png => en-us_image_0000002434076708.png} | Bin ...7.png => en-us_image_0000002434076796.png} | Bin ...6.png => en-us_image_0000002434077688.png} | Bin ...2.png => en-us_image_0000002434077820.png} | Bin ...6.png => en-us_image_0000002434077852.png} | Bin ...3.png => en-us_image_0000002434077884.png} | Bin ...6.png => en-us_image_0000002434077888.png} | Bin ...4.png => en-us_image_0000002434077952.png} | Bin ...3.png => en-us_image_0000002434077956.png} | Bin ...8.png => en-us_image_0000002434077960.png} | Bin ...8.png => en-us_image_0000002434077980.png} | Bin ...7.png => en-us_image_0000002434078060.png} | Bin ...5.png => en-us_image_0000002434078100.png} | Bin ...6.png => en-us_image_0000002434078164.png} | Bin ...2.jpg => en-us_image_0000002434078176.jpg} | Bin ...4.png => en-us_image_0000002434078268.png} | Bin ...4.png => en-us_image_0000002434078272.png} | Bin ...5.png => en-us_image_0000002434078288.png} | Bin ...6.png => en-us_image_0000002434078340.png} | Bin ...5.png => en-us_image_0000002434078352.png} | Bin ...3.png => en-us_image_0000002434078452.png} | Bin docs/cce/umn/en-us_image_0000002434078492.png | Bin 0 -> 225767 bytes ...7.png => en-us_image_0000002434078552.png} | Bin ...7.png => en-us_image_0000002434078624.png} | Bin ...4.png => en-us_image_0000002434078744.png} | Bin ...4.png => en-us_image_0000002434078836.png} | Bin docs/cce/umn/en-us_image_0000002434078944.png | Bin 0 -> 79992 bytes docs/cce/umn/en-us_image_0000002434078948.png | Bin 0 -> 31640 bytes ...4.png => en-us_image_0000002434078988.png} | Bin ...4.png => en-us_image_0000002434079000.png} | Bin ...7.png => en-us_image_0000002434079036.png} | Bin ...7.png => en-us_image_0000002434079080.png} | Bin ...3.png => en-us_image_0000002434079156.png} | Bin ...4.png => en-us_image_0000002434079172.png} | Bin ...3.png => en-us_image_0000002434079816.png} | Bin docs/cce/umn/en-us_image_0000002434079820.png | Bin 0 -> 29765 bytes docs/cce/umn/en-us_image_0000002434079924.png | Bin 0 -> 156721 bytes ...5.png => en-us_image_0000002434079976.png} | Bin ...6.png => en-us_image_0000002434080024.png} | Bin ...1.png => en-us_image_0000002434080032.png} | Bin ...8.png => en-us_image_0000002434080044.png} | Bin ...8.png => en-us_image_0000002434080052.png} | Bin docs/cce/umn/en-us_image_0000002434080064.png | Bin 0 -> 28642 bytes ...9.png => en-us_image_0000002434080104.png} | Bin ...5.png => en-us_image_0000002434080108.png} | Bin docs/cce/umn/en-us_image_0000002434080164.png | Bin 0 -> 17153 bytes ...0.png => en-us_image_0000002434080192.png} | Bin docs/cce/umn/en-us_image_0000002434080236.png | Bin 0 -> 55493 bytes ...7.png => en-us_image_0000002434080356.png} | Bin docs/cce/umn/en-us_image_0000002434080364.png | Bin 0 -> 16240 bytes ...0.png => en-us_image_0000002434080444.png} | Bin docs/cce/umn/en-us_image_0000002434080480.png | Bin 0 -> 32407 bytes ...7.png => en-us_image_0000002434080488.png} | Bin ...5.png => en-us_image_0000002434080664.png} | Bin ...7.png => en-us_image_0000002434080684.png} | Bin ...8.png => en-us_image_0000002434080764.png} | Bin ...7.png => en-us_image_0000002434080772.png} | Bin ...5.png => en-us_image_0000002434080784.png} | Bin ...8.png => en-us_image_0000002434080872.png} | Bin ...9.png => en-us_image_0000002434080944.png} | Bin ...8.png => en-us_image_0000002434080952.png} | Bin ...4.png => en-us_image_0000002434080996.png} | Bin docs/cce/umn/en-us_image_0000002434081028.png | Bin 0 -> 52865 bytes ...1.png => en-us_image_0000002434081032.png} | Bin ...6.png => en-us_image_0000002434081060.png} | Bin ...7.png => en-us_image_0000002434081088.png} | Bin ...1.png => en-us_image_0000002434081104.png} | Bin ...0.png => en-us_image_0000002434081108.png} | Bin ...6.png => en-us_image_0000002434081112.png} | Bin ...0.png => en-us_image_0000002434081116.png} | Bin ...3.png => en-us_image_0000002434081124.png} | Bin ...1.png => en-us_image_0000002434081132.png} | Bin ...5.png => en-us_image_0000002434081240.png} | Bin ...7.png => en-us_image_0000002434236552.png} | Bin ...6.png => en-us_image_0000002434236556.png} | Bin ...4.png => en-us_image_0000002434236576.png} | Bin ...1.png => en-us_image_0000002434237560.png} | Bin ...9.png => en-us_image_0000002434237644.png} | Bin ...9.png => en-us_image_0000002434237648.png} | Bin ...8.png => en-us_image_0000002434237664.png} | Bin ...0.png => en-us_image_0000002434237668.png} | Bin ...8.png => en-us_image_0000002434237712.png} | Bin ...1.png => en-us_image_0000002434237792.png} | Bin ...6.png => en-us_image_0000002434237800.png} | Bin ...2.png => en-us_image_0000002434237864.png} | Bin ...6.png => en-us_image_0000002434237960.png} | Bin ...8.png => en-us_image_0000002434237980.png} | Bin ...2.png => en-us_image_0000002434238008.png} | Bin ...5.png => en-us_image_0000002434238020.png} | Bin ...0.png => en-us_image_0000002434238076.png} | Bin ...5.png => en-us_image_0000002434238092.png} | Bin ...6.png => en-us_image_0000002434238140.png} | Bin ...9.png => en-us_image_0000002434238156.png} | Bin ...0.jpg => en-us_image_0000002434238160.jpg} | Bin ...4.jpg => en-us_image_0000002434238164.jpg} | Bin docs/cce/umn/en-us_image_0000002434238176.png | Bin 0 -> 27776 bytes ...3.png => en-us_image_0000002434238228.png} | Bin ...4.png => en-us_image_0000002434238264.png} | Bin ...0.png => en-us_image_0000002434238296.png} | Bin ...9.png => en-us_image_0000002434238492.png} | Bin ...1.png => en-us_image_0000002434238568.png} | Bin ...7.png => en-us_image_0000002434238636.png} | Bin ...1.png => en-us_image_0000002434238660.png} | Bin ...4.png => en-us_image_0000002434238776.png} | Bin ...5.png => en-us_image_0000002434238836.png} | Bin ...6.png => en-us_image_0000002434238848.png} | Bin ...5.png => en-us_image_0000002434238868.png} | Bin ...2.png => en-us_image_0000002434238916.png} | Bin ...9.png => en-us_image_0000002434238964.png} | Bin docs/cce/umn/en-us_image_0000002434238992.png | Bin 0 -> 43439 bytes ...7.png => en-us_image_0000002434239004.png} | Bin ...5.png => en-us_image_0000002434239008.png} | Bin ...4.png => en-us_image_0000002434239016.png} | Bin ...2.png => en-us_image_0000002434239032.png} | Bin ...6.png => en-us_image_0000002434239688.png} | Bin ...8.png => en-us_image_0000002434239756.png} | Bin ...8.png => en-us_image_0000002434239760.png} | Bin ...3.png => en-us_image_0000002434239808.png} | Bin ...1.png => en-us_image_0000002434239840.png} | Bin ...4.png => en-us_image_0000002434239860.png} | Bin ...9.png => en-us_image_0000002434239864.png} | Bin ...8.png => en-us_image_0000002434239928.png} | Bin ...6.png => en-us_image_0000002434239996.png} | Bin ...9.png => en-us_image_0000002434240060.png} | Bin ...6.png => en-us_image_0000002434240112.png} | Bin docs/cce/umn/en-us_image_0000002434240204.png | Bin 0 -> 32512 bytes docs/cce/umn/en-us_image_0000002434240212.png | Bin 0 -> 56168 bytes ...4.png => en-us_image_0000002434240216.png} | Bin ...1.png => en-us_image_0000002434240224.png} | Bin ...8.png => en-us_image_0000002434240328.png} | Bin ...1.png => en-us_image_0000002434240340.png} | Bin ...6.png => en-us_image_0000002434240368.png} | Bin ...2.png => en-us_image_0000002434240380.png} | Bin docs/cce/umn/en-us_image_0000002434240392.png | Bin 0 -> 37928 bytes ...2.png => en-us_image_0000002434240500.png} | Bin ...9.png => en-us_image_0000002434240556.png} | Bin ...4.png => en-us_image_0000002434240588.png} | Bin ...0.png => en-us_image_0000002434240692.png} | Bin ...5.png => en-us_image_0000002434240696.png} | Bin ...6.png => en-us_image_0000002434240756.png} | Bin ...4.png => en-us_image_0000002434240760.png} | Bin ...3.png => en-us_image_0000002434240800.png} | Bin ...7.png => en-us_image_0000002434240840.png} | Bin ...5.png => en-us_image_0000002434240844.png} | Bin docs/cce/umn/en-us_image_0000002434240884.png | Bin 0 -> 111844 bytes ...7.png => en-us_image_0000002434240896.png} | Bin docs/cce/umn/en-us_image_0000002434240904.png | Bin 0 -> 20399 bytes ...6.png => en-us_image_0000002434240924.png} | Bin ...0.png => en-us_image_0000002434240932.png} | Bin ...0.png => en-us_image_0000002434240944.png} | Bin ...5.png => en-us_image_0000002434241048.png} | Bin ...8.png => en-us_image_0000002467675109.png} | Bin ...5.png => en-us_image_0000002467676153.png} | Bin ...0.png => en-us_image_0000002467676157.png} | Bin ...4.png => en-us_image_0000002467676197.png} | Bin ...7.png => en-us_image_0000002467676209.png} | Bin ...1.png => en-us_image_0000002467676217.png} | Bin ...2.png => en-us_image_0000002467676241.png} | Bin ...6.png => en-us_image_0000002467676245.png} | Bin ...6.png => en-us_image_0000002467676473.png} | Bin ...7.png => en-us_image_0000002467676509.png} | Bin ...0.png => en-us_image_0000002467676597.png} | Bin ...6.png => en-us_image_0000002467676609.png} | Bin docs/cce/umn/en-us_image_0000002467676697.png | Bin 0 -> 576020 bytes ...3.png => en-us_image_0000002467676737.png} | Bin ...6.png => en-us_image_0000002467676785.png} | Bin ...0.png => en-us_image_0000002467676789.png} | Bin ...9.png => en-us_image_0000002467676797.png} | Bin ...8.png => en-us_image_0000002467676837.png} | Bin ...6.png => en-us_image_0000002467676981.png} | Bin ...9.png => en-us_image_0000002467677037.png} | Bin docs/cce/umn/en-us_image_0000002467677085.png | Bin 0 -> 34007 bytes ...7.png => en-us_image_0000002467677145.png} | Bin ...6.png => en-us_image_0000002467677157.png} | Bin ...7.png => en-us_image_0000002467677169.png} | Bin ...3.png => en-us_image_0000002467677189.png} | Bin ...3.png => en-us_image_0000002467677221.png} | Bin ...1.png => en-us_image_0000002467677273.png} | Bin ...3.png => en-us_image_0000002467677277.png} | Bin ...6.png => en-us_image_0000002467677281.png} | Bin ...4.png => en-us_image_0000002467677345.png} | Bin ...3.png => en-us_image_0000002467677433.png} | Bin ...5.png => en-us_image_0000002467677505.png} | Bin ...1.png => en-us_image_0000002467678045.png} | Bin docs/cce/umn/en-us_image_0000002467678129.png | Bin 0 -> 202 bytes ...1.png => en-us_image_0000002467678137.png} | Bin docs/cce/umn/en-us_image_0000002467678141.png | Bin 0 -> 151 bytes docs/cce/umn/en-us_image_0000002467678173.png | Bin 0 -> 29213 bytes docs/cce/umn/en-us_image_0000002467678177.png | Bin 0 -> 35845 bytes docs/cce/umn/en-us_image_0000002467678225.png | Bin 0 -> 35944 bytes ...1.png => en-us_image_0000002467678261.png} | Bin ...5.png => en-us_image_0000002467678269.png} | Bin ...7.png => en-us_image_0000002467678313.png} | Bin ...5.png => en-us_image_0000002467678317.png} | Bin ...9.png => en-us_image_0000002467678321.png} | Bin ...3.png => en-us_image_0000002467678353.png} | Bin ...9.png => en-us_image_0000002467678365.png} | Bin ...2.png => en-us_image_0000002467678445.png} | Bin docs/cce/umn/en-us_image_0000002467678485.png | Bin 0 -> 16513 bytes docs/cce/umn/en-us_image_0000002467678505.png | Bin 0 -> 429 bytes ...0.png => en-us_image_0000002467678561.png} | Bin docs/cce/umn/en-us_image_0000002467678629.png | Bin 0 -> 24483 bytes docs/cce/umn/en-us_image_0000002467678641.png | Bin 0 -> 41233 bytes ...8.png => en-us_image_0000002467678685.png} | Bin ...3.png => en-us_image_0000002467678717.png} | Bin ...6.png => en-us_image_0000002467678845.png} | Bin ...7.png => en-us_image_0000002467678853.png} | Bin ...4.png => en-us_image_0000002467678877.png} | Bin docs/cce/umn/en-us_image_0000002467678893.png | Bin 0 -> 65034 bytes ...2.png => en-us_image_0000002467678985.png} | Bin ...9.png => en-us_image_0000002467679005.png} | Bin ...4.png => en-us_image_0000002467679025.png} | Bin ...9.png => en-us_image_0000002467679061.png} | Bin ...3.png => en-us_image_0000002467679065.png} | Bin ...1.png => en-us_image_0000002467679101.png} | Bin ...3.png => en-us_image_0000002467679137.png} | Bin ...7.png => en-us_image_0000002467679205.png} | Bin ...2.png => en-us_image_0000002467679233.png} | Bin ...3.png => en-us_image_0000002467679261.png} | Bin ...9.png => en-us_image_0000002467679301.png} | Bin ...8.png => en-us_image_0000002467679305.png} | Bin ...6.png => en-us_image_0000002467679373.png} | Bin ...4.png => en-us_image_0000002467679385.png} | Bin docs/cce/umn/en-us_image_0000002467679405.png | Bin 0 -> 53675 bytes ...4.png => en-us_image_0000002467679431.png} | Bin ...6.png => en-us_image_0000002467679437.png} | Bin ...9.png => en-us_image_0000002467715213.png} | Bin ...5.png => en-us_image_0000002467715337.png} | Bin ...4.png => en-us_image_0000002467716173.png} | Bin ...4.png => en-us_image_0000002467716313.png} | Bin ...4.png => en-us_image_0000002467716341.png} | Bin ...6.png => en-us_image_0000002467716349.png} | Bin ...0.png => en-us_image_0000002467716361.png} | Bin ...2.png => en-us_image_0000002467716365.png} | Bin ...6.png => en-us_image_0000002467716449.png} | Bin ...7.png => en-us_image_0000002467716489.png} | Bin ...7.png => en-us_image_0000002467716501.png} | Bin ...1.png => en-us_image_0000002467716505.png} | Bin docs/cce/umn/en-us_image_0000002467716521.png | Bin 0 -> 62325 bytes ...4.png => en-us_image_0000002467716601.png} | Bin ...7.png => en-us_image_0000002467716629.png} | Bin ...1.png => en-us_image_0000002467716657.png} | Bin ...9.png => en-us_image_0000002467716749.png} | Bin ...3.png => en-us_image_0000002467716761.png} | Bin docs/cce/umn/en-us_image_0000002467716769.png | Bin 0 -> 23632 bytes ...8.png => en-us_image_0000002467716805.png} | Bin ...9.png => en-us_image_0000002467716841.png} | Bin ...0.png => en-us_image_0000002467716881.png} | Bin ...8.png => en-us_image_0000002467716901.png} | Bin ...8.png => en-us_image_0000002467716909.png} | Bin ...0.png => en-us_image_0000002467716933.png} | Bin ...2.png => en-us_image_0000002467716953.png} | Bin ...2.jpg => en-us_image_0000002467717097.jpg} | Bin ...2.png => en-us_image_0000002467717261.png} | Bin ...8.png => en-us_image_0000002467717277.png} | Bin ...4.png => en-us_image_0000002467717329.png} | Bin ...5.png => en-us_image_0000002467717421.png} | Bin ...2.png => en-us_image_0000002467717529.png} | Bin ...9.png => en-us_image_0000002467717557.png} | Bin docs/cce/umn/en-us_image_0000002467717625.png | Bin 0 -> 35451 bytes ...7.png => en-us_image_0000002467717633.png} | Bin ...6.png => en-us_image_0000002467717641.png} | Bin ...8.png => en-us_image_0000002467717649.png} | Bin docs/cce/umn/en-us_image_0000002467718269.png | Bin 0 -> 7466 bytes ...8.png => en-us_image_0000002467718301.png} | Bin ...3.png => en-us_image_0000002467718381.png} | Bin ...1.png => en-us_image_0000002467718461.png} | Bin ...3.jpg => en-us_image_0000002467718465.jpg} | Bin ...8.png => en-us_image_0000002467718541.png} | Bin docs/cce/umn/en-us_image_0000002467718549.png | Bin 0 -> 9528 bytes ...4.png => en-us_image_0000002467718661.png} | Bin docs/cce/umn/en-us_image_0000002467718693.png | Bin 0 -> 369 bytes docs/cce/umn/en-us_image_0000002467718709.png | Bin 0 -> 6830 bytes ...9.png => en-us_image_0000002467718757.png} | Bin ...9.png => en-us_image_0000002467718781.png} | Bin ...2.png => en-us_image_0000002467718921.png} | Bin docs/cce/umn/en-us_image_0000002467718941.png | Bin 0 -> 33453 bytes ...7.png => en-us_image_0000002467718953.png} | Bin docs/cce/umn/en-us_image_0000002467719021.png | Bin 0 -> 20900 bytes docs/cce/umn/en-us_image_0000002467719025.png | Bin 0 -> 66679 bytes docs/cce/umn/en-us_image_0000002467719029.png | Bin 0 -> 25116 bytes docs/cce/umn/en-us_image_0000002467719033.png | Bin 0 -> 45811 bytes docs/cce/umn/en-us_image_0000002467719037.png | Bin 0 -> 106287 bytes docs/cce/umn/en-us_image_0000002467719041.png | Bin 0 -> 39728 bytes docs/cce/umn/en-us_image_0000002467719053.png | Bin 0 -> 16280 bytes docs/cce/umn/en-us_image_0000002467719057.png | Bin 0 -> 78081 bytes ...7.png => en-us_image_0000002467719105.png} | Bin ...4.png => en-us_image_0000002467719125.png} | Bin ...5.png => en-us_image_0000002467719133.png} | Bin docs/cce/umn/en-us_image_0000002467719141.png | Bin 0 -> 16969 bytes ...1.png => en-us_image_0000002467719233.png} | Bin ...5.png => en-us_image_0000002467719245.png} | Bin docs/cce/umn/en-us_image_0000002467719381.png | Bin 0 -> 13781 bytes docs/cce/umn/en-us_image_0000002467719393.png | Bin 0 -> 16224 bytes ...1.png => en-us_image_0000002467719409.png} | Bin ...9.png => en-us_image_0000002467719473.png} | Bin ...5.png => en-us_image_0000002467719549.png} | Bin ...6.png => en-us_image_0000002467719573.png} | Bin ...9.png => en-us_image_0000002467719689.png} | Bin docs/cce/umn/en-us_image_0000002467719741.png | Bin 0 -> 232066 bytes docs/cce/umn/en-us_image_0258894622.png | Bin 7296 -> 0 bytes 840 files changed, 20812 insertions(+), 11621 deletions(-) create mode 100644 docs/cce/umn/cce_10_0362.html create mode 100644 docs/cce/umn/cce_10_0404.html create mode 100644 docs/cce/umn/cce_10_0643.html create mode 100644 docs/cce/umn/cce_10_0644.html create mode 100644 docs/cce/umn/cce_10_0645.html create mode 100644 docs/cce/umn/cce_10_0646.html create mode 100644 docs/cce/umn/cce_10_0741.html create mode 100644 docs/cce/umn/cce_10_0742.html create mode 100644 docs/cce/umn/cce_10_0779.html create mode 100644 docs/cce/umn/cce_10_0828.html create mode 100644 docs/cce/umn/cce_10_0844.html create mode 100644 docs/cce/umn/cce_10_0845.html create mode 100644 docs/cce/umn/cce_10_0846.html create mode 100644 docs/cce/umn/cce_10_0847.html create mode 100644 docs/cce/umn/cce_10_0848.html create mode 100644 docs/cce/umn/cce_10_0849.html create mode 100644 docs/cce/umn/cce_10_0857.html delete mode 100644 docs/cce/umn/cce_10_0940.html create mode 100644 docs/cce/umn/cce_10_0959.html create mode 100644 docs/cce/umn/cce_10_0960.html create mode 100644 docs/cce/umn/cce_10_0961.html create mode 100644 docs/cce/umn/cce_10_0962.html create mode 100644 docs/cce/umn/cce_10_0965.html create mode 100644 docs/cce/umn/cce_10_0966.html create mode 100644 docs/cce/umn/cce_10_0997.html create mode 100644 docs/cce/umn/cce_10_1006.html create mode 100644 docs/cce/umn/cce_10_1012.html create mode 100644 docs/cce/umn/cce_10_1016.html create mode 100644 docs/cce/umn/cce_10_1017.html create mode 100644 docs/cce/umn/cce_10_1077.html create mode 100644 docs/cce/umn/cce_10_1078.html create mode 100644 docs/cce/umn/cce_10_1079.html create mode 100644 docs/cce/umn/cce_bestpractice_0351.html create mode 100644 docs/cce/umn/cce_bestpractice_10069.html create mode 100644 docs/cce/umn/cce_bulletin_0104.html create mode 100644 docs/cce/umn/cce_faq_00130.html create mode 100644 docs/cce/umn/cce_faq_00277.html create mode 100644 docs/cce/umn/cce_faq_00488.html create mode 100644 docs/cce/umn/cce_faq_00493.html create mode 100644 docs/cce/umn/cce_faq_00501.html delete mode 100644 docs/cce/umn/en-us_image_0000002218659242.png delete mode 100644 docs/cce/umn/en-us_image_0000002218660418.png delete mode 100644 docs/cce/umn/en-us_image_0000002218660566.png delete mode 100644 docs/cce/umn/en-us_image_0000002218660782.png delete mode 100644 docs/cce/umn/en-us_image_0000002218818218.png delete mode 100644 docs/cce/umn/en-us_image_0000002218818934.png delete mode 100644 docs/cce/umn/en-us_image_0000002218819838.png delete mode 100644 docs/cce/umn/en-us_image_0000002218820402.png delete mode 100644 docs/cce/umn/en-us_image_0000002218820434.png delete mode 100644 docs/cce/umn/en-us_image_0000002253618649.png delete mode 100644 docs/cce/umn/en-us_image_0000002253618837.png delete mode 100644 docs/cce/umn/en-us_image_0000002253619653.png delete mode 100644 docs/cce/umn/en-us_image_0000002253619705.png delete mode 100644 docs/cce/umn/en-us_image_0000002253620097.png delete mode 100644 docs/cce/umn/en-us_image_0000002253620365.png delete mode 100644 docs/cce/umn/en-us_image_0000002253620433.png delete mode 100644 docs/cce/umn/en-us_image_0000002253620437.png delete mode 100644 docs/cce/umn/en-us_image_0000002253778377.png delete mode 100644 docs/cce/umn/en-us_image_0000002253779501.png delete mode 100644 docs/cce/umn/en-us_image_0000002253779921.png rename docs/cce/umn/{en-us_image_0000001696838310.png => en-us_image_0000002359774578.png} (100%) rename docs/cce/umn/{en-us_image_0000002218817314.png => en-us_image_0000002434076708.png} (100%) rename docs/cce/umn/{en-us_image_0000002253777197.png => en-us_image_0000002434076796.png} (100%) rename docs/cce/umn/{en-us_image_0000002218658206.png => en-us_image_0000002434077688.png} (100%) rename docs/cce/umn/{en-us_image_0000002254877052.png => en-us_image_0000002434077820.png} (100%) rename docs/cce/umn/{en-us_image_0000002218658506.png => en-us_image_0000002434077852.png} (100%) rename docs/cce/umn/{en-us_image_0000002253777953.png => en-us_image_0000002434077884.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818146.png => en-us_image_0000002434077888.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818234.png => en-us_image_0000002434077952.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618133.png => en-us_image_0000002434077956.png} (100%) rename docs/cce/umn/{en-us_image_0000002218658418.png => en-us_image_0000002434077960.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818158.png => en-us_image_0000002434077980.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618137.png => en-us_image_0000002434078060.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778245.png => en-us_image_0000002434078100.png} (100%) rename docs/cce/umn/{en-us_image_0000002218658526.png => en-us_image_0000002434078164.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818442.jpg => en-us_image_0000002434078176.jpg} (100%) rename docs/cce/umn/{en-us_image_0000002218658854.png => en-us_image_0000002434078268.png} (100%) rename docs/cce/umn/{en-us_image_0000002218658614.png => en-us_image_0000002434078272.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618345.png => en-us_image_0000002434078288.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818386.png => en-us_image_0000002434078340.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778205.png => en-us_image_0000002434078352.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778453.png => en-us_image_0000002434078452.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434078492.png rename docs/cce/umn/{en-us_image_0000002253778797.png => en-us_image_0000002434078552.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618457.png => en-us_image_0000002434078624.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818954.png => en-us_image_0000002434078744.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818994.png => en-us_image_0000002434078836.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434078944.png create mode 100644 docs/cce/umn/en-us_image_0000002434078948.png rename docs/cce/umn/{en-us_image_0000002218659254.png => en-us_image_0000002434078988.png} (100%) rename docs/cce/umn/{en-us_image_0000002218819094.png => en-us_image_0000002434079000.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619117.png => en-us_image_0000002434079036.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779017.png => en-us_image_0000002434079080.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778493.png => en-us_image_0000002434079156.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818734.png => en-us_image_0000002434079172.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619613.png => en-us_image_0000002434079816.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434079820.png create mode 100644 docs/cce/umn/en-us_image_0000002434079924.png rename docs/cce/umn/{en-us_image_0000002253779605.png => en-us_image_0000002434079976.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660286.png => en-us_image_0000002434080024.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779941.png => en-us_image_0000002434080032.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660298.png => en-us_image_0000002434080044.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820158.png => en-us_image_0000002434080052.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434080064.png rename docs/cce/umn/{en-us_image_0000002253619909.png => en-us_image_0000002434080104.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779825.png => en-us_image_0000002434080108.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434080164.png rename docs/cce/umn/{en-us_image_0000002218660430.png => en-us_image_0000002434080192.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434080236.png rename docs/cce/umn/{en-us_image_0000002253620537.png => en-us_image_0000002434080356.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434080364.png rename docs/cce/umn/{en-us_image_0000002218819650.png => en-us_image_0000002434080444.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434080480.png rename docs/cce/umn/{en-us_image_0000002253779397.png => en-us_image_0000002434080488.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619765.png => en-us_image_0000002434080664.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619737.png => en-us_image_0000002434080684.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660238.png => en-us_image_0000002434080764.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619937.png => en-us_image_0000002434080772.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619605.png => en-us_image_0000002434080784.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660438.png => en-us_image_0000002434080872.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620209.png => en-us_image_0000002434080944.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660478.png => en-us_image_0000002434080952.png} (100%) rename docs/cce/umn/{en-us_image_0000002218819774.png => en-us_image_0000002434080996.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434081028.png rename docs/cce/umn/{en-us_image_0000002253780361.png => en-us_image_0000002434081032.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660226.png => en-us_image_0000002434081060.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620397.png => en-us_image_0000002434081088.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620361.png => en-us_image_0000002434081104.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820570.png => en-us_image_0000002434081108.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820646.png => en-us_image_0000002434081112.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820650.png => en-us_image_0000002434081116.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620533.png => en-us_image_0000002434081124.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620541.png => en-us_image_0000002434081132.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620425.png => en-us_image_0000002434081240.png} (100%) rename docs/cce/umn/{en-us_image_0000002253617217.png => en-us_image_0000002434236552.png} (100%) rename docs/cce/umn/{en-us_image_0000002218817326.png => en-us_image_0000002434236556.png} (100%) rename docs/cce/umn/{en-us_image_0000002218657514.png => en-us_image_0000002434236576.png} (100%) rename docs/cce/umn/{en-us_image_0000002253617941.png => en-us_image_0000002434237560.png} (100%) rename docs/cce/umn/{en-us_image_0000002289589649.png => en-us_image_0000002434237644.png} (100%) rename docs/cce/umn/{en-us_image_0000002289592109.png => en-us_image_0000002434237648.png} (100%) rename docs/cce/umn/{en-us_image_0000002254877428.png => en-us_image_0000002434237664.png} (100%) rename docs/cce/umn/{en-us_image_0000002254895070.png => en-us_image_0000002434237668.png} (100%) rename docs/cce/umn/{en-us_image_0000002254978558.png => en-us_image_0000002434237712.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618121.png => en-us_image_0000002434237792.png} (100%) rename docs/cce/umn/{en-us_image_0000002218658406.png => en-us_image_0000002434237800.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818222.png => en-us_image_0000002434237864.png} (100%) rename docs/cce/umn/{en-us_image_0000002218658786.png => en-us_image_0000002434237960.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818398.png => en-us_image_0000002434237980.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818382.png => en-us_image_0000002434238008.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778265.png => en-us_image_0000002434238020.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818490.png => en-us_image_0000002434238076.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778225.png => en-us_image_0000002434238092.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818446.png => en-us_image_0000002434238140.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778269.png => en-us_image_0000002434238156.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818770.jpg => en-us_image_0000002434238160.jpg} (100%) rename docs/cce/umn/{en-us_image_0000002218658934.jpg => en-us_image_0000002434238164.jpg} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434238176.png rename docs/cce/umn/{en-us_image_0000002253618813.png => en-us_image_0000002434238228.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818914.png => en-us_image_0000002434238264.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818630.png => en-us_image_0000002434238296.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778449.png => en-us_image_0000002434238492.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778541.png => en-us_image_0000002434238568.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618817.png => en-us_image_0000002434238636.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618841.png => en-us_image_0000002434238660.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659274.png => en-us_image_0000002434238776.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778885.png => en-us_image_0000002434238836.png} (100%) rename docs/cce/umn/{en-us_image_0000002218819126.png => en-us_image_0000002434238848.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778965.png => en-us_image_0000002434238868.png} (100%) rename docs/cce/umn/{en-us_image_0000002218819222.png => en-us_image_0000002434238916.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618549.png => en-us_image_0000002434238964.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434238992.png rename docs/cce/umn/{en-us_image_0000002253778497.png => en-us_image_0000002434239004.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618605.png => en-us_image_0000002434239008.png} (100%) rename docs/cce/umn/{en-us_image_0000002218658914.png => en-us_image_0000002434239016.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818982.png => en-us_image_0000002434239032.png} (100%) rename docs/cce/umn/{en-us_image_0000002218819786.png => en-us_image_0000002434239688.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660018.png => en-us_image_0000002434239756.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659938.png => en-us_image_0000002434239760.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619713.png => en-us_image_0000002434239808.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620001.png => en-us_image_0000002434239840.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660294.png => en-us_image_0000002434239860.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620049.png => en-us_image_0000002434239864.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820018.png => en-us_image_0000002434239928.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660486.png => en-us_image_0000002434239996.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620189.png => en-us_image_0000002434240060.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820166.png => en-us_image_0000002434240112.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434240204.png create mode 100644 docs/cce/umn/en-us_image_0000002434240212.png rename docs/cce/umn/{en-us_image_0000002218820674.png => en-us_image_0000002434240216.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620561.png => en-us_image_0000002434240224.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659818.png => en-us_image_0000002434240328.png} (100%) rename docs/cce/umn/{en-us_image_0000002253780381.png => en-us_image_0000002434240340.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659866.png => en-us_image_0000002434240368.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820702.png => en-us_image_0000002434240380.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434240392.png rename docs/cce/umn/{en-us_image_0000002218819982.png => en-us_image_0000002434240500.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779469.png => en-us_image_0000002434240556.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660194.png => en-us_image_0000002434240588.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659930.png => en-us_image_0000002434240692.png} (100%) rename docs/cce/umn/{en-us_image_0000002253780085.png => en-us_image_0000002434240696.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660466.png => en-us_image_0000002434240756.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660474.png => en-us_image_0000002434240760.png} (100%) rename docs/cce/umn/{en-us_image_0000002253780093.png => en-us_image_0000002434240800.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620497.png => en-us_image_0000002434240840.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620305.png => en-us_image_0000002434240844.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434240884.png rename docs/cce/umn/{en-us_image_0000002253780457.png => en-us_image_0000002434240896.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002434240904.png rename docs/cce/umn/{en-us_image_0000002218660706.png => en-us_image_0000002434240924.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660710.png => en-us_image_0000002434240932.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660810.png => en-us_image_0000002434240944.png} (100%) rename docs/cce/umn/{en-us_image_0000002253780145.png => en-us_image_0000002434241048.png} (100%) rename docs/cce/umn/{en-us_image_0000002218657498.png => en-us_image_0000002467675109.png} (100%) rename docs/cce/umn/{en-us_image_0000002289476265.png => en-us_image_0000002467676153.png} (100%) rename docs/cce/umn/{en-us_image_0000002254879860.png => en-us_image_0000002467676157.png} (100%) rename docs/cce/umn/{en-us_image_0000002254895574.png => en-us_image_0000002467676197.png} (100%) rename docs/cce/umn/{en-us_image_0000002253777937.png => en-us_image_0000002467676209.png} (100%) rename docs/cce/umn/{en-us_image_0000002253777941.png => en-us_image_0000002467676217.png} (100%) rename docs/cce/umn/{en-us_image_0000002218658322.png => en-us_image_0000002467676241.png} (100%) rename docs/cce/umn/{en-us_image_0000002218658326.png => en-us_image_0000002467676245.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818366.png => en-us_image_0000002467676473.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778437.png => en-us_image_0000002467676509.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818310.png => en-us_image_0000002467676597.png} (100%) rename docs/cce/umn/{en-us_image_0000002218658606.png => en-us_image_0000002467676609.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467676697.png rename docs/cce/umn/{en-us_image_0000002253778733.png => en-us_image_0000002467676737.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818546.png => en-us_image_0000002467676785.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659110.png => en-us_image_0000002467676789.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618529.png => en-us_image_0000002467676797.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660718.png => en-us_image_0000002467676837.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659046.png => en-us_image_0000002467676981.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618569.png => en-us_image_0000002467677037.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467677085.png rename docs/cce/umn/{en-us_image_0000002253778737.png => en-us_image_0000002467677145.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818946.png => en-us_image_0000002467677157.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618897.png => en-us_image_0000002467677169.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778813.png => en-us_image_0000002467677189.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619133.png => en-us_image_0000002467677221.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778901.png => en-us_image_0000002467677273.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778853.png => en-us_image_0000002467677277.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659906.png => en-us_image_0000002467677281.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659314.png => en-us_image_0000002467677345.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779013.png => en-us_image_0000002467677433.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778485.png => en-us_image_0000002467677505.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619521.png => en-us_image_0000002467678045.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467678129.png rename docs/cce/umn/{en-us_image_0000002253619621.png => en-us_image_0000002467678137.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467678141.png create mode 100644 docs/cce/umn/en-us_image_0000002467678173.png create mode 100644 docs/cce/umn/en-us_image_0000002467678177.png create mode 100644 docs/cce/umn/en-us_image_0000002467678225.png rename docs/cce/umn/{en-us_image_0000002253619901.png => en-us_image_0000002467678261.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619005.png => en-us_image_0000002467678269.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779617.png => en-us_image_0000002467678313.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779625.png => en-us_image_0000002467678317.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620029.png => en-us_image_0000002467678321.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620033.png => en-us_image_0000002467678353.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779949.png => en-us_image_0000002467678365.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820242.png => en-us_image_0000002467678445.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467678485.png create mode 100644 docs/cce/umn/en-us_image_0000002467678505.png rename docs/cce/umn/{en-us_image_0000002218820410.png => en-us_image_0000002467678561.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467678629.png create mode 100644 docs/cce/umn/en-us_image_0000002467678641.png rename docs/cce/umn/{en-us_image_0000002218820658.png => en-us_image_0000002467678685.png} (100%) rename docs/cce/umn/{en-us_image_0000002253780433.png => en-us_image_0000002467678717.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820586.png => en-us_image_0000002467678845.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620477.png => en-us_image_0000002467678853.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660734.png => en-us_image_0000002467678877.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467678893.png rename docs/cce/umn/{en-us_image_0000002218660022.png => en-us_image_0000002467678985.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779849.png => en-us_image_0000002467679005.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820034.png => en-us_image_0000002467679025.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619569.png => en-us_image_0000002467679061.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779473.png => en-us_image_0000002467679065.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619601.png => en-us_image_0000002467679101.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779993.png => en-us_image_0000002467679137.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619977.png => en-us_image_0000002467679205.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820382.png => en-us_image_0000002467679233.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620213.png => en-us_image_0000002467679261.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779809.png => en-us_image_0000002467679301.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820458.png => en-us_image_0000002467679305.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820526.png => en-us_image_0000002467679373.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660654.png => en-us_image_0000002467679385.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467679405.png rename docs/cce/umn/{en-us_image_0000002218820214.png => en-us_image_0000002467679431.png} (100%) rename docs/cce/umn/{en-us_image_0000002218660366.png => en-us_image_0000002467679437.png} (100%) rename docs/cce/umn/{en-us_image_0000002253777129.png => en-us_image_0000002467715213.png} (100%) rename docs/cce/umn/{en-us_image_0000002253777225.png => en-us_image_0000002467715337.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818034.png => en-us_image_0000002467716173.png} (100%) rename docs/cce/umn/{en-us_image_0000002254895914.png => en-us_image_0000002467716313.png} (100%) rename docs/cce/umn/{en-us_image_0000002255002834.png => en-us_image_0000002467716341.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818126.png => en-us_image_0000002467716349.png} (100%) rename docs/cce/umn/{en-us_image_0000002218658310.png => en-us_image_0000002467716361.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818142.png => en-us_image_0000002467716365.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818246.png => en-us_image_0000002467716449.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618117.png => en-us_image_0000002467716489.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778017.png => en-us_image_0000002467716501.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778021.png => en-us_image_0000002467716505.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467716521.png rename docs/cce/umn/{en-us_image_0000002218658654.png => en-us_image_0000002467716601.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618517.png => en-us_image_0000002467716629.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778301.png => en-us_image_0000002467716657.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618329.png => en-us_image_0000002467716749.png} (100%) rename docs/cce/umn/{en-us_image_0000002253778253.png => en-us_image_0000002467716761.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467716769.png rename docs/cce/umn/{en-us_image_0000002218818458.png => en-us_image_0000002467716805.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618289.png => en-us_image_0000002467716841.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818530.png => en-us_image_0000002467716881.png} (100%) rename docs/cce/umn/{en-us_image_0000002218658938.png => en-us_image_0000002467716901.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659118.png => en-us_image_0000002467716909.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818590.png => en-us_image_0000002467716933.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659142.png => en-us_image_0000002467716953.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659182.jpg => en-us_image_0000002467717097.jpg} (100%) rename docs/cce/umn/{en-us_image_0000002218659302.png => en-us_image_0000002467717261.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659098.png => en-us_image_0000002467717277.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659174.png => en-us_image_0000002467717329.png} (100%) rename docs/cce/umn/{en-us_image_0000002253618845.png => en-us_image_0000002467717421.png} (100%) rename docs/cce/umn/{en-us_image_0000002218819242.png => en-us_image_0000002467717529.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619089.png => en-us_image_0000002467717557.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467717625.png rename docs/cce/umn/{en-us_image_0261818867.png => en-us_image_0000002467717633.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818686.png => en-us_image_0000002467717641.png} (100%) rename docs/cce/umn/{en-us_image_0000002218818738.png => en-us_image_0000002467717649.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467718269.png rename docs/cce/umn/{en-us_image_0000002218819718.png => en-us_image_0000002467718301.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779633.png => en-us_image_0000002467718381.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619701.png => en-us_image_0000002467718461.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779773.jpg => en-us_image_0000002467718465.jpg} (100%) rename docs/cce/umn/{en-us_image_0000002218820038.png => en-us_image_0000002467718541.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467718549.png rename docs/cce/umn/{en-us_image_0000002218660514.png => en-us_image_0000002467718661.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467718693.png create mode 100644 docs/cce/umn/en-us_image_0000002467718709.png rename docs/cce/umn/{en-us_image_0000002253780329.png => en-us_image_0000002467718757.png} (100%) rename docs/cce/umn/{en-us_image_0000002253780209.png => en-us_image_0000002467718781.png} (100%) rename docs/cce/umn/{en-us_image_0000002218659822.png => en-us_image_0000002467718921.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467718941.png rename docs/cce/umn/{en-us_image_0000002253619517.png => en-us_image_0000002467718953.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467719021.png create mode 100644 docs/cce/umn/en-us_image_0000002467719025.png create mode 100644 docs/cce/umn/en-us_image_0000002467719029.png create mode 100644 docs/cce/umn/en-us_image_0000002467719033.png create mode 100644 docs/cce/umn/en-us_image_0000002467719037.png create mode 100644 docs/cce/umn/en-us_image_0000002467719041.png create mode 100644 docs/cce/umn/en-us_image_0000002467719053.png create mode 100644 docs/cce/umn/en-us_image_0000002467719057.png rename docs/cce/umn/{en-us_image_0000002253779657.png => en-us_image_0000002467719105.png} (100%) rename docs/cce/umn/{en-us_image_0000002218819854.png => en-us_image_0000002467719125.png} (100%) rename docs/cce/umn/{en-us_image_0000002253619725.png => en-us_image_0000002467719133.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467719141.png rename docs/cce/umn/{en-us_image_0000002253619981.png => en-us_image_0000002467719233.png} (100%) rename docs/cce/umn/{en-us_image_0000002253779505.png => en-us_image_0000002467719245.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467719381.png create mode 100644 docs/cce/umn/en-us_image_0000002467719393.png rename docs/cce/umn/{en-us_image_0000002253779681.png => en-us_image_0000002467719409.png} (100%) rename docs/cce/umn/{en-us_image_0000002253620349.png => en-us_image_0000002467719473.png} (100%) rename docs/cce/umn/{en-us_image_0000002253780305.png => en-us_image_0000002467719549.png} (100%) rename docs/cce/umn/{en-us_image_0000002218820226.png => en-us_image_0000002467719573.png} (100%) rename docs/cce/umn/{en-us_image_0000002274473989.png => en-us_image_0000002467719689.png} (100%) create mode 100644 docs/cce/umn/en-us_image_0000002467719741.png delete mode 100644 docs/cce/umn/en-us_image_0258894622.png diff --git a/docs/cce/umn/ALL_META.TXT.json b/docs/cce/umn/ALL_META.TXT.json index a55f31336..076f195d6 100644 --- a/docs/cce/umn/ALL_META.TXT.json +++ b/docs/cce/umn/ALL_META.TXT.json @@ -45,9 +45,9 @@ "node_id":"cce_productdesc_0003.xml", "product_code":"cce", "code":"3", - "des":"CCE is a container service developed on Docker and Kubernetes. It offers a wide range of features that allow you to run containers on a large scale. CCE containers are hi", + "des":"CCE is a container service developed on Docker and Kubernetes. It offers a wide range of features that allow you to run containers in large clusters. CCE containers are h", "doc_type":"usermanual2", - "kw":"Product Advantages,Service Overview,User Guide", + "kw":"Docker,CCE Advantages,Service Overview,User Guide", "search_title":"", "metedata":[ { @@ -55,7 +55,7 @@ "documenttype":"usermanual" } ], - "title":"Product Advantages", + "title":"CCE Advantages", "githuburl":"" }, { @@ -135,9 +135,9 @@ "node_id":"cce_productdesc_0018.xml", "product_code":"cce", "code":"8", - "des":"Multi-cloud deployment and disaster recoveryTo ensure high service availability, services need to be deployed on container services of multiple clouds. When a cloud is fa", + "des":"Multi-cloud deployment, DR, and backupTo ensure high service availability, services need to be deployed on container services of multiple clouds. When a cloud is faulty, ", "doc_type":"usermanual2", - "kw":"Hybrid Cloud,Application Scenarios,User Guide", + "kw":"Hybrid Clouds,Application Scenarios,User Guide", "search_title":"", "metedata":[ { @@ -145,7 +145,7 @@ "documenttype":"usermanual" } ], - "title":"Hybrid Cloud", + "title":"Hybrid Clouds", "githuburl":"" }, { @@ -191,7 +191,7 @@ "code":"11", "des":"CCE needs to be interconnected with the following cloud services. It requires permissions to access these cloud services.", "doc_type":"usermanual2", - "kw":"ECS,VPC,ELB,SWR,EVS,OBS,cloud storage for data of any size,SFS,AOM,Related Services,Service Overview", + "kw":"VPC,ELB,SWR,EVS,OBS,cloud storage for data of any size,SFS,AOM,Related Services,Service Overview,Use", "search_title":"", "metedata":[ { @@ -608,11 +608,29 @@ "title":"Kubernetes Version Release Notes", "githuburl":"" }, + { + "uri":"cce_bulletin_0104.html", + "node_id":"cce_bulletin_0104.xml", + "product_code":"cce", + "code":"34", + "des":"CCE allows you to create Kubernetes 1.32 clusters. This section describes the changes made in Kubernetes 1.32.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku", + "doc_type":"usermanual2", + "kw":"Kubernetes 1.32 Release Notes,Kubernetes Version Release Notes,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Kubernetes 1.32 Release Notes", + "githuburl":"" + }, { "uri":"cce_bulletin_0099.html", "node_id":"cce_bulletin_0099.xml", "product_code":"cce", - "code":"34", + "code":"35", "des":"CCE allows you to create Kubernetes 1.31 clusters. This section describes the changes made in Kubernetes 1.31.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku", "doc_type":"usermanual2", "kw":"Kubernetes 1.31 Release Notes,Kubernetes Version Release Notes,User Guide", @@ -630,7 +648,7 @@ "uri":"cce_bulletin_0095.html", "node_id":"cce_bulletin_0095.xml", "product_code":"cce", - "code":"35", + "code":"36", "des":"CCE allows you to create Kubernetes 1.30 clusters. This section describes the changes made in Kubernetes 1.30.New and Enhanced FeaturesAPI Changes and RemovalsEnhanced Ku", "doc_type":"usermanual2", "kw":"Kubernetes 1.30 Release Notes,Kubernetes Version Release Notes,User Guide", @@ -648,7 +666,7 @@ "uri":"cce_bulletin_0089.html", "node_id":"cce_bulletin_0089.xml", "product_code":"cce", - "code":"36", + "code":"37", "des":"CCE allows you to create Kubernetes 1.29 clusters. This section describes the changes made in Kubernetes 1.29.New and Enhanced FeaturesAPI Changes and RemovalsIncompatibl", "doc_type":"usermanual2", "kw":"Kubernetes 1.29 Release Notes,Kubernetes Version Release Notes,User Guide", @@ -666,7 +684,7 @@ "uri":"cce_bulletin_0068.html", "node_id":"cce_bulletin_0068.xml", "product_code":"cce", - "code":"37", + "code":"38", "des":"CCE allows you to create Kubernetes 1.28 clusters. 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", @@ -684,7 +702,7 @@ "uri":"cce_bulletin_0059.html", "node_id":"cce_bulletin_0059.xml", "product_code":"cce", - "code":"38", + "code":"39", "des":"CCE allows you to create Kubernetes 1.27 clusters. This section describes the changes made in Kubernetes 1.27 compared with Kubernetes 1.25.New FeaturesDeprecations and R", "doc_type":"usermanual2", "kw":"Kubernetes 1.27 Release Notes,Kubernetes Version Release Notes,User Guide", @@ -702,10 +720,10 @@ "uri":"cce_bulletin_0058.html", "node_id":"cce_bulletin_0058.xml", "product_code":"cce", - "code":"39", + "code":"40", "des":"This section describes the changes made in Kubernetes 1.25 compared with Kubernetes 1.23.New FeaturesDeprecations and RemovalsEnhanced Kubernetes 1.25 on CCEReferencesKub", "doc_type":"usermanual2", - "kw":"Kubernetes 1.25 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide", + "kw":"Kubernetes 1.25 Release Notes,Kubernetes Version Release Notes,User Guide", "search_title":"", "metedata":[ { @@ -713,14 +731,14 @@ "documenttype":"usermanual" } ], - "title":"Kubernetes 1.25 (EOM) Release Notes", + "title":"Kubernetes 1.25 Release Notes", "githuburl":"" }, { "uri":"cce_bulletin_0027.html", "node_id":"cce_bulletin_0027.xml", "product_code":"cce", - "code":"40", + "code":"41", "des":"This section describes the updates in CCE Kubernetes 1.23.Kubernetes v1.23 Release NotesFlexVolume is deprecated. Use CSI.HorizontalPodAutoscaler v2 is promoted to GA, an", "doc_type":"usermanual2", "kw":"Kubernetes 1.23 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide", @@ -738,7 +756,7 @@ "uri":"cce_bulletin_0026.html", "node_id":"cce_bulletin_0026.xml", "product_code":"cce", - "code":"41", + "code":"42", "des":"This section describes the updates in CCE Kubernetes 1.21.Kubernetes v1.21 Release NotesCronJob is now in the stable state, and the version number changes to batch/v1.The", "doc_type":"usermanual2", "kw":"Kubernetes 1.21 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide", @@ -756,7 +774,7 @@ "uri":"cce_whsnew_0010.html", "node_id":"cce_whsnew_0010.xml", "product_code":"cce", - "code":"42", + "code":"43", "des":"This section describes the updates in CCE Kubernetes 1.19.Kubernetes v1.19 Release NotesvSphere in-tree volumes can be migrated to vSphere CSI drivers. The in-tree vSpher", "doc_type":"usermanual2", "kw":"Kubernetes 1.19 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide", @@ -774,7 +792,7 @@ "uri":"cce_whsnew_0007.html", "node_id":"cce_whsnew_0007.xml", "product_code":"cce", - "code":"43", + "code":"44", "des":"This section describes the updates in CCE Kubernetes 1.17.All resources in the apps/v1beta1 and apps/v1beta2 API versions are no longer served. Migrate to use the apps/v1", "doc_type":"usermanual2", "kw":"Kubernetes 1.17 (EOM) Release Notes,Kubernetes Version Release Notes,User Guide", @@ -792,7 +810,7 @@ "uri":"cce_10_0405.html", "node_id":"cce_10_0405.xml", "product_code":"cce", - "code":"44", + "code":"45", "des":"In CCE clusters of v1.25, containerd is the default runtime for nodes, except for nodes running EulerOS 2.5. In addition, clusters of v1.25 or later no longer support Eul", "doc_type":"usermanual2", "kw":"Patch Version Release Notes,Cluster Version Release Notes,User Guide", @@ -810,7 +828,7 @@ "uri":"cce_10_0298.html", "node_id":"cce_10_0298.xml", "product_code":"cce", - "code":"45", + "code":"46", "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 Cluster", @@ -828,7 +846,7 @@ "uri":"cce_10_0342.html", "node_id":"cce_10_0342.xml", "product_code":"cce", - "code":"46", + "code":"47", "des":"CCE provides different types of clusters for you to select. The following table lists the differences between them.", "doc_type":"usermanual2", "kw":"Comparison Between Cluster Types,Creating a Cluster,User Guide", @@ -846,8 +864,8 @@ "uri":"cce_10_0028.html", "node_id":"cce_10_0028.xml", "product_code":"cce", - "code":"47", - "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", + "code":"48", + "des":"CCE standard and Turbo clusters provide enterprise-class Kubernetes cluster hosting service that supports full lifecycle management of containerized applications. They of", "doc_type":"usermanual2", "kw":"Creating a CCE Standard/Turbo Cluster,Creating a Cluster,User Guide", "search_title":"", @@ -864,7 +882,7 @@ "uri":"cce_10_0349.html", "node_id":"cce_10_0349.xml", "product_code":"cce", - "code":"48", + "code":"49", "des":"kube-proxy is a key component of a Kubernetes cluster. It is used for load balancing and forwarding data between a Service and its backend pods.CCE supports the iptables ", "doc_type":"usermanual2", "kw":"kube-proxy,iptables,IP Virtual Server (IPVS),forwarding modes,Comparing iptables and IPVS,Creating a", @@ -882,10 +900,10 @@ "uri":"cce_10_0140.html", "node_id":"cce_10_0140.xml", "product_code":"cce", - "code":"49", + "code":"50", "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":"Connecting to a Cluster", + "kw":"Accessing a Cluster", "search_title":"", "metedata":[ { @@ -893,17 +911,35 @@ "documenttype":"usermanual" } ], - "title":"Connecting to a Cluster", + "title":"Accessing a Cluster", + "githuburl":"" + }, + { + "uri":"cce_10_0961.html", + "node_id":"cce_10_0961.xml", + "product_code":"cce", + "code":"51", + "des":"Accessing a cluster involves establishing communication with it and executing cluster management tasks. A CCE cluster is a distributed system consisting of multiple nodes", + "doc_type":"usermanual2", + "kw":"Cluster Access Overview,Accessing a Cluster,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Cluster Access Overview", "githuburl":"" }, { "uri":"cce_10_0107.html", "node_id":"cce_10_0107.xml", "product_code":"cce", - "code":"50", + "code":"52", "des":"kubectl is a command-line tool provided by Kubernetes, enabling you to manage cluster resources, view cluster status, deploy applications, and debug issues through the CL", "doc_type":"usermanual2", - "kw":"Intranet access,Internet access,kubectl,intranet access,Internet access,Two-Way Authentication for D", + "kw":"Intranet access,Internet access,kubectl,intranet access,Internet access,Two-Way Domain Name Trust,Er", "search_title":"", "metedata":[ { @@ -918,10 +954,10 @@ "uri":"cce_10_0175.html", "node_id":"cce_10_0175.xml", "product_code":"cce", - "code":"51", + "code":"53", "des":"X.509 certificates are essential for verifying identities and encrypting communication within CCE clusters. These certificates enable authorized clients to access target ", "doc_type":"usermanual2", - "kw":"X.509 certificate,Accessing a Cluster Using an X.509 Certificate,Connecting to a Cluster,User Guide", + "kw":"X.509 certificate,Accessing a Cluster Using an X.509 Certificate,Accessing a Cluster,User Guide", "search_title":"", "metedata":[ { @@ -936,10 +972,10 @@ "uri":"cce_10_0367.html", "node_id":"cce_10_0367.xml", "product_code":"cce", - "code":"52", + "code":"54", "des":"Subject Alternative Name (SAN) enables certificates to be associated with multiple values, including IP addresses and domain names. A SAN is usually used by the client to", "doc_type":"usermanual2", - "kw":"SAN,X.509 certificate,Accessing a Cluster Using a Custom Domain Name,Connecting to a Cluster,User Gu", + "kw":"SAN,X.509 certificate,Accessing a Cluster Using a Custom Domain Name,Accessing a Cluster,User Guide", "search_title":"", "metedata":[ { @@ -954,10 +990,10 @@ "uri":"cce_10_0864.html", "node_id":"cce_10_0864.xml", "product_code":"cce", - "code":"53", + "code":"55", "des":"You can bind an EIP to an API server of a Kubernetes cluster so that the API server can access the Internet.Binding an EIP to an API server for Internet access can pose a", "doc_type":"usermanual2", - "kw":"Configuring a Cluster's API Server for Internet Access,Connecting to a Cluster,User Guide", + "kw":"Configuring a Cluster's API Server for Internet Access,Accessing a Cluster,User Guide", "search_title":"", "metedata":[ { @@ -972,10 +1008,10 @@ "uri":"cce_10_0744.html", "node_id":"cce_10_0744.xml", "product_code":"cce", - "code":"54", + "code":"56", "des":"In multi-tenant scenarios, CCE generates a unique credential (such as a kubeconfig file or an X.509 certificate) for each user to access their designated cluster. These c", "doc_type":"usermanual2", - "kw":"Revoking a Cluster Access Credential,Connecting to a Cluster,User Guide", + "kw":"Revoking a Cluster Access Credential,Accessing a Cluster,User Guide", "search_title":"", "metedata":[ { @@ -990,10 +1026,10 @@ "uri":"cce_10_0031.html", "node_id":"cce_10_0031.xml", "product_code":"cce", - "code":"55", + "code":"57", "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", + "kw":"Managing Clusters", "search_title":"", "metedata":[ { @@ -1001,17 +1037,35 @@ "documenttype":"usermanual" } ], - "title":"Managing a Cluster", + "title":"Managing Clusters", + "githuburl":"" + }, + { + "uri":"cce_10_0962.html", + "node_id":"cce_10_0962.xml", + "product_code":"cce", + "code":"58", + "des":"Efficient, stable operation of containerized applications relies on proper management of CCE standard or Turbo clusters. CCE standard and Turbo clusters offer comprehensi", + "doc_type":"usermanual2", + "kw":"Cluster configuration parameters,change,Cluster Management Overview,Managing Clusters,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Cluster Management Overview", "githuburl":"" }, { "uri":"cce_10_0213.html", "node_id":"cce_10_0213.xml", "product_code":"cce", - "code":"56", + "code":"59", "des":"Cluster configuration parameters are underlying rules that define node behavior, resource allocation, communication rules, and scaling policies in a distributed system. T", "doc_type":"usermanual2", - "kw":"Cluster configuration parameters,cluster configuration parameters,Cluster configuration parameters,C", + "kw":"Cluster configuration parameters,cluster configuration parameters,Cluster configuration parameters,k", "search_title":"", "metedata":[ { @@ -1026,10 +1080,10 @@ "uri":"cce_10_0602.html", "node_id":"cce_10_0602.xml", "product_code":"cce", - "code":"57", + "code":"60", "des":"Cluster overload occurs when system load such as request volume or resource usage exceeds the system's processing capacity, leading to degraded performance or system fail", "doc_type":"usermanual2", - "kw":"Enabling Overload Control for a Cluster,Managing a Cluster,User Guide", + "kw":"Enabling Overload Control for a Cluster,Managing Clusters,User Guide", "search_title":"", "metedata":[ { @@ -1044,10 +1098,10 @@ "uri":"cce_10_0403.html", "node_id":"cce_10_0403.xml", "product_code":"cce", - "code":"58", + "code":"61", "des":"A cluster scale specifies the maximum number of nodes a cluster can manage. If the current cluster scale cannot meet your requirements, you can scale it out.A cluster tha", "doc_type":"usermanual2", - "kw":"scale it out,Changing a Cluster Scale,Managing a Cluster,User Guide", + "kw":"scale it out,Changing a Cluster Scale,Managing Clusters,User Guide", "search_title":"", "metedata":[ { @@ -1062,10 +1116,10 @@ "uri":"cce_10_0426.html", "node_id":"cce_10_0426.xml", "product_code":"cce", - "code":"59", + "code":"62", "des":"When creating a cluster, you can customize a node security group to centrally manage network security policies. For a created cluster, you can change its default node sec", "doc_type":"usermanual2", - "kw":"Changing the Default Security Group of a Node,Managing a Cluster,User Guide", + "kw":"Changing the Default Security Group of a Node,Managing Clusters,User Guide", "search_title":"", "metedata":[ { @@ -1080,10 +1134,10 @@ "uri":"cce_10_0212.html", "node_id":"cce_10_0212.xml", "product_code":"cce", - "code":"60", + "code":"63", "des":"Deleting a cluster will delete the workloads and Services in the cluster, and the deleted data cannot be recovered. Before performing this operation, ensure that related ", "doc_type":"usermanual2", - "kw":"Deleting a Cluster,Managing a Cluster,User Guide", + "kw":"Deleting a Cluster,Managing Clusters,User Guide", "search_title":"", "metedata":[ { @@ -1098,10 +1152,10 @@ "uri":"cce_10_0927.html", "node_id":"cce_10_0927.xml", "product_code":"cce", - "code":"61", + "code":"64", "des":"Unexpected deletion of clusters can occur in practice, especially when multiple users share an account and accidentally delete clusters that do not belong to them. To pre", "doc_type":"usermanual2", - "kw":"Preventing Cluster Deletion,Managing a Cluster,User Guide", + "kw":"Preventing Cluster Deletion,Managing Clusters,User Guide", "search_title":"", "metedata":[ { @@ -1116,10 +1170,10 @@ "uri":"cce_10_0214.html", "node_id":"cce_10_0214.xml", "product_code":"cce", - "code":"62", + "code":"65", "des":"If a cluster is not needed temporarily, hibernate it to reduce costs.After a cluster is hibernated, resources such as workloads cannot be created or managed in the cluste", "doc_type":"usermanual2", - "kw":"Hibernating or Waking Up a Cluster,Managing a Cluster,User Guide", + "kw":"Hibernating or Waking Up a Cluster,Managing Clusters,User Guide", "search_title":"", "metedata":[ { @@ -1134,7 +1188,7 @@ "uri":"cce_10_0215.html", "node_id":"cce_10_0215.xml", "product_code":"cce", - "code":"63", + "code":"66", "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":"Upgrading a Cluster", @@ -1152,7 +1206,7 @@ "uri":"cce_10_0197.html", "node_id":"cce_10_0197.xml", "product_code":"cce", - "code":"64", + "code":"67", "des":"CCE strictly complies with community consistency authentication. It releases three Kubernetes versions each year and offers a maintenance period of at least 24 months aft", "doc_type":"usermanual2", "kw":"cluster upgrade process,Node Priority,In-place upgrade,Cluster Upgrade Overview,Upgrading a Cluster,", @@ -1170,7 +1224,7 @@ "uri":"cce_10_0302.html", "node_id":"cce_10_0302.xml", "product_code":"cce", - "code":"65", + "code":"68", "des":"Before the upgrade, you can check whether your cluster can be upgraded and which versions are available on the CCE console. For details, see Cluster Upgrade Overview.Befo", "doc_type":"usermanual2", "kw":"Deprecated APIs,Before You Start,Upgrading a Cluster,User Guide", @@ -1188,7 +1242,7 @@ "uri":"cce_10_0560.html", "node_id":"cce_10_0560.xml", "product_code":"cce", - "code":"66", + "code":"69", "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", @@ -1206,7 +1260,7 @@ "uri":"cce_10_0568.html", "node_id":"cce_10_0568.xml", "product_code":"cce", - "code":"67", + "code":"70", "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", @@ -1224,7 +1278,7 @@ "uri":"cce_10_0569.html", "node_id":"cce_10_0569.xml", "product_code":"cce", - "code":"68", + "code":"71", "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", @@ -1242,7 +1296,7 @@ "uri":"cce_10_0567.html", "node_id":"cce_10_0567.xml", "product_code":"cce", - "code":"69", + "code":"72", "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", @@ -1260,7 +1314,7 @@ "uri":"cce_10_0561.html", "node_id":"cce_10_0561.xml", "product_code":"cce", - "code":"70", + "code":"73", "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", @@ -1278,7 +1332,7 @@ "uri":"cce_10_0565.html", "node_id":"cce_10_0565.xml", "product_code":"cce", - "code":"71", + "code":"74", "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", @@ -1296,7 +1350,7 @@ "uri":"cce_10_0566.html", "node_id":"cce_10_0566.xml", "product_code":"cce", - "code":"72", + "code":"75", "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", @@ -1314,7 +1368,7 @@ "uri":"cce_10_0210.html", "node_id":"cce_10_0210.xml", "product_code":"cce", - "code":"73", + "code":"76", "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", @@ -1332,7 +1386,7 @@ "uri":"cce_10_0550.html", "node_id":"cce_10_0550.xml", "product_code":"cce", - "code":"74", + "code":"77", "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", @@ -1350,7 +1404,7 @@ "uri":"cce_10_0549.html", "node_id":"cce_10_0549.xml", "product_code":"cce", - "code":"75", + "code":"78", "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", @@ -1368,7 +1422,7 @@ "uri":"cce_10_0431.html", "node_id":"cce_10_0431.xml", "product_code":"cce", - "code":"76", + "code":"79", "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", @@ -1386,7 +1440,7 @@ "uri":"cce_10_0432.html", "node_id":"cce_10_0432.xml", "product_code":"cce", - "code":"77", + "code":"80", "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", @@ -1404,7 +1458,7 @@ "uri":"cce_10_0433.html", "node_id":"cce_10_0433.xml", "product_code":"cce", - "code":"78", + "code":"81", "des":"Check the following items:Check whether the add-on status is normal.Check whether the add-on supports 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", @@ -1422,7 +1476,7 @@ "uri":"cce_10_0434.html", "node_id":"cce_10_0434.xml", "product_code":"cce", - "code":"79", + "code":"82", "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", @@ -1440,7 +1494,7 @@ "uri":"cce_10_0435.html", "node_id":"cce_10_0435.xml", "product_code":"cce", - "code":"80", + "code":"83", "des":"Check whether your master nodes can be accessed using SSH.There is a low probability that the SSH connectivity check fails due to network fluctuations. Perform the pre-up", "doc_type":"usermanual2", "kw":"SSH Connectivity of Master Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1458,7 +1512,7 @@ "uri":"cce_10_0436.html", "node_id":"cce_10_0436.xml", "product_code":"cce", - "code":"81", + "code":"84", "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", @@ -1476,7 +1530,7 @@ "uri":"cce_10_0437.html", "node_id":"cce_10_0437.xml", "product_code":"cce", - "code":"82", + "code":"85", "des":"Check whether the Protocol & Port of the worker node security groups is set to ICMP: All and whether the security group rule with the source IP address set to the master ", "doc_type":"usermanual2", "kw":"Security Groups,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1494,7 +1548,7 @@ "uri":"cce_10_0439.html", "node_id":"cce_10_0439.xml", "product_code":"cce", - "code":"83", + "code":"86", "des":"Check whether nodes need to be migrated.This issue is caused by either an error in the node's package pull component or the absence of key system components on the node, ", "doc_type":"usermanual2", "kw":"Residual Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1512,8 +1566,8 @@ "uri":"cce_10_0440.html", "node_id":"cce_10_0440.xml", "product_code":"cce", - "code":"84", - "des":"Check whether there are discarded resources in the clusters.Scenario 1: The Service in the clusters of v1.25 or later has discarded annotation tolerate-unready-endpoints.", + "code":"87", + "des":"Check whether there are discarded resources in the clusters.Scenario 1: The Service in the clusters of v1.25 or later has deprecated annotation tolerate-unready-endpoints", "doc_type":"usermanual2", "kw":"Discarded Kubernetes Resources,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -1530,7 +1584,7 @@ "uri":"cce_10_0441.html", "node_id":"cce_10_0441.xml", "product_code":"cce", - "code":"85", + "code":"88", "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", @@ -1548,7 +1602,7 @@ "uri":"cce_10_0442.html", "node_id":"cce_10_0442.xml", "product_code":"cce", - "code":"86", + "code":"89", "des":"Check whether cce-agent on the current node is of the latest version.Scenario 1: The error message \"you cce-agent no update, please restart it\" is displayed.This issue oc", "doc_type":"usermanual2", "kw":"CCE Agent Versions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1566,7 +1620,7 @@ "uri":"cce_10_0443.html", "node_id":"cce_10_0443.xml", "product_code":"cce", - "code":"87", + "code":"90", "des":"Check whether the node's CPU usage is above 90%.Upgrade the cluster during off-peak hours.Check whether too many pods are deployed on the node. If yes, reschedule pods to", "doc_type":"usermanual2", "kw":"Node CPU Usage,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1584,7 +1638,7 @@ "uri":"cce_10_0444.html", "node_id":"cce_10_0444.xml", "product_code":"cce", - "code":"88", + "code":"91", "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", @@ -1602,8 +1656,8 @@ "uri":"cce_10_0445.html", "node_id":"cce_10_0445.xml", "product_code":"cce", - "code":"89", - "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", + "code":"92", + "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 of available space.During", "doc_type":"usermanual2", "kw":"Node Disks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -1620,7 +1674,7 @@ "uri":"cce_10_0446.html", "node_id":"cce_10_0446.xml", "product_code":"cce", - "code":"90", + "code":"93", "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", @@ -1638,8 +1692,8 @@ "uri":"cce_10_0447.html", "node_id":"cce_10_0447.xml", "product_code":"cce", - "code":"91", - "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", + "code":"94", + "des":"Check whether the root directory permissions are properly assigned.Scenario 1: The error message \"user paas must have at least read and execute permissions on the root di", "doc_type":"usermanual2", "kw":"Node Key Directory File Permissions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -1656,8 +1710,8 @@ "uri":"cce_10_0448.html", "node_id":"cce_10_0448.xml", "product_code":"cce", - "code":"92", - "des":"Check whether the kubelet on the node is running properly.Scenario 1: The kubelet status is abnormal.If the kubelet malfunctions, the node will be unavailable. Restore th", + "code":"95", + "des":"Check whether the kubelet on the node is running properly.Scenario: The kubelet status is abnormal.If the kubelet malfunctions, the node will be unavailable. Restore the ", "doc_type":"usermanual2", "kw":"kubelet,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -1674,8 +1728,8 @@ "uri":"cce_10_0449.html", "node_id":"cce_10_0449.xml", "product_code":"cce", - "code":"93", - "des":"Check whether the node's memory usage is above 90%.Upgrade the cluster during off-peak hours.Check whether too many pods are deployed on the node. If yes, reschedule pods", + "code":"96", + "des":"Check whether the node's memory usage is above 90%.Upgrade the cluster during off-peak hours.Log in to the node, run the top command to obtain the memory usage of the pro", "doc_type":"usermanual2", "kw":"Node Memory,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -1692,7 +1746,7 @@ "uri":"cce_10_0450.html", "node_id":"cce_10_0450.xml", "product_code":"cce", - "code":"94", + "code":"97", "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", @@ -1710,7 +1764,7 @@ "uri":"cce_10_0451.html", "node_id":"cce_10_0451.xml", "product_code":"cce", - "code":"95", + "code":"98", "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", @@ -1728,7 +1782,7 @@ "uri":"cce_10_0452.html", "node_id":"cce_10_0452.xml", "product_code":"cce", - "code":"96", + "code":"99", "des":"Verify that the master nodes in your cluster have more than 2 CPU cores.The master nodes have only 2 CPU cores, which may lead to a cluster upgrade failure.Contact techni", "doc_type":"usermanual2", "kw":"Node CPU Cores,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1746,7 +1800,7 @@ "uri":"cce_10_0453.html", "node_id":"cce_10_0453.xml", "product_code":"cce", - "code":"97", + "code":"100", "des":"Check whether the Python commands are available on a node.If the command output is not 0, the check fails.Reset the node or manually install Python before attempting the ", "doc_type":"usermanual2", "kw":"Node Python Commands,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1764,7 +1818,7 @@ "uri":"cce_10_0455.html", "node_id":"cce_10_0455.xml", "product_code":"cce", - "code":"98", + "code":"101", "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", @@ -1782,7 +1836,7 @@ "uri":"cce_10_0456.html", "node_id":"cce_10_0456.xml", "product_code":"cce", - "code":"99", + "code":"102", "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", @@ -1800,7 +1854,7 @@ "uri":"cce_10_0457.html", "node_id":"cce_10_0457.xml", "product_code":"cce", - "code":"100", + "code":"103", "des":"Check whether the containerd.sock file is on the node. This file affects the startup of container runtime in the Euler OS.Scenario: The Docker used by the node is the cus", "doc_type":"usermanual2", "kw":"containerd.sock,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1818,7 +1872,7 @@ "uri":"cce_10_0458.html", "node_id":"cce_10_0458.xml", "product_code":"cce", - "code":"101", + "code":"104", "des":"This check item is not typical and implies that an internal error was found during the pre-upgrade check.Perform the pre-upgrade check again.If it fails again, submit a s", "doc_type":"usermanual2", "kw":"Internal Error,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1836,7 +1890,7 @@ "uri":"cce_10_0459.html", "node_id":"cce_10_0459.xml", "product_code":"cce", - "code":"102", + "code":"105", "des":"Check whether there are inaccessible mount points on the node.Scenario: There are inaccessible mount points on the node.If NFS (such as obsfs or SFS) is used by the node ", "doc_type":"usermanual2", "kw":"Node Mount Points,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1854,7 +1908,7 @@ "uri":"cce_10_0460.html", "node_id":"cce_10_0460.xml", "product_code":"cce", - "code":"103", + "code":"106", "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", @@ -1872,7 +1926,7 @@ "uri":"cce_10_0478.html", "node_id":"cce_10_0478.xml", "product_code":"cce", - "code":"104", + "code":"107", "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", @@ -1890,7 +1944,7 @@ "uri":"cce_10_0479.html", "node_id":"cce_10_0479.xml", "product_code":"cce", - "code":"105", + "code":"108", "des":"Check whether there are compatibility limitations between the current and target cce-controller-hpa add-on versions.There are compatibility limitations between the curren", "doc_type":"usermanual2", "kw":"cce-hpa-controller Limitations,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1908,7 +1962,7 @@ "uri":"cce_10_0480.html", "node_id":"cce_10_0480.xml", "product_code":"cce", - "code":"106", + "code":"109", "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", @@ -1926,7 +1980,7 @@ "uri":"cce_10_0484.html", "node_id":"cce_10_0484.xml", "product_code":"cce", - "code":"107", + "code":"110", "des":"Check whether the container runtime and network components on the worker nodes are healthy.Issue 1: CNI Agent is not active.If your cluster version is earlier than v1.17.", "doc_type":"usermanual2", "kw":"Health of Worker Node Components,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1944,7 +1998,7 @@ "uri":"cce_10_0485.html", "node_id":"cce_10_0485.xml", "product_code":"cce", - "code":"108", + "code":"111", "des":"Check whether cluster components such as the Kubernetes component, container runtime component, and network component are running properly before the upgrade.Perform the ", "doc_type":"usermanual2", "kw":"Health of Master Node Components,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -1962,7 +2016,7 @@ "uri":"cce_10_0486.html", "node_id":"cce_10_0486.xml", "product_code":"cce", - "code":"109", + "code":"112", "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", @@ -1980,7 +2034,7 @@ "uri":"cce_10_0487.html", "node_id":"cce_10_0487.xml", "product_code":"cce", - "code":"110", + "code":"113", "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", @@ -1998,7 +2052,7 @@ "uri":"cce_10_0488.html", "node_id":"cce_10_0488.xml", "product_code":"cce", - "code":"111", + "code":"114", "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 Support in CCE Turbo Clusters,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2016,7 +2070,7 @@ "uri":"cce_10_0489.html", "node_id":"cce_10_0489.xml", "product_code":"cce", - "code":"112", + "code":"115", "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":"NetworkManager,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2034,7 +2088,7 @@ "uri":"cce_10_0490.html", "node_id":"cce_10_0490.xml", "product_code":"cce", - "code":"113", + "code":"116", "des":"Check the ID file format.", "doc_type":"usermanual2", "kw":"Node ID File,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2052,8 +2106,8 @@ "uri":"cce_10_0491.html", "node_id":"cce_10_0491.xml", "product_code":"cce", - "code":"114", - "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", + "code":"117", + "des":"When you upgrade a cluster to v1.19 or later, CCE checks whether the following configuration files have been modified on the backend:/opt/cloud/cce/kubernetes/kubelet/kub", "doc_type":"usermanual2", "kw":"Node Configuration Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -2070,7 +2124,7 @@ "uri":"cce_10_0492.html", "node_id":"cce_10_0492.xml", "product_code":"cce", - "code":"115", + "code":"118", "des":"Check whether the configuration files of key components exist on the node.The following table lists the files to be checked.Reset the node. For details, see Resetting a N", "doc_type":"usermanual2", "kw":"Node Configuration File,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2088,7 +2142,7 @@ "uri":"cce_10_0493.html", "node_id":"cce_10_0493.xml", "product_code":"cce", - "code":"116", + "code":"119", "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", @@ -2106,7 +2160,7 @@ "uri":"cce_10_0494.html", "node_id":"cce_10_0494.xml", "product_code":"cce", - "code":"117", + "code":"120", "des":"Check whether the sudo commands and sudo-related files of the node are working.Scenario 1: The sudo command fails to be executed.During the in-place cluster upgrade, the ", "doc_type":"usermanual2", "kw":"sudo,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2124,8 +2178,8 @@ "uri":"cce_10_0495.html", "node_id":"cce_10_0495.xml", "product_code":"cce", - "code":"118", - "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", + "code":"121", + "des":"Whether some key commands that the node upgrade depends on are workingScenario 1: The RPM package manager command fails to be executed.The rpm command fails to be execute", "doc_type":"usermanual2", "kw":"Key Node Commands,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -2142,7 +2196,7 @@ "uri":"cce_10_0496.html", "node_id":"cce_10_0496.xml", "product_code":"cce", - "code":"119", + "code":"122", "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", @@ -2160,7 +2214,7 @@ "uri":"cce_10_0497.html", "node_id":"cce_10_0497.xml", "product_code":"cce", - "code":"120", + "code":"123", "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", @@ -2178,8 +2232,8 @@ "uri":"cce_10_0498.html", "node_id":"cce_10_0498.xml", "product_code":"cce", - "code":"121", - "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", + "code":"124", + "des":"This section describes how to diagnose and fix node-mount failures caused by CCE storage misconfigurations.Check item 1: mount point conflictsCheck ContentVerify that all", "doc_type":"usermanual2", "kw":"Node Mounting,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -2196,7 +2250,7 @@ "uri":"cce_10_0499.html", "node_id":"cce_10_0499.xml", "product_code":"cce", - "code":"122", + "code":"125", "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", @@ -2214,7 +2268,7 @@ "uri":"cce_10_0500.html", "node_id":"cce_10_0500.xml", "product_code":"cce", - "code":"123", + "code":"126", "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,7 +2286,7 @@ "uri":"cce_10_0501.html", "node_id":"cce_10_0501.xml", "product_code":"cce", - "code":"124", + "code":"127", "des":"Check the historical upgrade records of the cluster and confirm that the current version of the cluster meets the requirements for upgrading to the target version.Upgradi", "doc_type":"usermanual2", "kw":"Historical Upgrade Records,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2250,7 +2304,7 @@ "uri":"cce_10_0502.html", "node_id":"cce_10_0502.xml", "product_code":"cce", - "code":"125", + "code":"128", "des":"Check whether the CIDR block of the cluster management plane is the same as that configured on the backbone network.The CIDR block of the management plane has been modifi", "doc_type":"usermanual2", "kw":"CIDR Block of the Cluster Management Plane,Troubleshooting for Pre-upgrade Check Exceptions,User Gui", @@ -2268,10 +2322,10 @@ "uri":"cce_10_0503.html", "node_id":"cce_10_0503.xml", "product_code":"cce", - "code":"126", - "des":"CCE AI Suite (NVIDIA GPU) is involved in the upgrade, which may affect the GPU driver installation during the creation of a GPU node.The driver of CCE AI Suite (NVIDIA GP", + "code":"129", + "des":"Check whether CCE AI Suite (NVIDIA GPU) involved in the upgrade affects the GPU driver installation when creating a GPU node.The driver of CCE AI Suite (NVIDIA GPU) needs", "doc_type":"usermanual2", - "kw":"CCE AI Suite (NVIDIA GPU),Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "kw":"CCE AI Suite (NVIDIA GPU) Exceptions,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", "metedata":[ { @@ -2279,14 +2333,14 @@ "documenttype":"usermanual" } ], - "title":"CCE AI Suite (NVIDIA GPU)", + "title":"CCE AI Suite (NVIDIA GPU) Exceptions", "githuburl":"" }, { "uri":"cce_10_0504.html", "node_id":"cce_10_0504.xml", "product_code":"cce", - "code":"127", + "code":"130", "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 Parameters,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2304,8 +2358,8 @@ "uri":"cce_10_0505.html", "node_id":"cce_10_0505.xml", "product_code":"cce", - "code":"128", - "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", + "code":"131", + "des":"Check whether there is 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 cl", "doc_type":"usermanual2", "kw":"Residual Package Version Data,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -2322,7 +2376,7 @@ "uri":"cce_10_0506.html", "node_id":"cce_10_0506.xml", "product_code":"cce", - "code":"129", + "code":"132", "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", @@ -2340,7 +2394,7 @@ "uri":"cce_10_0507.html", "node_id":"cce_10_0507.xml", "product_code":"cce", - "code":"130", + "code":"133", "des":"Check whether swap has been enabled on CCE nodes.By default, swap is disabled on CCE nodes. Check the necessity of enabling swap manually and determine the impact of disa", "doc_type":"usermanual2", "kw":"Node Swap,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2358,7 +2412,7 @@ "uri":"cce_10_0508.html", "node_id":"cce_10_0508.xml", "product_code":"cce", - "code":"131", + "code":"134", "des":"Check item 1: Check whether there is an Nginx Ingress route whose ingress type is not specified (kubernetes.io/ingress.class: nginx is not added to annotations) in the cl", "doc_type":"usermanual2", "kw":"NGINX Ingress Controller,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2376,7 +2430,7 @@ "uri":"cce_10_0510.html", "node_id":"cce_10_0510.xml", "product_code":"cce", - "code":"132", + "code":"135", "des":"Check whether the service pods running on a containerd node are restarted when containerd is upgraded.containerd on your node may need to be restarted. To minimize the im", "doc_type":"usermanual2", "kw":"containerd Pod Restart Risks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2394,7 +2448,7 @@ "uri":"cce_10_0511.html", "node_id":"cce_10_0511.xml", "product_code":"cce", - "code":"133", + "code":"136", "des":"Check whether the configuration of CCE AI Suite (NVIDIA GPU) in a cluster has been intrusively modified. If so, upgrading the cluster may fail.", "doc_type":"usermanual2", "kw":"Key CCE AI Suite (NVIDIA GPU) Parameters,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2412,7 +2466,7 @@ "uri":"cce_10_0512.html", "node_id":"cce_10_0512.xml", "product_code":"cce", - "code":"134", + "code":"137", "des":"Check whether GPU 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 is con", "doc_type":"usermanual2", "kw":"GPU Pod Rebuild Risks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2430,7 +2484,7 @@ "uri":"cce_10_0513.html", "node_id":"cce_10_0513.xml", "product_code":"cce", - "code":"135", + "code":"138", "des":"Check whether ELB listener access control has been configured using annotations for the Services in the current cluster.If so, check whether their configurations are corr", "doc_type":"usermanual2", "kw":"ELB Listener Access Control,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2448,7 +2502,7 @@ "uri":"cce_10_0514.html", "node_id":"cce_10_0514.xml", "product_code":"cce", - "code":"136", + "code":"139", "des":"Check whether the flavor of the master nodes in the cluster is the same as the actual flavor of these nodes.This issue is typically caused by modifications made to the ma", "doc_type":"usermanual2", "kw":"Master Node Flavor,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2466,7 +2520,7 @@ "uri":"cce_10_0515.html", "node_id":"cce_10_0515.xml", "product_code":"cce", - "code":"137", + "code":"140", "des":"Check whether the number of available IP addresses in the cluster subnet supports rolling upgrade.Rolling upgrade is not supported if there are not enough IP addresses in", "doc_type":"usermanual2", "kw":"Subnet Quota of Master Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2484,7 +2538,7 @@ "uri":"cce_10_0516.html", "node_id":"cce_10_0516.xml", "product_code":"cce", - "code":"138", + "code":"141", "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 your node's runtime is not ", "doc_type":"usermanual2", "kw":"Node Runtime,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2502,7 +2556,7 @@ "uri":"cce_10_0517.html", "node_id":"cce_10_0517.xml", "product_code":"cce", - "code":"139", + "code":"142", "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 your node pool's runtime is", "doc_type":"usermanual2", "kw":"Node Pool Runtime,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2520,7 +2574,7 @@ "uri":"cce_10_0518.html", "node_id":"cce_10_0518.xml", "product_code":"cce", - "code":"140", + "code":"143", "des":"Check the number of images on your node. If there are more than 1000 images, it takes a long time for Docker to start, affecting the standard Docker output and functions ", "doc_type":"usermanual2", "kw":"Number of Node Images,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2538,10 +2592,10 @@ "uri":"cce_10_0520.html", "node_id":"cce_10_0520.xml", "product_code":"cce", - "code":"141", - "des":"Check whether the target version supports secret encryption. If it does not, clusters that have this feature enabled cannot be upgraded to the target version.Secret encry", + "code":"144", + "des":"Check whether the target version supports at-rest encryption for secrets. If it does not, clusters that have this feature enabled cannot be upgraded to the target version", "doc_type":"usermanual2", - "kw":"Compatibility Check of Secret Encryption,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", + "kw":"Compatibility Check of At-Rest Encryption for Secrets,Troubleshooting for Pre-upgrade Check Exceptio", "search_title":"", "metedata":[ { @@ -2549,14 +2603,14 @@ "documenttype":"usermanual" } ], - "title":"Compatibility Check of Secret Encryption", + "title":"Compatibility Check of At-Rest Encryption for Secrets", "githuburl":"" }, { "uri":"cce_10_0521.html", "node_id":"cce_10_0521.xml", "product_code":"cce", - "code":"142", + "code":"145", "des":"Make sure that CCE AI Suite (NVIDIA GPU) and Ubuntu nodes are compatible before using them in a cluster. If the Ubuntu kernel is 5.15.0-113-generic, the driver of the GPU", "doc_type":"usermanual2", "kw":"Compatibility Between the Ubuntu Kernel and GPU Driver,Troubleshooting for Pre-upgrade Check Excepti", @@ -2574,7 +2628,7 @@ "uri":"cce_10_0522.html", "node_id":"cce_10_0522.xml", "product_code":"cce", - "code":"143", + "code":"146", "des":"An unfinished drainage task is detected in the cluster, which may resume after the upgrade. If this happens, running pods will be evicted, which could impact your service", "doc_type":"usermanual2", "kw":"Drainage Tasks,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2592,7 +2646,7 @@ "uri":"cce_10_0523.html", "node_id":"cce_10_0523.xml", "product_code":"cce", - "code":"144", + "code":"147", "des":"Check the number of image layers on your node. If there are more than 5000 layers, it will take a long time for Docker or containerd to start, affecting the stdout of Doc", "doc_type":"usermanual2", "kw":"Image Layers on a Node,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2610,7 +2664,7 @@ "uri":"cce_10_0524.html", "node_id":"cce_10_0524.xml", "product_code":"cce", - "code":"145", + "code":"148", "des":"Check whether your cluster is eligible for a rolling upgrade. The result shows that the rolling upgrade is not supported.Rolling upgrades cannot be performed if the tenan", "doc_type":"usermanual2", "kw":"Cluster Rolling Upgrade,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2628,7 +2682,7 @@ "uri":"cce_10_0525.html", "node_id":"cce_10_0525.xml", "product_code":"cce", - "code":"146", + "code":"149", "des":"Check whether the number of certificates on your node is greater than 1000. During an upgrade, certificate files will be processed in batches. An excessive number of cert", "doc_type":"usermanual2", "kw":"Rotation Certificates,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2646,7 +2700,7 @@ "uri":"cce_10_0526.html", "node_id":"cce_10_0526.xml", "product_code":"cce", - "code":"147", + "code":"150", "des":"Check whether any modifications have been made to the listener, forwarding policy, forwarding rule, backend cloud server group, backend cloud server, or certificate confi", "doc_type":"usermanual2", "kw":"Ingress and ELB Configuration Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Guid", @@ -2664,7 +2718,7 @@ "uri":"cce_10_0527.html", "node_id":"cce_10_0527.xml", "product_code":"cce", - "code":"148", + "code":"151", "des":"Check the network policy settings on the master nodes in your cluster. If any manual modifications have been made, they will be reset during the upgrade.Check whether net", "doc_type":"usermanual2", "kw":"Network Policies of Cluster Network Components,Troubleshooting for Pre-upgrade Check Exceptions,User", @@ -2682,7 +2736,7 @@ "uri":"cce_10_0528.html", "node_id":"cce_10_0528.xml", "product_code":"cce", - "code":"149", + "code":"152", "des":"Check whether the nic-max-above-warm-target value configured for the network component of the current cluster exceeds the maximum value allowed.Determine the scope of imp", "doc_type":"usermanual2", "kw":"Cluster and Node Pool Configurations,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2700,7 +2754,7 @@ "uri":"cce_10_0529.html", "node_id":"cce_10_0529.xml", "product_code":"cce", - "code":"150", + "code":"153", "des":"Check whether the time zone of the master nodes matches the cluster's time zone. If they are different, the master nodes will be updated to match the cluster's time zone ", "doc_type":"usermanual2", "kw":"Time Zone of Master Nodes,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2718,7 +2772,7 @@ "uri":"cce_10_0530.html", "node_id":"cce_10_0530.xml", "product_code":"cce", - "code":"151", + "code":"154", "des":"Check whether the SNATIPRanges value has changed after the upgrade. This check is available only for CCE Turbo clusters.In a CCE Turbo cluster, the CIDR blocks in SNATIPR", "doc_type":"usermanual2", "kw":"SNATIPRanges,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", @@ -2736,8 +2790,8 @@ "uri":"cce_10_0531.html", "node_id":"cce_10_0531.xml", "product_code":"cce", - "code":"152", - "des":"Manual modifications to add-on configuration parameters (typically ConfigMaps), instead of modifications through the CCE console or APIs, may be overwritten after an upgr", + "code":"155", + "des":"Manual modifications to add-on configuration parameters (typically ConfigMaps), instead of modifications through the CCE console or add-on API updates, may be overwritten", "doc_type":"usermanual2", "kw":"Add-on Configuration Consistency,Troubleshooting for Pre-upgrade Check Exceptions,User Guide", "search_title":"", @@ -2754,7 +2808,7 @@ "uri":"cce_10_0183.html", "node_id":"cce_10_0183.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":"Nodes", @@ -2772,7 +2826,7 @@ "uri":"cce_10_0180.html", "node_id":"cce_10_0180.xml", "product_code":"cce", - "code":"154", + "code":"157", "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", @@ -2790,7 +2844,7 @@ "uri":"cce_10_0462.html", "node_id":"cce_10_0462.xml", "product_code":"cce", - "code":"155", + "code":"158", "des":"Container engines, one of the most important components of Kubernetes, manage the lifecycle of images and containers. The kubelet interacts with a container runtime throu", "doc_type":"usermanual2", "kw":"Container Engines,Nodes,User Guide", @@ -2808,7 +2862,7 @@ "uri":"cce_10_0476.html", "node_id":"cce_10_0476.xml", "product_code":"cce", - "code":"156", + "code":"159", "des":"This section describes the mappings between released cluster versions and OS versions.", "doc_type":"usermanual2", "kw":"Node OSs,Nodes,User Guide", @@ -2826,8 +2880,8 @@ "uri":"cce_10_0363.html", "node_id":"cce_10_0363.xml", "product_code":"cce", - "code":"157", - "des":"At least one cluster has been created.A key pair has been created for identity authentication upon remote node login.The DNS configuration of a subnet where a node is loc", + "code":"160", + "des":"At least one cluster is available.A key pair is available for remote node login using key-pair authentication. If you use a password for login, skip this step.If you use ", "doc_type":"usermanual2", "kw":"Creating a Node,Nodes,User Guide", "search_title":"", @@ -2844,8 +2898,8 @@ "uri":"cce_10_0198.html", "node_id":"cce_10_0198.xml", "product_code":"cce", - "code":"158", - "des":"In CCE, you can create a node (Creating a Node) or add existing nodes (ECSs) to your cluster for management.When accepting an ECS, you can reset the ECS OS to a standard ", + "code":"161", + "des":"In CCE, you can create a node (Creating a Node) or add existing nodes (ECSs) to your cluster for management.When accepting an ECS, you can reset its OS to a standard publ", "doc_type":"usermanual2", "kw":"Accepting Nodes for Management,Nodes,User Guide", "search_title":"", @@ -2862,8 +2916,8 @@ "uri":"cce_10_0185.html", "node_id":"cce_10_0185.xml", "product_code":"cce", - "code":"159", - "des":"Before you log in to a node using SSH, ensure that the SSH port (22 by default) is enabled in the security group of the node.Before you log in to a node (an ECS) using SS", + "code":"162", + "des":"Before you log in to a node using SSH, ensure the SSH port (22 by default) is enabled in the security group of the node.Before you log in to a node (an ECS) via SSH over ", "doc_type":"usermanual2", "kw":"Logging In to a Node,Nodes,User Guide", "search_title":"", @@ -2880,7 +2934,7 @@ "uri":"cce_10_0672.html", "node_id":"cce_10_0672.xml", "product_code":"cce", - "code":"160", + "code":"163", "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", @@ -2898,7 +2952,7 @@ "uri":"cce_10_0004.html", "node_id":"cce_10_0004.xml", "product_code":"cce", - "code":"161", + "code":"164", "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", @@ -2916,7 +2970,7 @@ "uri":"cce_10_0352.html", "node_id":"cce_10_0352.xml", "product_code":"cce", - "code":"162", + "code":"165", "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", @@ -2934,7 +2988,7 @@ "uri":"cce_10_0003.html", "node_id":"cce_10_0003.xml", "product_code":"cce", - "code":"163", + "code":"166", "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", @@ -2952,7 +3006,7 @@ "uri":"cce_10_0338.html", "node_id":"cce_10_0338.xml", "product_code":"cce", - "code":"164", + "code":"167", "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", @@ -2970,10 +3024,10 @@ "uri":"cce_10_0184.html", "node_id":"cce_10_0184.xml", "product_code":"cce", - "code":"165", + "code":"168", "des":"Each node in a cluster is a cloud server or physical machine. After a cluster node is created, you can change the cloud server name or specifications as required. Modifyi", "doc_type":"usermanual2", - "kw":"synchronize the ECS,Synchronizing the Data of Cloud Servers,Management Nodes,User Guide", + "kw":"synchronize it,Synchronizing the Data of Cloud Servers,Management Nodes,User Guide", "search_title":"", "metedata":[ { @@ -2988,7 +3042,7 @@ "uri":"cce_10_0605.html", "node_id":"cce_10_0605.xml", "product_code":"cce", - "code":"166", + "code":"169", "des":"After you enable nodal drainage on the console, CCE configures the node to be non-schedulable and securely evicts all pods that comply with Rules for Draining Nodes on th", "doc_type":"usermanual2", "kw":"nodal drainage,nodal drainage,Draining a Node,Management Nodes,User Guide", @@ -3006,8 +3060,8 @@ "uri":"cce_10_0186.html", "node_id":"cce_10_0186.xml", "product_code":"cce", - "code":"167", - "des":"If a node is no longer needed, delete it from the node list on the CCE console if the node is billed on a pay-per-use basis. Do not manually remove nodes using kubectl de", + "code":"170", + "des":"If a node is no longer needed, delete it on the CCE console if the node is billed on a pay-per-use basis. Do not manually remove nodes using kubectl delete node, as this ", "doc_type":"usermanual2", "kw":"Deleting a Node,Management Nodes,User Guide", "search_title":"", @@ -3024,7 +3078,7 @@ "uri":"cce_10_0036.html", "node_id":"cce_10_0036.xml", "product_code":"cce", - "code":"168", + "code":"171", "des":"When a node in the cluster is stopped, all services on that node will also be stopped, and the node will no longer be available for scheduling. Check if your services wil", "doc_type":"usermanual2", "kw":"Stopping a Node,Management Nodes,User Guide", @@ -3042,7 +3096,7 @@ "uri":"cce_10_0276.html", "node_id":"cce_10_0276.xml", "product_code":"cce", - "code":"169", + "code":"172", "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", @@ -3060,7 +3114,7 @@ "uri":"cce_10_0704.html", "node_id":"cce_10_0704.xml", "product_code":"cce", - "code":"170", + "code":"173", "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", @@ -3078,10 +3132,10 @@ "uri":"cce_10_0178.html", "node_id":"cce_10_0178.xml", "product_code":"cce", - "code":"171", + "code":"174", "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", + "kw":"total number of node resources,Node Resource Reservation Rules,Node O&M,User Guide", "search_title":"", "metedata":[ { @@ -3089,14 +3143,14 @@ "documenttype":"usermanual" } ], - "title":"Node Resource Reservation Policy", + "title":"Node Resource Reservation Rules", "githuburl":"" }, { "uri":"cce_10_0341.html", "node_id":"cce_10_0341.xml", "product_code":"cce", - "code":"172", + "code":"175", "des":"This section describes how to allocate data disk space to nodes so that you can configure the data disk space accordingly.In clusters of a version earlier than v1.23.18-r", "doc_type":"usermanual2", "kw":"Data Disk Space Allocation,Container engine and container image space,container engine and container", @@ -3114,8 +3168,8 @@ "uri":"cce_10_0348.html", "node_id":"cce_10_0348.xml", "product_code":"cce", - "code":"173", - "des":"The maximum number of pods that can be created on a node is calculated based on the cluster type:When creating a cluster in the VPC network model, follow the and specify", + "code":"176", + "des":"The maximum number of pods that can be created on a node is calculated based on the cluster type:The number of allocatable pod IP addresses on a node is the maximum numbe", "doc_type":"usermanual2", "kw":"Maximum Number of Pods on a Node,alpha.cce/fixPoolMask,maximum number of pods,Maximum Number of Pods", "search_title":"", @@ -3132,7 +3186,7 @@ "uri":"cce_10_0883.html", "node_id":"cce_10_0883.xml", "product_code":"cce", - "code":"174", + "code":"177", "des":"To maintain the stability of nodes, CCE stores Kubernetes and container runtime components on separate data disks. Kubernetes uses the /mnt/paas/kubernetes directory, and", "doc_type":"usermanual2", "kw":"Differences in kubelet and Runtime Component Configurations Between CCE and the Native Community,Nod", @@ -3150,7 +3204,7 @@ "uri":"cce_10_0601.html", "node_id":"cce_10_0601.xml", "product_code":"cce", - "code":"175", + "code":"178", "des":"As of Kubernetes v1.24, dockershim has been deprecated. To maintain compatibility and ensure continued support for future Kubernetes releases, switch your node's containe", "doc_type":"usermanual2", "kw":"Migrating Nodes from Docker to containerd,Node O&M,User Guide", @@ -3168,8 +3222,8 @@ "uri":"cce_10_0659.html", "node_id":"cce_10_0659.xml", "product_code":"cce", - "code":"176", - "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", + "code":"179", + "des":"Node fault detection depends on the CCE Node Problem Detector add-on (CCE Node Problem Detector). The add-on instance runs on each node to monitor node faults. This secti", "doc_type":"usermanual2", "kw":"Node Fault Detection,Check Items,Configuring Node Fault Detection Policies,Node O&M,User Guide", "search_title":"", @@ -3183,10 +3237,10 @@ "githuburl":"" }, { - "uri":"cce_bestpractice_10020.html", - "node_id":"cce_bestpractice_10020.xml", + "uri":"cce_bestpractice_10020_0.html", + "node_id":"cce_bestpractice_10020_0.xml", "product_code":"cce", - "code":"177", + "code":"180", "des":"When creating a node, use the pre- or -installation commands to install tools or perform security hardening on the node. This section provides guidance for you to correct", "doc_type":"usermanual2", "kw":"Executing the Pre- or Post-installation Commands During Node Creation,Node O&M,User Guide", @@ -3204,7 +3258,7 @@ "uri":"cce_10_0035.html", "node_id":"cce_10_0035.xml", "product_code":"cce", - "code":"178", + "code":"181", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Node Pools", @@ -3222,7 +3276,7 @@ "uri":"cce_10_0081.html", "node_id":"cce_10_0081.xml", "product_code":"cce", - "code":"179", + "code":"182", "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,", @@ -3240,7 +3294,7 @@ "uri":"cce_10_0012.html", "node_id":"cce_10_0012.xml", "product_code":"cce", - "code":"180", + "code":"183", "des":"This section describes how to create a node pool and perform operations on the node pool. For details about how a node pool works, see Node Pool Overview.Basic SettingsNo", "doc_type":"usermanual2", "kw":"Creating a Node Pool,Node Pools,User Guide", @@ -3258,7 +3312,7 @@ "uri":"cce_10_0658.html", "node_id":"cce_10_0658.xml", "product_code":"cce", - "code":"181", + "code":"184", "des":"You can specify a specification in a node pool for scaling.The default node pool does not support scaling. Use Creating a Node to add a node.Resize: Add or reduce nodes f", "doc_type":"usermanual2", "kw":"Scaling a Node Pool,Node Pools,User Guide", @@ -3276,10 +3330,10 @@ "uri":"cce_10_0222.html", "node_id":"cce_10_0222.xml", "product_code":"cce", - "code":"182", + "code":"185", "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", + "kw":"Managing Node Pools", "search_title":"", "metedata":[ { @@ -3287,17 +3341,17 @@ "documenttype":"usermanual" } ], - "title":"Managing a Node Pool", + "title":"Managing Node Pools", "githuburl":"" }, { "uri":"cce_10_0653.html", "node_id":"cce_10_0653.xml", "product_code":"cce", - "code":"183", + "code":"186", "des":"Changes to the container engine, OS, or pre-/post-installation script in a node pool take effect only on new nodes. To synchronize the modification onto existing nodes, m", "doc_type":"usermanual2", - "kw":"base size,Updating a Node Pool,Managing a Node Pool,User Guide", + "kw":"base size,Updating a Node Pool,Managing Node Pools,User Guide", "search_title":"", "metedata":[ { @@ -3312,10 +3366,10 @@ "uri":"cce_10_0727.html", "node_id":"cce_10_0727.xml", "product_code":"cce", - "code":"184", + "code":"187", "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", + "kw":"Updating an AS Configuration,Managing Node Pools,User Guide", "search_title":"", "metedata":[ { @@ -3330,10 +3384,10 @@ "uri":"cce_10_0652.html", "node_id":"cce_10_0652.xml", "product_code":"cce", - "code":"185", - "des":"The default node pool does not support the management operations described in this section.CCE allows you to highly customize Kubernetes parameter settings on core compon", + "code":"188", + "des":"If the default node configurations of in cluster do not meet service requirements, you can customize parameters for core components, such as kubelet, kube-proxy, and the ", "doc_type":"usermanual2", - "kw":"Modifying Node Pool Configurations,Managing a Node Pool,User Guide", + "kw":"Modifying Node Pool Configurations,Managing Node Pools,User Guide", "search_title":"", "metedata":[ { @@ -3348,10 +3402,10 @@ "uri":"cce_10_0886.html", "node_id":"cce_10_0886.xml", "product_code":"cce", - "code":"186", + "code":"189", "des":"If you want to add a newly created ECS to a node pool in a cluster, or remove a node from a node pool and add it to the node pool again, accept the node.When an ECS is ac", "doc_type":"usermanual2", - "kw":"Accepting Nodes in a Node Pool,Managing a Node Pool,User Guide", + "kw":"Accepting Nodes in a Node Pool,Managing Node Pools,User Guide", "search_title":"", "metedata":[ { @@ -3366,10 +3420,10 @@ "uri":"cce_10_0655.html", "node_id":"cce_10_0655.xml", "product_code":"cce", - "code":"187", + "code":"190", "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", + "kw":"Copying a Node Pool,Managing Node Pools,User Guide", "search_title":"", "metedata":[ { @@ -3384,10 +3438,10 @@ "uri":"cce_10_0654.html", "node_id":"cce_10_0654.xml", "product_code":"cce", - "code":"188", + "code":"191", "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", + "kw":"Synchronizing Node Pools,Managing Node Pools,User Guide", "search_title":"", "metedata":[ { @@ -3402,10 +3456,10 @@ "uri":"cce_10_0660.html", "node_id":"cce_10_0660.xml", "product_code":"cce", - "code":"189", + "code":"192", "des":"After CCE releases a new OS image, if existing nodes cannot be automatically upgraded, you can manually upgrade them in batches.This section describes how to upgrade an O", "doc_type":"usermanual2", - "kw":"Upgrading an OS,Managing a Node Pool,User Guide", + "kw":"Upgrading an OS,Managing Node Pools,User Guide", "search_title":"", "metedata":[ { @@ -3420,10 +3474,10 @@ "uri":"cce_10_0656.html", "node_id":"cce_10_0656.xml", "product_code":"cce", - "code":"190", + "code":"193", "des":"You can migrate nodes between node pools within a cluster. Table 1 lists migration scenarios.Migration scenariosMigration ScenarioMigrationOperationSource Node PoolTarget", "doc_type":"usermanual2", - "kw":"Migrating a Node,Managing a Node Pool,User Guide", + "kw":"Migrating a Node,Managing Node Pools,User Guide", "search_title":"", "metedata":[ { @@ -3438,10 +3492,10 @@ "uri":"cce_10_0657.html", "node_id":"cce_10_0657.xml", "product_code":"cce", - "code":"191", - "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", + "code":"194", + "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 will cause P", "doc_type":"usermanual2", - "kw":"Deleting a Node Pool,Managing a Node Pool,User Guide", + "kw":"Deleting a Node Pool,Managing Node Pools,User Guide", "search_title":"", "metedata":[ { @@ -3456,7 +3510,7 @@ "uri":"cce_10_0046.html", "node_id":"cce_10_0046.xml", "product_code":"cce", - "code":"192", + "code":"195", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Workloads", @@ -3474,10 +3528,10 @@ "uri":"cce_10_0006.html", "node_id":"cce_10_0006.xml", "product_code":"cce", - "code":"193", + "code":"196", "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", + "kw":"Deployments,StatefulSets,DaemonSets,jobs,cron jobs,Workload Overview,Workloads,User Guide", "search_title":"", "metedata":[ { @@ -3485,14 +3539,14 @@ "documenttype":"usermanual" } ], - "title":"Overview", + "title":"Workload Overview", "githuburl":"" }, { "uri":"cce_10_0673.html", "node_id":"cce_10_0673.xml", "product_code":"cce", - "code":"194", + "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":"Creating a Workload", @@ -3510,8 +3564,8 @@ "uri":"cce_10_0047.html", "node_id":"cce_10_0047.xml", "product_code":"cce", - "code":"195", - "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", + "code":"198", + "des":"A Deployment is a Kubernetes application that does not retain data or state while running. Each pod of the same Deployment is identical, allowing for seamless creation, d", "doc_type":"usermanual2", "kw":"create a workload using kubectl,Creating a Deployment,Creating a Workload,User Guide", "search_title":"", @@ -3528,8 +3582,8 @@ "uri":"cce_10_0048.html", "node_id":"cce_10_0048.xml", "product_code":"cce", - "code":"196", - "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", + "code":"199", + "des":"A StatefulSet is an application that needs to retain data or state while running. StatefulSets are ideal for stateful applications, such as databases, cache services, and", "doc_type":"usermanual2", "kw":"Using kubectl,Creating a StatefulSet,Creating a Workload,User Guide", "search_title":"", @@ -3546,8 +3600,8 @@ "uri":"cce_10_0216.html", "node_id":"cce_10_0216.xml", "product_code":"cce", - "code":"197", - "des":"CCE provides deployment and management capabilities for multiple types of containers and supports features of container workloads, including creation, configuration, moni", + "code":"200", + "des":"A DaemonSet is a Kubernetes workload type that ensures a pod runs on all or selected nodes in a cluster. When a new node is added to the cluster, the DaemonSet controller", "doc_type":"usermanual2", "kw":"create a workload using kubectl,Creating a DaemonSet,Creating a Workload,User Guide", "search_title":"", @@ -3564,8 +3618,8 @@ "uri":"cce_10_0150.html", "node_id":"cce_10_0150.xml", "product_code":"cce", - "code":"198", - "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", + "code":"201", + "des":"A job is a Kubernetes workload designed for managing batch processing tasks, handling one-time or short-lived tasks. Unlike long-running services managed by Deployments o", "doc_type":"usermanual2", "kw":"Creating a Job,Creating a Workload,User Guide", "search_title":"", @@ -3582,10 +3636,10 @@ "uri":"cce_10_0151.html", "node_id":"cce_10_0151.xml", "product_code":"cce", - "code":"199", - "des":"A CronJob runs on a repeating schedule. You can perform time synchronization for all active nodes at a fixed time point.A CronJob runs periodically at the specified time.", + "code":"202", + "des":"A CronJob is a Kubernetes workload designed to run periodic tasks, similar to crontab in Linux. CronJobs follow a Cron format. They periodically execute jobs at predefine", "doc_type":"usermanual2", - "kw":"time synchronization,Creating a CronJob,Creating a Workload,User Guide", + "kw":"Creating a CronJob,Creating a Workload,User Guide", "search_title":"", "metedata":[ { @@ -3600,7 +3654,7 @@ "uri":"cce_10_0130.html", "node_id":"cce_10_0130.xml", "product_code":"cce", - "code":"200", + "code":"203", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Configuring a Workload", @@ -3618,7 +3672,7 @@ "uri":"cce_10_0463.html", "node_id":"cce_10_0463.xml", "product_code":"cce", - "code":"201", + "code":"204", "des":"Compared with a common runtime, a secure runtime allows each container (pod) to run on its own micro-VM with a separate OS kernel. This ensures secure isolation at the vi", "doc_type":"usermanual2", "kw":"Secure Runtime and Common Runtime,Configuring a Workload,User Guide", @@ -3636,8 +3690,8 @@ "uri":"cce_10_0354.html", "node_id":"cce_10_0354.xml", "product_code":"cce", - "code":"202", - "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", + "code":"205", + "des":"When creating a workload, you can enable time zone synchronization, so that the container can use the same time zone as the node.Configure the following parameters:hostPa", "doc_type":"usermanual2", "kw":"Configuring Time Zone Synchronization,Configuring a Workload,User Guide", "search_title":"", @@ -3654,7 +3708,7 @@ "uri":"cce_10_0353.html", "node_id":"cce_10_0353.xml", "product_code":"cce", - "code":"203", + "code":"206", "des":"When a workload is created, the container image is pulled from the image repository to the node. The image is also pulled when the workload is restarted or upgraded.By de", "doc_type":"usermanual2", "kw":"Configuring an Image Pull Policy,Configuring a Workload,User Guide", @@ -3672,8 +3726,8 @@ "uri":"cce_10_0009.html", "node_id":"cce_10_0009.xml", "product_code":"cce", - "code":"204", - "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", + "code":"207", + "des":"Third-party images are container images provided by organizations or individuals other than the official image repository and SWR image repository. These images typically", "doc_type":"usermanual2", "kw":"Using Third-Party Images,Configuring a Workload,User Guide", "search_title":"", @@ -3690,7 +3744,7 @@ "uri":"cce_10_0163.html", "node_id":"cce_10_0163.xml", "product_code":"cce", - "code":"205", + "code":"208", "des":"CCE allows you to set resource requirements and limits, such as CPU and RAM, for added containers during workload creation. Kubernetes also allows using YAML to set requi", "doc_type":"usermanual2", "kw":"ephemeral storage,Configuring Container Specifications,Configuring a Workload,User Guide", @@ -3708,10 +3762,10 @@ "uri":"cce_10_0105.html", "node_id":"cce_10_0105.xml", "product_code":"cce", - "code":"206", - "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", + "code":"209", + "des":"Container lifecycle hooks are core mechanisms provided by Kubernetes that enable you to insert custom logic at key phases throughout the container lifecycle. These hooks ", "doc_type":"usermanual2", - "kw":"Startup Command,Post-Start,Pre-Stop,Configuring Container Lifecycle Parameters,Configuring a Workloa", + "kw":"Configuring the Container Lifecycle,Configuring a Workload,User Guide", "search_title":"", "metedata":[ { @@ -3719,17 +3773,17 @@ "documenttype":"usermanual" } ], - "title":"Configuring Container Lifecycle Parameters", + "title":"Configuring the Container Lifecycle", "githuburl":"" }, { "uri":"cce_10_0112.html", "node_id":"cce_10_0112.xml", "product_code":"cce", - "code":"207", - "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", + "code":"210", + "des":"Health check regularly checks the health of containers when the containers are running. If health check is not configured, a pod cannot detect application exceptions or a", "doc_type":"usermanual2", - "kw":"Health check,HTTP request,TCP port,CLI,Configuring Container Health Check,Configuring a Workload,Use", + "kw":"Health check,Liveness probe,Readiness probe,Startup probe,HTTP,TCP,Command,Configuring Container Hea", "search_title":"", "metedata":[ { @@ -3744,8 +3798,8 @@ "uri":"cce_10_0113.html", "node_id":"cce_10_0113.xml", "product_code":"cce", - "code":"208", - "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", + "code":"211", + "des":"Container environment variables (for example, DB_HOST=db.example.com) are configuration parameters dynamically transferred when a container is running. They allow you to ", "doc_type":"usermanual2", "kw":"Configuring Environment Variables,Configuring a Workload,User Guide", "search_title":"", @@ -3762,10 +3816,10 @@ "uri":"cce_10_0397.html", "node_id":"cce_10_0397.xml", "product_code":"cce", - "code":"209", - "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", + "code":"212", + "des":"After a workload is created, you can upgrade it and roll it back. The flexible upgrade and rollback mechanism enables smooth version transitions without interrupting serv", "doc_type":"usermanual2", - "kw":"Configuring Workload Upgrade Policies,Configuring a Workload,User Guide", + "kw":"Upgrading and Rolling Back a Workload,Configuring a Workload,User Guide", "search_title":"", "metedata":[ { @@ -3773,14 +3827,14 @@ "documenttype":"usermanual" } ], - "title":"Configuring Workload Upgrade Policies", + "title":"Upgrading and Rolling Back a Workload", "githuburl":"" }, { "uri":"cce_10_0728.html", "node_id":"cce_10_0728.xml", "product_code":"cce", - "code":"210", + "code":"213", "des":"Tolerations allow the scheduler to schedule pods to nodes with target taints. Tolerances work with node taints. Each node allows one or more taints. If no tolerance is co", "doc_type":"usermanual2", "kw":"Configuring Tolerance Policies,Configuring a Workload,User Guide", @@ -3798,8 +3852,8 @@ "uri":"cce_10_0386.html", "node_id":"cce_10_0386.xml", "product_code":"cce", - "code":"211", - "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", + "code":"214", + "des":"To support multi-dimensional metadata management, Kubernetes offers labels and annotations. They both attach metadata to resources in the format of key-value pairs, but t", "doc_type":"usermanual2", "kw":"Configuring Labels and Annotations,Configuring a Workload,User Guide", "search_title":"", @@ -3816,7 +3870,7 @@ "uri":"cce_10_0889.html", "node_id":"cce_10_0889.xml", "product_code":"cce", - "code":"212", + "code":"215", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Scheduling a Workload", @@ -3834,7 +3888,7 @@ "uri":"cce_10_0232.html", "node_id":"cce_10_0232.xml", "product_code":"cce", - "code":"213", + "code":"216", "des":"Kubernetes schedules workloads based on pods. After you create a workload, the scheduler automatically assigns pods. For example, the scheduler distributes pods to nodes ", "doc_type":"usermanual2", "kw":"Overview,Scheduling a Workload,User Guide", @@ -3852,8 +3906,8 @@ "uri":"cce_10_0891.html", "node_id":"cce_10_0891.xml", "product_code":"cce", - "code":"214", - "des":"To select a node for scheduling in Kubernetes, simply configure the nodeSelector field in the workload. This field allows you to configure the label of the desired node t", + "code":"217", + "des":"In Kubernetes, to schedule a workload to a specified node, simply configure the nodeSelector field in the workload. By setting the target node label in this field, Kubern", "doc_type":"usermanual2", "kw":"Configuring Specified Node Scheduling (nodeSelector),Scheduling a Workload,User Guide", "search_title":"", @@ -3870,7 +3924,7 @@ "uri":"cce_10_0892.html", "node_id":"cce_10_0892.xml", "product_code":"cce", - "code":"215", + "code":"218", "des":"Kubernetes can schedule workload pods to affinity nodes based on their labels and label values. For example, some nodes support GPU computing, and node affinity schedulin", "doc_type":"usermanual2", "kw":"Specify node,Specify node pool,Configuring Node Affinity Scheduling (nodeAffinity),Scheduling a Work", @@ -3888,7 +3942,7 @@ "uri":"cce_10_0893.html", "node_id":"cce_10_0893.xml", "product_code":"cce", - "code":"216", + "code":"219", "des":"Kubernetes offers workload affinity and anti-affinity scheduling, which allows for flexible scheduling of new workloads on either related or unrelated nodes. This results", "doc_type":"usermanual2", "kw":"Configuring Workload Affinity or Anti-affinity Scheduling (podAffinity or podAntiAffinity),Schedulin", @@ -3906,7 +3960,7 @@ "uri":"cce_10_00356.html", "node_id":"cce_10_00356.xml", "product_code":"cce", - "code":"217", + "code":"220", "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":"Logging In to a Container,Workloads,User Guide", @@ -3924,10 +3978,10 @@ "uri":"cce_10_0007.html", "node_id":"cce_10_0007.xml", "product_code":"cce", - "code":"218", - "des":"After a workload is created, you can upgrade, log, monitor, roll back, or delete the workload, as well as edit its YAML file.Workload/Job managementOperationDescriptionMo", + "code":"221", + "des":"After a workload is created, you can upgrade it, edit its YAML file, view logs and monitoring data, roll it back, and delete it.Workload/Job managementOperationDescriptio", "doc_type":"usermanual2", - "kw":"Managing Workloads,Workloads,User Guide", + "kw":"Managing Labels,Managing Workloads,Workloads,User Guide", "search_title":"", "metedata":[ { @@ -3942,7 +3996,7 @@ "uri":"cce_10_0833.html", "node_id":"cce_10_0833.xml", "product_code":"cce", - "code":"219", + "code":"222", "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", @@ -3960,7 +4014,7 @@ "uri":"cce_10_0465.html", "node_id":"cce_10_0465.xml", "product_code":"cce", - "code":"220", + "code":"223", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Pod Security", @@ -3978,7 +4032,7 @@ "uri":"cce_10_0275.html", "node_id":"cce_10_0275.xml", "product_code":"cce", - "code":"221", + "code":"224", "des":"A pod security policy (PSP) is a cluster-level resource that controls sensitive security aspects of the pod specification. The PodSecurityPolicy object in Kubernetes defi", "doc_type":"usermanual2", "kw":"Configuring a Pod Security Policy,Pod Security,User Guide", @@ -3996,7 +4050,7 @@ "uri":"cce_10_0466.html", "node_id":"cce_10_0466.xml", "product_code":"cce", - "code":"222", + "code":"225", "des":"Before using pod security admission, understand Kubernetes Pod Security Standards. These standards define different isolation levels for pods. They let you define how you", "doc_type":"usermanual2", "kw":"Configuring Pod Security Admission,Pod Security,User Guide", @@ -4010,11 +4064,29 @@ "title":"Configuring Pod Security Admission", "githuburl":"" }, + { + "uri":"cce_10_1006.html", + "node_id":"cce_10_1006.xml", + "product_code":"cce", + "code":"226", + "des":"Application Armor (AppArmor) is a security module of the Linux kernel, which is usually used in OSs such as Ubuntu. AppArmor allows system administrators to associate eac", + "doc_type":"usermanual2", + "kw":"Using AppArmor to Confine Container Access to Resources,Pod Security,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Using AppArmor to Confine Container Access to Resources", + "githuburl":"" + }, { "uri":"cce_10_0674.html", "node_id":"cce_10_0674.xml", "product_code":"cce", - "code":"223", + "code":"227", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Scheduling", @@ -4032,10 +4104,10 @@ "uri":"cce_10_0702.html", "node_id":"cce_10_0702.xml", "product_code":"cce", - "code":"224", - "des":"CCE supports different types of resource scheduling and task scheduling, improving application performance and overall cluster resource utilization. This section describe", + "code":"228", + "des":"CCE supports multiple resource and task scheduling policies to enhance application performance and overall cluster resource utilization. This section describes the main f", "doc_type":"usermanual2", - "kw":"Overview,Scheduling,User Guide", + "kw":"Scheduling Overview,Scheduling,User Guide", "search_title":"", "metedata":[ { @@ -4043,14 +4115,14 @@ "documenttype":"usermanual" } ], - "title":"Overview", + "title":"Scheduling Overview", "githuburl":"" }, { "uri":"cce_10_0551.html", "node_id":"cce_10_0551.xml", "product_code":"cce", - "code":"225", + "code":"229", "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", @@ -4068,7 +4140,7 @@ "uri":"cce_10_0351.html", "node_id":"cce_10_0351.xml", "product_code":"cce", - "code":"226", + "code":"230", "des":"By default, kubelet uses CFS quotas to enforce pod CPU limits. When a node runs many CPU-bound pods, the workload can move to different CPU cores depending on whether the", "doc_type":"usermanual2", "kw":"CPU Policy,CPU Scheduling,User Guide", @@ -4086,8 +4158,8 @@ "uri":"cce_10_0552.html", "node_id":"cce_10_0552.xml", "product_code":"cce", - "code":"227", - "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", + "code":"231", + "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 pinn", "doc_type":"usermanual2", "kw":"Enhanced CPU Policy,CPU Scheduling,User Guide", "search_title":"", @@ -4104,7 +4176,7 @@ "uri":"cce_10_0720.html", "node_id":"cce_10_0720.xml", "product_code":"cce", - "code":"228", + "code":"232", "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", @@ -4118,12 +4190,102 @@ "title":"GPU Scheduling", "githuburl":"" }, + { + "uri":"cce_10_0845.html", + "node_id":"cce_10_0845.xml", + "product_code":"cce", + "code":"233", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual2", + "kw":"GPU Driver Version", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"GPU Driver Version", + "githuburl":"" + }, + { + "uri":"cce_10_0846.html", + "node_id":"cce_10_0846.xml", + "product_code":"cce", + "code":"234", + "des":"Before using GPU-accelerated ECSs, install the necessary NVIDIA infrastructure software to enable accelerated GPU computing. To use GPUs, select and install the appropria", + "doc_type":"usermanual2", + "kw":"Selecting a GPU Driver Version for Nodes,GPU Driver Version,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Selecting a GPU Driver Version for Nodes", + "githuburl":"" + }, + { + "uri":"cce_10_0847.html", + "node_id":"cce_10_0847.xml", + "product_code":"cce", + "code":"235", + "des":"This section describes the recommended driver versions for CCE clusters. If you use a non-recommended GPU driver version, make sure to check its compatibility with the mo", + "doc_type":"usermanual2", + "kw":"Recommended GPU Driver Versions for CCE,GPU Driver Version,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Recommended GPU Driver Versions for CCE", + "githuburl":"" + }, + { + "uri":"cce_10_0848.html", + "node_id":"cce_10_0848.xml", + "product_code":"cce", + "code":"236", + "des":"You can use the CCE AI Suite (NVIDIA GPU) add-on to configure the driver file path for a node. After the node is restarted, the driver will be installed automatically. Al", + "doc_type":"usermanual2", + "kw":"Manually Upgrading the Driver Version of a GPU Node,GPU Driver Version,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Manually Upgrading the Driver Version of a GPU Node", + "githuburl":"" + }, + { + "uri":"cce_10_0849.html", + "node_id":"cce_10_0849.xml", + "product_code":"cce", + "code":"237", + "des":"To ensure proper functioning of GPU nodes, upgrade the NVIDIA driver version if it does not match the CUDA library you use. It is recommended that you use node pools to e", + "doc_type":"usermanual2", + "kw":"Upgrading the Driver Version of a GPU Node Using a Node Pool,GPU Driver Version,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Upgrading the Driver Version of a GPU Node Using a Node Pool", + "githuburl":"" + }, { "uri":"cce_10_0345.html", "node_id":"cce_10_0345.xml", "product_code":"cce", - "code":"229", - "des":"You can use GPUs in CCE containers.A GPU node has been created. For details, see Creating a Node.The CCE AI Suite (NVIDIA GPU) add-on has been installed, with the selecte", + "code":"238", + "des":"CCE standard and Turbo clusters support Kubernetes' default GPU scheduling mode. This mode uses a device plugin to manage GPUs as a standard resource type. After the CCE ", "doc_type":"usermanual2", "kw":"Default GPU Scheduling in Kubernetes,GPU Scheduling,User Guide", "search_title":"", @@ -4136,14 +4298,140 @@ "title":"Default GPU Scheduling in Kubernetes", "githuburl":"" }, + { + "uri":"cce_10_0643.html", + "node_id":"cce_10_0643.xml", + "product_code":"cce", + "code":"239", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual2", + "kw":"GPU Virtualization", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"GPU Virtualization", + "githuburl":"" + }, + { + "uri":"cce_10_0644.html", + "node_id":"cce_10_0644.xml", + "product_code":"cce", + "code":"240", + "des":"CCE uses xGPU virtualization technologies to dynamically divide the GPU memory and computing power. A single GPU can be virtualized into a maximum of 20 virtual GPU devic", + "doc_type":"usermanual2", + "kw":"Overview,GPU Virtualization,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Overview", + "githuburl":"" + }, + { + "uri":"cce_10_0645.html", + "node_id":"cce_10_0645.xml", + "product_code":"cce", + "code":"241", + "des":"CCE uses xGPU virtualization technologies to dynamically divide the GPU memory and computing power. A single GPU can be virtualized into a maximum of 20 virtual GPU devic", + "doc_type":"usermanual2", + "kw":"Preparing Virtualized GPU Resources,GPU Virtualization,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Preparing Virtualized GPU Resources", + "githuburl":"" + }, + { + "uri":"cce_10_0646.html", + "node_id":"cce_10_0646.xml", + "product_code":"cce", + "code":"242", + "des":"This section describes how to use the GPU virtualization capability to isolate the computing power from the GPU memory and efficiently use GPU device resources.You have p", + "doc_type":"usermanual2", + "kw":"Using GPU Virtualization,GPU Virtualization,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Using GPU Virtualization", + "githuburl":"" + }, + { + "uri":"cce_10_0742.html", + "node_id":"cce_10_0742.xml", + "product_code":"cce", + "code":"243", + "des":"With GPU virtualization enabled, workloads can still use nvidia.com/gpu (Kubernetes' default GPU scheduling) while optionally adding fine-grained isolation via volcano.sh", + "doc_type":"usermanual2", + "kw":"Enabling Kubernetes' Default GPU Scheduling in GPU Virtualization,GPU Virtualization,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Enabling Kubernetes' Default GPU Scheduling in GPU Virtualization", + "githuburl":"" + }, + { + "uri":"cce_10_0965.html", + "node_id":"cce_10_0965.xml", + "product_code":"cce", + "code":"244", + "des":"In AI training, inference, and scientific computing, a single GPU often falls short due to limited compute power or memory. Multiple GPUs are therefore needed to work tog", + "doc_type":"usermanual2", + "kw":"Equal Distribution Scheduling on Virtual GPUs,GPU Virtualization,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Equal Distribution Scheduling on Virtual GPUs", + "githuburl":"" + }, + { + "uri":"cce_10_1016.html", + "node_id":"cce_10_1016.xml", + "product_code":"cce", + "code":"245", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual2", + "kw":"GPU Monitoring", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"GPU Monitoring", + "githuburl":"" + }, { "uri":"cce_10_0955.html", "node_id":"cce_10_0955.xml", "product_code":"cce", - "code":"230", + "code":"246", "des":"The CCE AI Suite (NVIDIA GPU) add-on provides GPU monitoring metrics. This add-on offers additional GPU observability options. This section describes the metrics provided", "doc_type":"usermanual2", - "kw":"GPU Metrics,GPU Scheduling,User Guide", + "kw":"GPU Metrics,GPU Monitoring,User Guide", "search_title":"", "metedata":[ { @@ -4154,11 +4442,83 @@ "title":"GPU Metrics", "githuburl":"" }, + { + "uri":"cce_10_0741.html", + "node_id":"cce_10_0741.xml", + "product_code":"cce", + "code":"247", + "des":"Monitoring GPU metrics optimizes performance, identifies faults quickly, and allocates resources efficiently. It improves GPU utilization and lowers O&M costs. Using Prom", + "doc_type":"usermanual2", + "kw":"Comprehensive Monitoring of GPU, Virtualization, and Pod Resource Metrics,GPU Monitoring,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Comprehensive Monitoring of GPU, Virtualization, and Pod Resource Metrics", + "githuburl":"" + }, + { + "uri":"cce_10_1017.html", + "node_id":"cce_10_1017.xml", + "product_code":"cce", + "code":"248", + "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 Auto Scaling", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"GPU Auto Scaling", + "githuburl":"" + }, + { + "uri":"cce_10_0844.html", + "node_id":"cce_10_0844.xml", + "product_code":"cce", + "code":"249", + "des":"In a standard or Turbo cluster, you can configure HPA policies for workloads that use GPU resources based on GPU monitoring metrics. This enables applications to automati", + "doc_type":"usermanual2", + "kw":"Configuring Workload Scaling Based on GPU Monitoring Metrics,GPU Auto Scaling,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Configuring Workload Scaling Based on GPU Monitoring Metrics", + "githuburl":"" + }, + { + "uri":"cce_10_0779.html", + "node_id":"cce_10_0779.xml", + "product_code":"cce", + "code":"250", + "des":"In a Kubernetes environment, managing GPU resources is complex, and diagnosing and recovering from faults can be challenging and costly. When a GPU becomes faulty, the CC", + "doc_type":"usermanual2", + "kw":"GPU Fault Handling,GPU Scheduling,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"GPU Fault Handling", + "githuburl":"" + }, { "uri":"cce_10_0423.html", "node_id":"cce_10_0423.xml", "product_code":"cce", - "code":"231", + "code":"251", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Volcano Scheduling", @@ -4176,10 +4536,10 @@ "uri":"cce_10_0721.html", "node_id":"cce_10_0721.xml", "product_code":"cce", - "code":"232", + "code":"252", "des":"Volcano is a batch processing platform that runs on Kubernetes for machine learning, deep learning, bioinformatics, genomics, and other big data applications. It provides", "doc_type":"usermanual2", - "kw":"Overview,Volcano Scheduling,User Guide", + "kw":"Volcano Scheduling Overview,Volcano Scheduling,User Guide", "search_title":"", "metedata":[ { @@ -4187,14 +4547,14 @@ "documenttype":"usermanual" } ], - "title":"Overview", + "title":"Volcano Scheduling Overview", "githuburl":"" }, { "uri":"cce_10_0722.html", "node_id":"cce_10_0722.xml", "product_code":"cce", - "code":"233", + "code":"253", "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", @@ -4212,7 +4572,7 @@ "uri":"cce_10_0768.html", "node_id":"cce_10_0768.xml", "product_code":"cce", - "code":"234", + "code":"254", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Resource Usage-based Scheduling", @@ -4230,8 +4590,8 @@ "uri":"cce_10_0773.html", "node_id":"cce_10_0773.xml", "product_code":"cce", - "code":"235", - "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", + "code":"255", + "des":"Bin packing is an optimization algorithm that aims to properly allocate resources to each job and get the jobs done using the minimum number of resources. After bin packi", "doc_type":"usermanual2", "kw":"Bin Packing,Resource Usage-based Scheduling,User Guide", "search_title":"", @@ -4248,7 +4608,7 @@ "uri":"cce_10_0766.html", "node_id":"cce_10_0766.xml", "product_code":"cce", - "code":"236", + "code":"256", "des":"Scheduling in a cluster is the process of binding pending pods to nodes, and is performed by a component called kube-scheduler or Volcano Scheduler. The scheduler uses a ", "doc_type":"usermanual2", "kw":"Descheduling,Resource Usage-based Scheduling,User Guide", @@ -4266,7 +4626,7 @@ "uri":"cce_10_0767.html", "node_id":"cce_10_0767.xml", "product_code":"cce", - "code":"237", + "code":"257", "des":"In scenarios such as node pool replacement and rolling node upgrade, an old resource pool needs to be replaced with a new one. To prevent the node pool replacement from a", "doc_type":"usermanual2", "kw":"Node Pool Affinity,Resource Usage-based Scheduling,User Guide", @@ -4284,7 +4644,7 @@ "uri":"cce_10_0789.html", "node_id":"cce_10_0789.xml", "product_code":"cce", - "code":"238", + "code":"258", "des":"Volcano Scheduler offers CPU and memory load-aware scheduling for pods and preferentially schedules pods to the node with the lightest load to balance node loads. This pr", "doc_type":"usermanual2", "kw":"Load-aware Scheduling,Resource Usage-based Scheduling,User Guide", @@ -4302,7 +4662,7 @@ "uri":"cce_10_0813.html", "node_id":"cce_10_0813.xml", "product_code":"cce", - "code":"239", + "code":"259", "des":"Volcano scheduling involves node filtering and scoring, which is used to filter the nodes meeting scheduling conditions and score the filtered nodes to find the one with ", "doc_type":"usermanual2", "kw":"Configuration Cases for Resource Usage-based Scheduling,Resource Usage-based Scheduling,User Guide", @@ -4320,7 +4680,7 @@ "uri":"cce_10_0774.html", "node_id":"cce_10_0774.xml", "product_code":"cce", - "code":"240", + "code":"260", "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", @@ -4338,7 +4698,7 @@ "uri":"cce_10_0775.html", "node_id":"cce_10_0775.xml", "product_code":"cce", - "code":"241", + "code":"261", "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", @@ -4356,7 +4716,7 @@ "uri":"cce_10_0776.html", "node_id":"cce_10_0776.xml", "product_code":"cce", - "code":"242", + "code":"262", "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", @@ -4374,7 +4734,7 @@ "uri":"cce_10_0777.html", "node_id":"cce_10_0777.xml", "product_code":"cce", - "code":"243", + "code":"263", "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", @@ -4392,7 +4752,7 @@ "uri":"cce_10_0778.html", "node_id":"cce_10_0778.xml", "product_code":"cce", - "code":"244", + "code":"264", "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", @@ -4410,7 +4770,7 @@ "uri":"cce_10_0425.html", "node_id":"cce_10_0425.xml", "product_code":"cce", - "code":"245", + "code":"265", "des":"In non-uniform memory access (NUMA) architecture, a NUMA node is a fundamental component that includes a processor and local memory. These nodes are physically separate b", "doc_type":"usermanual2", "kw":"NUMA Affinity Scheduling,Volcano Scheduling,User Guide", @@ -4428,7 +4788,7 @@ "uri":"cce_10_0709.html", "node_id":"cce_10_0709.xml", "product_code":"cce", - "code":"246", + "code":"266", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Cloud Native Hybrid Deployment", @@ -4446,7 +4806,7 @@ "uri":"cce_10_0384.html", "node_id":"cce_10_0384.xml", "product_code":"cce", - "code":"247", + "code":"267", "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", @@ -4464,10 +4824,10 @@ "uri":"cce_10_0020.html", "node_id":"cce_10_0020.xml", "product_code":"cce", - "code":"248", + "code":"268", "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", + "kw":"Networking", "search_title":"", "metedata":[ { @@ -4475,17 +4835,17 @@ "documenttype":"usermanual" } ], - "title":"Network", + "title":"Networking", "githuburl":"" }, { "uri":"cce_10_0010.html", "node_id":"cce_10_0010.xml", "product_code":"cce", - "code":"249", - "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", + "code":"269", + "des":"The CCE cluster network architecture is based on the Kubernetes native network model. Combined with the cloud infrastructure capabilities, the architecture builds a three", "doc_type":"usermanual2", - "kw":"Overview,Network,User Guide", + "kw":"Networking Overview,Networking,User Guide", "search_title":"", "metedata":[ { @@ -4493,17 +4853,17 @@ "documenttype":"usermanual" } ], - "title":"Overview", + "title":"Networking Overview", "githuburl":"" }, { "uri":"cce_10_0280.html", "node_id":"cce_10_0280.xml", "product_code":"cce", - "code":"250", + "code":"270", "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", + "kw":"Container Networks", "search_title":"", "metedata":[ { @@ -4511,17 +4871,17 @@ "documenttype":"usermanual" } ], - "title":"Container Network", + "title":"Container Networks", "githuburl":"" }, { "uri":"cce_10_0281.html", "node_id":"cce_10_0281.xml", "product_code":"cce", - "code":"251", - "des":"The container network assigns IP addresses to pods in a cluster and provides networking services. In CCE, you can select the following network models for your cluster:Clo", + "code":"271", + "des":"A 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:Cloud", "doc_type":"usermanual2", - "kw":"Overview,Container Network,User Guide", + "kw":"Overview,Container Networks,User Guide", "search_title":"", "metedata":[ { @@ -4536,7 +4896,7 @@ "uri":"cce_10_0678.html", "node_id":"cce_10_0678.xml", "product_code":"cce", - "code":"252", + "code":"272", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Cloud Native Network 2.0 Settings", @@ -4554,8 +4914,8 @@ "uri":"cce_10_0284.html", "node_id":"cce_10_0284.xml", "product_code":"cce", - "code":"253", - "des":"Cloud Native Network 2.0 is a proprietary, next-generation container network model that combines the elastic network interfaces (ENIs) and supplementary network interface", + "code":"273", + "des":"The proprietary, next-generation Cloud Native Network 2.0 combines the network interfaces and supplementary network interfaces of VPC. This allows you to bind network int", "doc_type":"usermanual2", "kw":"Cloud Native Network 2.0,Cloud Native Network 2.0 Settings,User Guide", "search_title":"", @@ -4572,10 +4932,10 @@ "uri":"cce_10_0906.html", "node_id":"cce_10_0906.xml", "product_code":"cce", - "code":"254", - "des":"If the pod subnet configured during CCE Turbo cluster creation cannot meet service expansion requirements, you can add a pod subnet for the cluster.This function is avail", + "code":"274", + "des":"If the pod subnet configured during CCE Turbo cluster creation cannot meet service expansion requirements, you can add a pod subnet for the cluster.This function is only ", "doc_type":"usermanual2", - "kw":"Configuring a Default Container Subnet for a CCE Turbo Cluster,Cloud Native Network 2.0 Settings,Use", + "kw":"Adding or Deleting the Default Pod Subnet of a CCE Turbo Cluster,Cloud Native Network 2.0 Settings,U", "search_title":"", "metedata":[ { @@ -4583,69 +4943,15 @@ "documenttype":"usermanual" } ], - "title":"Configuring a Default Container Subnet for a CCE Turbo Cluster", - "githuburl":"" - }, - { - "uri":"cce_10_0897.html", - "node_id":"cce_10_0897.xml", - "product_code":"cce", - "code":"255", - "des":"In Cloud Native Network 2.0, pods use ENIs or sub-ENIs of the VPC. You can configure a security group for a pod using a pod's annotation.Configure a security group in eit", - "doc_type":"usermanual2", - "kw":"Binding a Security Group to a Pod Using an Annotation,Cloud Native Network 2.0 Settings,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"cce", - "documenttype":"usermanual" - } - ], - "title":"Binding a Security Group to a Pod Using an Annotation", - "githuburl":"" - }, - { - "uri":"cce_10_0288.html", - "node_id":"cce_10_0288.xml", - "product_code":"cce", - "code":"256", - "des":"In Cloud Native Network 2.0, pods use VPC ENIs or sub-ENIs for networking. You can directly bind security groups and EIPs to pods. To bind CCE pods with security groups, ", - "doc_type":"usermanual2", - "kw":"Binding a Security Group to a Workload Using a Security Group Policy,Cloud Native Network 2.0 Settin", - "search_title":"", - "metedata":[ - { - "prodname":"cce", - "documenttype":"usermanual" - } - ], - "title":"Binding a Security Group to a Workload Using a Security Group Policy", - "githuburl":"" - }, - { - "uri":"cce_10_0196.html", - "node_id":"cce_10_0196.xml", - "product_code":"cce", - "code":"257", - "des":"In a CCE Turbo cluster, you can configure subnets and security groups for containers by namespace or workload using NetworkAttachmentDefinition CRDs. To configure a parti", - "doc_type":"usermanual2", - "kw":"Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configurati", - "search_title":"", - "metedata":[ - { - "prodname":"cce", - "documenttype":"usermanual" - } - ], - "title":"Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configuration", + "title":"Adding or Deleting the Default Pod Subnet of a CCE Turbo Cluster", "githuburl":"" }, { "uri":"cce_10_0603.html", "node_id":"cce_10_0603.xml", "product_code":"cce", - "code":"258", - "des":"In Cloud Native Network 2.0, each pod is associated with an ENI, providing a static IP address to the StatefulSet pods (container ENI). This is a common practice in acces", + "code":"275", + "des":"In Cloud Native Network 2.0, each pod is assigned a VPC network interface with a static IP address. This is particularly applicable to StatefulSet pods. This practice is ", "doc_type":"usermanual2", "kw":"Configuring a Static IP Address for a Pod,Cloud Native Network 2.0 Settings,User Guide", "search_title":"", @@ -4662,8 +4968,8 @@ "uri":"cce_10_0734.html", "node_id":"cce_10_0734.xml", "product_code":"cce", - "code":"259", - "des":"In Cloud Native Network 2.0, pods use VPC ENIs or sub-ENIs for networking. You can directly bind EIPs to pods.To associate an EIP with a pod, simply set the value of the ", + "code":"276", + "des":"In Cloud Native Network 2.0, pods use VPC elastic network interfaces or supplementary network interfaces for networking. You can directly bind and EIPs to pods.To associa", "doc_type":"usermanual2", "kw":"Configuring an EIP for a Pod,Cloud Native Network 2.0 Settings,User Guide", "search_title":"", @@ -4680,7 +4986,7 @@ "uri":"cce_10_0651.html", "node_id":"cce_10_0651.xml", "product_code":"cce", - "code":"260", + "code":"277", "des":"In Cloud Native Network 2.0, static public IP addresses (EIPs) can be assigned to StatefulSets or pods created directly.You can configure a static EIP for a pod only in C", "doc_type":"usermanual2", "kw":"static EIPs,Configuring a Static EIP for a Pod,Cloud Native Network 2.0 Settings,User Guide", @@ -4698,10 +5004,10 @@ "uri":"cce_10_0604.html", "node_id":"cce_10_0604.xml", "product_code":"cce", - "code":"261", - "des":"By default, pods with IPv6 dual-stack ENIs can access only the IPv6 private network. To access the public network, configure shared bandwidth for such pods.Only CCE Turbo", + "code":"278", + "des":"By default, pods with IPv6 dual-stack network interfaces can access only the IPv6 private network. To access the public network, configure shared bandwidth for such pods.", "doc_type":"usermanual2", - "kw":"Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack ENIs,Cloud Native Network 2.0 Settings,U", + "kw":"Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack Network Interfaces,Cloud Native Network ", "search_title":"", "metedata":[ { @@ -4709,14 +5015,119 @@ "documenttype":"usermanual" } ], - "title":"Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack ENIs", + "title":"Configuring Shared Bandwidth for a Pod with IPv6 Dual-Stack Network Interfaces", + "githuburl":"" + }, + { + "uri":"cce_10_1077.html", + "node_id":"cce_10_1077.xml", + "product_code":"cce", + "code":"279", + "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 Security Group for a Workload in a CCE Turbo Cluster", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"Configuring a Security Group for a Workload in a CCE Turbo Cluster", + "githuburl":"" + }, + { + "uri":"cce_10_1078.html", + "node_id":"cce_10_1078.xml", + "product_code":"cce", + "code":"280", + "des":"In CCE Turbo clusters, pods can be directly bound to security groups using VPC network interfaces or supplementary network interfaces. CCE Turbo provides multi-dimensiona", + "doc_type":"usermanual2", + "kw":"Comparison of Workload Security Group Configuration Methods,Configuring a Security Group for a Workl", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"Comparison of Workload Security Group Configuration Methods", + "githuburl":"" + }, + { + "uri":"cce_10_0897.html", + "node_id":"cce_10_0897.xml", + "product_code":"cce", + "code":"281", + "des":"In cloud native network 2.0, pods use VPC network interfaces or supplementary network interfaces for networking, which allow you to configure security groups. You can bin", + "doc_type":"usermanual2", + "kw":"Binding a Security Group to a Pod Using an Annotation,Configuring a Security Group for a Workload in", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Binding a Security Group to a Pod Using an Annotation", + "githuburl":"" + }, + { + "uri":"cce_10_0288.html", + "node_id":"cce_10_0288.xml", + "product_code":"cce", + "code":"282", + "des":"In Cloud Native Network 2.0, pods use VPC elastic network interfaces or supplementary network interfaces for networking. You can directly bind security groups and EIPs to", + "doc_type":"usermanual2", + "kw":"Binding a Security Group to a Workload Using a Security Group Policy,Configuring a Security Group fo", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Binding a Security Group to a Workload Using a Security Group Policy", + "githuburl":"" + }, + { + "uri":"cce_10_1079.html", + "node_id":"cce_10_1079.xml", + "product_code":"cce", + "code":"283", + "des":"In Cloud Native Network 2.0, pods can be directly bound to security groups using VPC network interfaces or supplementary network interfaces. CCE Turbo allows you to confi", + "doc_type":"usermanual2", + "kw":"Using Node Pool Settings to Bind the Default Security Group to Pods in the Node Pool,Configuring a S", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"Using Node Pool Settings to Bind the Default Security Group to Pods in the Node Pool", + "githuburl":"" + }, + { + "uri":"cce_10_0196.html", + "node_id":"cce_10_0196.xml", + "product_code":"cce", + "code":"284", + "des":"In a CCE Turbo cluster, you can configure subnets and security groups for containers by namespace or workload using NetworkAttachmentDefinition CRDs. To configure a parti", + "doc_type":"usermanual2", + "kw":"Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configurati", + "search_title":"", + "metedata":[ + { + "prodname":"cce", + "documenttype":"usermanual" + } + ], + "title":"Binding a Subnet and Security Group to a Namespace or Workload Using a Container Network Configuration", "githuburl":"" }, { "uri":"cce_10_0904.html", "node_id":"cce_10_0904.xml", "product_code":"cce", - "code":"262", + "code":"285", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"VPC Network Settings", @@ -4734,7 +5145,7 @@ "uri":"cce_10_0283.html", "node_id":"cce_10_0283.xml", "product_code":"cce", - "code":"263", + "code":"286", "des":"The VPC network model seamlessly combines VPC routing with the underlying network, making it ideal for high-performance scenarios. However, the maximum number of nodes al", "doc_type":"usermanual2", "kw":"VPC Network Model,VPC Network Settings,User Guide", @@ -4752,10 +5163,10 @@ "uri":"cce_10_0680.html", "node_id":"cce_10_0680.xml", "product_code":"cce", - "code":"264", + "code":"287", "des":"If the container CIDR block configured during CCE cluster creation cannot meet service expansion requirements, you can add a container CIDR block for the cluster.This fun", "doc_type":"usermanual2", - "kw":"Adding a Container CIDR Block for a Cluster,VPC Network Settings,User Guide", + "kw":"Expanding the Container CIDR Block of a Cluster That Uses a VPC Network,VPC Network Settings,User Gu", "search_title":"", "metedata":[ { @@ -4763,14 +5174,14 @@ "documenttype":"usermanual" } ], - "title":"Adding a Container CIDR Block for a Cluster", + "title":"Expanding the Container CIDR Block of a Cluster That Uses a VPC Network", "githuburl":"" }, { "uri":"cce_10_0677.html", "node_id":"cce_10_0677.xml", "product_code":"cce", - "code":"265", + "code":"288", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Tunnel Network Settings", @@ -4788,8 +5199,8 @@ "uri":"cce_10_0282.html", "node_id":"cce_10_0282.xml", "product_code":"cce", - "code":"266", - "des":"A container tunnel network creates a separate network plane for containers by using tunnel encapsulation on the host network plane. The container tunnel network of a CCE ", + "code":"289", + "des":"A container tunnel network creates a separate network plane for containers by using tunnel encapsulation on the host network plane. This network model uses VXLAN for tunn", "doc_type":"usermanual2", "kw":"Tunnel Network Model,Tunnel Network Settings,User Guide", "search_title":"", @@ -4806,7 +5217,7 @@ "uri":"cce_10_0675.html", "node_id":"cce_10_0675.xml", "product_code":"cce", - "code":"267", + "code":"290", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual2", "kw":"Pod Network Settings", @@ -4824,8 +5235,8 @@ "uri":"cce_10_0402.html", "node_id":"cce_10_0402.xml", "product_code":"cce", - "code":"268", - "des":"Kubernetes allows pods to directly use the host/node network. When a pod is configured with hostNetwork: true, applications running in the pod can directly view the netwo", + "code":"291", + "des":"Generally, containers in a pod use the network set up using Kubernetes network plugins. These plugins ensure network communications between pods. However, you may need to", "doc_type":"usermanual2", "kw":"Configuring hostNetwork for Pods,Pod Network Settings,User Guide", "search_title":"", @@ -4842,7 +5253,7 @@ "uri":"cce_10_0382.html", "node_id":"cce_10_0382.xml", "product_code":"cce", - "code":"269", + "code":"292", "des":"Bandwidth preemption occurs between different containers deployed on the same node, which may cause service jitter. You can configure bandwidth limitation for the pod to ", "doc_type":"usermanual2", "kw":"Configuring QoS for a Pod,Pod Network Settings,User Guide", @@ -4860,8 +5271,8 @@ "uri":"cce_10_0059.html", "node_id":"cce_10_0059.xml", "product_code":"cce", - "code":"270", - "des":"Network policies are designed by Kubernetes to restrict pod access. It is equivalent to a firewall at the application layer to enhance network security. The capabilities ", + "code":"293", + "des":"Network policies are designed by Kubernetes to restrict pod access. Like a firewall at the application layer, network policies enhance network security. The capabilities ", "doc_type":"usermanual2", "kw":"Configuring Network Policies to Restrict Pod Access,Pod Network Settings,User Guide", "search_title":"", @@ -4878,8 +5289,8 @@ "uri":"cce_10_0945.html", "node_id":"cce_10_0945.xml", "product_code":"cce", - "code":"271", - "des":"DataPlane V2 can be enabled for clusters that use Cloud Native 2.0 networks. After this function is enabled, eBPF redirection will be enabled for the capability of networ", + "code":"294", + "des":"DataPlane V2 can be enabled for clusters that use VPC networks or Cloud Native 2.0 networks. Once enabled, eBPF redirection is supported, which allows the use of network ", "doc_type":"usermanual2", "kw":"DataPlane V2 Network Acceleration,Pod Network Settings,User Guide", "search_title":"", @@ -4896,10 +5307,10 @@ "uri":"cce_10_0247.html", "node_id":"cce_10_0247.xml", "product_code":"cce", - "code":"272", + "code":"295", "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", + "kw":"Services", "search_title":"", "metedata":[ { @@ -4907,17 +5318,17 @@ "documenttype":"usermanual" } ], - "title":"Service", + "title":"Services", "githuburl":"" }, { "uri":"cce_10_0249.html", "node_id":"cce_10_0249.xml", "product_code":"cce", - "code":"273", - "des":"After a pod is created, accessing it directly can result in certain problems:The pod can be deleted and recreated at any time by a controller such as a Deployment. If the", + "code":"296", + "des":"In Kubernetes, a Service makes an application running on a set of pods network-accessible. It provides a consistent DNS name for these pods and distributes traffic across", "doc_type":"usermanual2", - "kw":"Overview,Service,User Guide", + "kw":"kube-proxy,iptables,IPVS,Service Overview,Services,User Guide", "search_title":"", "metedata":[ { @@ -4925,17 +5336,17 @@ "documenttype":"usermanual" } ], - "title":"Overview", + "title":"Service Overview", "githuburl":"" }, { "uri":"cce_10_0011.html", "node_id":"cce_10_0011.xml", "product_code":"cce", - "code":"274", - "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

Solution

Do not run an untrusted container image in the cluster before the vulnerabilities are fixed.

-

CCE will release a new version of the add-on to fix these vulnerabilities. For details, see CCE AI Suite (NVIDIA GPU) Release History.

+

CCE has released a new version of the CCE AI Suite (NVIDIA GPU) add-on to fix these vulnerabilities. Upgrade the add-on to the fixed version. For details, see CCE AI Suite (NVIDIA GPU) Release History.

Helpful Links

NVIDIA Container Toolkit Security Bulletin: https://nvidia.custhelp.com/app/answers/detail/a_id/5659

diff --git a/docs/cce/umn/cce_01_0300.html b/docs/cce/umn/cce_01_0300.html index 64e8fb822..182de047c 100644 --- a/docs/cce/umn/cce_01_0300.html +++ b/docs/cce/umn/cce_01_0300.html @@ -8,7 +8,16 @@ -

2025-07-25

+

2025-09-12

+ +

Add:

+ +

Update:

+ + + +

2025-07-25

Added Notice of the NVIDIA Container Toolkit Container Escape Vulnerabilities (CVE-2025-23266 and CVE-2025-23267).

@@ -48,7 +57,7 @@

2025-03-31

Update:

- +

2025-03-10

diff --git a/docs/cce/umn/cce_10_0003.html b/docs/cce/umn/cce_10_0003.html index 918af2b25..1663fcf25 100644 --- a/docs/cce/umn/cce_10_0003.html +++ b/docs/cce/umn/cce_10_0003.html @@ -4,11 +4,11 @@

Scenario

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 node. If a node is unavailable because you modify the node configuration, you can reset the node to rectify the fault.

-

Notes and Constraints

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

Notes and Constraints

  • Node resetting in CCE standard clusters or CCE Turbo clusters is supported for cluster versions v1.13 and later.
-

Precautions

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

Precautions

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

Resetting Nodes in the Default Pool

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

    Compute Settings +

    Resetting Nodes in the Default Pool

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

      Compute Settings
      - @@ -112,14 +112,16 @@ - - @@ -130,7 +132,7 @@

      Resetting Nodes in a Node Pool

      • When resetting a node in a node pool, you can only change its storage configuration. All other configurations will follow the settings of the node pool.
      • Resetting a node will execute the pre- and post-installation scripts in the current node pool and update the security group configurations to those of the node pool.
      -
      1. Log in to the CCE console and click the cluster name to access the cluster console.
      2. In the navigation pane, choose Nodes. On the displayed page, click the Nodes tab.
      3. In the node list of the target node pool, select a node to be reset and choose More > Reset Node in the Operation column.
      4. Modify the node storage parameters.

        +

        1. Log in to the CCE console and click the cluster name to access the cluster console.
        2. In the navigation pane, choose Nodes. On the displayed page, click the Nodes tab.
        3. In the node list of the target node pool, select a node to be reset and choose More > Reset Node in the Operation column.
        4. Modify the node storage parameters.

      Table 1 Configuration parameters

      Parameter

      Description

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

      Data Disk

      • At least one default data disk must be added for storing container runtime and kubelet components if System Component Storage is set to Data Disk. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable. This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.
      • If System Component Storage is set to System Disk, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.
      +
      • At least one default data disk must be added for storing container runtime and kubelet components if System Component Storage is set to Data Disk. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable.
      • If System Component Storage is set to System Disk, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.

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

      -

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

      +

      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.

      Pre-installation Command

      Installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.

      +

      Installation script command. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.

      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

      Installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.

      -

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

      +

      Installation script command. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.

      +
      The script will be executed after Kubernetes software is installed, which does not affect the installation. During post-installation script execution, pods can be scheduled normally. However, if the script execution times out, node installation will fail. To prevent pods from being scheduled to nodes with incomplete script execution, enable the option to schedule pods only after the post-installation script execution completes.
      CAUTION:

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

      +
      +
      - @@ -94,7 +94,7 @@
      Table 4 Configuration parameters

      Parameter

      Description

      diff --git a/docs/cce/umn/cce_10_0004.html b/docs/cce/umn/cce_10_0004.html index d0603b5f5..a95557391 100644 --- a/docs/cce/umn/cce_10_0004.html +++ b/docs/cce/umn/cce_10_0004.html @@ -29,7 +29,7 @@

      New: node.kubernetes.io/baremetal

      Old: failure-domain.beta.kubernetes.io/is-baremetal

      Whether the node is a bare metal node

      +

      Whether it is a bare metal node

      false indicates that the node is not a bare metal node.
      -

      Adding or Deleting a Node Label

      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, select the target node and click Labels and Taints in the upper left corner.
      3. In the displayed dialog box, click Add operation under Batch Operation, and then choose Add/Update or Delete.

        Enter the key and value of the label to be added or deleted, and click OK.

        +

        Adding or Deleting a Node Label

        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, select the target node and click Labels and Taints in the upper left corner.
        3. In the displayed dialog box, click Add operation under Batch Operation, and then choose Add/Update or Delete.

          Enter the key and value of the label to be added or deleted, and click OK.

          For example, the key is deploy_qa and the value is true, indicating that the node is used to deploy the QA (test) environment.

        4. After the label is added, check the added label in node data.
        diff --git a/docs/cce/umn/cce_10_0006.html b/docs/cce/umn/cce_10_0006.html index 428e6f516..9c0e119a6 100644 --- a/docs/cce/umn/cce_10_0006.html +++ b/docs/cce/umn/cce_10_0006.html @@ -1,6 +1,6 @@ -

        Overview

        +

        Workload Overview

        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 an abstract model of a group of pods in Kubernetes. Workloads in Kubernetes are classified as Deployments, StatefulSets, DaemonSets, jobs, and cron jobs.

        CCE provides Kubernetes-native container deployment and management and supports lifecycle management of container workloads, including creation, configuration, monitoring, auto scaling, upgrade, uninstall, service discovery, and load balancing.

        Overview of Pods

        Pods are the smallest unit that you can create or deploy in Kubernetes. Each pod comprises one or more containers, shared storage (volumes), a unique IP address, and container runtime policies.

        diff --git a/docs/cce/umn/cce_10_0007.html b/docs/cce/umn/cce_10_0007.html index 58a09e8bc..f07fbe6c8 100644 --- a/docs/cce/umn/cce_10_0007.html +++ b/docs/cce/umn/cce_10_0007.html @@ -1,7 +1,7 @@

        Managing Workloads

        -

        Scenario

        After a workload is created, you can upgrade, log, monitor, roll back, or delete the workload, as well as edit its YAML file. +

        Scenario

        After a workload is created, you can upgrade it, edit its YAML file, view logs and monitoring data, roll it back, and delete it.
        -
        Table 1 Workload/Job management

        Operation

        Description

        @@ -10,7 +10,7 @@

        Monitor

        You can view the CPU and memory usage of workloads and pods on the CCE console.

        +

        You can view the CPU and memory usage of workloads and pods on the CCE console to determine the resource specifications you may need.

        View Log

        @@ -71,52 +71,52 @@

        Monitoring a Workload

        You can view the CPU and memory usage of Deployments and pods on the CCE console to determine the resource specifications you may need. This section uses a Deployment as an example to describe how to monitor a workload.

        -
        1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
        2. Click the Deployments tab and click Monitor of the target workload. On the page that is displayed, you can view CPU usage and memory usage of the workload.
        3. Click the workload name. On the Pods tab page, click the Monitor of the target pod to view its CPU and memory usage.
        +
        1. Log in to the CCE console, go to the console of an existing cluster, and choose Workloads in the navigation pane.
        2. Click the Deployments tab and click Monitor of the target workload. On the page that is displayed, you can view CPU usage and memory usage of the workload.
        3. Click the workload name. On the Pods tab page, click the Monitor of the target pod to view its CPU and memory usage.

        Viewing Logs

        You can view logs of Deployments, StatefulSets, DaemonSets, and jobs. This section uses a Deployment as an example to describe how to view logs.

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

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

          +
          1. Log in to the CCE console, go to the console of an existing cluster, and choose Workloads in the navigation pane.
          2. Click the Deployments tab and click 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 Collecting Container Logs Using ICAgent.

        Upgrading a Workload

        You quickly upgrade Deployments, StatefulSets, and DaemonSets on the CCE console.

        This section uses a Deployment as an example to describe how to upgrade a workload.

        -

        Before replacing an image or image version, upload the new image to the SWR service.

        -
        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 Upgrade of the target workload.

          • Workloads cannot be upgraded in batches.
          • Before performing an in-place StatefulSet upgrade, you must manually delete old pods. Otherwise, the upgrade status is always displayed as Processing.
          +

          Before replacing an image or image tag, upload the new image to the SWR service.

          +
          1. Log in to the CCE console,go to the console of an existing cluster, and choose Workloads in the navigation pane.
          2. Click the Deployments tab and click Upgrade of the target workload.

            • Workloads cannot be upgraded in batches.
            • Before performing an in-place StatefulSet upgrade, you must manually delete old pods. Otherwise, the upgrade status is always displayed as Processing.

          3. Upgrade the workload based on service requirements. The method for setting parameter is the same as that for creating a workload.
          4. After the update is complete, click Upgrade Workload, manually confirm the YAML file, and submit the upgrade.

          Editing a YAML file

          You can modify and download YAML files of Deployments, StatefulSets, DaemonSets, CronJobs, and pods on the CCE console. YAML files of jobs can only be viewed, copied, and downloaded. This section uses a Deployment as an example to describe how to edit the YAML file.

          -
          1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
          2. Click the Deployments tab and choose More > Edit YAML in the Operation column of the target workload. In the dialog box that is displayed, modify the YAML file.
          3. Click OK.
          4. (Optional) In the Edit YAML window, click Download to download the YAML file.
          +
          1. Log in to the CCE console, go to the console of an existing cluster, and choose Workloads in the navigation pane.
          2. Click the Deployments tab and choose More > Edit YAML in the Operation column of the target workload. In the dialog box that is displayed, modify the YAML file.
          3. Click OK.
          4. (Optional) In the Edit YAML window, click Download to download the YAML file.

          Rolling Back a Workload (Available Only for Deployments)

          CCE records the release history of all Deployments. You can roll back a Deployment to a specified version.

          -
          1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
          2. Click the Deployments tab and choose More > Roll Back in the Operation column of the target workload.
          3. Switch to the Change History tab page, click Roll Back to This Version of the target version, manually confirm the YAML file, and click OK.
          +
          1. Log in to the CCE console, go to the console of an existing cluster, and choose Workloads in the navigation pane.
          2. Click the Deployments tab and choose More > Roll Back in the Operation column of the target workload.
          3. Switch to the Change History tab page, click Roll Back to This Version of the target version, manually confirm the YAML file, and click OK.

          Redeploying a Workload

          After you redeploy a workload, all pods in the workload will be restarted. This section uses Deployments as an example to illustrate how to redeploy a workload.

          -
          1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
          2. Click the Deployments tab and choose More > Redeploy in the Operation column of the target workload.
          3. In the dialog box that is displayed, click Yes to redeploy the workload.
          +
          1. Log in to the CCE console, go to the console of an existing cluster, and choose Workloads in the navigation pane.
          2. Click the Deployments tab and choose More > Redeploy in the Operation column of the target workload.
          3. In the dialog box that is displayed, click Yes to redeploy the workload.

          Disabling/Enabling Upgrade (Available Only for Deployments)

          Only Deployments support this operation.

          • After the upgrade is disabled, the upgrade command can be delivered but will not be applied to the pods.

            If you are performing a rolling upgrade, the rolling upgrade stops after the disabling upgrade command is delivered. In this case, the new and old pods co-exist.

          • After the upgrade is enabled, a Deployment can be upgraded or rolled back. Its pods will inherit the latest updates of the Deployment. If they are inconsistent, the pods will be upgraded automatically according to the latest information of the Deployment.

          Deployments in the disable upgrade state cannot be rolled back.

          -
          1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
          2. Click the Deployments tab and choose More > Disable/Enable Upgrade in the Operation column of the workload.
          3. In the dialog box that is displayed, click Yes.
          +
          1. Log in to the CCE console, go to the console of an existing cluster, and choose Workloads in the navigation pane.
          2. Click the Deployments tab and choose More > Disable/Enable Upgrade in the Operation column of the workload.
          3. In the dialog box that is displayed, click Yes.
          -

          Managing Labels

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

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

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

            +

            Managing Labels

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

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

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

            Deleting a Workload/Job

            You can delete a workload or job that is no longer needed. Deleted workloads or jobs cannot be recovered. This section uses a Deployment as an example to describe how to delete a workload.

            -
            1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
            2. In the same row as the workload you will delete, choose Operation > More > Delete.

              Read the system prompts carefully. A workload cannot be recovered after it is deleted. Exercise caution when performing this operation.

              +
              1. Log in to the CCE console, go to the console of an existing cluster, and choose Workloads in the navigation pane.
              2. In the same row as the workload you will delete, choose Operation > More > Delete.

                Read the system prompts carefully. A workload cannot be recovered after it is deleted. Exercise caution when performing this operation.

              3. Click Yes.

                • If the node where the pod is located is unavailable or shut down and the workload cannot be deleted, you can forcibly delete the pod from the pod list on the workload details page.
                • Ensure that the storage volumes to be deleted are not used by other workloads. If these volumes are imported or have snapshots, you can only unbind them.

            Events

            This section uses a Deployment as an example to describe how to view events of a workload. To view the event of a job or CronJob, click View Event in the Operation column of the target workload.

            -
            1. Log in to the CCE console, go to an existing cluster, and choose Workloads in the navigation pane.
            2. On the Deployments tab page, click the target workload. In the Pods tab page, click the View Events to view the event name, event type, number of occurrences, Kubernetes event, first occurrence time, and last occurrence time.

              Event data will be retained for one hour and then automatically deleted.

              +
              1. Log in to the CCE console, go to the console of an existing cluster, and choose Workloads in the navigation pane.
              2. On the Deployments tab page, click the target workload. In the Pods tab page, click the View Events to view the event name, event type, number of occurrences, Kubernetes event, first occurrence time, and last occurrence time.

                Event data will be retained for one hour and then automatically deleted.

              diff --git a/docs/cce/umn/cce_10_0009.html b/docs/cce/umn/cce_10_0009.html index a6e865329..16668e56c 100644 --- a/docs/cce/umn/cce_10_0009.html +++ b/docs/cce/umn/cce_10_0009.html @@ -1,30 +1,145 @@

              Using Third-Party Images

              -

              Scenario

              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 authentication (using your account and password). CCE uses the secret-based authentication to pull images. Therefore, create a secret for an image repository before pulling images from the repository.

              +

              Third-party images are container images provided by organizations or individuals other than the official image repository and SWR image repository. These images typically contain custom applications, tools, or specific versions of OSs to meet particular service requirements. In a CCE standard or Turbo cluster, you can create workloads using third-party images pulled through secret authentication. For more information, see Images | Kubernetes.

              +

              Prerequisites

              If third-party images are used, the CCE standard or Turbo cluster must be able to access the network environment where the third-party image repository is deployed. The network access types include:

              +
              • Intranet: If the third-party image repository supports intranet access, consider the following scenarios:
                • If the third-party image repository is in the same VPC as the cluster, pods can directly pull images over the intranet without additional configurations.
                • If the third-party image repository and the cluster are in different VPCs in the same region, you can use a VPC peering connection to enable network connectivity between the two VPCs. Pods can then directly pull images over the intranet.
                +
              • Internet: If the third-party image repository is accessible over the Internet, pods can pull images directly. In this case, ensure the pods can access the Internet using one of the following methods:

                Ensure sufficient bandwidth when pulling images over the Internet. Insufficient bandwidth may cause slow or failed image pulls.

                +
                +
                • In a standard or Turbo cluster, configure an SNAT rule to enable all pods in the cluster to access the Internet. After the configuration, pods can pull images directly over the Internet. For details, see Accessing the Internet from a Container.
                • In a standard cluster, bind an EIP to the node running the workload. This allows all workloads on that node to access the Internet.
                +
              • Direct Connect or VPN: To use images from an on-premises image repository, use Direct Connect or VPN to connect the on-premises network to the cluster's VPC. Once the network environment is connected to the VPC, no additional configuration is needed.
              -

              Prerequisites

              The node where the workload is running is accessible from public networks.

              +

              Using the Console

              To create a secret on the console and pull a third-party image to create a workload, follow these steps.

              +
              1. Create a cluster secret to authenticate and pull images from a third-party repository if authentication is required.

                1. Log in to the CCE console.
                2. Click the name of the target cluster to access the cluster.
                3. In the navigation pane, choose ConfigMaps and Secrets. On the Secrets tab, click Create Secret.
                4. In the Create Secret dialog box, configure parameters based on Table 1. For more details, see Creating a Secret.
                +

                + +
                + + + + + + + + + + + + + + + + + +
                Table 1 Parameters for creating a secret

                Parameter

                +

                Example Value

                +

                Description

                +

                Name

                +

                test

                +

                Name for the secret.

                +

                Enter up to 253 characters, starting and ending with a lowercase letter or digit. Only lowercase letters, digits, hyphens (-), and periods (.) are allowed.

                +

                Secret Type

                +

                kubernetes.io/dockerconfigjson

                +

                Type of the secret.

                +

                The value is fixed at kubernetes.io/dockerconfigjson, indicating that the secret is used for authentication when third-party images are pulled.

                +

                Data

                +

                Image Repository Address: www.example.com

                +

                Username: ssl

                +

                Password: xxx

                +
                • Image Repository Address: Enter the address of the third-party image repository.
                • Username: Enter the username for accessing the third-party image repository.
                • Password: Enter the password for accessing the third-party image repository.
                +
                -

                Using the Console

                1. Create a secret for accessing a third-party image repository.

                  Click the cluster name to access the cluster console. In the navigation pane, choose ConfigMaps and Secrets. On the Secrets tab page, click Create Secret in the upper right corner. Set Secret Type to kubernetes.io/dockerconfigjson. For details, see Creating a Secret.

                  -

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

                  -

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

              2. In the navigation pane, choose Workloads. In the upper right corner of the displayed page, click Create Workload. On the Create Workload page, set Image Name (Container Settings > Container Information > Basic Info) to the third-party image path. Select the secret created in 1 for Image Access Credential.

                If you do not specify a domain name when entering a third-party image address, for example, nginx:latest, the image will be pulled from docker.io by default. To specify the default image pull address, configure the Modify Image Repository Configuration parameter in the container engine configuration of the node pool.

                +
                +

                +

              3. Configure other parameters and click Create Workload. If the workload status is Running, the third-party image has been pulled.
              -

              Using kubectl

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

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

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

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

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

                A kubernetes.io/dockerconfigjson secret is used for authentication when you obtain a private image. The following is an example of using the myregistrykey for authentication.
                apiVersion: v1
-kind: Pod
+
                Using kubectl
                1. Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
                2. If the third-party image repository has an account and password, you need to create a secret in the cluster as the identity credential for pulling images.
                  1. Create a secret. The secret type is kubernetes.io/dockerconfigjson by default, which indicates that the secret is used for authentication when third-party images are pulled.
                    kubectl create secret docker-registry test  -n default --docker-server=www.example.com --docker-username=ssl --docker-password=xxx --docker-email=example@123.com
                    
+
                    In the command, test indicates the secret name, default indicates the namespace where the secret is located, and other parameters are described in the following table.
                    
+
+
                    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                    Table 2 Secret parameters
                    Parameter
                    
+
                    Example Value
                    
+
                    Description
                    
+
                    docker-server
                    
+
                    www.example.com
                    
+
                    Enter the address of the third image repository.
                    
+
                    docker-username
                    
+
                    ssl
                    
+
                    Enter the username for accessing the third-party image repository.
                    
+
                    docker-password
                    
+
                    xxx
                    
+
                    Enter the password for accessing the third-party image repository.
                    
+
                    docker-email
                    
+
                    example@123.com
                    
+
                    Email address of the third-party image repository. This parameter is optional.
                    
+
                    
+
                    
+
                    Information similar to the following is displayed:
                    
+
                    secret/test created
                    
+
                  2. Check whether the secret has been created.
                    kubectl get secret
                    
+
                    If the following information is displayed, the secret has been created:
                    
+
                    NAME             TYPE                             DATA   AGE
+default-secret   kubernetes.io/dockerconfigjson   1      41h
+paas.elb         cfe/secure-opaque                1      41h
+test             kubernetes.io/dockerconfigjson   1      16s
                    
+
                  
+
                3. Create a workload using a third-party image.
                  1. Create a YAML file for creating a workload. In this example, the file name is deployment.yaml. You can change it as needed.
                    vim deployment.yaml
                    
+
                    The file content is as follows:
                    apiVersion: apps/v1
+kind: Deployment
 metadata:
-  name: foo
-  namespace: default
+  name: foo
+  namespace: default
 spec:
-  containers:
-    - name: foo
-      image: www.3rdregistry.com/janedoe/awesomeapp:v1
-  imagePullSecrets:
-    - name: myregistrykey              # Use the created secret.
                    
+  replicas: 1
+  selector:
+    matchLabels:
+      app: foo
+  strategy:
+    type: RollingUpdate
+  template:
+    metadata:
+      labels:
+        app: foo
+    spec:
+      containers:
+      - image: www.example.com/janedoe/awesomeapp:v1    # Third-party image path
+        imagePullPolicy: Always
+        name: foo
+      imagePullSecrets:
+      - name: test    # Use the created secret for identity authentication when images are pulled.
                +

                If you do not specify a domain name when entering a third-party image address, for example, nginx:latest, the image will be pulled from docker.io by default. To specify the default image pull address, configure the Modify Image Repository Configuration parameter in the container engine configuration of the node pool.

                +
                +
              4. Create the workload.
                kubectl create -f deployment.yaml
                +

                If information similar to the following is displayed, the workload is being created:

                +
                deployment.apps/foo created
                +
              5. Check the workload status.
                kubectl get deployment
                +

                If all the pods of the workload are available, the workload has been created.

                +
                NAME     READY   UP-TO-DATE   AVAILABLE   AGE
+foo      1/1     1            1           4m59s
                +

            diff --git a/docs/cce/umn/cce_10_0010.html b/docs/cce/umn/cce_10_0010.html index a99833169..23d0965f6 100644 --- a/docs/cce/umn/cce_10_0010.html +++ b/docs/cce/umn/cce_10_0010.html @@ -1,38 +1,41 @@ -

            Overview

            -

            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 number is also affected by the container network. For details, see the container network model.

              -
            • Container Network

              A container network assigns IP addresses to pods in a cluster. CCE inherits the IP-Per-Pod-Per-Network network model of Kubernetes. That is, each pod has an independent IP address on a network plane and all containers in a pod share the same network namespace. All pods in a cluster exist in a directly connected flat network. They can access each other through their IP addresses without using NAT. Kubernetes only provides a network mechanism for pods, but does not directly configure pod networks. The configuration of pod networks is implemented by specific container network add-ons. The container network add-ons are responsible for configuring networks for pods and managing container IP addresses.

              -

              Currently, CCE supports the following container network models:

              -
              • Container tunnel network: The container tunnel network is constructed on but independent of the node network through tunnel encapsulation. This network model uses VXLAN to encapsulate Ethernet packets into UDP packets and transmits them in tunnels. Open vSwitch serves as the backend virtual switch.
              • VPC network: The VPC network model seamlessly combines VPC routing with the underlying network, making it ideal for high-performance scenarios. However, the maximum number of nodes allowed in a cluster is determined by the VPC route quota. Each node is assigned a CIDR block of a fixed size. The VPC network model outperforms the container tunnel network model in terms of performance because it does not have tunnel encapsulation overhead. In addition, as VPC routing includes routes to node IP addresses and the container CIDR block, container pods in a cluster can be directly accessed from outside the cluster.
              • Developed by CCE, Cloud Native Network 2.0 deeply integrates Elastic Network Interfaces (ENIs) and Sub Network Interfaces (sub-ENIs) of VPC. Container IP addresses are allocated from the VPC CIDR block. ELB passthrough networking is supported to direct access requests to containers. Security groups and EIPs are bound to deliver high performance.
              -

              The performance, networking scale, and application scenarios of a container network vary according to the container network model. For details about the functions and features of different container network models, see Overview.

              -
            • Service Network

              Service is also a Kubernetes object. Each Service has a static IP address. When creating a cluster on CCE, you can specify the Service CIDR block. The Service CIDR block cannot overlap with the node or container CIDR block. The Service CIDR block can be used only within a cluster.

              -
            +

            Networking Overview

            +

            The CCE cluster network architecture is based on the Kubernetes native network model. Combined with the cloud infrastructure capabilities, the architecture builds a three-layer communication system covering nodes, containers, and services. It is built to efficiently forward intra-cluster and inter-cluster traffic, discover services, and isolate networks. It meets the requirements of all scenarios that cover small- and medium-sized applications and large-scale microservice architectures.

            +

            You can learn about the cluster network from the following aspects:

            +
            • Cluster network structure (Cluster Network Structure): A cluster consists of multiple nodes, and each node runs multiple pods (containers). To ensure the communications between nodes, between nodes and pods, and between pods, a cluster requires:
              • A node network: enables all nodes in a cluster to communicate with each other.
              • A container network: enables all pods in a cluster to communicate with each other using IP addresses without NAT.
              • A Service network: ensures Services in a cluster can be accessed by other pods or Services in that cluster through stable virtual IP addresses.
              +
            • Pod access in a cluster: Kubernetes provides Services (Service) and ingresses (Ingress) for pod access. This section summarizes common network access scenarios. You can select the appropriate scenario based on site requirements. For details about the network access scenarios, see Access Scenarios.
            +

            Cluster Network Structure

            Cluster networks are the core of Kubernetes. They ensure that containers in a cluster can communicate with each other and with external systems. There are:

            +
            • Node network: CCE uses VPC subnets as the node network of a cluster. The available IP addresses of a subnet limit the maximum number of nodes that can be created in a cluster. For example, a subnet with a mask of /24 can allocate a maximum of 254 node IP addresses. The number of nodes that can be created in a cluster is also affected by the container network. For details, see container network models.
            • Container network: Pods in a cluster are allocated independent IP addresses. All pods in a cluster are on a flat network and can be accessed using their IP addresses without NAT. Kubernetes uses Container Network Interface (CNI) to standardize the network between containers. Network model plugins are used to allocate independent IP addresses to pods for flat network communications in a cluster. Different network models have different allocation principles.
              Figure 1 Container network
              +

              Currently, CCE supports the following container network models:

              +
              • Container tunnel network: This network model is constructed based on the node network through tunnel encapsulation, but it is independent of the node network. It uses VXLAN to encapsulate Ethernet packets into UDP packets and transmits them in tunnels. Open vSwitch serves as the backend virtual switch.
              • VPC network: This network model seamlessly combines VPC routing with the underlying network, making it ideal for high-performance scenarios. However, the maximum number of nodes allowed in a cluster is determined by the VPC route quota. Each node in a cluster that uses a VPC network is running in a subnet with a fixed number of IP addresses. The VPC network model outperforms the container tunnel network model in terms of performance because it does not have tunnel encapsulation overhead. In addition, as the routes destined for nodes and containers are added to a VPC route table, containers can be directly accessed from outside the cluster.
              • Cloud Native Network 2.0 is a next-generation model developed by CCE and combines the network interfaces and supplementary network interfaces of VPC. Pod IP addresses are allocated from the VPC CIDR block. ELB passthrough networking is supported to forward requests to containers. Security groups and EIPs are associated to deliver high performance.
              +

              The performance, networking scale, and application scenarios of a container network vary depending on the container network model. For details about the functions and features of different container network models, see Overview.

              +
            • Service network: Services are a kind of Kubernetes resource object. Each Service has a fixed IP address. Kubernetes provides stable access entries for pods through Services. When creating a cluster on CCE, you can specify the Service CIDR block. Service CIDR blocks cannot overlap with the node CIDR blocks or container CIDR blocks. They can be used only in a cluster.
            -

            Service

            A Service is used for pod access. With a static IP address, a Service forwards access traffic to pods and performs load balancing for these pods.

            -
            Figure 1 Accessing pods through a Service
            +

            Service

            In Kubernetes, pods are considered ephemeral and can be replaced at any time. When a pod is destroyed or replaced, its network resources also change. You need to provide a stable access method for pods. Kubernetes uses a Service to provide a fixed access entry for a group of pods with the same functions and balances the load among these pods.

            +

            As shown in the following figure, a Service is associated with a group of pods through a selector. When the IP address and port of the Service are accessed, traffic is distributed to these pods. When pods change, the Service automatically updates the backend forwarding rules to ensure that the latest pods can be accessed through the Service.

            +
            Figure 2 Accessing pods through a Service

            You can configure the following types of Services:

            • ClusterIP: used to make the Service only reachable from within a cluster.
            • NodePort: used for access from outside a cluster. A NodePort Service is accessed through the port on the node.
            • LoadBalancer: used for access from outside a cluster. It is an extension of NodePort, to which a load balancer routes, and external systems only need to access the load balancer.
            -

            For details about the Service, see Overview.

            +

            For details about the Service, see Service Overview.

            Ingress

            Services forward requests using TCP and UDP at Layer 4. Ingresses forward requests using HTTP and HTTPS at Layer 7. Domain names and paths can be used for access of finer granularities.

            -
            Figure 2 An ingress and associated Services
            -

            For details about the ingress, see Overview.

            +
            Figure 3 An ingress and associated Services
            +

            For details about the ingress, see Ingress Overview.

            +
            +

            DNS

            CCE uses CoreDNS to implement service discovery in a cluster. For example, a client can access backend pods through a ClusterIP Service whose name is mapped to a cluster-scoped virtual IP address. This approach decouples the invoking between applications in a cluster from specific IP addresses and deployment environments. For details about the cluster DNS settings, see DNS Overview.

            +
            Figure 4 Example of domain name resolution in a cluster

            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 a VPC network or tunnel network is used), bind an EIP to the pod IP address (when Cloud Native Network 2.0 is used), or configure SNAT rules through the NAT gateway. For details, see Accessing the Internet from a Container.
              +
            • The workload can access the external network as follows:
              • Accessing a private network: The workload accesses the private network address, but the implementation method varies depending on container network models. Ensure that the peer security group allows access from the container CIDR block.
              • Accessing a public network: Assign an EIP to the node where the workload runs (when a VPC network or tunnel network is used), bind an EIP to the pod IP address (when Cloud Native Network 2.0 is used), or configure an SNAT rule on the NAT gateway. For details, see Accessing the Internet from a Container.
            -
            Figure 3 Network access diagram
            +
            Figure 5 Network access diagram
            -
            Parent topic: Network
            +
            Parent topic: Networking
            diff --git a/docs/cce/umn/cce_10_0011.html b/docs/cce/umn/cce_10_0011.html index ec6803eb6..30aa54ec9 100644 --- a/docs/cce/umn/cce_10_0011.html +++ b/docs/cce/umn/cce_10_0011.html @@ -1,16 +1,57 @@

            ClusterIP

            -

            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)
            +

            ClusterIP is the default Service type of Kubernetes and provides stable intra-cluster access. Kubernetes assigns a virtual IP address (cluster-scoped IP address) that can only be accessed within the cluster from the Service CIDR block of the cluster. CoreDNS maps the cluster-internal domain name to the assigned cluster IP address. The domain name format is <Service-name>.<namespace-of-the-workload>.svc.cluster.local:<port>, for example, nginx.default.svc.cluster.local:80.

            +

            If pods need to communicate with each other within a cluster, you can create a ClusterIP Service. For example, if a frontend pod in a cluster needs to access a backend database in the same cluster, you can create a ClusterIP Service.

            +

            Figure 1 shows how ClusterIP works. You can learn about the access channel, container port, and access port mapping rules of this type of Service.

            +
            Figure 1 Intra-cluster access (ClusterIP)
            +

            Using the CCE Console

            1. Log in to the CCE console and click the cluster name to access the cluster console.
            2. In the navigation pane, choose Services & Ingresses. In the upper right corner, click Create Service.
            3. Configure intra-cluster access parameters.

              +

              + + + + + + + + + + + + + + + + + + + + + + +

              Parameter

              +

              Description

              +

              Service Name

              +

              Enter a name, which can be the same as the workload name.

              +

              Service Type

              +

              Select ClusterIP.

              +

              Namespace

              +

              Select the namespace that the workload belongs to.

              +

              Selector

              +

              The Service will be associated with the workload pods based on the label and direct traffic to the pods with this label.

              +

              You can add a key and value for the pod label and click Confirm.

              +

              You can also click Reference Workload Label to use the label of an existing workload. In the dialog box displayed, select a workload and click OK.

              +

              Protocol Version

              +

              Select the IP address of different versions based on service requirements. This function is displayed only when IPv6 is enabled during the creation of clusters of v1.15 or later.

              +

              Port

              +
              • Protocol: the protocol supported by the Service.
              • Container Port: the listening port of the service containers. The port ranges from 1 to 65535. You need to determine the port based on the container image. For example, the default port of Nginx is 80, and the default port of MySQL is 3306.
              • Service Port: the port used to access the ClusterIP Service. You can customize the port as required. The port ranges from 1 to 65535.
              +
              -

              Creating a ClusterIP Service

              1. Log in to the CCE console and click the cluster name to access the cluster console.
              2. In the navigation pane, choose Services & Ingresses. In the upper right corner, click Create Service.
              3. Configure intra-cluster access parameters.

                • Service Name: Specify a Service name, which can be the same as the workload name.
                • Service Type: Select ClusterIP.
                • Namespace: namespace that the workload belongs to.
                • Selector: Add a label and click Confirm. The Service will use this label to select pods. You can also click Reference Workload Label to use the label of an existing workload. In the dialog box that is displayed, select a workload and click OK.
                • Protocol Version: Select the IP address of different versions based on service requirements. This parameter is available only in clusters of v1.15 or later with IPv6 enabled (set during cluster creation).
                • Ports
                  • Protocol: protocol used by the Service.
                  • Service Port: port used by the Service. The port number ranges from 1 to 65535.
                  • Container Port: listener port of the workload. For example, Nginx uses port 80 by default.
                  -
                -

              4. Click OK.
              +

            4. Click OK. Then, access the Service through <ClusterIP>:<Service-port>.

              +

              +

            -

            Setting the Access Type Using kubectl

            You can configure Service access using kubectl. This section uses an Nginx workload as an example to describe how to implement intra-cluster access using kubectl.

            +

            Using kubectl

            You can configure Service access using kubectl. This section uses an Nginx workload as an example to describe how to implement intra-cluster access using kubectl.

            1. Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
            2. Create and edit the nginx-deployment.yaml file to configure the sample workload. For details, see Creating a Deployment. nginx-deployment.yaml is an example file name. You can rename it as needed.

              vi nginx-deployment.yaml
              File content:
              apiVersion: apps/v1
 kind: Deployment
@@ -63,13 +104,12 @@ spec:
 
              Check the created Service.
              
 
              kubectl get svc
              
 
              If information similar to the following is displayed, the Service has been created, and a cluster-internal IP address has been assigned to the Service.
              
-
              # kubectl get svc
-NAME              TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE
+
              NAME              TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE
 kubernetes        ClusterIP   10.247.0.1     <none>        443/TCP    4d6h
 nginx-clusterip   ClusterIP   10.247.74.52   <none>        8080/TCP   14m
            3. Access the Service from a container or node in the cluster.

              1. Create a pod and access its container.
                kubectl run -i --tty --image nginx:alpine test --rm /bin/sh
              2. Run the curl command to access the Service.
                • Access through IP:Port:
                  curl 10.247.74.52:8080
                  -
                • Access through Domain-name:Port:
                  curl nginx-clusterip.default.svc.cluster.local:8080
                  +
                • Access using Domain name:Port (not supported on nodes):
                  curl nginx-clusterip.default.svc.cluster.local:8080

                  nginx-clusterip is the Service name, default is the namespace where the Service is located, and svc.cluster.local is the DNS domain for the ClusterIP Service.

                  You can simplify the domain name based on your requirements. For example, if the Service and the accessing pod are in the same namespace, you can use nginx-clusterip:8080 to access it. If they are in different namespaces, you can use nginx-clusterip.default:8080 to access it.

                @@ -105,7 +145,7 @@ Commercial support is available at
            -
            Parent topic: Service
            +
            Parent topic: Services
            diff --git a/docs/cce/umn/cce_10_0012.html b/docs/cce/umn/cce_10_0012.html index 05a16c4cf..4079efcf4 100644 --- a/docs/cce/umn/cce_10_0012.html +++ b/docs/cce/umn/cce_10_0012.html @@ -3,7 +3,7 @@

            Creating a Node Pool

            Scenario

            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.

            -

            Procedure

            1. Log in to the CCE console.
            2. Click the cluster name to access the cluster console. Choose Nodes in the navigation pane. In the right pane, click the Node Pools tab.
            3. In the upper right corner of the page, click Create Node Pool.

              Basic Settings

              +

              Procedure

              1. Log in to the CCE console.
              2. Click the cluster name to access the cluster console. Choose Nodes in the navigation pane. In the right pane, click the Node Pools tab.
              3. In the upper right corner of the page, click Create Node Pool.

                Basic Settings

                @@ -30,15 +30,15 @@ - @@ -78,7 +78,7 @@ @@ -92,7 +92,7 @@ - - - -
                Table 1 Basic settings

                Parameter

                Node Type

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

                -
                CCE standard clusters support the following node types:
                • ECS (VM): A virtualized ECS is used as a cluster node.
                +
                CCE standard clusters support the following node types:
                • ECS (VM): A VM ECS is used as a cluster node.
                -
                CCE Turbo clusters support the following node types:
                • ECS (VM): A VM ECS is used as a cluster node. A CCE Turbo cluster supports only the cloud servers that allow multiple ENIs. Select a server type displayed on the CCE console.
                +
                CCE Turbo clusters support the following node types:
                • ECS (VM): A VM ECS is used as a cluster node. A CCE Turbo cluster supports only the cloud servers that allow multiple network interfaces. 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. For details, see the CCE console. For the supported node flavors, see Node Flavor Description.
                NOTE:
                • If a node pool is configured with multiple node flavors, only the flavors (which can be located in different AZs) of the same node type are supported. For example, a node pool consisting of general computing-plus nodes supports only general computing-plus node flavors, but not the flavors of general computing nodes.
                • A maximum of 10 node flavors can be added to a node pool (the flavors in different AZs are counted separately). When adding a node flavor, you can choose multiple AZs, but you need to specify them.
                • Nodes in a newly created node pool are created using the default flavor. If the resources for the default flavor are insufficient, node creation will fail.
                • After a node pool is created, the flavors of existing nodes cannot be deleted.
                +
                Select a node flavor based on service requirements. The available node flavors vary depending on regions. For details, see the CCE console. For the supported node flavors, see Node Flavor Description.
                NOTE:
                • If a node pool is configured with multiple node flavors, only the flavors (which can be located in different AZs) of the same node type are supported. For example, a node pool consisting of general computing-plus nodes supports only general computing-plus node flavors, but not the flavors of general computing nodes.
                • Nodes added to a single node pool must have the same GPU type. For example, if you select the nvidia-v100 flavor, you are not allowed to select the nvidia-t4 flavor.
                • A maximum of 10 node flavors can be added to a node pool (the flavors in different AZs are counted separately). When adding a node flavor, you can choose multiple AZs, but you need to specify them.
                • Nodes in a newly created node pool are created using the default flavor. If the resources for the default flavor are insufficient, node creation will fail.
                • After a node pool is created, the flavors of existing nodes cannot be deleted.

                System Disk

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

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

                Data Disk

                • At least one default data disk must be added for storing container runtime and kubelet components if System Component Storage is set to Data Disk. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable. This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.
                  • Default data disk: used for container runtime and kubelet components. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.
                  • Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.
                  +
                • At least one default data disk must be added for storing container runtime and kubelet components if System Component Storage is set to Data Disk. This data disk cannot be deleted or detached. Otherwise, the node will be unavailable. This function is available for clusters of a version earlier than v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, or v1.29.4-r0.
                  • Default data disk: used for container runtime and kubelet components. The disk size ranges from 20 GiB to 32768 GiB. The default value is 100 GiB.
                  • Other common data disks: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB.
                • If System Component Storage is set to System Disk, you do not need to add a default data disk. In this case, all data disks are common ones: You can set the data disk size to a value ranging from 10 GiB to 32768 GiB. The default value is 100 GiB. This function is available for clusters of v1.23.18-r0, v1.25.13-r0, v1.27.10-r0, v1.28.8-r0, v1.29.4-r0, or later versions.
                NOTE:
                • If the node flavor is disk-intensive or ultra-high I/O, one data disk can be a local disk.
                • Local disks may break down and do not ensure data reliability. Store your service data in EVS disks, which are more reliable than local disks.
                @@ -162,7 +162,7 @@

                You can add resource tags to classify resources.

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

                -

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

                +

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

                Kubernetes Label

                @@ -210,22 +210,22 @@

                Pre-installation Command

                Installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.

                +

                Installation script command. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.

                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

                Installation script command, in which Chinese characters are not allowed. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.

                -

                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.

                +

                Installation script command. The script command will be Base64-transcoded. The characters of both the pre-installation and post-installation scripts are centrally calculated, and the total number of characters after transcoding cannot exceed 10240.

                +
                The script will be executed after Kubernetes software is installed, which does not affect the installation. During post-installation script execution, pods can be scheduled normally. However, if the script execution times out, node installation will fail. To prevent pods from being scheduled to nodes with incomplete script execution, enable the option to schedule pods only after the post-installation script execution completes.
                CAUTION:

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

                +

                Agency

                An agency is created by the tenant administrator on the IAM console. Using 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 on the right to create one.

                +

                If you need to share ECS resources with other accounts or delegate a more professional person or team to manage the resources, you can create an agency on IAM and grant the agency the permissions to manage ECS resources. The delegated account can log in to the cloud system and switch to your account to manage resources. You do not need to share security credentials (such as passwords) with other accounts, ensuring the security of your account.

                +

                If you have created an agency, select the agency from the drop-down list. If no agency is available, click Create Agency on the right to create one.

                Custom Prefix and Suffix

                diff --git a/docs/cce/umn/cce_10_0014.html b/docs/cce/umn/cce_10_0014.html index 9166892a1..03d71d585 100644 --- a/docs/cce/umn/cce_10_0014.html +++ b/docs/cce/umn/cce_10_0014.html @@ -6,7 +6,7 @@
                -
                Parent topic: Service
                +
                Parent topic: Services
                diff --git a/docs/cce/umn/cce_10_0015.html b/docs/cce/umn/cce_10_0015.html index 9bb53d52f..63ae8f0d5 100644 --- a/docs/cce/umn/cce_10_0015.html +++ b/docs/cce/umn/cce_10_0015.html @@ -15,7 +15,7 @@ data:
              4. When a ConfigMap is used as an environment variable, data is not automatically updated when the ConfigMap is updated. To update the data, restart the pod.

                5. Configuring Environment Variables of a Workload

                Using the CCE console

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

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

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

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

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

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

                    @@ -94,9 +94,9 @@ CCE

                Configuring Command Line Parameters

                You can use a ConfigMap as an environment variable to set commands or parameter values for a container by using the environment variable substitution syntax $(VAR_NAME).

                Using the CCE console

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

                  When creating a workload, click Environment Variables in the Container Settings area, and click Add Variable. In this example, select Added from ConfigMap.

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

                    When creating a workload, click Environment Variables in the Container Settings area, and click Add Variable. In this example, select Added from ConfigMap.

                    • Added from ConfigMap: Select a ConfigMap to import all of its keys as environment variables.
                    -

                  3. Click Lifecycle in the Container Settings area, click the Post-Start tab on the right, and set the following parameters:

                    • Processing Method: CLI
                    • Command: Enter the following three command lines. SPECIAL_LEVEL and SPECIAL_TYPE are the environment variable names in the workload, which are key names in the cce-configmap ConfigMap.
                      /bin/bash
+
                    • Click Lifecycle in the Container Settings area, click the Post-Start tab on the right, and configure parameters.

                      • Processing Method: CLI
                      • Command: Enter the following three command lines. SPECIAL_LEVEL and SPECIAL_TYPE are the environment variable names in the workload, which are key names in the cce-configmap ConfigMap.
                        /bin/bash
 -c
 echo $SPECIAL_LEVEL $SPECIAL_TYPE > /usr/share/nginx/html/index.html
                      @@ -146,7 +146,7 @@ spec:

                Mounting a ConfigMap to a Workload Data Volume

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

                Using the CCE console

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

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

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

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

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

                    diff --git a/docs/cce/umn/cce_10_0016.html b/docs/cce/umn/cce_10_0016.html index a3e802071..076c6609c 100644 --- a/docs/cce/umn/cce_10_0016.html +++ b/docs/cce/umn/cce_10_0016.html @@ -19,7 +19,7 @@ data:

                    Configuring Environment Variables of a Workload

                    Using the CCE console

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

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

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

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

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

                          For example, after you import the value of username in secret mysecret as the value of workload environment variable username, an environment variable named username exists in the container.

                        @@ -94,7 +94,7 @@ spec:

                    Configuring the Data Volume of a Workload

                    You can mount a secret as a volume to the specified container path. Contents in a secret are user-defined. Before that, create a secret. For details, see Creating a Secret.

                    Using the CCE console

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

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

                      +
                      1. Log in to the CCE console and click the cluster name to access the cluster console.
                      2. Choose Workloads in the navigation pane. In the right pane, click the Deployments tab. Click Create Workload in the upper right corner.

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

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

                    Table 1 Mounting a ConfigMap volume

                    Parameter
                    diff --git a/docs/cce/umn/cce_10_0018.html b/docs/cce/umn/cce_10_0018.html index f517d110b..8403ff0c1 100644 --- a/docs/cce/umn/cce_10_0018.html +++ b/docs/cce/umn/cce_10_0018.html @@ -1,12 +1,12 @@

                    Collecting Container Logs Using ICAgent

                    -

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

                    -

                    Constraints

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

                    +

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

                    +

                    Constraints

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

                    -

                    Using ICAgent to Collect Logs

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

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

                      +

                      Using ICAgent to Collect Logs

                      1. When creating a workload, choose Logging in Container Information.
                      2. Click to add a log policy.

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

                      3. Set Volume Type to hostPath or emptyDir.

                        -

                    Table 1 Mounting a secret volume

                    Parameter
                    Table 1 Configuring log policies

                    Parameter

                    +
                    @@ -14,7 +14,7 @@ - - @@ -34,22 +34,22 @@ @@ -59,8 +59,8 @@

                  4. Click OK.
                    5. -

                    YAML Example

                    You can set the container log storage path by defining a YAML file.

                    -

                    As shown in the following figure, an emptyDir volume is mounted a temporary path to /var/log/nginx. In this way, the ICAgent collects logs in /var/log/nginx. The policy field is customized by CCE and allows the ICAgent to identify and collect logs.

                    +

                    Example YAML

                    You can set the container log storage path by defining a YAML file.

                    +

                    As shown below, an emptyDir volume is mounted to /var/log/nginx. In this way, the ICAgent collects logs in /var/log/nginx. policy is a custom field of CCE and allows the ICAgent to identify and collect logs.

                    apiVersion: apps/v1
 kind: Deployment
 metadata:
@@ -97,7 +97,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 collect logs in /var/log/nginx, without deleting the logs from /tmp/log.

                    apiVersion: apps/v1
 kind: Deployment
 metadata:
@@ -145,7 +145,7 @@ spec:
                    - @@ -154,8 +154,8 @@ spec: @@ -173,9 +173,9 @@ spec: @@ -202,10 +202,10 @@ spec:

                    Viewing Logs

                    After a log collection path is configured and the workload is created, the ICAgent collects log files from the configured path. The collection takes about 1 minute.

                    After the log collection is complete, go to the workload details page and click Logs in the upper right corner to view logs.

                    You can also view logs on the AOM console.

                    -

                    You can also run the kubectl logs command to view the container stdout.

                    +

                    You can also run the kubectl logs command to view the container stdout.

                    • View the logs of a specified pod.
                      kubectl logs <pod_name> -n <namespace>
                    • View the logs of a specified pod in real time.
                      kubectl logs -f <pod_name> -n <namespace>
                      -
                    • View logs of a specified container in a specified pod.
                      kubectl logs <pod_name> -c <container_name> -n <namespace>
                      +
                    • View the logs of a specified container in a specified pod.
                      kubectl logs <pod_name> -c <container_name> -n <namespace>
                    • View the logs of a specified container in a specified pod in real time.
                      kubectl logs -f <pod_name> -c <container_name> -n <namespace>
                    diff --git a/docs/cce/umn/cce_10_0019.html b/docs/cce/umn/cce_10_0019.html index 39e8c15d9..d0b08afbb 100644 --- a/docs/cce/umn/cce_10_0019.html +++ b/docs/cce/umn/cce_10_0019.html @@ -1,10 +1,10 @@ -

                    Helm Chart

                    +

                    Helm Charts

                      -
                    • Overview of a Chart
                      +
                    • Chart Overview
                    • Deploying an Application from a Chart
                      • diff --git a/docs/cce/umn/cce_10_0020.html b/docs/cce/umn/cce_10_0020.html index 8fecd17e2..1dcd64036 100644 --- a/docs/cce/umn/cce_10_0020.html +++ b/docs/cce/umn/cce_10_0020.html @@ -1,14 +1,14 @@ -

                      Network

                      +

                      Networking

                        -
                      • Overview
                        +
                      • Networking Overview
                        • -
                      • Container Network
                        +
                      • Container Networks
                        • -
                      • Service
                        +
                      • Services
                      • Ingresses
                        • diff --git a/docs/cce/umn/cce_10_0024.html b/docs/cce/umn/cce_10_0024.html index 02f5f7fc4..bc863fd2c 100644 --- a/docs/cce/umn/cce_10_0024.html +++ b/docs/cce/umn/cce_10_0024.html @@ -4,7 +4,7 @@
                          -
                        • CCE Operations Supported by Cloud Trace Service
                          +
                        • CCE Operations Supported by CTS
                        • Viewing CTS Traces in the Trace List
                          • diff --git a/docs/cce/umn/cce_10_0025.html b/docs/cce/umn/cce_10_0025.html index 8f20fc3bf..1c6ce67b5 100644 --- a/docs/cce/umn/cce_10_0025.html +++ b/docs/cce/umn/cce_10_0025.html @@ -1,588 +1,1479 @@ -

                          CCE Operations Supported by Cloud Trace Service

                          -

                          Cloud Trace Service (CTS) records operations on cloud service resources, allowing users to query, audit, and backtrack the resource operation requests initiated from the management console or open APIs as well as responses to the requests.

                          +

                          CCE Operations Supported by CTS

                          +

                          Cloud Trace Service (CTS) records operations on cloud service resources, allowing you to query, audit, and backtrack the resource operation requests initiated from the CCE console or open APIs as well as responses to the requests.

                          +

                          To collect the query events (Get and List) listed in the table below, enable read-only event reporting of CCE in CTS. Because query operations occur far more frequently than addition, deletion, or modification operations, enabling this function may generate a large volume of events. Assess the potential impact before enabling it.

                          +
                          -
                    Table 1 Parameters for configuring a log policy

                    Parameter

                    Description

                    Volume Type

                    • hostPath: A host path is mounted to the specified container path (mount path). In the node host path, you can view the container logs output into the mount path.
                    • emptyDir: A temporary path of the node is mounted to the specified path (mount path). Log data that exists in the temporary path but is not reported by the collector to AOM will disappear after the pod is deleted.
                    +
                    • hostPath: A host path is mounted to the specified container path (mount path). After it is mounted, you can view the container logs that have been saved there.
                    • emptyDir: A temporary path of the node is mounted to the specified path (mount path). After it is mounted, any logs in the temporary path that are not reported to AOM by the collector will be lost if the pod is deleted.

                    hostPath

                    @@ -24,7 +24,7 @@

                    Mount Path

                    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.
                    +
                    Container path (for example, /tmp) that the storage resources will be mounted to.
                    NOTICE:
                    • Do not mount a volume to a system directory such as / or /var/run, or 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. If there are such files, they will be replaced, which will lead to a container startup or workload creation failure.
                    • If the container is mounted to a high-risk directory, use an account with minimum permissions to start the container. Otherwise, high-risk files on the host may be damaged.
                    • 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 text log files in .log, .trace, and .out formats in the mount paths.
                    • For details about how to set permissions for mount points in a container, see Configure a Security Context for a Pod or Container.

                    This parameter is mandatory only if Volume Type is set to hostPath.

                    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.
                    +
                    • 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.

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

                    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 version 5.12.22 or later.

                    +
                    • If no collection path is specified, log files in .log, .trace, and .out formats will be collected from the current path.
                    • Entering ** indicates that all log files in .log, .trace, and .out formats will be recursively collected from the specified path and all subdirectories of five levels deep.
                    • Entering * indicates fuzzy matching.
                    +

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

                    +
                    CAUTION:

                    Ensure that the version of ICAgent is 5.12.22 or later.

                    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. 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.
                    • Disabled: AOM does not dump log files.
                    +
                    • Enable: 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 resides. 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.
                    • Disable: 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.

                    Description

                    Description

                    +

                    Remarks

                    Extended host path

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

                    -

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

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

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

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

                    policy.logs.rotate

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

                    Log dump

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

                    -
                    • Enabled: AOM scans log files every minute. When a log file exceeds 50 MB, it is dumped immediately. A new .zip file is generated in the directory where the log file locates. For a log file, AOM stores only the latest 20 .zip files. When the number of .zip files exceeds 20, earlier .zip files will be deleted. After the dump is complete, the log file in AOM will be cleared.
                    • Disabled: AOM does not dump log files.
                    +
                    • Enable: 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 resides. 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.
                    • Disable: 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.
                    -

                    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 version 5.12.22 or later.

                    +
                    • If no collection path is specified, log files in .log, .trace, and .out formats will be collected from the current path.
                    • Entering ** indicates that all log files in .log, .trace, and .out formats will be recursively collected from the specified path and all subdirectories of five levels deep.
                    • Entering * indicates fuzzy matching.
                    +

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

                    +
                    CAUTION:

                    Ensure that the version of ICAgent is 5.12.22 or later.
                    Table 1 CCE Operations Supported by CTS

                    Operation

                    +
                    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/cce/umn/cce_10_0026.html b/docs/cce/umn/cce_10_0026.html index 4ce73e548..b8162e570 100644 --- a/docs/cce/umn/cce_10_0026.html +++ b/docs/cce/umn/cce_10_0026.html @@ -1,20 +1,68 @@

                    Viewing CTS Traces in the Trace List

                    -

                    Scenarios

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

                    +

                    Scenarios

                    Cloud Trace Service (CTS) records operations performed on cloud service resources. A record contains information such as the user who performed the operation, IP address, operation content, and returned response message. These records facilitate security auditing, issue tracking, and resource locating. They also help you plan and use resources, and identify high-risk or non-compliant operations.

                    -

                    Viewing Real-Time Traces in the Trace List

                    1. Log in to the management console.
                    2. Click in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
                    3. Choose Trace List in the navigation pane on the left.
                    4. Set filters to search for your desired traces, as shown in Figure 1. The following filters are available.
                      Figure 1 Filters
                      -
                      • Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
                        • If you select Resource ID for Search By, specify a resource ID.
                        • If you select Trace name for Search By, specify a trace name.
                        • If you select Resource name for Search By, specify a resource name.
                        -
                      • Operator: Select a user.
                      • Trace Status: Select All trace statuses, Normal, Warning, or Incident.
                      • Time range: Select Last 1 hour, Last 1 day, or Last 1 week, or specify a custom time range within the last seven days.
                      +

                      What Is a Trace?

                      A trace is an operation log for a cloud service resource, tracked and stored by CTS. Traces record operations such as adding, modifying, or deleting cloud service resources. You can view them to identify who performed operations and when for detailed tracking.

                      -
                    5. Click Query.
                    6. On the Trace List page, you can also export and refresh the trace list.
                      • Click Export to export all traces in the query result as a CSV file. The file can contain up to 5,000 records.
                      • Click to view the latest information about traces.
                      -
                    7. Click on the left of a trace to expand its details.

                      +

                      Viewing Traces in the Trace List

                      1. Log in to the management console, click in the upper left corner, and choose Management & Deployment > Cloud Trace Service.
                      2. In the navigation pane, choose Trace List.
                      3. In the upper right corner of the page, set a desired query time range: Last 1 hour, Last 1 day, or Last 1 week. You can also click Customize to specify a custom time range within the last seven days.
                      4. Set filters to search for your desired traces, as shown in Figure 1.

                        Figure 1 Filters
                        + +
                    Table 1 CCE operations supported by CTS

                    Operation

                    Resource Type

                    +

                    Resource

                    Event Name

                    +

                    Trace Name

                    Creating an agency

                    +

                    Creating an agency

                    Cluster

                    +

                    Cluster

                    createUserAgencies

                    +

                    createUserAgencies

                    Creating a cluster

                    +

                    Querying an agency

                    Cluster

                    +

                    Cluster

                    createCluster

                    +

                    getUserAgencies

                    Updating the description of a cluster

                    +

                    Obtaining an access policy

                    Cluster

                    +

                    Cluster

                    updateCluster

                    +

                    getAccessPolicy

                    Upgrading a cluster

                    +

                    Creating an access policy

                    Cluster

                    +

                    Cluster

                    clusterUpgrade

                    +

                    createAccessPolicy

                    Deleting a cluster

                    +

                    Deleting an access policy

                    Cluster

                    +

                    Cluster

                    claimCluster/deleteCluster

                    +

                    deleteAccessPolicy

                    Downloading a cluster certificate

                    +

                    Obtaining the access policy list

                    Cluster

                    +

                    Cluster

                    getClusterCertByUID

                    +

                    listAccessPolicy

                    Binding and unbinding an EIP

                    +

                    Updating an access policy

                    Cluster

                    +

                    Cluster

                    operateMasterEIP

                    +

                    updateAccessPolicy

                    Waking up a cluster and resetting node management (V2)

                    +

                    Creating a cluster

                    Cluster

                    +

                    Cluster

                    operateCluster

                    +

                    createCluster

                    Hibernating a cluster (V3)

                    +

                    Updating the description of a cluster

                    Cluster

                    +

                    Cluster

                    hibernateCluster

                    +

                    updateCluster

                    Waking up a cluster (V3)

                    +

                    Upgrading a cluster

                    Cluster

                    +

                    Cluster

                    awakeCluster

                    +

                    clusterUpgrade

                    Changing the specifications of a cluster

                    +

                    Deleting a cluster

                    Cluster

                    +

                    Cluster

                    resizeCluster

                    +

                    claimCluster/deleteCluster

                    Modifying configurations of a cluster

                    +

                    Obtaining the cluster list

                    Cluster

                    +

                    Cluster

                    updateConfiguration

                    +

                    listCluster

                    Creating a node pool

                    +

                    Obtaining the cluster list in a project

                    Node pool

                    +

                    Cluster

                    createNodePool

                    +

                    getClustersByProjectID

                    Updating a node pool

                    +

                    Obtaining the number of clusters

                    Node pool

                    +

                    Cluster

                    updateNodePool

                    +

                    getClusterInstances

                    Deleting a node pool

                    +

                    Obtaining a cluster

                    Node pool

                    +

                    Cluster

                    claimNodePool

                    +

                    getClusterByUID

                    Migrating a node pool

                    +

                    Obtaining the cluster package list

                    Node pool

                    +

                    Cluster

                    migrateNodepool

                    +

                    getPackageLists

                    Modifying node pool configurations

                    +

                    Obtaining the package configuration of a cluster

                    Node pool

                    +

                    Cluster

                    updateConfiguration

                    +

                    getPackageConfigs

                    Creating a node

                    +

                    Downloading a cluster certificate

                    Node

                    +

                    Cluster

                    createNode

                    +

                    getClusterCertByUID

                    Deleting all the nodes from a specified cluster

                    +

                    Revoking a cluster certificate

                    Node

                    +

                    Cluster

                    deleteAllHosts

                    +

                    revokeClusterCert

                    Deleting a single node

                    +

                    Binding and unbinding an EIP

                    Node

                    +

                    Cluster

                    deleteOneHost/claimOneHost

                    +

                    operateMasterEIP

                    Updating the description of a node

                    +

                    Waking up a cluster and resetting node management (V2)

                    Node

                    +

                    Cluster

                    updateNode

                    +

                    operateCluster

                    Creating an add-on instance

                    +

                    Hibernating a cluster (V3)

                    Add-on instance

                    +

                    Cluster

                    createAddonInstance

                    +

                    hibernateCluster

                    Deleting an add-on instance

                    +

                    Waking up a cluster (V3)

                    Add-on instance

                    +

                    Cluster

                    deleteAddonInstance

                    +

                    awakeCluster

                    Uploading a chart

                    +

                    Changing the specifications of a cluster

                    Chart

                    +

                    Cluster

                    uploadChart

                    +

                    resizeCluster

                    Updating a chart

                    +

                    Modifying configurations of a cluster

                    Chart

                    +

                    Cluster

                    updateChart

                    +

                    updateConfiguration

                    Deleting a chart

                    +

                    Obtaining cluster configuration

                    Chart

                    +

                    Cluster

                    deleteChart

                    +

                    getClusterConfiguration

                    Creating a release

                    +

                    Obtaining all configurations of the current cluster version

                    Release

                    +

                    Cluster

                    createRelease

                    +

                    getClusterConfigurationDetail

                    Upgrading a release

                    +

                    Querying the detailed configuration items of a cluster by cluster version or type

                    Release

                    +

                    Cluster

                    updateRelease

                    +

                    getClusterSupportConfiguration

                    Deleting a release

                    +

                    Obtaining cluster quotas

                    Release

                    +

                    Cluster

                    deleteRelease

                    +

                    getQuotas

                    Creating a ConfigMap

                    +

                    Obtaining the global OBS access secret configuration of a cluster

                    Kubernetes resource

                    +

                    Cluster

                    createConfigmaps

                    +

                    getClusterLongAKSKConfig

                    Creating a DaemonSet

                    +

                    Updating the global OBS access secret configuration of a cluster

                    Kubernetes resource

                    +

                    Cluster

                    createDaemonsets

                    +

                    updateClusterLongAKSKConfig

                    Creating a Deployment

                    +

                    Updating the global OBS access secret configuration in a project

                    Kubernetes resource

                    +

                    Cluster

                    createDeployments

                    +

                    UpdateAKSKConfig

                    Creating an event

                    +

                    Obtaining the global OBS access secret configuration in a project

                    Kubernetes resource

                    +

                    Cluster

                    createEvents

                    +

                    GetAKSKConfig

                    Creating an Ingress

                    +

                    Obtaining the IP address of a master node

                    Kubernetes resource

                    +

                    Cluster

                    createIngresses

                    +

                    GetOpenAPIInfo

                    Creating a job

                    +

                    Obtaining the cluster access address

                    Kubernetes resource

                    +

                    Cluster

                    createJobs

                    +

                    GetEndpoints

                    Creating a namespace

                    +

                    Retrying a cluster upgrade

                    Kubernetes resource

                    +

                    Cluster

                    createNamespaces

                    +

                    ClusterUpgradeRetry

                    Creating a node

                    +

                    Pausing a cluster upgrade

                    Kubernetes resource

                    +

                    Cluster

                    createNodes

                    +

                    ClusterUpgradePause

                    Creating a PersistentVolumeClaim

                    +

                    Continuing a cluster upgrade

                    Kubernetes resource

                    +

                    Cluster

                    createPersistentvolumeclaims

                    +

                    ClusterUpgradeContinue

                    Creating a pod

                    +

                    Rolling back a cluster upon an upgrade failure

                    Kubernetes resource

                    +

                    Cluster

                    createPods

                    +

                    Rollback

                    Creating a replica set

                    +

                    Rolling back a cluster upon an upgrade retry failure

                    Kubernetes resource

                    +

                    Cluster

                    createReplicasets

                    +

                    ClusterRollbackRetry

                    Creating a resource quota

                    +

                    Pausing a cluster upgrade rollback

                    Kubernetes resource

                    +

                    Cluster

                    createResourcequotas

                    +

                    ClusterRollbackPause

                    Creating a secret

                    +

                    Continuing a cluster upgrade rollback

                    Kubernetes resource

                    +

                    Cluster

                    createSecrets

                    +

                    ClusterRollbackContinue

                    Creating a service

                    +

                    Querying the cluster rollback history

                    Kubernetes resource

                    +

                    Cluster

                    createServices

                    +

                    GetRollbackTasks

                    Creating a StatefulSet

                    +

                    Querying the cluster upgrade history

                    Kubernetes resource

                    +

                    Cluster

                    createStatefulsets

                    +

                    GetUpgradeTasks

                    Creating a volume

                    +

                    Querying the records of a cluster upgrade

                    Kubernetes resource

                    +

                    Cluster

                    createVolumes

                    +

                    GetUpgradeTask

                    Deleting a ConfigMap

                    +

                    Querying cluster labels

                    Kubernetes resource

                    +

                    Cluster

                    deleteConfigmaps

                    +

                    GetLabels

                    Deleting a DaemonSet

                    +

                    Querying the configuration of a cluster

                    Kubernetes resource

                    +

                    Cluster

                    deleteDaemonsets

                    +

                    GetUpgradeInfo

                    Deleting a Deployment

                    +

                    Obtaining the certificate rotation state

                    Kubernetes resource

                    +

                    Cluster

                    deleteDeployments

                    +

                    GetRotationState

                    Deleting an event

                    +

                    Rotating certificates

                    Kubernetes resource

                    +

                    Cluster

                    deleteEvents

                    +

                    RotateCredentials

                    Deleting an Ingress

                    +

                    Downloading certificates

                    Kubernetes resource

                    +

                    Cluster

                    deleteIngresses

                    +

                    DownloadNodeCredentials

                    Deleting a job

                    +

                    Rolling back certificates

                    Kubernetes resource

                    +

                    Cluster

                    deleteJobs

                    +

                    RollbackCredentials

                    Deleting a namespace

                    +

                    Completing certificate rotation

                    Kubernetes resource

                    +

                    Cluster

                    deleteNamespaces

                    +

                    FinishEncryptionKeyRotation

                    Deleting a node

                    +

                    Supplementing the component certificates of a master node

                    Kubernetes resource

                    +

                    Cluster

                    deleteNodes

                    +

                    CompleteComponentCredential

                    Deleting a Pod

                    +

                    Updating cluster certificates

                    Kubernetes resource

                    +

                    Cluster

                    deletePods

                    +

                    RotateClusterCredentials

                    Deleting a replica set

                    +

                    Enabling the cluster upgrade workflow booting task

                    Kubernetes resource

                    +

                    Cluster

                    deleteReplicasets

                    +

                    UpgradeWorkFlow

                    Deleting a resource quota

                    +

                    Querying cluster upgrade workflows

                    Kubernetes resource

                    +

                    Cluster

                    deleteResourcequotas

                    +

                    GetUpgradeWorkFlows

                    Deleting a secret

                    +

                    Querying details about a cluster upgrade task

                    Kubernetes resource

                    +

                    Cluster

                    deleteSecrets

                    +

                    UpgradeWorkFlowUpdate

                    Deleting a service

                    +

                    Performing a pre-upgrade check for a cluster

                    Kubernetes resource

                    +

                    Cluster

                    deleteServices

                    +

                    PreCheck

                    Deleting a StatefulSet

                    +

                    Obtaining the list of historical check records

                    Kubernetes resource

                    +

                    Cluster

                    deleteStatefulsets

                    +

                    GetPreCheckList

                    Deleting volumes

                    +

                    Obtaining a specific check record

                    Kubernetes resource

                    +

                    Cluster

                    deleteVolumes

                    +

                    GetPreCheck

                    Replacing a specified ConfigMap

                    +

                    Performing a post-upgrade check

                    Kubernetes resource

                    +

                    Cluster

                    updateConfigmaps

                    +

                    PostCheck

                    Replacing a specified DaemonSet

                    +

                    Performing a rolling upgrade on the cluster control plane

                    Kubernetes resource

                    +

                    Cluster

                    updateDaemonsets

                    +

                    RollingUpdateControlPlane

                    Replacing a specified Deployment

                    +

                    Retrying a rolling upgrade on the cluster control plane

                    Kubernetes resource

                    +

                    Cluster

                    updateDeployments

                    +

                    RetryRollingUpdateControlPlane

                    Replacing a specified event

                    +

                    Creating a node pool

                    Kubernetes resource

                    +

                    Node pool

                    updateEvents

                    +

                    createNodePool

                    Replacing a specified ingress

                    +

                    Updating a node pool

                    Kubernetes resource

                    +

                    Node pool

                    updateIngresses

                    +

                    updateNodePool

                    Replacing a specified job

                    +

                    Deleting a node pool

                    Kubernetes resource

                    +

                    Node pool

                    updateJobs

                    +

                    claimNodePool

                    Replacing a specified namespace

                    +

                    Migrating a node pool

                    Kubernetes resource

                    +

                    Node pool

                    updateNamespaces

                    +

                    migrateNodepool

                    Replacing a specified node

                    +

                    Updating the node pool configuration

                    Kubernetes resource

                    +

                    Node pool

                    updateNodes

                    +

                    updateConfiguration

                    Replacing a specified PersistentVolumeClaim

                    +

                    Obtaining the node pool configuration

                    Kubernetes resource

                    +

                    Node pool

                    updatePersistentvolumeclaims

                    +

                    getConfiguration

                    Replacing a specified pod

                    +

                    Obtaining node pool details

                    Kubernetes resource

                    +

                    Node pool

                    updatePods

                    +

                    getConfigurationDetail

                    Replacing a specified replica set

                    +

                    Querying a node pool

                    Kubernetes resource

                    +

                    Node pool

                    updateReplicasets

                    +

                    getNodePool

                    Replacing a specified resource quota

                    +

                    Querying the node pool quota

                    Kubernetes resource

                    +

                    Node pool

                    updateResourcequotas

                    +

                    getNodePoolQuota

                    Replacing a specified secret

                    +

                    Querying all node pools in a cluster

                    Kubernetes resource

                    +

                    Node pool

                    updateSecrets

                    +

                    listNodePools

                    Replacing a specified service

                    +

                    Scaling down a node pool

                    Kubernetes resource

                    +

                    Node pool

                    updateServices

                    +

                    scaleNodePool

                    Replacing a specified StatefulSet

                    +

                    Upgrading a node pool

                    Kubernetes resource

                    +

                    Node pool

                    updateStatefulsets

                    +

                    upgradeNodePool

                    Replacing the specified status

                    +

                    Adding nodes

                    Kubernetes resource

                    +

                    Node

                    updateStatus

                    +

                    addNodes

                    Uploading a chart

                    +

                    Creating a node

                    Kubernetes resource

                    +

                    Node

                    uploadChart

                    +

                    createNode

                    Updating a component template

                    +

                    Deleting all nodes from a cluster

                    Kubernetes resource

                    +

                    Node

                    updateChart

                    +

                    deleteAllHosts

                    Deleting a chart

                    +

                    Deleting a node

                    Kubernetes resource

                    +

                    Node

                    deleteChart

                    +

                    deleteOneHost/claimOneHost

                    Creating a template application

                    +

                    Updating the description of a node

                    Kubernetes resource

                    +

                    Node

                    createRelease

                    +

                    updateNode

                    Updating a template application

                    +

                    Obtaining the list of nodes in a cluster

                    Kubernetes resource

                    +

                    Node

                    updateRelease

                    +

                    getHostsList

                    Deleting a template application

                    +

                    Obtaining a node

                    Kubernetes resource

                    +

                    Node

                    deleteRelease

                    +

                    getOneHost

                    +

                    Removing nodes

                    +

                    Node

                    +

                    removeNodesTask

                    +

                    Resetting nodes

                    +

                    Node

                    +

                    resetNodes

                    +

                    Migrating nodes to the node pool

                    +

                    Node

                    +

                    MigrateNodes

                    +

                    Synchronizing nodes in a batch

                    +

                    Node

                    +

                    SyncNodes

                    +

                    Migrating nodes

                    +

                    Node

                    +

                    MigrateNodesTask

                    +

                    Locking a node pool so that it will not be scaled down

                    +

                    Node

                    +

                    LockNodepoolNodeScaleDown

                    +

                    Unlocking a node pool so that it can be scaled down

                    +

                    Node

                    +

                    UnLockNodepoolNodeScaleDown

                    +

                    Deleting all jobs

                    +

                    Job

                    +

                    deleteJobs

                    +

                    Deleting a job

                    +

                    Job

                    +

                    deleteOneJob

                    +

                    Obtaining jobs in a project

                    +

                    Job

                    +

                    getJobsByProjectID

                    +

                    Obtaining a job

                    +

                    Job

                    +

                    getJobByUID

                    +

                    Creating an add-on instance

                    +

                    Add-on instance

                    +

                    createAddonInstance

                    +

                    Querying an add-on instance

                    +

                    Add-on instance

                    +

                    getAddonInstance

                    +

                    Deleting an add-on instance

                    +

                    Add-on instance

                    +

                    deleteAddonInstance

                    +

                    Obtaining the add-on list

                    +

                    Add-on instance

                    +

                    getAddonsList

                    +

                    Updating an add-on instance

                    +

                    Add-on instance

                    +

                    updateAddonInstance

                    +

                    Rolling back an add-on instance

                    +

                    Add-on instance

                    +

                    rollbackAddonInstance

                    +

                    Obtaining add-on details by add-on ID

                    +

                    Add-on instance

                    +

                    GetAddonTemplate

                    +

                    Obtaining the add-on template list

                    +

                    Add-on instance

                    +

                    GetAddonTemplateList

                    +

                    Uploading a chart

                    +

                    Chart

                    +

                    uploadChart

                    +

                    Updating a chart

                    +

                    Chart

                    +

                    updateChart

                    +

                    Deleting a chart

                    +

                    Chart

                    +

                    deleteChart

                    +

                    Downloading a chart

                    +

                    Chart

                    +

                    downloadChart

                    +

                    Querying a chart

                    +

                    Chart

                    +

                    getChart

                    +

                    Obtaining chart details

                    +

                    Chart

                    +

                    getChartValues

                    +

                    Obtaining the chart list

                    +

                    Chart

                    +

                    listCharts

                    +

                    Obtaining the chart quota

                    +

                    Chart

                    +

                    getUserChartsQuotas

                    +

                    Creating a release

                    +

                    Release

                    +

                    createRelease

                    +

                    Upgrading a release

                    +

                    Release

                    +

                    updateRelease

                    +

                    Deleting a release

                    +

                    Release

                    +

                    deleteRelease

                    +

                    Querying a release

                    +

                    Release

                    +

                    getRelease

                    +

                    Querying the release history

                    +

                    Release

                    +

                    getReleaseHistory

                    +

                    Querying the release list

                    +

                    Release

                    +

                    listReleases

                    +

                    Creating a ConfigMap

                    +

                    Kubernetes resource

                    +

                    createConfigmaps

                    +

                    Querying a ConfigMap

                    +

                    Kubernetes resource

                    +

                    getConfigmaps

                    +

                    Creating a DaemonSet

                    +

                    Kubernetes resource

                    +

                    createDaemonsets

                    +

                    Querying a DaemonSet

                    +

                    Kubernetes resource

                    +

                    getDaemonsets

                    +

                    Creating a Deployment

                    +

                    Kubernetes resource

                    +

                    createDeployments

                    +

                    Querying a Deployment

                    +

                    Kubernetes resource

                    +

                    getDeployments

                    +

                    Creating an event

                    +

                    Kubernetes resource

                    +

                    createEvents

                    +

                    Querying an event

                    +

                    Kubernetes resource

                    +

                    getEvents

                    +

                    Creating an ingress

                    +

                    Kubernetes resource

                    +

                    createIngresses

                    +

                    Querying an ingress

                    +

                    Kubernetes resource

                    +

                    getIngresses

                    +

                    Creating a job

                    +

                    Kubernetes resource

                    +

                    createJobs

                    +

                    Querying a job

                    +

                    Kubernetes resource

                    +

                    getJobs

                    +

                    Creating a namespace

                    +

                    Kubernetes resource

                    +

                    createNamespaces

                    +

                    Querying a namespace

                    +

                    Kubernetes resource

                    +

                    getNamespaces

                    +

                    Creating a node

                    +

                    Kubernetes resource

                    +

                    createNodes

                    +

                    Querying a node

                    +

                    Kubernetes resource

                    +

                    getNodes

                    +

                    Creating a PersistentVolumeClaim

                    +

                    Kubernetes resource

                    +

                    createPersistentvolumeclaims

                    +

                    Querying a PersistentVolumeClaim

                    +

                    Kubernetes resource

                    +

                    getPersistentvolumeclaims

                    +

                    Creating a pod

                    +

                    Kubernetes resource

                    +

                    createPods

                    +

                    Querying a pod

                    +

                    Kubernetes resource

                    +

                    getPods

                    +

                    Creating a ReplicaSet

                    +

                    Kubernetes resource

                    +

                    createReplicasets

                    +

                    Querying a ReplicaSet

                    +

                    Kubernetes resource

                    +

                    getReplicasets

                    +

                    Creating a resource quota

                    +

                    Kubernetes resource

                    +

                    createResourcequotas

                    +

                    Creating a secret

                    +

                    Kubernetes resource

                    +

                    createSecrets

                    +

                    Querying a secret

                    +

                    Kubernetes resource

                    +

                    getSecrets

                    +

                    Creating a Service

                    +

                    Kubernetes resource

                    +

                    createServices

                    +

                    Querying a Service

                    +

                    Kubernetes resource

                    +

                    getServices

                    +

                    Creating a StatefulSet

                    +

                    Kubernetes resource

                    +

                    createStatefulsets

                    +

                    Querying a StatefulSet

                    +

                    Kubernetes resource

                    +

                    getStatefulsets

                    +

                    Creating a volume

                    +

                    Kubernetes resource

                    +

                    createVolumes

                    +

                    Querying a volume

                    +

                    Kubernetes resource

                    +

                    getVolumes

                    +

                    Deleting a ConfigMap

                    +

                    Kubernetes resource

                    +

                    deleteConfigmaps

                    +

                    Deleting a DaemonSet

                    +

                    Kubernetes resource

                    +

                    deleteDaemonsets

                    +

                    Deleting a Deployment

                    +

                    Kubernetes resource

                    +

                    deleteDeployments

                    +

                    Deleting an event

                    +

                    Kubernetes resource

                    +

                    deleteEvents

                    +

                    Deleting an ingress

                    +

                    Kubernetes resource

                    +

                    deleteIngresses

                    +

                    Deleting a job

                    +

                    Kubernetes resource

                    +

                    deleteJobs

                    +

                    Deleting a namespace

                    +

                    Kubernetes resource

                    +

                    deleteNamespaces

                    +

                    Deleting a node

                    +

                    Kubernetes resource

                    +

                    deleteNodes

                    +

                    Deleting a Pod

                    +

                    Kubernetes resource

                    +

                    deletePods

                    +

                    Deleting a ReplicaSet

                    +

                    Kubernetes resource

                    +

                    deleteReplicasets

                    +

                    Deleting a resource quota

                    +

                    Kubernetes resource

                    +

                    deleteResourcequotas

                    +

                    Deleting a secret

                    +

                    Kubernetes resource

                    +

                    deleteSecrets

                    +

                    Deleting a Service

                    +

                    Kubernetes resource

                    +

                    deleteServices

                    +

                    Deleting a StatefulSet

                    +

                    Kubernetes resource

                    +

                    deleteStatefulsets

                    +

                    Deleting a volume

                    +

                    Kubernetes resource

                    +

                    deleteVolumes

                    +

                    Replacing a ConfigMap

                    +

                    Kubernetes resource

                    +

                    updateConfigmaps

                    +

                    Replacing a DaemonSet

                    +

                    Kubernetes resource

                    +

                    updateDaemonsets

                    +

                    Replacing a Deployment

                    +

                    Kubernetes resource

                    +

                    updateDeployments

                    +

                    Replacing an event

                    +

                    Kubernetes resource

                    +

                    updateEvents

                    +

                    Replacing an ingress

                    +

                    Kubernetes resource

                    +

                    updateIngresses

                    +

                    Replacing a job

                    +

                    Kubernetes resource

                    +

                    updateJobs

                    +

                    Replacing a namespace

                    +

                    Kubernetes resource

                    +

                    updateNamespaces

                    +

                    Replacing a node

                    +

                    Kubernetes resource

                    +

                    updateNodes

                    +

                    Replacing a PersistentVolumeClaim

                    +

                    Kubernetes resource

                    +

                    updatePersistentvolumeclaims

                    +

                    Replacing a pod

                    +

                    Kubernetes resource

                    +

                    updatePods

                    +

                    Replacing a ReplicaSet

                    +

                    Kubernetes resource

                    +

                    updateReplicasets

                    +

                    Replacing a resource quota

                    +

                    Kubernetes resource

                    +

                    updateResourcequotas

                    +

                    Replacing a secret

                    +

                    Kubernetes resource

                    +

                    updateSecrets

                    +

                    Replacing a Service

                    +

                    Kubernetes resource

                    +

                    updateServices

                    +

                    Replacing a StatefulSet

                    +

                    Kubernetes resource

                    +

                    updateStatefulsets

                    +

                    Replacing a status

                    +

                    Kubernetes resource

                    +

                    updateStatus

                    +

                    Uploading a component chart

                    +

                    Kubernetes resource

                    +

                    uploadChart

                    +

                    Updating a component chart

                    +

                    Kubernetes resource

                    +

                    updateChart

                    +

                    Deleting a component chart

                    +

                    Kubernetes resource

                    +

                    deleteChart

                    +

                    Querying a component chart

                    +

                    Kubernetes resource

                    +

                    getChart

                    +

                    Creating a release

                    +

                    Kubernetes resource

                    +

                    createRelease

                    +

                    Updating a release

                    +

                    Kubernetes resource

                    +

                    updateRelease

                    +

                    Deleting a release

                    +

                    Kubernetes resource

                    +

                    deleteRelease

                    +

                    Querying a release

                    +

                    Kubernetes resource

                    +

                    getRelease

                    +

                    Backing up a cluster

                    +

                    Cluster

                    +

                    Snapshot

                    +

                    Querying the snapshot task list of a cluster

                    +

                    Cluster

                    +

                    GetSnapshotTasks

                    +

                    Synchronizing the node pool configuration to existing nodes

                    +

                    Cluster

                    +

                    SyncNodePool

                    +

                    Obtaining tenant permission application records

                    +

                    Cluster

                    +

                    ListPermissionApplyOrders

                    +

                    Applying for tenant permissions

                    +

                    Cluster

                    +

                    CreatePermissionApplyOrder

                    +

                    Adding resource tags to a cluster in a batch

                    +

                    Cluster

                    +

                    BatchCreateDeleteResourceTags

                    +

                    Deleting tags from a cluster in a batch

                    +

                    Cluster

                    +

                    BatchCreateDeleteResourceTags

                    +

                    Creating a partition

                    +

                    Cluster

                    +

                    CreatePartition

                    +

                    Querying a partition

                    +

                    Cluster

                    +

                    GetOnePartition

                    +

                    Querying the partition list of a cluster

                    +

                    Cluster

                    +

                    GetPartitionList

                    +

                    Updating a partition

                    +

                    Cluster

                    +

                    UpdatePartition

                    +

                    Querying a warm-up pool

                    +

                    Cluster

                    +

                    GetWarmUpPool

                    +

                    Querying the warm-up pool list

                    +

                    Cluster

                    +

                    ListWarmUpPool

                    +

                    Updating a warm-up pool

                    +

                    Cluster

                    +

                    UpdateWarmUpPool

                    +

                    Creating a warm-up pool

                    +

                    Cluster

                    +

                    CreateWarmUpPool

                    +

                    Deleting a warm-up pool

                    +

                    Cluster

                    +

                    DeleteWarmUpPool

                    +

                    Querying an upgrade path

                    +

                    Cluster

                    +

                    GetClusterUpgradePaths

                    +

                    Querying upgrade feature gates

                    +

                    Cluster

                    +

                    GetUpgradeFeatureGates

                    +

                    Obtaining an automatic upgrade plan

                    +

                    Cluster

                    +

                    GetUpgradePlans

                    +

                    Deleting an automatic upgrade plan

                    +

                    Cluster

                    +

                    DeleteUpgradePlan

                    +

                    Obtaining a cluster maintenance window

                    +

                    Cluster

                    +

                    GetMaintenanceWindow

                    +

                    Updating a cluster maintenance window

                    +

                    Cluster

                    +

                    UpdateMaintenanceWindow

                    +

                    Creating a cluster maintenance window

                    +

                    Cluster

                    +

                    CreateMaintenanceWindow

                    +

                    Deleting a cluster maintenance window

                    +

                    Cluster

                    +

                    DeleteMaintenanceWindow
                    + + + + + + + + + + + + + + + + + + + + + + +
                    Table 1 Trace filtering parameters

                    Parameter

                    +

                    Description

                    +

                    Trace Type

                    +

                    Select Management or Data.

                    +
                    • Management traces record operations performed by users on cloud service resources, including creation, modification, and deletion.
                    • Data traces are reported by OBS and record operations performed on data in OBS buckets, including uploads and downloads.
                    +

                    Trace Source

                    +

                    Select the name of the cloud service that triggers a trace from the drop-down list.

                    +

                    Resource type

                    +

                    Select the type of the resource involved in a trace from the drop-down list.

                    +

                    For details about the resource types of each cloud service, see section "Supported Services and Operations" in the Cloud Trace Service User Guide.

                    +

                    Search By

                    +

                    Select one of the following options:

                    +
                    • Resource ID: ID of the cloud resource involved in a trace.

                      Leave this field empty if the resource has no resource ID or if resource creation failed.

                      +
                    • Trace name: name of a trace.

                      For details about the operations that can be audited for each cloud service, see section "Supported Services and Operations" in the Cloud Trace Service User Guide.

                      +
                    • Resource name: name of the cloud resource involved in a trace.

                      If the cloud resource involved in the trace does not have a resource name or the corresponding API operation does not involve the resource name parameter, leave this field empty.

                      +
                    +

                    Operator

                    +

                    User who triggers a trace.

                    +

                    Select one or more operators from the drop-down list.

                    +

                    If the value of trace_type in a trace is SystemAction, the operation is triggered by the service and the trace's operator may be empty.

                    +

                    Trace Status

                    +

                    Select one of the following options:

                    +
                    • Normal: The operation succeeded.
                    • Warning: The operation failed.
                    • Incident: The operation caused a fault that is more serious than a normal failure, for example, causing other faults.
                    +
                    +
                    +

                  5. Click Query.
                  6. On the Trace List page, you can also export and refresh the trace list.

                    • Click Export to export all traces in the query result as a CSV file. The file can contain up to 5,000 records.
                    • Click to view the latest information about traces.
                    +

                  7. Click on the left of a trace to expand its details.

                    -

                    -

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

                    -
                  9. For details about key fields in the trace structure, see Trace Structure and Example Traces in the CTS User Guide.
                    10. +

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

                    +

                    11. + +

                    Helpful Links

                    diff --git a/docs/cce/umn/cce_10_0028.html b/docs/cce/umn/cce_10_0028.html index 668a4b988..19ae29c09 100644 --- a/docs/cce/umn/cce_10_0028.html +++ b/docs/cce/umn/cce_10_0028.html @@ -1,360 +1,545 @@

                    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.

                    -

                    Precautions

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

                    Step 1: Log In to the CCE Console

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

                    Step 2: Configure the Cluster

                    On the Create Cluster page, configure the parameters.

                    -

                    Basic Settings

                    -

                    +

                    CCE standard and Turbo clusters provide enterprise-class Kubernetes cluster hosting service that supports full lifecycle management of containerized applications. They offer a highly scalable, high-performance solution for deploying and managing cloud native applications. On the CCE console, you can easily create CCE standard and Turbo clusters. After a cluster is created, CCE hosts the master nodes. You only need to create worker nodes. In this way, you can implement cost-effective O&M and efficient service deployment.

                    +

                    Before creating a CCE standard or Turbo cluster, you are advised to learn about What Is CCE? Networking Overview, and Planning CIDR Blocks for a Cluster.

                    +

                    Step 1: Configure Basic Settings

                    Basic settings define the core architecture and underlying resource rules of a cluster, providing a framework for cluster running and resource allocation.

                    +
                    1. Log in to the CCE console. In the upper left corner of the page, click and select a region for your cluster. The closer the selected region is to the region where resources are deployed, the lower the network latency and the faster the access.

                      After confirming the region, click Create Cluster. If you use CCE for the first time, you need to create an agency following instructions.

                      +

                    2. Configure the basic settings of the cluster. For details, see Table 1.

                      -

                      Parameter

                      +
                      - + - - + - - + - - + - - + - - - - -
                      Table 1 Basic settings of a cluster (applicable to standard and Turbo clusters)

                      Parameter

                      Description

                      +

                      Description

                      +

                      Modifiable After Cluster Creation

                      Type

                      +

                      Type

                      Select CCE Standard Cluster or CCE Turbo Cluster as required.

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

                      For more details, see cluster types.

                      +

                      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, see cluster types.

                      +

                      No

                      Cluster Name

                      +

                      Cluster Name

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

                      +

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

                      +

                      Enter 4 to 128 characters. Start with a lowercase letter and do not end with a hyphen (-). Only lowercase letters, digits, and hyphens (-) are allowed.

                      +

                      Yes

                      Cluster Version

                      +

                      Cluster Version

                      Select the Kubernetes version used by the cluster.

                      +

                      Select a Kubernetes version. The latest commercial version is recommended, and it provides you with more stable, reliable features.

                      +

                      Yes

                      Cluster Scale

                      +

                      Cluster Scale

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

                      +

                      Select a cluster scale as required. This parameter controls the maximum number of worker nodes that a cluster can manage.

                      +

                      Yes

                      +

                      The cluster that has been created can only be scaled out. For details, see Changing a Cluster Scale.

                      Master Nodes

                      +

                      Master Nodes

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

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

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

                      +
                      • 3 Masters: Three master nodes will be created for high cluster availability.
                      • Single: Only one master node will be created in your cluster.
                        NOTE:

                        If more than half of the master nodes in a CCE cluster are faulty, the cluster cannot function properly.

                      -
                      You can also select AZs for deploying the master nodes of a specific cluster. By default, AZs are allocated automatically for the master nodes.
                      • Automatic: Master nodes are randomly distributed in different AZs for cluster DR. If the number of available AZs is less than the number of nodes to be created, CCE will create the nodes in the AZs with sufficient resources to preferentially ensure cluster creation. In this case, AZ-level DR may not be ensured.
                      • Custom: Master nodes are deployed in specific AZs.
                        If there is one master node in your cluster, you can select one AZ for the master node. If there are multiple master nodes in your cluster, you can select multiple AZs for the master nodes.
                        • AZ: Master nodes are deployed in different AZs for cluster DR.
                        • Host: Master nodes are deployed on different hosts in the same AZ for cluster DR.
                        • Custom: Master nodes are deployed in the AZs you specified.
                        +
                        You can also select AZs for deploying the master nodes of a specific cluster. By default, AZs are allocated automatically for the master nodes.
                        • Automatic: Master nodes are randomly distributed in different AZs for cluster DR. If there are not enough AZs available, CCE will prioritize assigning nodes in AZs with enough resources to ensure cluster creation. However, this may result in AZ-level DR not being guaranteed.
                        • Custom: Master nodes are deployed in specific AZs.
                          If there is one master node in a cluster, you can select one AZ for the master node. If there are multiple master nodes in a cluster, you can select multiple AZs for the master nodes.
                          • AZ: Master nodes are deployed in different AZs for cluster DR.
                          • Host: Master nodes are deployed on different hosts in the same AZ for cluster DR.
                          • Custom: Master nodes are deployed in the AZs you specified.
                      -
                      -

                      Network Settings

                      -

                      The network settings cover nodes, containers, and Services. For details about the cluster networking and container network models, see Overview.

                      -

                      - -
                      - - - - - - - - - - - - - -
                      Table 1 Cluster network settings

                      Parameter

                      -

                      Description

                      -

                      VPC

                      -

                      Select the VPC to which the cluster belongs. If no VPC is available, click Create VPC to create one. The value cannot be changed after the cluster is created.

                      -

                      Node Subnet

                      -

                      Select the subnet to which the master nodes belong. If no subnet is available, click Create Subnet to create one. The value cannot be changed after the cluster is created.

                      -

                      Default Node Security Group

                      -
                      Select the security group automatically generated by CCE or use the existing one as the default security group of the node.
                      NOTICE:

                      The default security group must allow traffic from certain ports to ensure normal communication. Otherwise, the node cannot be created. For details, see Configuring Cluster Security Group Rules.

                      -
                      -
                      -

                      IPv6

                      -

                      If enabled, cluster resources, including nodes and workloads, can be accessed through IPv6 CIDR blocks.

                      -
                      • IPv4/IPv6 dual stack is not supported by clusters using the VPC networks.
                      +

                      No

                      +

                      After the cluster is created, the number of master nodes and the AZs where they are deployed cannot be changed.
                      -

                      +

                      + +

                      Step 2: Configure Network Settings

                      Network configuration follows a hierarchical management system. It ensures end-to-end network connectivity and security assurance for containerized applications through collaborative configuration of the cluster networks, container networks, and Service networks.

                      +
                      • Cluster network: handles communication between nodes, transmitting pod and Service traffic while ensuring cluster infrastructure connectivity and security.
                      • Container network: assigns each pod an independent IP address, enabling direct container communication and cross-node communication.
                      • Service network: establishes a stable access entry, supports load balancing, and optimizes traffic management for Services within a cluster.
                      +

                      Before configuring the network settings, you are advised to learn the concepts and relationships of the three types of networks. For details, see Networking Overview.

                      +
                      +

                      Configuring Network Settings for a CCE Standard Cluster

                      1. Configure cluster network settings. For details, see Table 2.

                        -
                        Table 2 Container network settings

                        Parameter

                        +
                        - + - - + - - + + + + + + + + + + + +
                        Table 2 Cluster network settings

                        Parameter

                        Description

                        +

                        Description

                        +

                        Modifiable After Cluster Creation

                        Network Model

                        +

                        VPC

                        Select VPC network or Tunnel network for your CCE standard cluster.

                        -

                        Select Cloud Native Network 2.0 for your CCE Turbo cluster.

                        -

                        For more information about their differences, see Overview.

                        +

                        Select a VPC for a cluster.

                        +

                        If no VPC is available, click Create VPC to create one. After the VPC is created, click the refresh icon.

                        +

                        No

                        DataPlane V2 (supported by CCE Turbo clusters)

                        +

                        Default Node Subnet

                        DataPlane V2 uses eBPF to enable features like Service ClusterIP, NetworkPolicy, and egress bandwidth. For details, see DataPlane V2 Network Acceleration.

                        -

                        This function is available for new clusters of v1.27 or later. After this function is enabled, CCE will automatically deploy the cilium-agent on every node in the cluster. Each cilium-agent will use 80 MiB of memory, and the memory usage will increase by 10 KiB whenever a new pod is added. After the cluster is created, you cannot disable this function. Additionally, the nodes can run only HCE OS 2.0. Therefore, enable this function only when you fully understand the constraints in DataPlane V2 Network Acceleration.

                        -
                        NOTE:

                        CCE DataPlane V2 is released with restrictions. To use this feature, submit a service ticket to CCE.

                        +

                        Select a subnet. Once selected, all nodes in the cluster will automatically use the IP addresses assigned within that subnet. However, during node or node pool creation, the subnet settings can be reconfigured.

                        +

                        No

                        +

                        Default Node Security Group

                        +

                        Select the security group automatically generated by CCE or select an existing one.

                        +

                        The default node security group must allow traffic from certain ports to ensure normal communication. Otherwise, the node cannot be created. For details, see Configuring Cluster Security Group Rules.

                        +

                        Yes

                        +

                        IPv6

                        +

                        After this function is enabled, the cluster supports the IPv4/IPv6 dual-stack, meaning each worker node can have both an IPv4 and IPv6 address. Both IP addresses support private and public network access. Before enabling this function, ensure that Default Node Subnet includes an IPv6 CIDR block.

                        +
                        • CCE standard clusters (using VPC networks): IPv6 is not supported.
                        +

                        No

                        +
                        +
                        +

                      2. Configure container network parameters. For details, see Table 3.

                        + +
                        + + + + + + + + + + - - - - - + - - - - - - - - - - -
                        Table 3 Container network settings

                        Parameter

                        +

                        Description

                        +

                        Modifiable After Cluster Creation

                        +

                        Network Model

                        +
                        The network model used by the container network in a cluster.
                        • Tunnel network: applies to large clusters (with up to 2000 nodes) and scenarios that do not demand high performance such as web applications and data middle- and back-end services with low access traffic.
                        • VPC network: applies to small clusters (with 1000 nodes or fewer) and scenarios that demand high performance such as AI and big data computing.
                        +
                        +

                        For more details about their differences, see Overview.

                        +

                        No

                        +

                        DataPlane V2 (supported by clusters using the VPC networks)

                        +

                        eBPF is used at the kernel layer for Kubernetes network acceleration, enhancing high-performance service communication through ClusterIP Services, precise traffic control via network policies, and intelligent bandwidth management with egress bandwidth. For details, see DataPlane V2 Network Acceleration.

                        +

                        This function has the restrictions below. For details, see the restrictions in DataPlane V2 Network Acceleration.

                        +
                        • Restrictions on clusters: This function can be enabled only for clusters of v1.27.16-r30, v1.28.15-r20, v1.29.13-r0, v1.30.10-r0, v1.31.6-r0, or later that use VPC networks.
                        • Restrictions on memory: After this function is enabled, CCE will automatically deploy the cilium-agent on every node in a cluster. Each cilium-agent will use 80 MiB of memory, and the memory usage will increase by 10 KiB whenever a new pod is added.
                        • Restrictions on OSs: After a node is created, it can only use HCE OS 2.0.
                        +
                        NOTE:

                        CCE DataPlane V2 is released with restrictions. To use this feature, submit a service ticket to CCE.

                        Network Policies (supported by CCE standard clusters using a tunnel network)

                        -

                        Policy-based network control for clusters. For details, see Configuring Network Policies to Restrict Pod Access.

                        -

                        After this function is enabled, if the CIDR blocks of a customer's service conflict with the on-premises CIDR blocks, the link to a newly added gateway may not be established.

                        -

                        For example, when a cluster accesses an external address through a Direct Connect connection, the external switch does not support ip-option. If the network policy is enabled, the network access may fail.

                        +

                        No

                        Container CIDR Block

                        +

                        Network Policies (supported by clusters using the tunnel networks)

                        Specify the CIDR block for containers, which determines the maximum number of containers allowed in the cluster. This parameter is available only for CCE standard clusters. CCE standard clusters allow both manual and automatic CIDR block settings.

                        -
                        • Manually set: You can customize the container CIDR blocks as needed. For cross-VPC passthrough networking, make sure the container CIDR block does not overlap with the VPC CIDR block to be accessed to prevent conflicts. For details, see Planning CIDR Blocks for a Cluster. The VPC network model allows you to configure multiple CIDR blocks, and container CIDR blocks can be added even after the cluster is created. For details, see Adding a Container CIDR Block for a Cluster.
                        • Auto select: CCE will randomly allocate a non-conflicting CIDR block from the ranges 172.16.0.0/16 to 172.31.0.0/16, or from 10.0.0.0/12, 10.16.0.0/12, 10.32.0.0/12, 10.48.0.0/12, 10.64.0.0/12, 10.80.0.0/12, 10.96.0.0/12, and 10.112.0.0/12. Since the allocated CIDR block cannot be modified after the cluster is created, you are advised to manually configure the CIDR blocks, especially in commercial scenarios.
                        +

                        Policy-based network control for a cluster. For details, see Configuring Network Policies to Restrict Pod Access.

                        +

                        After this function is enabled, if the CIDR blocks of a customer's service conflict with the on-premises CIDR blocks, the link to a newly added gateway may not be established.

                        +

                        For example, if a cluster uses a Direct Connect connection to access an external address, the external switch does not support ip-option. Enabling network policies in this scenario could result in network access failure.

                        +

                        Yes

                        Pod IP Addresses Reserved for Each Node (supported by CCE standard clusters using a VPC network)

                        +

                        Container CIDR Block

                        Specify the number of container IP addresses that can be allocated to each node (alpha.cce/fixPoolMask) when creating a cluster. This parameter determines the maximum number of pods that can be created on each node and cannot be changed after the cluster is created.

                        -

                        When a container network is used, each pod occupies one IP address. If a node's reserved container IP addresses are insufficient, pods cannot be created. For details, see Number of Allocatable Container IP Addresses on a Node.

                        -

                        Pod Subnet

                        -

                        Select the subnet to which the pod belongs. If no subnet is available, click Create Subnet to create one. This parameter is available only for CCE Turbo clusters. The pod subnet determines the maximum number of containers in a cluster. You can add pod subnets after a cluster is created.

                        -

                        Default Security Group

                        -
                        Select the security group automatically generated by CCE or use the existing one as the default security group of the containers.
                        NOTICE:

                        The default security group of containers must allow access from specified ports to ensure proper communication between containers in the cluster. For details about how to configure security group ports, see How Do I Harden the Automatically Created Security Group Rules for CCE Cluster Nodes?

                        -
                        -
                        -
                        -
                        -

                        - -
                        - - - - - - - - - - - - - -
                        Table 3 Service network settings

                        Parameter

                        -

                        Description

                        -

                        Service CIDR Block

                        -

                        Configure the Service CIDR blocks for containers in the same cluster to access each other. The value determines the maximum number of Services you can create. The value cannot be changed after the cluster is created.

                        -

                        Request Forwarding

                        -

                        Select IPVS or iptables for your cluster. For details, see Comparing iptables and IPVS.

                        -
                        • iptables is the traditional kube-proxy mode. This mode applies to the scenario where the number of Services is small or a large number of short connections are concurrently sent on the client. IPv6 clusters do not support iptables.
                        • IPVS allows higher throughput and faster forwarding. This mode is suitable for large cluster scales or when there are a large number of Services.
                        -

                        IPv6 Service CIDR Block

                        -

                        Configure this parameter only when IPv6 dual stack is enabled for a CCE Turbo cluster. This configuration cannot be modified after the cluster is created.

                        -
                        -
                        -

                        (Optional) Advanced Settings

                        -

                        - -
                        - - - - - - - - - - - - - - - - - - - - - - - - - - - -

                        Parameter

                        -

                        Description

                        -

                        IAM Authentication

                        -

                        CCE clusters support IAM authentication. You can call IAM authenticated APIs to access CCE clusters.

                        -

                        Certificate Authentication

                        -
                        • If Automatically generated is selected, the X.509-based authentication mode will be enabled by default. X.509 is a commonly used certificate format.
                        • If Bring your own is selected, the cluster can identify users based on the header in the request body for authentication.

                          Upload your CA root certificate, client certificate, and private key.

                          -
                          CAUTION:
                          • Upload a file smaller than 1 MB. The CA certificate and client certificate can be in .crt or .cer format. The private key of the client certificate can only be uploaded unencrypted.
                          • The validity period of the client certificate must be longer than five years.
                          • The uploaded CA root certificate is used by the authentication proxy and for configuring the kube-apiserver aggregation layer. If any of the uploaded certificates is invalid, the cluster cannot be created.
                          • Starting from v1.25, Kubernetes no longer supports certificate authentication generated using the SHA1WithRSA or ECDSAWithSHA1 algorithm. The certificate authentication generated using the SHA256 algorithm is supported instead.
                          +

                        CIDR block used by containers. This parameter determines the maximum number of containers in the cluster. CCE standard clusters support:

                        +
                        • Manually set: You can customize the container CIDR blocks as needed. For cross-VPC passthrough networking, make sure the container CIDR block does not overlap with the VPC CIDR block to be accessed to prevent conflicts. For details, see Planning CIDR Blocks for a Cluster. The VPC network model allows you to configure multiple CIDR blocks, and container CIDR blocks can be added even after the cluster is created. For details, see Expanding the Container CIDR Block of a Cluster That Uses a VPC Network.
                        • Auto select: CCE will randomly allocate a non-conflicting CIDR block from the ranges 172.16.0.0/16 to 172.31.0.0/16, or from 10.0.0.0/12, 10.16.0.0/12, 10.32.0.0/12, 10.48.0.0/12, 10.64.0.0/12, 10.80.0.0/12, 10.96.0.0/12, and 10.112.0.0/12. Since the allocated CIDR block cannot be modified after the cluster is created, you are advised to manually configure the CIDR blocks, especially in commercial scenarios.
                          NOTE:

                          After a cluster using a container tunnel network is created, the container CIDR block cannot be expanded later. To prevent IP address exhaustion, it is advised to set the container CIDR block with a maximum mask length of 19 bits.

                        CPU Management

                        -

                        If enabled, exclusive CPU cores can be allocated to workload pods. For details, see CPU Policy.

                        +

                        No

                        +

                        After a cluster using a VPC network is created, you can add container CIDR blocks to the cluster but cannot modify or delete the existing ones.

                        Disk Encryption for Master Nodes

                        +

                        Pod IP Addresses Reserved for Each Node (supported by clusters using the VPC networks)

                        If enabled, dynamic data and static data on disks can be encrypted, providing powerful security protection for your data.

                        -

                        After encryption, the disk read/write performance deteriorates, and the configuration cannot be modified after the cluster is created.

                        -

                        This function is available only for clusters of v1.25 or later.

                        +

                        The number of pod IP addresses that can be allocated on each node (alpha.cce/fixPoolMask). This parameter determines the maximum number of pods that can be created on each node.

                        +

                        In a container network, each pod is assigned a unique IP address. If the number of pod IP addresses reserved for each node is insufficient, pods cannot be created. For details, see Number of Allocatable Pod IP Addresses on a Node.

                        Overload Control

                        -

                        After this function is enabled, concurrent requests will be dynamically controlled based on the resource demands received by master nodes to ensure the stable running of the master nodes and the cluster. For details, see Enabling Overload Control for a Cluster.

                        -

                        Cluster Deletion Protection

                        -

                        A measure taken to prevent accidental deletion of clusters through the console or APIs. After this function is enabled, you will not be able to delete or unsubscribe from clusters on CCE. You can modify the function status in the cluster Settings after creating it.

                        -

                        Time Zone

                        -

                        The cluster's scheduled tasks and nodes are subject to the chosen time zone.

                        -

                        Resource Tag

                        -

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

                        -

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

                        -

                        Description

                        -

                        You can enter description for the cluster. A maximum of 200 characters are allowed.

                        +

                        No
                        - -

                        Step 3: Select Add-ons

                        Click Next: Select Add-on. On the page displayed, select the add-ons to be installed during cluster creation.

                        -

                        -

                        Basic capabilities

                        +

                      3. Configure Service network parameters. For details, see Table 4.

                        -

                        Add-on Name

                        +
                        - + - - + - - - - -
                        Table 4 Service network settings

                        Parameter

                        Description

                        +

                        Description

                        +

                        Modifiable After Cluster Creation

                        CCE Container Network (Yangtse CNI)

                        +

                        Service CIDR Block

                        This is the basic cluster add-on. It provides network connectivity, Internet access, and security isolation for pods in your cluster.

                        +

                        Configure an IP address range for the ClusterIP Services in a cluster. This parameter controls the maximum number of ClusterIP Services in a cluster. ClusterIP Services enable communication between containers in a cluster. The Service CIDR block cannot overlap with the node subnet or container CIDR block.

                        +

                        No

                        CCE Container Storage (Everest)

                        +

                        Request Forwarding

                        This add-on (CCE Container Storage (Everest)) is installed by default. It is a cloud native container storage system based on CSI and supports cloud storage services such as EVS.

                        +

                        Configure load balancing and route forwarding of Service traffic in a cluster. IPVS and iptables are supported. For details, see Comparing iptables and IPVS.

                        +
                        • iptables: the traditional kube-proxy mode. It applies to the scenario where the number of Services is small or a large number of short connections are concurrently sent on the client. IPv6 clusters do not support iptables.
                        • IPVS: allows higher throughput and faster forwarding. It is suitable for large clusters or when there are a large number of Services.

                        CoreDNS

                        -

                        This add-on (CoreDNS) is installed by default. It provides DNS resolution for your cluster and can be used to access the in-cloud DNS server.

                        +

                        No
                        -
                        Observability -
                        - - - - - - - - - - - - - -

                        Add-on Name

                        -

                        Description

                        -

                        Cloud Native Cluster Monitoring

                        -

                        (Optional) If selected, this add-on (Cloud Native Cluster Monitoring) will be automatically installed. Cloud Native Cluster Monitoring collects monitoring metrics for your cluster and reports the metrics to AOM. The agent mode does not support HPA based on custom Prometheus statements. If related functions are required, install this add-on manually after the cluster is created.

                        -

                        Cloud Native Logging

                        -

                        (Optional) If selected, this add-on (Cloud Native Log Collection) will be automatically installed. Cloud Native Logging helps report logs to LTS. After the cluster is created, you are allowed to obtain and manage collection rules on the Logging page of the CCE cluster console.

                        -

                        CCE Node Problem Detector

                        -

                        (Optional) If selected, this add-on (CCE Node Problem Detector) will be automatically installed to detect faults and isolate nodes for prompt cluster troubleshooting.

                        -
                        +

                        -
                        - -

                        Step 4: Configure Add-ons

                        Click Next: Add-on Configuration.

                        -

                        Basic capabilities

                        +

                        Configuring Network Settings for a CCE Turbo Cluster

                        1. Configure cluster network settings. For details, see Table 5.

                          -

                          Add-on Name

                          +
                          - + - - + - - + - - + + + + +
                          Table 5 Cluster network settings

                          Parameter

                          Description

                          +

                          Description

                          +

                          Modifiable After Cluster Creation

                          CCE Container Network (Yangtse CNI)

                          +

                          VPC

                          This add-on is unconfigurable.

                          +

                          Select a VPC for a cluster.

                          +

                          If no VPC is available, click Create VPC to create one. After the VPC is created, click the refresh icon.

                          +

                          No

                          CCE Container Storage (Everest)

                          +

                          Default Node Subnet

                          This add-on is unconfigurable. After the cluster is created, choose Add-ons in the navigation pane of the cluster console and modify the configuration.

                          +

                          Select a subnet. Once selected, all nodes in the cluster will automatically use the IP addresses assigned within that subnet. However, during node or node pool creation, the subnet settings can be reconfigured.

                          +

                          No

                          CoreDNS

                          +

                          Default Node Security Group

                          This add-on is unconfigurable. After the cluster is created, choose Add-ons in the navigation pane of the cluster console and modify the configuration.

                          +

                          Select the security group automatically generated by CCE or select an existing one.

                          +

                          The default node security group must allow traffic from certain ports to ensure normal communication. Otherwise, the node cannot be created. For details, see Configuring Cluster Security Group Rules.

                          +

                          Yes

                          +

                          IPv6

                          +

                          After this function is enabled, the cluster supports the IPv4/IPv6 dual-stack, meaning each worker node can have both an IPv4 and IPv6 address. Both IP addresses support private and public network access. Before enabling this function, ensure that Default Node Subnet includes an IPv6 CIDR block.

                          +
                          • CCE standard clusters (using VPC networks): IPv6 is not supported.
                          +

                          No
                          -

                          Observability

                          -

                          -
                          -

                          Add-on Name

                          +

                        2. Configure container network parameters. For details, see Table 6.

                          + +
                          - + - - + - - + - - + + + + + + + +
                          Table 6 Container network settings

                          Parameter

                          Description

                          +

                          Description

                          +

                          Modifiable After Cluster Creation

                          Cloud Native Cluster Monitoring

                          +

                          Network Model

                          Select an AOM instance for Cloud Native Cluster Monitoring to report metrics. If no AOM instance is available, click Creating Instance to create one.

                          +

                          The network model used by the container network in a cluster. Only Cloud Native Network 2.0 is supported.

                          +

                          For more details about this network model, see Overview.

                          +

                          No

                          Cloud Native Logging

                          +

                          DataPlane V2

                          Select the logs to be collected. If enabled, a log group named k8s-log-{clusterId} will be automatically created, and a log stream will be created for each selected log type.

                          -
                          • Container log: Standard output logs of containers are collected. The corresponding log stream is named in the format of stdout-{Cluster ID}.
                          • Kubernetes Events: Kubernetes logs are collected. The corresponding log stream is named in the format of event-{Cluster ID}.
                          • Kubernetes Audit Logs: Audit logs of the master nodes are collected. The log streams are named in the format of audit-{Cluster ID}.
                          • Control Plane Logs: Logs from critical components such as kube-apiserver, kube-controller-manage, and kube-scheduler that run on the master nodes are collected. The log streams are named in the format of kube-apiserver-{Cluster ID}, kube-controller-manage-{Cluster ID}, and kube-scheduler-{Cluster ID}, respectively.
                          -

                          If log collection is disabled, choose Logging in the navigation pane of the cluster console after the cluster is created and enable this function.

                          +

                          eBPF is used at the kernel layer for Kubernetes network acceleration, enhancing high-performance service communication through ClusterIP Services, precise traffic control via network policies, and intelligent bandwidth management with egress bandwidth. For details, see DataPlane V2 Network Acceleration.

                          +

                          This function has the restrictions below. For details, see the restrictions in DataPlane V2 Network Acceleration.

                          +
                          • Restrictions on clusters: The cluster version must be v1.27.16-r10, v1.28.15-r0, v1.29.10-r0, v1.30.6-r0, or later.
                          • Restrictions on memory: After this function is enabled, CCE will automatically deploy the cilium-agent on every node in a cluster. Each cilium-agent will use 80 MiB of memory, and the memory usage will increase by 10 KiB whenever a new pod is added.
                          • Restrictions on OSs: After a node is created, it can only use HCE OS 2.0.
                          +
                          NOTE:

                          CCE DataPlane V2 is released with restrictions. To use this feature, submit a service ticket to CCE.

                          +
                          +

                          No

                          CCE Node Problem Detector

                          +

                          Pod Subnet

                          This add-on is unconfigurable. After the cluster is created, choose Add-ons in the navigation pane of the cluster console and modify the configuration.

                          +

                          Select the subnet to which the pod belongs. If no subnet is available, click Create Subnet to create one. The pod subnet determines the maximum number of containers in a cluster. You can add pod subnets after a cluster is created.

                          +

                          Yes

                          +

                          Default Security Group

                          +

                          Select the security group automatically generated by CCE or select an existing one. This parameter controls inbound and outbound traffic to prevent unauthorized access.

                          +

                          The default security group of containers must allow access from specified ports to ensure proper communication between containers in the cluster. For details about how to configure security group ports, see How Do I Harden the Automatically Created Security Group Rules for CCE Cluster Nodes?

                          +

                          Yes

                          +
                          +
                          +

                        3. Configure Service network parameters. For details, see Table 7.

                          + +
                          + + + + + + + + + + + + + + + + + +
                          Table 7 Service network settings

                          Parameter

                          +

                          Description

                          +

                          Modifiable After Cluster Creation

                          +

                          Service CIDR Block

                          +

                          Configure an IP address range for the ClusterIP Services in a cluster. This parameter controls the maximum number of ClusterIP Services in a cluster. ClusterIP Services enable communication between containers in a cluster. The Service CIDR block cannot overlap with the node subnet or container CIDR block.

                          +

                          No

                          +

                          Request Forwarding

                          +

                          Configure load balancing and route forwarding of Service traffic in a cluster. IPVS and iptables are supported. For details, see Comparing iptables and IPVS.

                          +
                          • iptables: the traditional kube-proxy mode. It applies to the scenario where the number of Services is small or a large number of short connections are concurrently sent on the client. IPv6 clusters do not support iptables.
                          • IPVS: allows higher throughput and faster forwarding. It is suitable for large clusters or when there are a large number of Services.
                          +

                          No

                          +

                          IPv6 Service CIDR Block

                          +

                          Configure IPv6 addresses for Services. This parameter is only available after IPv6 is enabled.

                          +

                          No

                          +
                          +
                          +

                          4. + +

                          (Optional) Step 3: Configure Advanced Settings

                          Advanced settings extend and strengthen previous settings, enhancing security, stability, and compliance within clusters. This is achieved through capabilities like improved authentication, resource management, and security mechanisms.

                          +

                          + +
                          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                          Table 8 Advanced settings

                          Parameter

                          +

                          Description

                          +

                          Modifiable After Cluster Creation

                          +

                          IAM Authentication

                          +

                          CCE clusters support IAM authentication. You can call IAM authenticated APIs to access CCE clusters.

                          +

                          No

                          +

                          Certificate Authentication

                          +

                          Certificate authentication is used for identity authentication and access control. It ensures that only authorized users or services can access specific cluster.

                          +
                          • Automatically generated: CCE automatically creates and hosts X.509 certificates for your clusters. It automatically maintains and rotates cluster certificates.
                          • Bring your own: You can add a custom certificate to your cluster and use this certificate for authentication. In this case, you need to upload CA root certificate, client certificate, and client certificate private key.
                            CAUTION:
                            • Upload a file smaller than 1 MiB. The CA certificate and client certificate can be in .crt or .cer format. The private key of the client certificate can only be uploaded unencrypted.
                            • The validity period of the client certificate must be longer than five years.
                            • The uploaded CA root certificate is used by the authentication proxy and for configuring the kube-apiserver aggregation layer. If any of the uploaded certificates is invalid, the cluster cannot be created.
                            • In clusters of v1.25 and later, Kubernetes no longer supports certificate authentication generated using the SHA1WithRSA or ECDSAWithSHA1 algorithms. You are advised to use the certificates generated using the SHA-256 algorithm for authentication.
                            +
                            +
                          +

                          No

                          +

                          CPU Management

                          +

                          CPU management policies allow precise control over CPU allocation for pods. For details, see CPU Policy.

                          +
                          • Disabled: The default CPU affinity policy is used. Affinity policies other than the default behavior of the OS scheduler are not provided. While many CPUs remain available in the shared pool, workloads cannot exclusively use any of them.
                          • Enabled: Workload pods can exclusively use CPUs. If a pod with a QoS class of Guaranteed requests an integer number of CPUs, the containers within the pod are pinned to physical CPUs on the host node. This mode benefits workloads sensitive to CPU cache hit ratio and scheduling latency.
                          +

                          Yes

                          +

                          Disk Encryption for Master Nodes

                          +

                          After this function is enabled, dynamic and static data on disks can be encrypted, providing strong security protection for your data.

                          +

                          After encryption, the disk read/write performance deteriorates. This function is available only for clusters of v1.25 or later.

                          +

                          No

                          +

                          Overload Control

                          +

                          After this function is enabled, concurrent requests will be dynamically controlled based on the resource demands received by master nodes, ensuring stable running of the master nodes and the cluster. For details, see Enabling Overload Control for a Cluster.

                          +

                          Yes

                          +

                          Cluster Deletion Protection

                          +

                          After this function is enabled, you will not be able to delete or unsubscribe from clusters on CCE. This option is a measure to prevent accidental deletion of clusters through the console or APIs. You can modify the function status in Settings after creating it.

                          +

                          Yes

                          +

                          Time Zone

                          +

                          The cluster's scheduled tasks and nodes are subject to the chosen time zone.

                          +

                          ×

                          +

                          Resource Tag

                          +

                          Adding tags to resources allows for customized classification and organization. A maximum of 20 resource tags can be added.

                          +

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

                          +

                          Yes

                          +

                          Description

                          +

                          Cluster description helps users and administrators quickly understand the basic settings, status, and usage of a cluster. The description can contain a maximum of 200 characters.

                          +

                          Yes
                          +

                          Step 4: Select Add-ons

                          CCE provides a variety of add-ons to extend cluster functions and enhance the functionality and flexibility of containerized applications. You can select add-ons as required. Some basic add-ons are set as mandatory by default. If non-basic add-ons are not installed during cluster creation, they can still be added later on the Add-ons page after the cluster is created.

                          +
                          1. Click Next: Select Add-on. On the page displayed, select the add-ons to be installed during cluster creation.
                          2. Select basic add-ons to ensure the proper running of the cluster. For details, see Table 9.

                            + +
                            + + + + + + + + + + + + + + + + +
                            Table 9 Basic add-ons

                            Add-on

                            +

                            Description

                            +

                            CCE Container Network (Yangtse CNI)

                            +

                            This add-on provides network connectivity, Internet access, and security isolation for pods in a cluster. It is the basic cluster add-on.

                            +

                            CCE Container Storage (Everest)

                            +

                            This add-on (CCE Container Storage (Everest)) is installed by default. It is a cloud native container storage system based on CSI and supports cloud storage services such as EVS.

                            +

                            CoreDNS

                            +

                            This add-on (CoreDNS) is installed by default. It provides DNS resolution for your cluster and can be used to access the in-cloud DNS server.

                            +

                            NodeLocal DNSCache

                            +

                            (Optional) After you select this option, CCE will automatically install NodeLocal DNSCache. NodeLocal DNSCache improves cluster DNS performance by running a DNS cache proxy on cluster nodes.

                            +
                            -

                            Step 5: Confirm the Configuration

                            After the parameters are specified, click Next: Confirm configuration. The cluster resource list is displayed. Confirm the information and click Submit.

                            -

                            It takes about 5 to 10 minutes to create a cluster. You can click Back to Cluster List to perform other operations on the cluster or click Go to Cluster Events to view the cluster details.

                            +

                          3. Select the observability add-ons to experience the full observability function. For details, see Table 9.

                            +
                            + + + + + + + + + + + + + +
                            Table 10 Observability add-ons

                            Add-on

                            +

                            Description

                            +

                            Cloud Native Cluster Monitoring

                            +

                            (Optional) After you select this option, CCE will automatically install Cloud Native Cluster Monitoring. Cloud Native Cluster Monitoring collects monitoring metrics for your cluster and reports the metrics to AOM. The agent mode does not support HPA based on custom Prometheus statements. If related functions are required, install this add-on manually after the cluster is created.

                            +

                            Cloud Native Log Collection

                            +

                            (Optional) After you select this option, CCE will automatically install Cloud Native Log Collection. Cloud Native Log Collection helps report logs to LTS. After the cluster is created, you are allowed to obtain and manage collection rules on the Logging page of the CCE cluster console.

                            +

                            CCE Node Problem Detector

                            +

                            (Optional) After you select this option, CCE will automatically install CCE Node Problem Detector to detect faults and isolate nodes for prompt cluster troubleshooting.

                            +
                            -

                            Related Operations

                            +
                            +

                          +
                          +

                          Step 5: Configure Add-ons

                          Configure the selected add-ons to ensure they operate stably and accurately and meet service requirements.

                          +
                          1. Click Next: Configure Add-on.
                          2. Configure the basic add-ons. For details, see Table 11.

                            +

                            + + + + + + + + + + + + + + + + +
                            Table 11 Basic add-on settings

                            Add-on

                            +

                            Description

                            +

                            CCE Container Network (Yangtse CNI)

                            +

                            This add-on is unconfigurable.

                            +

                            CCE Container Storage (Everest)

                            +

                            This add-on is unconfigurable. After the cluster is created, you can go to Add-ons to modify the settings.

                            +

                            CoreDNS

                            +

                            This add-on is unconfigurable. After the cluster is created, you can go to Add-ons to modify the settings.

                            +

                            NodeLocal DNSCache

                            +

                            This add-on is unconfigurable. After the cluster is created, you can go to Add-ons to modify the settings.

                            +
                            +
                            +

                          3. Configure the observability add-ons. For details, see Table 12.

                            +
                            + + + + + + + + + + + + + +
                            Table 12 Observability add-on settings

                            Add-on

                            +

                            Description

                            +

                            Cloud Native Cluster Monitoring

                            +

                            Select an AOM instance for Cloud Native Cluster Monitoring to report metrics. If no AOM instance is available, click Creating Instance to create one.

                            +

                            Cloud Native Log Collection

                            +

                            Select the logs to be collected. If enabled, a log group named k8s-log-{clusterId} will be automatically created, and a log stream will be created for each selected log type.

                            +
                            • Container log: Standard output logs of containers are collected. The corresponding log stream is named in the format of stdout-{Cluster ID}.
                            • Kubernetes Events: Kubernetes logs are collected. The corresponding log stream is named in the format of event-{Cluster ID}.
                            • Kubernetes Audit Logs: Audit logs of the master nodes are collected. The log streams are named in the format of audit-{Cluster ID}.
                            • Control Plane Logs: Logs from critical components such as kube-apiserver, kube-controller-manage, and kube-scheduler that run on the master nodes are collected. The log streams are named in the format of kube-apiserver-{Cluster ID}, kube-controller-manage-{Cluster ID}, and kube-scheduler-{Cluster ID}, respectively.
                            +

                            If log collection is disabled, choose Logging in the navigation pane of the cluster console after the cluster is created and enable this option.

                            +

                            CCE Node Problem Detector

                            +

                            This add-on is unconfigurable. After the cluster is created, you can go to Add-ons to modify the settings.

                            +
                            +
                            +
                            +

                          +
                          +

                          Helpful Links

                          diff --git a/docs/cce/umn/cce_10_0031.html b/docs/cce/umn/cce_10_0031.html index 4e83e4dc2..12e59de3f 100644 --- a/docs/cce/umn/cce_10_0031.html +++ b/docs/cce/umn/cce_10_0031.html @@ -1,9 +1,11 @@ -

                          Managing a Cluster

                          +

                          Managing Clusters

                          How the Add-on Works

                          An Nginx ingress consists of the ingress object, ingress controller, and Nginx. The ingress controller assembles ingresses into the Nginx configuration file (nginx.conf) and reloads Nginx to make the configuration changes apply. When it detects that the pod in a Service changes, it dynamically changes the upstream server group configuration of Nginx. In this case, the Nginx process does not need to be reloaded. Figure 1 shows how this add-on works.

                          • An ingress is a group of access rules that forward requests to specified Services based on domain names or URLs. Ingresses are stored in the object storage service etcd and are added, deleted, modified, and queried through APIs.
                          • The ingress controller monitors the changes of resource objects such as ingresses, Services, endpoints, secrets (mainly TLS certificates and keys), nodes, and ConfigMaps in real time and automatically performs operations on Nginx.
                          • Nginx implements load balancing and access control at the application layer.
                          -
                          Figure 1 Working principles of NGINX Ingress Controller
                          +
                          Figure 1 Working principles of NGINX Ingress Controller

                          Precautions

                          • For clusters earlier than v1.23, kubernetes.io/ingress.class: "nginx" must be added to the annotation of the ingress created through the API.
                          • A dedicated load balancer must be of the network type (TCP/UDP) and support private networks (with a private IP address).
                          • If the node where NGINX Ingress Controller runs and containers on this node cannot access Nginx ingress, you need to configure anti-affinity for the workload pods and Nginx Ingress Controller. For details, see Configuring Anti-Affinity Between a Workload and Nginx Ingress Controller.
                          • During the NGINX Ingress Controller pod upgrade, 10s are reserved for deleting the NGINX Ingress Controller at the ELB backend.
                          • The timeout duration for the graceful exit of the NGINX Ingress Controller is 300s. If the timeout duration is longer than 300s during the upgrade of the NGINX Ingress Controller, persistent connections will be disconnected, and connectivity will be interrupted for a short period of time.

                          Prerequisites

                          Before installing this add-on, you have one available cluster and there is a node running properly. If no cluster is available, create one according to Creating a CCE Standard/Turbo Cluster.

                          -

                          Installing the Add-on

                          1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Add-ons, locate NGINX Ingress Controller on the right, and click Install.
                          2. On the Install Add-on page, configure the specifications as needed.

                            You can adjust the number of add-on pods and resource quotas as required. High availability is not possible with a single pod. If an error occurs on the node where the add-on instance runs, the add-on will fail.

                            +

                            Installing the Add-on

                            1. Log in to the CCE console and click the cluster name to access the cluster console.
                            2. In the navigation pane, choose Add-ons. Locate NGINX Ingress Controller on the right and click Install.
                            3. On the Install Add-on page, configure the specifications as needed.

                              You can adjust the number of add-on pods and resource quotas as required. High availability is not possible with a single pod. If an error occurs on the node where the add-on instance runs, the add-on will fail.

                            4. Configure the add-on parameters.