Kubernetes Ingress: Your Router, Your Rules
summary
Explains that Kubernetes Ingress is a declarative set of routing rules that must be applied by an Ingress controller, not a Service; GKE provides L7 integration but most clusters need an operator. Walks through an NGINX-based controller implemented in ~80 lines, deploys a Helm chart (CrockHunter), and proves branch-per-environment through Helm+CI branch-based ingresses using Buildkite to create ephemeral subdomains. Claims: decouples networking from app lifecycle, supports TLS, path and vhost routing, and the demo works end-to-end.
AI-written summary · about
chapters (9)
- 0:00Ingress Your Router, Your Rules Gerred Dillon Deisl @justicefrieshe
- 0:34Container Networking at Scale
- 4:54Service Semantically related set of resources
- 6:18Ingress Mapping of external traffic to virtual resources
- 9:38What is Ingress, really? Rules for routing inbound traffic to cluster resources
- 10:15Why wouldn't I just use a service? → Services are limited, and their routing rules are attached to the lifecycle of the service. → Ingress decouples your routing rules from your application → More importantly...
- 11:36Ingress Controller Control loop that manages rules enabling inbound traffic to applications.
- 17:52Ingress Controller!
- 21:36The Challenge
related talks
20mInside Kubernetes Ingress
37mJourney Through Kubernetes Ingress: Past, Present, and Beyond
15mSimplify Kubernetes Connectivity
49mAdvanced Ingress for Your Kubernetes Apps
25mKubernetes Ingress: Do More with Less
22mCreating an ingress controller
28mApplication delivery on k8s - the past, present and future
25mKubernetes Ingress-Nginx Security from Beginner to Expert