Service-Mesh for Enterprise Multi-Tenant Kubernetes
summary
Describes JP Morgan Chase’s design and operation of a managed service mesh for multi-tenant enterprise Kubernetes clusters, addressing the problem that existing meshes are installed cluster-wide (breaking tenancy) and that tenant apps run with restricted privileges. Explains how they modified or configured service-mesh deployment and runtime to preserve multi-tenancy and accommodate limited-privilege tenant workloads while still delivering service-mesh benefits (e.g., discovery, traffic management) on Kubernetes.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:10What is a Service Mesh?
- 4:29Benefits of Service Mesh
- 6:54Application Deployment in Kubernetes
- 8:22Components of Service Mesh - with Privileges
- 11:59Service Mesh for Enterprise
- 13:28Multi-tenancy in Kubernetes via Namespaces
- 14:25Why Service Mesh Should be Multi-Tenant?
- 16:17How To Achieve Multi-Tenancy (Istio) - Basic
- 17:43How To Achieve Multi-Tenancy (Istio) - Advanced
- 19:39Summary
related talks
27mSingle Mesh vs Multi Mesh- Tradeoffs for Enterprise Multi-Tenant Support- Ding Shaojun (Iris Ding) & Zhang Huailong (Steve Zhang), Intel
50mMulti-Cluster Kubernetes and Service Mesh Patterns
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
24mImplementing Service Mesh on Kubernetes: Best Practices and Common Challenges
11mWelcome & Opening Remarks
33mSolving Multi-Service Without a Service Mesh
05mNamespace Multi-Tenancy, But All The Problems Related To It
05mBest Practices on Setting up Multi Cluster Service Mesh in AWS
