yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
218900ecfc237f6c0ba9f9684f9afa10f1d5ea9a
doc-exports/docs/cce/umn/cce_10_0531.html
qiujiandong1 ab1e53a279 CCE UMN 20251031 version 
Reviewed-by: Gergo-Bence Lorincz <a200452876@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
2026-01-15 10:25:22 +00:00

2.2 KiB
Raw Blame History

Add-on Configuration Consistency

Check Items

Manual modifications to add-on configuration parameters (typically ConfigMaps), instead of modifications through the CCE console or add-on API updates, may be overwritten after an upgrade, potentially affecting service operation.

Solutions

  • Non-forced upgrades
    • When upgrading your cluster, if the add-on version is compatible with both the source and target cluster versions, you need to determine whether to upgrade the add-on version.
    • If the add-on configurations are inconsistent but a forced upgrade is not required, you can skip this check item and leave the add-on upgrade option unselected during the cluster upgrade.
  • Forced upgrades
    • If the add-on version is no longer compatible with the target cluster version, you must upgrade the add-on.
    • If the add-on configurations are inconsistent and a forced upgrade is required, you cannot skip this check item. In this case, reconfigure the add-on parameters through the CCE console or APIs to ensure configuration consistency before proceeding with the upgrade.

    If the CoreDNS add-on configurations are inconsistent, see CoreDNS Configuration Consistency.