Stretching the Service Mesh Beyond the Clouds
summary
Demo builds a HashiCorp Consul service mesh on Kubernetes in AWS, plus a Consul Terraform Sync module that auto-configures an AWS Application Load Balancer to route traffic between a data center VM and cloud services. The demo moves traffic to a 50/50 canary, hits a 504 from the cloud, and Consul Terraform Sync immediately resets cloud weight to 0%. A second topology shows federated service mesh via mesh gateways, Prometheus/Grafana scraping Envoy metrics and Spinnaker (Kayenta) doing a 20–30 minute automated canary that succeeds and shifts to 100% cloud.
AI-written summary · about
chapters (15)
- 0:00Introduction to multi-cloud challenges
- 2:36Defining the core problem
- 5:00What is a service mesh
- 7:30Service mesh complexity trade-offs
- 9:37Network automation topology
- 11:43Demo network automation setup
- 14:31Testing traffic routing
- 22:00Federated service mesh approach
- 25:50Automated canary deployment
- 29:00Demo canary setup overview
- 31:49Running the canary pipeline
- 36:43Successful canary results
- 39:10Handling failed canaries
- 41:39Comparing topology solutions
- 43:04Resources and conclusion
related talks
15mLightning Talk: Automate and Secure Consul Service Mesh on AWS ECS
49mEnterprise service networking with HashiCorp Consul and AWS (PRT238)
37mStretching the Mesh
29mBuilding for massive scale and security with the HashiCorp Cloud Platform
25mConsul Terraform Sync - Awesome Use Cases
40mBuilding a Modern Infrastructure Stack
33mHow to Recreate AWS in Your Data Center
22mConsul Product Updates and Vision - HashiConf 2022