Network Configurations for High-Performance Streaming Connectivity in K8s
summary
Hands-on comparison of Kafka/Redpanda networking in Kubernetes using sockperf on a three-node EKS cluster (m5.2xlarge): nodePort yields the lowest latency, load balancer is next, and adding a proxy such as Envoy proxy raises tail latency and halves efficiency at scale. Practical build details include StatefulSets with headless and per-broker services, advertised addresses via DNS or node IPs, NVMe local storage with XFS and LVM striping, CPU pinning for brokers, and tuning producers/consumers and partition counts to balance throughput, latency, and metadata overhead.
AI-written summary · about
chapters (8)
- 0:00Streaming on Kubernetes
- 1:53Kafka vs HTTP services
- 3:43K8s architecture for Kafka
- 8:23NodePort vs LoadBalancer
- 12:38Network options performance
- 17:23Tuning Kafka brokers/clients
- 23:05Producer/consumer configs
- 26:34Q&A
related talks
13mScaling Kafka on Kubernetes
34mDistributed applications and Kubernetes
27mRunning Kafka in Kubernetes a practical guide
47mRunning Kafka in Kubernetes: a practical guide
15mHow We Solved the K8s Cluster Communication Challenge
36mKafka Without Disks: Making Streaming Brokers Disposable on K8S
37mDisaster Recovery Options running Apache Kafka in Kubernetes
42mKubernetes Networking at Scale
