Keynote Demo: Service Mesh Networking Features
summary
Demo shows a front-end calling backend member services through a sidecar Envoy proxy that resolves a local 127.x.x.x address while backend instances report different instance IPs, proving transparent proxying and per-request load balancing. One failing instance causes retries from the mesh until success, and traffic shifts with 80/20 weighted routing between app versions via API. Scripts and CF apps listings are used to show live behavior and convergence.
AI-written summary · about
chapters (4)
related talks
53mDo you need a Service Mesh?
39mDo you need a Service Mesh?
45mMulti-Runtime Service Mesh With Consul
05mUnlocking Next-Gen Networking and Security with Cilium Service Mesh
24mTransform Your Network: Master API Control & Security
32mService Networking Within Air-Gapped Environments: Deployment Strategies and Operat...
31mBridging Mesh Enclaves: Securing and Maintaining Mesh Heterogeneity
38mModern Service Networking With Consul Connect, Envoy and Kubernetes