openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Merge pull request #77976 from openshift-cherrypick-robot/cherry-pick-76445-to-enterprise-4.16

Browse Source 
[enterprise-4.16] Drain master node doesn't succeed without --force option
This commit is contained in:
Michael Burke
2024-06-24 13:47:51 -04:00
committed by GitHub
parent 56326babb3 58a07a642c
commit 664f0a4d0d
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
modules/graceful-shutdown.adoc
View File

@@ -62,7 +62,7 @@ node/ci-ln-mgdnf4b-72292-n547t-worker-c-vcmtn cordoned
[source,terminal]
+
----
$ for node in $(oc get nodes -l node-role.kubernetes.io/worker -o jsonpath='{.items[*].metadata.name}'); do echo ${node} ; oc adm drain ${node} --delete-emptydir-data --ignore-daemonsets=true --timeout=15s ; done
$ for node in $(oc get nodes -l node-role.kubernetes.io/worker -o jsonpath='{.items[*].metadata.name}'); do echo ${node} ; oc adm drain ${node} --delete-emptydir-data --ignore-daemonsets=true --timeout=15s --force ; done
----
. Shut down all of the nodes in the cluster. You can do this from your cloud provider’s web console, or by running the following loop:
@@ -107,4 +107,4 @@ Cluster administrators are responsible for ensuring a clean restart of their own
[IMPORTANT]
====
If you deployed your cluster on a cloud-provider platform, do not shut down, suspend, or delete the associated cloud resources. If you delete the cloud resources of a suspended virtual machine, {product-title} might not restore successfully.
====
====