From ef3c9ec370c55038903358c738bfda5b0434da83 Mon Sep 17 00:00:00 2001 From: "Steven E. Harris" Date: Tue, 8 Jan 2019 07:21:44 -0500 Subject: [PATCH] Correct ResourceQuota PriorityClass config example (#12055) The LimitedResource type has the field "MatchScopes" as a sibling to the field "Resource," but the YAML document in the example showed the "MatchScopes" field as a child of the top-level Configuration type. Correct the example to match the actual schema. While we're here, swap the order of the "scopeName" and "operator" fields used in the YAML, to make it clearer in infix style that the operator binds the scope name to a (possibly empty) set of values. --- content/en/docs/concepts/policy/resource-quotas.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/docs/concepts/policy/resource-quotas.md b/content/en/docs/concepts/policy/resource-quotas.md index e3be95b50c..40c813e00c 100644 --- a/content/en/docs/concepts/policy/resource-quotas.md +++ b/content/en/docs/concepts/policy/resource-quotas.md @@ -551,10 +551,10 @@ plugins: kind: Configuration limitedResources: - resource: pods - matchScopes: - - operator : In - scopeName: PriorityClass - values: ["cluster-services"] + matchScopes: + - scopeName: PriorityClass + operator: In + values: ["cluster-services"] ``` Now, "cluster-services" pods will be allowed in only those namespaces where a quota object with a matching `scopeSelector` is present. @@ -562,8 +562,8 @@ For example: ```yaml scopeSelector: matchExpressions: - - operator : In - scopeName: PriorityClass + - scopeName: PriorityClass + operator: In values: ["cluster-services"] ```