Sequential Breakdown and Verification of the Update Process

In this lesson, first, we will go through the sequential breakdown of the cluster update process and then verify the update.

We'll cover the following

Sequential Breakdown of the Update Process

Let’s see what happened when we executed the kops update command.

  1. Kops retrieved the desired state from the S3 bucket.

  2. Kops sent requests to AWS API to change the values of the workers ASG.

  3. AWS modified the values of the workers ASG by increasing them by 1.

  4. ASG created a new EC2 instance to comply with the new sizing.

  5. Protokube installed Kubelet and Docker and created the manifest file with the list of Pods.

  6. Kubelet read the manifest file and run the container that forms the kube-proxy Pod (the only Pod on the worker nodes).

  7. Kubelet sent a request to the kube-apiserver (through the dns-controller) to register the new node and join it to the cluster. The information about the new node is stored in etcd.

This process is almost identical to the one used to create the nodes of the cluster.

Get hands-on with 1200+ tech skills courses.