Sequential Breakdown of the Process

Let’s see what happens when we create an Ingress resource.

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

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

3. The Ingress controller configures the load balancer. In this case, it is nginx that modifies nginx.conf with the values of all go-demo-2-api endpoints.

Now that one of the applications is accessible through Ingress, we should apply the same principles to the other application.

Creating a second ingress resource