Service Mesh and Your Legacy Apps: Connecting to Kubernetes with Consul
summary
Consul 1.6’s Consul mesh gateway links a VM-based legacy data center and a GKE cluster so services appear in a single control plane; demo shows Helm installs, grabbing the gossip encryption key, CA cert and ACL replication token, wiring WAN federation and exposing the mesh gateway address, then restarting agents to join. Kubernetes workloads use auto sidecar injection (Envoy) for mTLS service-to-service traffic, and the UI shows both VM and pod services; the demo works end-to-end, proving secure discovery and traffic routing across cloud and on‑prem.
AI-written summary · about
chapters (5)
related talks
40mIntroducing A New Architecture for Simplified Service Mesh Deployments
53mDo you need a Service Mesh?
30mA Developer’s Introduction to Service Mesh
33mBenefits of a Service Mesh When Integrating Kubernetes with Legacy Services
50mMulti-Cluster Kubernetes and Service Mesh Patterns
53mService Mesh: What, Why, And How?
39mDo you need a Service Mesh?
26mNavigating the Service Mesh Landscape - Paul Bouwer, Microsoft