Kubernetes Ingress Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
The Ingress mechanism consists of an Ingress controller and an Ingress resource. | The Ingress mechanism consists of an Ingress controller and an Ingress resource. | ||
=Ingress API Resource= | =Ingress API Resource= | ||
=Ingress Controller= | =Ingress Controller= | ||
Revision as of 23:00, 24 September 2020
External
Internal
TODO
- De-yellow Kubernetes in Action Section 5.4.
- https://medium.com/google-cloud/understanding-kubernetes-networking-ingress-1bc341c84078
Overview
An Ingress is a mechanism that operates at the application layer of the network stack (HTTP) and brings layer 7 features such as host and path-based routing and cookie-based session affinity to services. Ingress cooperates with services to distribute load to pods. It exposes multiple services through a single IP address, and its implementation differs fundamentally from the implementation of ClusterIP, NodePort and LoadBalancer services.
The Ingress mechanism consists of an Ingress controller and an Ingress resource.