Back to basics, getting traffic into your Kubernetes cluster
summary
Creates a two-node kind cluster, deploys pods and shows pod IPs change while a Service provides a stable ClusterIP; maps NodePort through kind to curl the service and observe simple round‑robin across pods. Replaces NodePort with a LoadBalancer backed by MetalLB to get an external IP locally. Uses an APISIX/ingress implementation (called api6) to demonstrate routing and explains annotations used for rewrites (implementation‑specific). Describes the Gateway API and its HTTPRoute objects that add header/query/path matching and filter-based rewrites, but warns implementations (and api6) are uneven and some features still missing.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:19Kubernetes basics
- 7:42Services for stable access
- 12:18Load balancer objects
- 16:18Ingress controllers
- 25:09Gateway API
- 31:38Q&A
related talks
34mBack to Basics, Getting Traffic Into your Kubernetes Cluster
15mSimplify Kubernetes Connectivity
22mNavigating the Kubernetes Networking Maze
28mApplication delivery on k8s - the past, present and future
20mKubernetes Networking 101
37mJourney Through Kubernetes Ingress: Past, Present, and Beyond
51mKubernetes SIG-Network: Intro and Deep-Dive
29mInside Kubernetes Networking