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]] | ||
=TODO= | |||
<font color=darkgray> | |||
* Kubernetes in Action Section 5.4 | |||
* https://medium.com/google-cloud/understanding-kubernetes-networking-ingress-1bc341c84078 | |||
</font> | |||
=Overview= | =Overview= | ||
Revision as of 01:14, 21 September 2020
External
Internal
TODO
- Kubernetes in Action Section 5.4
- https://medium.com/google-cloud/understanding-kubernetes-networking-ingress-1bc341c84078
Overview
An Ingress resource is a different mechanism for exposing multiple services through a single IP address, and its implementation differs fundamentally from the implementation of ClusterIP, NodePort and LoadBalancer services. Unlike these services, which operate at layer 4, an Ingress operates at HTTP protocol layer (layer 7).
Ingress provides host and path-based routing.