Ingress controller
The reverse proxy running in a Kubernetes cluster that reads Ingress rules and routes incoming traffic accordingly.
In more detail
Popular controllers include ingress-nginx, Envoy-based controllers and Traefik. The controller terminates TLS, applies settings from annotations and only sends traffic to ready pods.
Example
ingressClassName: nginxRelated terms
- Ingress — A Kubernetes object that describes how outside HTTP traffic reaches services inside the cluster, by host name and URL path.
- reverse proxy — A server that receives requests on behalf of other servers and forwards them, returning their responses as if they were its own.
- TLS termination — Ending an encrypted TLS connection at a proxy or gateway, which decrypts the traffic and forwards it on to the service.
- data plane — The part of a system that actually carries the traffic or does the work, as opposed to the control plane that decides what should happen.
- nginx — A popular open-source web server and reverse proxy.
Taught in
- Kubernetes Ingress, Routing & TLS Termination — Production Full-Stack Engineering
- Bootstrap A Local Cluster And Check Your Context — Kubernetes: Production-Grade Container Orchestration
- NodePort, LoadBalancer And ExternalName — Kubernetes: Production-Grade Container Orchestration
- Ingress: Controllers, Hosts, Paths And TLS — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: DNS, Empty Endpoints And Broken Routes — Kubernetes: Production-Grade Container Orchestration