the term
In this article you will see some terms are used in other parts of the cross, in order to prevent ambiguity, we first clarify under.
- Node: Kubernetes cluster on a single physical machine or virtual machine.
- Clusters: node located after the Internet firewall, which is the main computing resources kubernetes management.
- Border routers: Perform router firewall policy for the cluster mandatory. This may be caused by a cloud provider or physical hardware management gateway.
- Cluster network: a set of logical or physical links, according Kubernetes network model communications within the cluster implementation. Implement cluster network includes Overlay model of flannel and based on the SDN OVS .
- Services: Using the tag selector to identify a group of pod becoming Kubernetes service . Unless otherwise noted, assume that the service can be accessed only through a virtual IP network within the cluster.
What is the Ingress?
Typically, service and pod of IP is only accessible within the cluster. Outside the cluster need to be forwarded to the service request on the Node NodePort exposed through the load balancer, and then through the edge router kube-proxy (edge router) to forward it to the relevant Pod or discarded. As shown below
internet | ------------ [Services]
Ingress is to provide the rules for routing incoming request cluster set, as shown in FIG.
Ingress can provide external access to the service URL of the cluster, load balancing, SSL termination, HTTP routing. To configure these Ingress rules, administrators need to deploy a cluster Ingress the Controller , it listens change Ingress and service, and to configure load balancing according to the rules and provides access to the entrance.