Multi-Runtime Service Mesh With Consul
summary
Deploys Consul with Envoy sidecars across four runtimes (Kubernetes, ECS, Nomad, VMs) spanning three clouds, registers a Lambda via a terminating gateway, and runs a five‑service HashiCops storefront. Uses mesh gateways for cross‑datacenter mTLS, Prometheus federation and Grafana for unified metrics, and Intentions to instantly block/allow traffic. Performs a live 50/50 splitter rollout from legacy payment to a Vault‑backed Lambda, and the demo mostly succeeds with real clusters and observable traffic through the service mesh.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:45Service mesh 101
- 7:28Federation and multicluster
- 10:40Demo architecture
- 13:53Deploying the services
- 19:18Finalizing the demo
- 27:24Security and intentions
- 30:38Observability and metrics
- 33:28AWS Lambda and conclusion
related talks
15mLightning Talk: Automate and Secure Consul Service Mesh on AWS ECS
53mDo you need a Service Mesh?
38mModern Service Networking With Consul Connect, Envoy and Kubernetes
44mService Mesh - The New Single Point of Failure
10mService Mesh Security in a Nutshell
31mEffective building blocks for securing...
39mDo you need a Service Mesh?
28mService Meshes: At What Cost?