Handle different RabbitMQ clusters in Kubernetes (...)
summary
Traefik 2.x acts as a TCP/TLS proxy that uses SNI-based routing to expose multiple RabbitMQ clusters on a single public IP; the demo wires two clusters (one-node "bugs", three-node "bunny") behind one mqps endpoint and proves clients set the TLS server_name to pick the right cluster. TLS passthrough works end-to-end and certificate mismatch blocks wrong SNI, while TLS termination plus origination enables logging/inspection. Caveats: added proxy can be a scaling bottleneck and you trade multiple public IPs for one manageable ingress.
AI-written summary · about
chapters (6)
- 0:0004:36 - Introduction
- 4:3705:45 - What is Traefik?
- 5:4507:44 - What is SNI?
- 7:4510:50 - Access through Proxy
- 10:5121:52 - Demo
- 21:5328:09 - QnA
related talks
26mDeploy and Monitor a RabbitMQ Cluster on Kubernetes
12mService Mesh & Kubernetes Multicluster Communication With Linkerd
32mStretching Strimzi: Exploring Multi-Cluster Kafka for High Availability
39mDo you need a Service Mesh?
32mSolving Multi-Cluster Network Connectivity With Submariner
47mPainless Multi-Tenant Kafka on Kubernetes with Istio at ASML
36mKubernetes Multi-Cluster Made Easy - Federica Ciuffo and Marco Ballerini
28mMulti-Cluster is Easier Than You Think with Linkerd and Ambassador