Skip to main content

Pod Restart

Last updated 27/02/2026

Overview​

The pod restart capability in Five enables authorized users to restart an individual pod if it becomes unresponsive, unhealthy, or temporarily disconnected, without requiring removal and full redeployment. Pods can be restarted directly, significantly improving recovery speed, reducing downtime, and simplifying operational management.

Purpose​

The pod restart capability is designed to:

  • Improve service reliability
  • Reduce downtime during transient failures
  • Minimize unnecessary redeployments
  • Provide controlled operational recovery
  • Maintain stability across development, testing, and production environments

Environment Access and Role Permissions​

Pod restart access is controlled by both environment and user role.

Development Environment​

In the development environment, pod restart is available to users with the following roles:

  • Admin
  • Control
  • Developer

Pods can be restarted via:

  • Five's toolbar
  • Cluster Management

This enables fast recovery during development and debugging cycles.

Testing Environment​

In the testing environment, pod restart is available only to:

  • Admin
  • Control

Restart must be performed via the Cluster Management in the Testing window. The toolbar restart option is not available in testing to ensure tighter operational control.

Production Environment​

In the production environment, pod restart is available only to:

  • Admin
  • Control

Restart must be performed via the Cluster Management in the Production window. This ensures governance, operational oversight, and reduced risk of unintended disruption in live systems.

When to Restart a Pod​

A pod restart is appropriate when:

  • The pod becomes unresponsive
  • Health checks fail
  • The pod drops out of the cluster
  • A transient runtime issue occurs
  • Resource exhaustion temporarily impacts availability

Restarting is intended for transient failures. Persistent configuration or code-related issues require running or deployment of application.

Operational Impact​

Reduced recovery time - restarting a single pod avoids reinitializing the entire deployment.

Lower operational risk - deployment configuration remains untouched.

Improved resilience - encourages runtime-level recovery before deployment-level intervention.

Controlled governance - role-based access and environment segmentation ensure restart authority is aligned with operational responsibility.

How to Restart Pods​

Your application must be deployed to have the restart pod capability.

Restart Development Pod​

1. Click the Restart Pod from Development button in Five's toolbar; or


Restart Pod from Development button
Figure 1 - Restart Pod from Development button

2. Click the Restart Pod from Development button in the Cluster Management.


Restart Pod from Development button
Figure 2 - Restart Pod from Development button

Restart Testing Pod​

1. Click the Restart Pod from Testing button in the Cluster Management.


Restart Pod from Testing button
Figure 3 - Restart Pod from Testing button

Restart Production Pod​

1. Click the Restart Pod from Production button in the Cluster Management.


Restart Pod from Production button
Figure 4 - Restart Pod from Production button