---
title: Turbine - Restarting Services in Swimlane Using Kubernetes Rollout Restart Commands
slug: turbine-upgrade-guide/turbine-restarting-services-in-swimlane-using-kubernetes-rollout-restart-commands
docTags: 
createdAt: 2025-12-01T07:18:30.184Z
---

For restarting different services in Swimlane, use the Kubernetes commands as listed below. This guide will demonstrate how to restart the following services:

1. Turbine-engine
2. Turbine-api
3. Turbine-agent
4. Swimlane-api
5. Swimlane-tasks
6. Coredns (In case your DNS server has been modified and playbooks doesn't get these DNS modifications)
7. Rabbitmq-server (STS)

## Step-by-Step Instructions

### Restarting Deployments

The first five services (turbine-engine, turbine-API, turbine-agent, Swimlane-API, and swimlane-tasks) are managed as Kubernetes deployments. To restart these services, follow these steps:

1. **List All Deployments in the Namespace**
   First, list all the deployments in the swimlane namespace to ensure they are correctly mapped:

:::BlockQuote{indent="1"}
kubectl get deployments -A ### this command will list all the deployments in the cluster. 
kubectl get deployments -n \<namespace> ### this command will give only the deployments that are under in the specific namespace.
:::

:::Paragraph{indent="1"}
The above Command will display the following output:
:::

![](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/8132950141/original/l1p7Eb-5IQY1CkzxU0BlOXG-v7XDhCDhPQ.png?1721674819)

2. **Restart Each Deployment**
   Restart each deployment using the following commands, replacing \<namespace> with the actual namespace (usually swimlane):&#x20;

:::BlockQuote{indent="1"}
kubectl rollout restart deployment turbine-engine -n \<namespace>&#x20;
:::

:::BlockQuote{indent="1"}
kubectl rollout restart deployment turbine-api -n \<namespace>&#x20;
:::

:::BlockQuote{indent="1"}
kubectl rollout restart deployment turbine-agent -n \<namespace>&#x20;
:::

:::BlockQuote{indent="1"}
kubectl rollout restart deployment swimlane-api -n \<namespace>&#x20;
:::

:::BlockQuote{indent="1"}
kubectl rollout restart deployment swimlane-tasks -n \<namespace>&#x20;
:::

:::BlockQuote{indent="1"}
kubectl rollout restart deployment coredns -n \<namespace>&#x20;
:::

3. **Restarting StatefulSets**

:::Paragraph{indent="1"}
The **rabbitmq-server** is managed as a Kubernetes StatefulSet. To restart the RabbitMQ server pods, follow the steps below:
:::

:::Paragraph{indent="1"}
**Restart the StatefulSet**
Restart the StatefulSet using the following command, replacing\<namespace>with the actual namespace (typicallyswimlane):
:::

:::BlockQuote{indent="1"}
kubectl get sts -A # will give the list of STS&#x20;
kubectl get sts -n \<namespace> # will list the STS under the particular namespace.
:::

:::Paragraph{indent="1"}
For restarting the STS use the. below command:
:::

:::BlockQuote{indent="1"}
kubectl rollout restart sts rabbitmq-server -n \<namespace>
:::

By following these commands, you will restart the specified services in the Swimlane environment. This ensures that all pods associated with these deployments and StatefulSets are restarted, This would help us to apply updates and recover from any issues.