Tenancy

This feature allows
AKO
to map each Kubernetes/OpenShift cluster uniquely to a tenant in
Avi Load Balancer
or to map each namespace in a single Kubernetes/OpenShift cluster uniquely to a tenant in
Avi Load Balancer
.
Avi Load Balancer
non admin tenants primarily operate in 2 modes:
  1. Provider context
  2. Tenant context.

Provider Context

Service Engine Groups and VRF context are shared with the admin tenant. All the other objects like virtual services and pools are created within the tenant.
This requires
config_settings.se_in_provider_context
flag to be set to
True
when creating tenant.

Tenant Context

Service Engines are isolated from admin tenant. A new Default group is created within the tenant. All the objects including Service Engines are created in tenant context. It requires
config_settings.se_in_provider_context
flag to be set to
False
when creating tenant.