It was tough to understand — Kubernetes: Ingress and Ingress controller Resources
Ingress makes our Ops & Load balancer management simple and easy. We get a Single endpoint for all Kube Services.
Ingress resource : metadata of the /Routes and Kube endpoints (Pods)
Ingress Controller resource : is the actual Nginx LB — Container (Pod) running, which uses the Metadata specified in all Kube Ingress Objects.
Ingress Controller → watches the Kube API for changes in Services and Pods, then updates the Nginx Config file of the Nginx Pod automatically. This process is called Dynamic configuration of Upstream servers inside the Nginx Config file.
Ingress helps you in routing requests to Multiple Kube Services based on the request host or path, using a Single entry point. We don’t need multiple Host endpoints for different Kube Services.
All Kube Services can have a Single end point. We can use Path based routing, using the Kube — Ingress resource.
Ingress: additional info and code snippets:
