Comparison
Multi-tenancyvsResource quota
Multi-tenancy
several teams or customers share one cluster, and every performance question becomes 'is it us or is it them'.
Running multiple independent workloads or customers on shared infrastructure. It is what makes a platform economical, and it introduces isolation, fairness, quota and noisy-neighbour problems that dedicated infrastructure simply does not have. The critical distinction is whether the tenants trust one another: sharing between internal teams and sharing between hostile customers require entirely different boundaries.
Full entry →Resource quota
one team's runaway job could not consume the whole cluster, because their slice had a declared ceiling.
A cap on how much of a shared cluster one team, namespace or tenant may request. It is the main tool that makes a shared platform politically viable, since it converts 'someone took all the capacity' from an incident into a rejected request. It also relocates the argument to quota allocation, which is the correct place for it, and requires an obvious, fast path to raising one.
Full entry →