Sequential Breakdown of the Process

Understand the sequential breakdown of the Kubernetes Deployment process.

We'll cover the following

The sequence#

Before we move onto Deployment updates, we’ll go through our usual ritual of seeing the process through a sequence diagram. We won’t repeat the explanation of the events that happened after the ReplicaSet object was created as those steps were already explained in the previous chapters.

  1. Kubernetes client (kubectl) sent a request to the API server requesting the creation of a Deployment defined in the go-demo-2-db.yml file.

  2. The deployment controller is watching the API server for new events, and it detected that there is a new Deployment object.

  3. The deployment controller creates a new ReplicaSet object.

The sequence of events followed by request to create a deployment
The sequence of events followed by request to create a deployment

The above illustration is self-explanatory with the sequence of the processes linked to the deployment process.

Deploying new Releases
Updating Deployments
Mark as Completed
Report an Issue