Consul Service Mesh and Your Legacy Application
summary
Demonstrates that Consul bridges long‑running VM apps to Kubernetes by using mesh gateways and a federated peering model; setup runs on GCP with an nginx “hello world” front end on VMs, a backend pod in Kubernetes, Consul control planes and DNS service discovery, and an Envoy sidecar attached to the VM. Three backend instances return private pod IPs via DNS; five Consul agents appear in one cluster. Starting Envoy makes the VM service healthy and the front end start returning dynamic images, proving the approach works.
AI-written summary · about
chapters (6)
- 0:00Introduction to service mesh
- 2:09Evolution of IT infrastructure
- 4:55Why use a service mesh?
- 7:20Consul and mesh gateways
- 10:34Federation vs. peering
- 13:39Live demo and conclusion
related talks
46mContainerizing Legacy Applications
14mBridging Multicast to the Cloud
36mMeshing Legacy Systems with Habitat Deployed Components to...
50mHow to be cool in the age of legacy
31mStrategies to "Kubernetify" Legacy Applications
42mTilling the Brownfield: A Container Story
29mFrom EC2 to Kubernetes Takeaways from a Brownfield Migration
36mIntroduction to Virtual Kubelet – Featuring Titus by Netflix