Service Restarts
The Service Restarts page rolls a platform deployment without shell access. A restart is a rolling update, so pods recycle one at a time rather than all at once. Open Operations, then Service Restarts (/admin/operations/services).
Restarting a service
The table lists each restartable service with its deployment name and a short description. Press Restart on a row. The dialog asks you to confirm, and offers a Wait for rollout to complete before returning option so the page reports success only once the new pods are up.
Use a restart after a configuration change that a service reads only at startup, or when a service is unresponsive and its pod has not recovered by itself.
A restart is a live change. Expect a short interruption while the new pod starts. Restarting the Core API briefly interrupts runners polling for tasks and the Control Centre’s own Sessions and Tasks pages. Restarting HEAT Auth briefly interrupts sign-in and token validation for both the dashboard and the Control Centre.