From 2c3438919ccc399378b4c97e3663246f9b60455a Mon Sep 17 00:00:00 2001 From: Will Beason Date: Fri, 16 Nov 2018 10:25:57 -0800 Subject: [PATCH] Fix ResourceQuota doc (#11016) We don't support multiple ResourceQuota definitions in the same namespace. --- content/en/docs/concepts/policy/resource-quotas.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/policy/resource-quotas.md b/content/en/docs/concepts/policy/resource-quotas.md index 3374593230..e3be95b50c 100644 --- a/content/en/docs/concepts/policy/resource-quotas.md +++ b/content/en/docs/concepts/policy/resource-quotas.md @@ -27,7 +27,7 @@ Resource quotas work like this: - Different teams work in different namespaces. Currently this is voluntary, but support for making this mandatory via ACLs is planned. -- The administrator creates one or more `ResourceQuotas` for each namespace. +- The administrator creates one `ResourceQuota` for each namespace. - Users create resources (pods, services, etc.) in the namespace, and the quota system tracks usage to ensure it does not exceed hard resource limits defined in a `ResourceQuota`. - If creating or updating a resource violates a quota constraint, the request will fail with HTTP