Skip to main content

HAP Microservices Upgrade

1. Pulling Images​

Before initiating the upgrade, ensure that all microservice nodes have successfully imported the images corresponding to their architecture (for offline environments, please refer to Offline Package Download first).

Tip

If there is no real-time progress output during the image pulling process, please wait for the task to complete patiently.

AMD64 Image Pulling
crictl pull registry.cn-hangzhou.aliyuncs.com/mdpublic/mingdaoyun-hap:7.2.3

2. Upgrading Microservices Version​

Notes

  • Resource Requirements: Rolling Upgrade requires approximately 40% free memory on each node server. If resources are insufficient, choose the Non-Rolling Upgrade option.

  • Additional Operation Check: Before upgrading, please carefully review the Version Release History page. If there are versions with the label “Includes Additional Operations” between the current version and the target version, ensure that corresponding guidelines are followed to complete the necessary tasks.

  • License Validity Check: Verify that your license key remains valid for the "upgrade service" period. If the release date of the target major version exceeds the license expiry date, forcing an upgrade will trigger system restrictions and cause the license to automatically downgrade to the free version. It is recommended to confirm the alignment between the version release date and licensing period prior to upgrading.

Go to the configuration file directory on the control node (default directory: /data/mingdao/script/kubernetes) and execute the following upgrade command:

AMD64 Rolling Upgrade
bash update.sh update hap 7.2.3
  • Estimated Duration: Restart is expected to complete within 3-5 minutes.
  • Status Verification: Run kubectl get pod, and confirm all Pod statuses have returned to 2/2.