Sequential Breakdown of the Process

In this lesson, we will go through the sequential processes kicked off by a Service creation.

We'll cover the following

The Sequence

The processes that were initiated with the creation of the Service are as follows:

  1. Kubernetes client (kubectl) sent a request to the API server requesting the creation of the Service based on Pods created through the go-demo-2 ReplicaSet.

  2. Endpoint controller is watching the API server for new service events. It detected that there is a new Service object.

  3. Endpoint controller created endpoint objects with the same name as the Service, and it used Service selector to identify endpoints (in this case the IP and the port of go-demo-2 Pods).

  4. kube-proxy is watching for service and endpoint objects. It detected that there is a new Service and a new endpoint object.

  5. kube-proxy added iptables rules which capture traffic to the Service port and redirect it to endpoints. For each endpoint object, it adds iptables rule which selects a Pod.

  6. The kube-dns add-on is watching for Service. It detected that there is a new service.

  7. The kube-dns added db's record to the dns server (skydns).

Get hands-on with 1400+ tech skills courses.