A rolling restart will restart all deployed pods one at a time (while keeping the other pods running) until they have all been updated.
The primary benefit of performing a rolling restart is that your environment can keep functioning and your application will not be affected or go down.
You might need to perform a rolling restart in the following situations:
- Unforeseen software behavior.
- A pod is stuck in a terminating state for a long time.
- An error occurs in a pod and needs to be restarted.
- Timeouts or exceptions.
- Erroneous deployments.
- Requesting persistent volumes that are not available.
While there are many pod restart methods, the simplest and safest way to restart Kubernetes pods is by performing a rolling restart.
- An environment must be created and launched with appropriate resources.
- In these running environments, applications must have been deployed.
- Login to Facets Control Plane.
- Select the Environment in your defined Blueprint.
- Navigate to the Resources tab from the sidebar and select the application in which you want to perform a rolling restart.
- In Live Releases tab, click on the Rolling Restart All button under the Pods section.
- A popup will appear for confirmation.
- Click on "Confirm" button to start rolling restart of all pods in the application.
- A success toaster is displayed if the rolling restart is initiated successfully.
- An error toaster with appropriate error message is displayed if the rolling restart fails.
Updated 7 months ago