Ingress controller
An ingress controller is a Kubernetes component that implements Ingress routing rules by directing external network traffic to services within a cluster.
Acing the Certified Kubernetes Administrator Exam, Second Edition
An ingress controller is a Kubernetes component that implements Ingress routing rules for external access to services.
- How it is used
- Routes external HTTP and HTTPS requests through Ingress rules to Services inside the cluster.
- How deep it goes
- Works through controller installation, backend creation, Ingress configuration and request verification without detailing controller internals.
- Examples
- Uses an ingress-nginx installation, a hello Deployment and ClusterIP Service, a two-host Ingress manifest and a curl check.
- What you can do after
- Operate/configure it by installing a controller, defining Service-backed Ingress rules and verifying external requests.
Kubernetes in Action, Second Edition
An ingress controller is a Kubernetes controller that implements external HTTP or HTTPS traffic routing defined by Ingress objects.
- How it is used
- Routes external HTTP or HTTPS requests to cluster Services through one externally reachable ingress proxy.
- How deep it goes
- Explains API watching, proxy configuration, installation, controller selection, and routing, while deferring custom HTTPRoute contents.
- Examples
- Uses NGINX installation commands, kind and Minikube setup, multi-controller IngressClass selection, and an HTTPRoute resource backend.
- What you can do after
- Operate/configure it by installing an implementation, creating Ingress rules, selecting an IngressClass, and routing requests to Services.
Read how Kubernetes in Action, Second Edition explains ingress controller →
Software Security for Developers
An ingress controller is software that implements Kubernetes ingress routing and commonly handles TLS termination, load balancing, and path-based routing.
- How it is used
- Centralizes external Kubernetes traffic routing and TLS termination for public-facing applications.
- How deep it goes
- Explains the deployment choice, certificate-management rationale, and manifest configuration, but not controller internals.
- Examples
- Uses an ACME web application, app.acme.com, an NGINX manifest, a TLS secret, and the acme-webapp service.
- What you can do after
- Configure HTTPS ingress with certificate references, redirects, host rules, paths, and a Kubernetes service backend.
Read how Software Security for Developers explains ingress controller →
Google Anthos in Action
An ingress controller is a Kubernetes control-plane component that implements Ingress routing rules for incoming traffic.
- How it is used
- Exposes web-based Kubernetes Services and routes incoming traffic through declared Ingress rules.
- How deep it goes
- Explains controller placement, proxy behavior, external load balancing, and routing, but does not provide configuration commands.
- Examples
- Uses ASM Ingress, TCP LoadBalancer Services, and a three-tier GKE migration with frontend and database access policies.
- What you can do after
- Evaluate and configure exposure choices for web-based and TCP-based Services across Anthos and GKE deployments.
Read how Google Anthos in Action explains ingress controller →
Related concepts
- ingress objectimplements · A Kubernetes Ingress is an API resource that specifies rules for routing external HTTP and HTTPS requests to services within a cluster.
- ingress routing ruleimplements · An ingress routing rule maps conditions such as a host and path to a destination service and port for incoming network traffic.
- reverse proxyconfigures · A reverse proxy is a server-side intermediary that receives client requests, forwards them to backend servers or services, and relays their responses to clients.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.