IngressRoute: A Path Towards a Better Ingress Object for Kubernetes
summary
Contour is an ingress controller that uses Envoy data plane and ships an IngressRoute CRD that replaces ambiguous Kubernetes Ingress behavior with one-host-per-resource, explicit TLS settings, and route-level policies. It implements delegation so admins keep TLS secrets while teams manage path subtrees, and supports multi-backend weighted routing for canaries (example: 90%/10% traffic split). It’s built for production (used by Yahoo Japan) and is available from VMware on GitHub.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 6:27Kubernetes Ingress problems
- 19:21Ingress limitations
- 20:24Introducing IngressRoute
- 31:59Q&A
related talks
36mIngressRoute: A Path Towards a Better Ingress Object for Kubernetes
35mContour, a High Performance Multitenant Ingress Controller for Kubernetes
25mContour, A High Performance Multitenant Ingress Controller for Kubernetes
38mContour Ingress Intro and Deep Dive
27mContour, a High Performance Multitenant Ingress Controller for Kubernetes
12mTalk Deep Dive
32mKubernetes Ingress: Your Router, Your Rules
20mInside Kubernetes Ingress