---
title: Stop and Restart a Single-Node Deployment
slug: install-10x/stop-and-restart-a-single-node-deployment
docTags: 
createdAt: 2025-07-16T13:29:40.596Z
---

On occasion, single-node SPI deployments must be stopped and restarted. One example of this is when you need to perform scheduled maintenance.

To stop and restart a single-node SPI Deployment:

1. Login to the node as a user with administrator privileges.
2. Find the name of the node. In the example within this topic, the node is named `master3a`.

:::BlockQuote{indent="1"}
\# kubectl get nodes
NAME       STATUS   ROLES    AGE   VERSION
master3a   Ready    master   30d   v1.17.3
:::

3. Drain the node.

:::BlockQuote{indent="1"}
\# /bin/kubectl drain master3a --ignore-daemonsets --delete-local-data
:::

4. Check that the node is in the “Ready,SchedulingDisabled” status.

:::BlockQuote{indent="1"}
\# kubectl get nodes
NAME       STATUS                     ROLES    AGE   VERSION
master3a   Ready,SchedulingDisabled   master   27d   v1.17.3
:::

5. Stop or restart the server or VM.
6. Next, uncordon the node (i.e. make the node schedulable).

:::BlockQuote{indent="1"}
\# kubectl uncordon master3a
:::

7. Finally, ensure that the node is in the “Ready” status.

:::BlockQuote{indent="1"}
\# kubectl get nodes
NAME       STATUS   ROLES    AGE   VERSION
master3a   Ready    master   30d   v1.17.3
:::