KubeCon: A Story of Two Service Discoveries: Bringing Legacy to Kubernetes
summary
Xoom preserves its legacy DNS/proxy discovery by pulling the per-pod sidecar into a single node-level instance, running the proxy as a daemonset in the host network namespace and running dnsmasq (configured to return the node IP for zoom.api) on each node, while kubelet injects the node IP into containers' /etc/resolv.conf. Pod IPs are fully routable using Calico, registration is sub-second, and this reduces hundreds of MBs of Java memory per pod.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:39Kubernetes Label Service Discovery
- 4:30The Controller Manager
- 12:09Dns Addon
- 18:29What Do You Get Back for Srb Queries
- 19:29How Quickly Did Your Services Get Registered
- 20:55Mark Petrovich
- 23:59Crafting Developer Environments
- 38:24Shell Script Entry Point for Dns Mask
related talks
35mKubernetes, Lessons Learnt
51mKubernetes SIG-Network: Intro and Deep-Dive
19mService Mesh and Your Legacy Apps: Connecting to Kubernetes with Consul
34mRethinking the K8s DNS for the Modern Enterprise
30mThe Unconspicuous Role of Conntrack in Kubernetes Networking
53mManaging Containers at Scale with CoreOS and Kubernetes
29mWhy We Ditched Kube-proxy: Scaling 10M Daily Browser Sessions With Kubernetes Endpoi...
33mBenefits of a Service Mesh When Integrating Kubernetes with Legacy Services