Member-only story
AWS EKS: The Ultimate Guide To Deploy AWS Load Balancer Controller add-on
Are you having a hard time deploying an Ingress Controller on AWS Elastic Kubernetes Service?
Ingress Controllers are essential in a Kubernetes infrastructure but deploying them on Cloud Providers’ Ecosystems can quickly drive you mad.
I can see a folk trying to install a Kubernetes Ingress Controller on AWS for the first time: and … again … IT DOES NOT WORK!
No worries. In this article, I’ll walk you through how to set up an Ingress Controller on EKS with a clear understanding of all the concepts in the easiest and quickest way possible.
What is an Ingress Controller?
In order to allow HTTP external traffic into your Kubernetes cluster, we often (if not always) use Ingress Controllers. Let’s clarify first what an Ingress Controller is.
Ingress is a Kubernetes Object which exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. Traffic routing is controlled by rules defined on the Ingress resource. — Kubernetes Official Documentation.
In other words, an Ingress is a Kubernetes resource that has got a set of HTTP rules to direct traffic to your cluster resources.
📌 But there is an important consideration here: an Ingress alone is like a mere cog in the routing machine; it needs an Ingress Controller to work. The Ingress Controller is the resource that will apply those rules and control the routing to your cluster.
There are tons of Ingress Controllers out there and none of them come natively installed on Kubernetes: we must install them. You should agree with me that it makes sense since each provider has its own implementation.
