Architecting Kubernetes Clusters for High Traffic Sites
summary
Practical notes on running Kubernetes edge traffic with the NGINX Ingress Controller and related pieces: deploy as a Deployment, DaemonSet, or on dedicated nodes; expect a single tiny controller instance to scale to 10 Gbit/s and hundreds–thousands RPS; export >100 metrics into Prometheus/Grafana; use VirtualServer CRD (or annotations) to give teams routing and RBAC control; plug an inline WAF with thousands of signatures that WAF adds negligible latency; Gateway API v0 support and open source distribution are available.
AI-written summary · about
chapters (15)
- 0:00Introduction and overview
- 1:28Kubernetes basics for high traffic
- 3:18Control plane and cluster architecture
- 5:30Ingress controller role and challenges
- 7:17Key challenges in traffic management
- 9:26Introducing NGINX Ingress Controller
- 12:21Performance and automation benefits
- 15:15Security and monitoring integration
- 16:19Deploying NGINX Ingress Controller
- 17:45Scaling strategies for traffic
- 18:46When to adopt advanced solutions
- 20:15Custom resources and traffic routing
- 21:38Role-based access and policies
- 23:23Gateway API and future trends
- 24:48Q&A and closing remarks
related talks
20mOperating High Traffic Websites on Kubernetes
15mSimplify Kubernetes Connectivity
34mOperating High Traffic Websites on Kubernetes
01mWhat is
49mAdvanced Ingress for Your Kubernetes Apps
29mKubernetes Ingress Controller with Apache Traffic Server [I]
37mJourney Through Kubernetes Ingress: Past, Present, and Beyond
01h 16mIntro + Deep Dive: Kubernetes IoT Edge WG