Which mechanism governs ResourceQuota distribution across Rancher Project namespaces?

Rancher utilizes Project-level Resource Quotas to group multiple Kubernetes namespaces under a single administrative boundary, enforcing limits on CPU, memory, and pod counts via the underlying Kubernetes ResourceQuota API.

When quotas are defined at the project level, the system must manage how these limits are applied or distributed across the constituent namespaces. In large-scale multi-tenant environments, there is a known tension regarding the eventual consistency of quota updates when changes are propagated across a high volume of namespaces.

Does Rancher implement a dynamic sharing model where namespaces draw from a collective project pool, or are quotas statically partitioned upon namespace creation? What is the expected behavior regarding consistency delays when updating project-level limits across dozens of namespaces?