liveBook · Manning

Ingress controller

As explained in Google Anthos in Action

An ingress controller is a Kubernetes control-plane component that implements Ingress routing rules for incoming traffic.

An ingress controller implements Kubernetes Ingress rules for incoming traffic. It typically runs inside the cluster as an L7 proxy, while an L3/L4 load balancer exposes the controller externally. The controller listens for requests and routes them to the appropriate Service, making Ingress the recommended exposure method for web-based Services. section 10.4.1

Deployment choices depend on traffic type and platform:

  • Use Ingress for web-based HTTP(S) Services and define its rules as part of the Service deployment pipeline. section 10.4.1
  • Use a Service of type LoadBalancer for TCP-based Services when direct load-balancer exposure is appropriate; this creates an accessible Service VIP. section 10.4.1
  • Use ASM Ingress when Anthos requires additional Layer 7 functions such as authentication and authorization, including for HTTP(S) or TCP traffic. section 10.4.1

Three-tier migration

A migrated three-tier application can expose its frontend through the GKE Google load balancer for scalability, while network policies restrict access so only frontend Pods reach the application layer and only the application layer reaches the database. section 15.5

How Google Anthos in Action covers it

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 it assumes
Assumes familiarity with Kubernetes clusters, Services, Pods, load balancers, and deployment pipelines.
What you can do after
Evaluate and configure exposure choices for web-based and TCP-based Services across Anthos and GKE deployments.
How it connects
Ties Ingress controllers to Kubernetes Services, Service VIPs, load balancers, ASM, L7 proxies, and network policies.

Also explained in

Compare how 4 books explain ingress controller →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.