Single Mesh vs Multi Mesh- Tradeoffs for Enterprise Multi-Tenant Support- Ding Shaojun (Iris Ding) & Zhang Huailong (Steve Zhang), Intel
summary
Compares concrete designs and demos for multi-tenant service mesh showing a patched multi-mesh-in-single-cluster that relies on istio discovery selectors, a single-mesh with sidecar CR and exportTo for service/config isolation plus authorization policy to deny-then-allow cross-namespace traffic, and a certificate flow using a cert-manager style signer watching CSRs that lets tenants have per-tenant signing roots. Shows demo with namespaces bar and foo running httpbin and sleep, verifies intra- and inter-namespace connectivity and outlines using Intel SGX enclaves to protect tenant private keys.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:28Agenda
- 1:10Background
- 2:16Challenges
- 3:39Service Mesh
- 4:46Service Discovery Selector
- 5:26Patched Solution
- 6:38Discovery Isolation
- 7:47Config Isolation
- 8:00Authorization Policy
- 10:25Identity Isolation
- 12:01MultiTenant in Single Mesh
- 16:00MultiTenant in Service Mesh
- 20:01Demo
- 25:53Summary
related talks
21mService-Mesh for Enterprise Multi-Tenant Kubernetes
45mIstio Service Mesh Simplified Beyond a Single Cluster
31mMulti(Control Plane/Network/Mesh)??: A Practical MultiCluster...
11mWelcome & Opening Remarks
24mMulticluster Service Mesh
40mReimagining Application Networking and Security
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
20mThe Crazy Service Mesh Ecosystem
