May 2018
Intermediate to advanced
554 pages
13h 51m
English
DaemonSets keep monitoring every Kubernetes node, so when one of the Pods crashes, DaemonSets recreates it on the same Kubernetes node.
To simulate this, go back to the DaemonSets example and use kubectl delete pods to delete an existing Pod from node1 manually, as follows:
$ kubectl delete pod ram-check-6ldngpod "ram-check-6ldng" deleted$ kubectl get pods -o wideNAME READY STATUS RESTARTS AGE IP NODEram-check-6ldng 1/1 Terminating 0 29m 10.233.102.132 node1ram-check-ddpdb 1/1 Running 0 29m 10.233.75.5 node2ram-check-dpdmt 1/1 Running 0 13m 10.233.71.0 node3$ kubectl get pods -o wideNAME READY STATUS RESTARTS AGE IP NODEram-check-ddpdb 1/1 Running 0 30m 10.233.75.5 node2ram-check-dh5hq 1/1 Running 0 24s 10.233.102.135 ...
Read now
Unlock full access