Inside Kubernetes Ingress
Talkat KubeCon + CloudNativeCon North America 2020 Virtual · on Friday, 2020-11-20· at 17:05· Intrado Virtual Event Platform,·
summary
Kubernetes Ingress is a composition of Network Ingress (admission of traffic into the cluster) and kubernetes Ingress (HTTP routing inside the cluster) implemented as three parts: an Ingress resource with a decision table of host and path rules, an Ingress controller that reads the API and programs a proxy, and an Ingress proxy that matches host/path (e.g., foo.org:/ -> service foo:8080, bar.org:/a -> bar:9090) and forwards requests accordingly. Popular API gateways like Ambassador can serve as controller plus proxy.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:55Ingress for Kubernetes Problem
- 1:15Ingress for Kubernetes Solution
- 2:40Ingress for Kubernetes Intuition
- 4:57Ingress for Kubernetes Definition
- 17:49Conclusion
- 19:19What is the difference between Kubernetes Ingress and an API Gateway like the Ambassador API Gateway?
related talks
32mKubernetes Ingress: Your Router, Your Rules
43mKubernetes Ingress and API Gateways
37mJourney Through Kubernetes Ingress: Past, Present, and Beyond
49mAdvanced Ingress for Your Kubernetes Apps
25mKubernetes Ingress: Do More with Less
28mApplication delivery on k8s - the past, present and future
15mSimplify Kubernetes Connectivity
22mCreating an ingress controller