Kubernetes Ingress Concepts: Difference between revisions
Jump to navigation
Jump to search
(→TODO) |
|||
| Line 8: | Line 8: | ||
* [[Kubernetes_Service_Concepts#Ingress|Service Concepts]] | * [[Kubernetes_Service_Concepts#Ingress|Service Concepts]] | ||
* [[Amazon_EKS_Concepts#Load_Balancing_and_Ingress|Amazon EKS Concepts - Load Balancing and Ingress]] | * [[Amazon_EKS_Concepts#Load_Balancing_and_Ingress|Amazon EKS Concepts - Load Balancing and Ingress]] | ||
=Overview= | =Overview= | ||
Revision as of 23:00, 24 September 2020
External
Internal
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.