oc adm cordon vs oc adm manage-node node1 --schedulable=false

Author: mburke5678

modules/nodes-nodes-viewing-listing-pods.adoc

@@ -13,12 +13,12 @@ You can list all the pods on a specific node.
 +
 [source,bash]
 ----
-$ oc adm manage-node <node1> <node2> --list-pods [--pod-selector=<pod_selector>] [-o json|yaml]
+$ oc describe node <node1> <node2> --list-pods [--pod-selector=<pod_selector>] [-o json|yaml]
 ----
 
 * To list all or selected pods on selected nodes:
 +
 [source,bash]
 ----
-$ oc adm manage-node --selector=<node_selector> --list-pods [--pod-selector=<pod_selector>] [-o json|yaml]
+$ oc describe --selector=<node_selector> --list-pods [--pod-selector=<pod_selector>] [-o json|yaml]
 ----

modules/nodes-nodes-working-marking.adoc

@@ -14,14 +14,16 @@ scheduled on the node. Existing pods on the node are not affected.
 +
 [source,bash]
 ----
-$ oc adm manage-node <node1> <node2> --schedulable=false
+$ oc adm cordon <node>
 ----
 +
 For example:
 +
 [source,bash,options="nowrap"]
 ----
-$ oc adm manage-node node1.example.com --schedulable=false
+$ oc cordon node1.example.com
+node/node1.example.com cordoned
+
 NAME                 LABELS                                        STATUS
 node1.example.com    kubernetes.io/hostname=node1.example.com      Ready,SchedulingDisabled
 ----
@@ -30,9 +32,8 @@ node1.example.com    kubernetes.io/hostname=node1.example.com      Ready,Schedul
 +
 [source,bash]
 ----
-$ oc adm manage-node <node1> <node2> --schedulable
+$ oc uncordon <node1>
 ----
 +
-Alternatively, instead of specifying specific node names (for example, `<node1>
-<node2>`), you can use the `--selector=<node_selector>` option to mark selected
+Alternatively, instead of specifying specific node names (for example, `<node>`), you can use the `--selector=<node_selector>` option to mark selected
 nodes as schedulable or unschedulable.