Kubernetes Ingress Concepts: Difference between revisions
Jump to navigation
Jump to search
(→TODO) |
|||
| Line 17: | Line 17: | ||
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 [[Kubernetes_Service_Concepts#Service_.28ClusterIP_Service.29|ClusterIP]], [[Kubernetes_Service_Concepts#NodePort_Service|NodePort]] and [[Kubernetes_Service_Concepts#LoadBalancer_Service|LoadBalancer]] services. Unlike these services, which operate at layer 4, an Ingress operates at HTTP protocol layer (layer 7). | 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 [[Kubernetes_Service_Concepts#Service_.28ClusterIP_Service.29|ClusterIP]], [[Kubernetes_Service_Concepts#NodePort_Service|NodePort]] and [[Kubernetes_Service_Concepts#LoadBalancer_Service|LoadBalancer]] services. Unlike these services, which operate at layer 4, an Ingress operates at HTTP protocol layer (layer 7). | ||
=Need for Ingress= | |||
Ingress provides host and path-based routing. | Ingress provides host and path-based routing. | ||
Revision as of 18:07, 23 September 2020
External
Internal
TODO
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).
Need for Ingress
Ingress provides host and path-based routing.