Day-33
Today’s focus was on Kubernetes Ingress & Ingress Controllers — the real gateway that connects the outside world to your in-cluster applications
In Kubernetes, Services like NodePort and LoadBalancer can expose applications externally — but they have their own challenges: higher cost, cloud dependency, and limited flexibility.
That’s where Ingress becomes a game changer
That’s where Ingress shines :
1) Learned how Ingress acts as a smart traffic router using host-based and path-based rules
2) Understood the difference between Ingress Resource, Ingress Controller, and LoadBalancer
3) Explored NGINX Ingress Controller setup (deployment via YAML and Helm)
4) Implemented routing for a “Hello World” app with custom domain mapping
5) Discovered how ingressClassName prevents conflicts in multi-controller clusters
Comments
Post a Comment