Skip to content

Commit 0f91b4e

Browse files
committed
OSDOCS#12867: Noting that SNO can't have workloads running to shut down
1 parent 777cf41 commit 0f91b4e

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

modules/graceful-shutdown.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@ You can shut down a cluster until a year from the installation date and expect i
1717

1818
* You have access to the cluster as a user with the `cluster-admin` role.
1919
* You have taken an etcd backup.
20+
* If you are running a {sno} cluster, you must evacuate all workload pods off of the cluster before you shut it down.
2021
2122
.Procedure
2223

@@ -77,7 +78,7 @@ Ensure that the control plane node with the API VIP assigned is the last node pr
7778
$ for node in $(oc get nodes -o jsonpath='{.items[*].metadata.name}'); do oc debug node/${node} -- chroot /host shutdown -h 1; done <1>
7879
----
7980
+
80-
<1> `-h 1` indicates how long, in minutes, this process lasts before the control plane nodes are shut down. For large-scale clusters with 10 nodes or more, set to `-h 10` or longer to make sure all the compute nodes have time to shut down first.
81+
<1> `-h 1` indicates how long, in minutes, this process lasts before the control plane nodes are shut down. For large-scale clusters with 10 nodes or more, set to `-h 10` or longer to make sure all the compute nodes have time to shut down first.
8182
+
8283
.Example output
8384
[source,terminal]

0 commit comments

Comments
 (0)