Kubernetes Ingress Controller with Apache Traffic Server [I]
summary
Oath runs 12 Kubernetes clusters across six datacenters serving 100+ apps at ~150k RPS and ~40k containers; the ingress uses Apache Traffic Server plus a custom controller with a service watcher, health monitor, compiler and a traffic-manager plugin that applies memory-map updates to avoid hot reloads and update routes in seconds. Health-probed endpoints and config-map driven cluster and app failout enable seamless regional diverting, and a dynamic admission webhook prevents multiple apps claiming the same domain. The stack supports native Ingress YAML with a few custom annotations for ports and aliases.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:32Team
- 2:23K8s @ Oath: Architecture
- 9:41ATS Ingress Controller Design
- 12:21Ingress Specification
- 13:42Salient Features
- 16:04Hostname Collision - Ingress Admission Controller
- 21:43Open Source Authorization plugins
related talks
28mArchitecting Kubernetes Clusters for High Traffic Sites
28mIstio in Action: Taking Kubernetes Traffic Control to the Next Level
15mSimplify Kubernetes Connectivity
12mSimpler and more flexible Kubernetes Ingress: Apache APISIX
20mInside Kubernetes Ingress
49mAdvanced Ingress for Your Kubernetes Apps
41mEffortless Secure and Control Traffic Using Kubernetes Gateway API for Ingress, Egress an...
20mOperating High Traffic Websites on Kubernetes