Tenancy considerations

We will start by looking closely at what multi-tenancy implies, why tenancy is important, and, in general, what architectural choices, trade-offs, and compromises regarding expenses need to be made when planning for such shared deployments.

Designating tenants

Each enterprise usually has a very different interpretation when it comes to identifying their tenants, but by and large, a tenant is defined as a select group of users granted specific privileges to access a shared software installation. When tenants represent different companies altogether, users belonging to one tenant are generally unaware of the existence of other tenant users. However, even such isolation can be relaxed when it comes to users within the same enterprise, and employees in the same company may be members of multiple tenant "accounts."

Here are some example situations where a Cluster Operations team may want to designate "tenants" that share the same OpenShift...