Why does custom configuration affect upgrades?

After the platform deployment is completed, you can modify some default configurations based on actual business needs. The modified non-platform default configurations are personalized configurations, such as component environment variables, image addresses, startup parameters, resource limits, etc.

To avoid your personalized configurations being overwritten during the upgrade process, the platform will retain your personalized configurations during the upgrade. However, this also poses a risk of platform abnormalities or upgrade failures due to incompatible configurations between the new and old versions after the upgrade. For example, if the current environment version is v3.6 and the default component image version is modified, and the platform is upgraded to v3.8, the component image version in the personalized configuration is still v3.6, which will cause platform abnormalities and upgrade failures due to incompatible new and old versions.

Therefore, before upgrading, the platform will remind you of the existence of personalized configurations and hope that you can confirm with technical support personnel whether to delete personalized configurations or adjust them to adapt to the upgraded version.