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



