EKS cluster and Ingress-NGINX
Site moved to https://vettom.pages.dev
Ingress-Nginx is a popular Reverse Proxy and Loadbalancer. In this example, I will demonstrate complete EKS cluster with ingress controller and Sample app to verify installation.
EKS with ingress-Nginx contains everything required for you to spin up a new cluster and expose application via Ingress-Nginx controller. Source Code. Sample app.
Why do we need AWS LB controller?
If Ingress-NGINX is configured without LB controller, it will provision LB with target type of NodePort. VPC CNI and LB controller enables you to make use of target type 'ip' and traffic can flow direct to Pod's IP and Port
| Advantages of Ingress-Nginx over ALB controller? |
|---|
| Services can be configured using Cluster IP, not exposing in local network |
| Traffic routed direct to pod and its port from Ingress controller |
| Ingress metrics (prometheus) available with in cluster |
| No IAM permissions requirement (LB controller requires IAM) |
| Certificate manager can be used for SSL certs |
Resources
- VPC with 2 privat and 2 public zones
- VPC CNI add-on with prefix delegation
- AWS Loadbalancer controller
- Ingress-Nginx controller.