Separating Kubernetes resources is crucial for administrators to maintain security and integrity in a large organization. Separation of workspaces or environments involves creating multiple tenants on the same infrastructure to facilitate the development and delivery of software for various application teams.
Since Istio abstracts the network and security out of the application, admins can find it challenging to set up their new infrastructure (Istio) to comply with their existing multi-tenancy. Architecture for applying multi-tenancy to Istio can be different based on how the cluster or namespace is shared with existing teams i.e., Developers, DevOps, SREs, etc.
If you are an architecture or infra admin, then join our webinar to learn: Various scenarios of multi-tenancy in large organizations
Architecture to implement Istio to achieve multi-tenancy
Common best practices to set up Istio control plane and data plane single and multiple clusters.