Why do I need multitenancy in a service mesh?
Multitenancy in Tetrate Service Bridge (TSB) is about separating concerns and isolating resources under management so different teams in an organization have the visibility and control they need to get things done without stepping on each other’s toes.
Security, network, infrastructure and application concerns are traditionally siloed within the teams responsible for them. Gaining visibility and coordinating policy across those silos is hard, causing drag on business continuity and agility. TSB offers a central point of coordination that gives all stakeholders the control they need to author policy with the visibility they need to ensure that policy is correctly implemented.
Under the hood, TSB uses the underlying isolation primitives of the mesh, adding a multitenancy model and controls that align with the way your people and assets are organized. Teams may be organized by what they do and what they’re responsible for. Services may be grouped together into logical applications so app teams can focus on the services they need to monitor and manage. Give InfoSec teams control that cuts across tenants and workspaces to establish global and default policy – for example, deny network egress by default. Give app teams a custom view of the services that make up their applications. And, where they once may have spent days or weeks to coordinate policy updates with infosec and network teams, give them the latitude within the scope of their application to add exceptions where needed – for example, allow egress for a particular service. Platform administrators get a bird’s eye view of all resources and can organize them according to the needs of their constituents.