Kubernetes is everywhere nowadays, so are the container images and fetching the images from a private registry is a norm because of N number of reasons including security, that being the topmost.

\n\n\n\n

Recap

\n\n\n\n

Just to give you a heads up before we dive further, let’s assume I run kubectl create deployment nginx –image nginx what do you think happens?

\n\n\n\n

1. Using kubeconfig, kubectl first authenticates with the API server.

\n\n\n\n

2. It then constructs a deployment object using the values which we provided like deployment name as nginx, image to be used as nginx and some default values and then sends a request to the API server.

\n\n\n\n

3. API server then validates the request and the object definition.

\n\n\n\n

4. This is further stored in etcd datastore.

\n\n\n\n

5. Then the controller manager specifically deployment controller comes into the picture which creates a replica set.

\n\n\n\n

6. Then the replica set creates a pod (this is where our nginx image will be used).

\n\n\n\n

7. Then the scheduler assigns the pod to a node, where it will run based on multiple conditions. If interested please check out my previous article on what all things happens in the background: