Setup Kubernetes Ingress on GKE

We have seen in my previous blog how we can access the application externally using Service object. We have two options to get traffic outside the cluster

• NodePort
• LoadBalancer

Mostly the load balancer option is preferred in the public cloud providers.

Limitations:

1. The problem is that one LoadBalancer can only point towards a single Kubernetes service object.

So now if you have 100 microservices -> you need 100 load balancers -> very expensive

2. Let’s suppose that you have a web service running at test.com and you want test.com/users to go to one microservice and test.com/notifications to go to another completely separate microservice. Before the arrival of Ingress, you would need to set up your own Kubernetes Service and do the internal path resolution to your app.

The above issue is resolved using Kubernetes Ingress resource.

What is Ingress ?

An API object that manages external access to the…