Expose a GKE-deployed app publicly behind a Cloud HTTP(S) load balancer. What should you configure?

To expose a GKE-deployed application publicly behind a Cloud HTTP(S) load balancer, you should configure a GKE Ingress resource. An Ingress resource manages external access to services in a cluster, typically HTTP(S), and provides load balancing, SSL termination, and name-based virtual hosting. When you create an Ingress in GKE, it automatically provisions a Google Cloud HTTP(S) Load Balancer. A GKE Service resource (even with type: LoadBalancer) primarily handles internal load balancing within the cluster or provisions a Network Load Balancer (for TCP/UDP traffic), not an HTTP(S) Load Balancer. While a Service of type: LoadBalancer can expose an application externally, it doesn't provide the advanced HTTP(S) routing capabilities or integrate with the Cloud HTTP(S) Load Balancer in the same way an Ingress does. An Ingress resource with type: LoadBalancer is not a standard Kubernetes or GKE concept; Ingress resources do not have a type field in that manner.