Kubernetes Ingress Concepts: Difference between revisions
Jump to navigation
Jump to search
(→TODO) |
|||
| Line 17: | Line 17: | ||
=Overview= | =Overview= | ||
An Ingress | 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 [[Kubernetes_Service_Concepts#Service_.28ClusterIP_Service.29|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 [[Kubernetes_Service_Concepts#Service_.28ClusterIP_Service.29|ClusterIP]], [[Kubernetes_Service_Concepts#NodePort_Service|NodePort]] and [[Kubernetes_Service_Concepts#LoadBalancer_Service|LoadBalancer]] services. | ||
The Ingress mechanism consists of an Ingress controller and an Ingress resource. | |||
=Need for Ingress= | =Need for Ingress= | ||
Revision as of 22:57, 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.