In Chapter 5, Building Continuous Delivery Pipelines, we learned about the concept of ingress , and when and how to use it. Ingress defines a set of rules allowing the inbound connection to access Kubernetes cluster services. It routes the traffic into cluster at L7, and the controller brings the traffic to the nodes. When GCP is the cloud provider, a L7 load balancer will be created if an ingress is created, as well as related firewall rules, health checks, backend services, forwarding rules, and a URL map. A URL map in GCP is a mechanism that contains a set of rules and forwards requests to the corresponding backend services.
In this recipe, we'll reuse the examples from Chapter 5, Building Continuous Delivery Pipelines, Nodeport-deployment.yaml ...
