From d396aa054b488351cbd59dceea951d6cc03f1226 Mon Sep 17 00:00:00 2001 From: Jiahui Feng Date: Mon, 3 Apr 2023 09:34:14 -0700 Subject: [PATCH] Update content/en/docs/reference/access-authn-authz/validating-admission-policy.md Co-authored-by: Qiming Teng --- .../reference/access-authn-authz/validating-admission-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/reference/access-authn-authz/validating-admission-policy.md b/content/en/docs/reference/access-authn-authz/validating-admission-policy.md index 45f05e3ed3a88..93e6bd4d33796 100644 --- a/content/en/docs/reference/access-authn-authz/validating-admission-policy.md +++ b/content/en/docs/reference/access-authn-authz/validating-admission-policy.md @@ -490,7 +490,7 @@ Type Checking has the following limitation: - No wildcard matching. If `spec.matchConstraints.resourceRules` contains `"*"` in any of `apiGroups`, `apiVersions` or `resources`, the types that `"*"` matches will not be checked. -- The number of matched types is limited to 10. This is to prevent a policy that manually specifying too many types +- The number of matched types is limited to 10. This is to prevent a policy that manually specifying too many types. to consume excessive computing resources. In the order of ascending group, version, and then resource, 11th combination and beyond are ignored. - Type Checking does not affect the policy behavior in any way. Even if the type checking detects errors, the policy will continue to evaluate. If errors do occur during evaluate, the failure policy will decide its outcome.