Upgrading Pods Without Interrupting Services
Scenario
You can use rolling upgrade to upgrade pods without interrupting services.
In this mode, pods are upgraded one by one, not all at once.
Prerequisites
The workload to be upgraded has at least two pods. If there is only one pod, you are advised to perform the upgrade after manually scaling the workload into two pods.
Procedure
- Log in to the CCE console. In the navigation pane on the left, choose .
- In the workload list, click the name of the workload to be upgraded. The workload details page is displayed.
- On the Scaling tab page, check the value of Maximum Number of Unavailable Pods. The value should range from 0 to the number of workload pods. If the maximum number of unavailable pods is the number of workload pods, services may be interrupted. Figure 2 Setting maximum number of unavailable pods
- Upgrade the workload in rolling upgrade mode.
- In the workload list, click the name of the workload to be upgraded. The workload details page is displayed.
- On the Upgrade tab page, replace the image or select a new image version.
- Click Submit and OK. Figure 3 Replacing the image or the image version
- On the Pods tab page, you can view that one pod is being created and then the other is being stopped. This ensures that there is always a pod running and the service is not interrupted during the upgrade. Figure 4 Rolling upgrade
- Click
on the right. If both pods are in the running state, the upgrade is successful.
Last Article: Properly Allocating Container Computing Resources
Next Article: Modifying Kernel Parameters Using a Privileged Container
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.