Tinder's Move to Kubernetes
Talkat KubeCon + CloudNativeCon North America 2019 · on Thursday, 2019-11-21· at 16:25· Ballroom Sec 20AB - San Diego Convention Center, Upper Level·
summary
Tinder moves 200 services to Kubernetes using a builder-container CI/CD that pushes images to ECR and updates Deployments, then peels traffic over with weighted DNS and ELBs. Scaling hits include ARP table exhaustion on flannel (fixed by raising sysctl limits and restarting nodes) and a conntrack/SNAT DNS race that surfaces at ~250,000 DNS requests/sec, solved by running a node-local DNS cache daemonset so lookups hit the node first. Load skew is fixed with Envoy sidecars + TCP ELBs and preStop drain hooks. migrated 200 services 2000-node cluster, 18,000 cores 250k DNS requests/sec
AI-written summary · about
chapters (11)
- 0:00TINDER'S MOVE TO KUBERNETES
- 1:59Overview
- 2:27Legacy Architecture
- 3:05Building Images
- 4:10CI/CD
- 5:53Original Architecture
- 6:51Migration
- 8:02Learnings
- 11:07Load Balancing
- 14:07Current Architecture
- 14:57Monitoring Stack
related talks
35mKubernetes, Lessons Learnt
46mThe Journey of Migrating 2500 Apps to Multi-Cluster Kubernetes and Zero Trust Istio
35mKubernetes journey
46mKeep Building Fresh: Shopify's Journey to Kubernetes
32mMigrating 2 million CPU cores to Kubernetes
48mScaling a Migration to CD at Airbnb
29mAccelerate AppDev with KIK (Kubernetes-Istio-Knative)
38mBuilding the Perfect Infrastructure with Kubernetes