minor updates tutorial

- change afinity field value to match yaml spec
- update and reorder steps for cordoning nodes to make more sense. currenlty says "all but four". In reality, want to cordon the three nodes that the pods are scheduled on. not "all but four".
- add new line to code snippet for easier "copy/paste"
reviewable/pr5623/r1
Adam Fordham 2017-08-24 00:56:49 -07:00 committed by Andrew Chen
parent f7edb82547
commit 7b305cb11c
1 changed files with 9 additions and 8 deletions

View File

@ -1022,13 +1022,6 @@ Get the nodes in your cluster.
kubectl get nodes
```
Use [`kubectl cordon`](/docs/user-guide/kubectl/{{page.version}}/#cordon) to
cordon all but four of the nodes in your cluster.
```shell{% raw %}
kubectl cordon < node name >
```{% endraw %}
Get the `zk-budget` PodDisruptionBudget.
```shell
@ -1060,6 +1053,13 @@ kubernetes-minion-group-i4c4
{% endraw %}
```
Use [`kubectl cordon`](/docs/user-guide/kubectl/{{page.version}}/#cordon) to
cordon the three nodes that the Pods are currently scheduled on.
```shell{% raw %}
kubectl cordon < node name >
{% endraw %}```
Use [`kubectl drain`](/docs/user-guide/kubectl/{{page.version}}/#drain) to cordon and
drain the node on which the `zk-0` Pod is scheduled.
@ -1095,7 +1095,8 @@ Keep watching the StatefulSet's Pods in the first terminal and drain the node on
`zk-1` is scheduled.
```shell{% raw %}
kubectl drain $(kubectl get pod zk-1 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-local-data "kubernetes-minion-group-ixsl" cordoned
kubectl drain $(kubectl get pod zk-1 --template {{.spec.nodeName}}) --ignore-daemonsets --force --delete-local-data
node "kubernetes-minion-group-ixsl" cordoned
WARNING: Deleting pods not managed by ReplicationController, ReplicaSet, Job, or DaemonSet: fluentd-cloud-logging-kubernetes-minion-group-ixsl, kube-proxy-kubernetes-minion-group-ixsl; Ignoring DaemonSet-managed pods: node-problem-detector-v0.1-voc74
pod "zk-1" deleted
node "kubernetes-minion-group-ixsl" drained