A Practical Guide to Kubernetes/

...

/

Exploring and Verifying the Output

Exploring and Verifying the Output

Explore the sequential occurrence of events as a result of the rolling update and verify the change of Kubernetes version.

We'll cover the following...

Exploring the Sequence of Events

The rolling update has finally finished, and the output starts with the same information we got when we asked for a preview, so there’s not much to comment.

Press + to interact
I0225 23:03:03.993068       1 instancegroups.go:130] Draining the node: "ip-172-20-40-167...".
node "ip-172-20-40-167..." cordoned
node "ip-172-20-40-167..." cordoned
WARNING: Deleting pods not managed by ReplicationController, ReplicaSet, Job, DaemonSet or StatefulSet: etcd-server-events-ip-172-20-40-167..., etcd-server-ip-172-20-40-167..., kube-apiserver-ip-172-20-40-167..., kube-controller-manager-ip-172-20-40-167..., kube-proxy-ip-172-20-40-167..., kube-scheduler-ip-172-20-40-167...
node "ip-172-20-40-167..." drained

Instead of destroying the first node, kOps picks one primary node and drains it. This way, the applications running on it can shut down gracefully. We can see that it drains the following:

  • etcd-server-events
  • etcd-server-ip
  • kube-apiserver
  • kube-controller-manager
  • kube-proxy
  • kube-scheduler
  • Pods running on the
...
Access this course and 1400+ top-rated courses and projects.