Sequential Breakdown of the Process

In this lesson, we will first go through the sequential breakdown of Ingress resource creation process and then create the second Ingress resource.

We'll cover the following

Let’s see, through a sequence diagram, what happened when we created the Ingress resource.

  1. The Kubernetes client (kubectl) sent a request to the API server requesting the creation of the Ingress resource defined in the ingress/go-demo-2.yml file.

  2. The ingress controller is watching the API server for new events. It detected that there is a new Ingress resource.

  3. The ingress controller configured the load balancer. In this case, it is nginx which was enabled by minikube addons enable ingress command. It modified nginx.conf with the values of all go-demo-2-api endpoints.

Get hands-on with 1400+ tech skills courses.