Simplify Kubernetes Connectivity
summary
Shows how an Ingress controller runs as a pod at the cluster edge or as a sidecar proxy, performing Layer 7 HTTP and Layer 4 TCP/UDP load balancing with session persistence, health checks and dynamic, non‑disruptive routing when pods scale or die. Describes three flavors (community, open source, NGINX Plus), service‑mesh features like mTLS and Prometheus/Jaeger telemetry, deployment patterns—blue/green, canary, rate limiting—and an open reference called the MARA framework plus NGINX App Protect WAF.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:03NGINX history and capabilities
- 2:26Kubernetes Ingress controllers
- 3:53NGINX in Kubernetes
- 6:03North-South vs East-West traffic
- 7:47Advanced traffic management
- 8:29NGINX Ingress controller
- 10:35Service mesh with NGINX
- 11:57F5 and NGINX Plus offerings
- 13:01F5’s Kubernetes networking
- 14:05NGINX Plus security
- 14:47Securing Kubernetes with App Protect
- 15:09Closing
related talks
37mJourney Through Kubernetes Ingress: Past, Present, and Beyond
28mArchitecting Kubernetes Clusters for High Traffic Sites
32mKubernetes Ingress: Your Router, Your Rules
28mApplication delivery on k8s - the past, present and future
49mAdvanced Ingress for Your Kubernetes Apps
20mInside Kubernetes Ingress
25mApplication Networking on Kubernetes, where are we now?
25mKubernetes Ingress: Do More with Less