From 8a8f9c40f9f386dac6ab9c7f117f521c5bc79bcd Mon Sep 17 00:00:00 2001 From: Wang Date: Sun, 5 Dec 2021 21:05:08 +0900 Subject: [PATCH] Update admission-controllers.md --- .../reference/access-authn-authz/admission-controllers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/reference/access-authn-authz/admission-controllers.md b/content/en/docs/reference/access-authn-authz/admission-controllers.md index 0461c09f53..17354fc58f 100644 --- a/content/en/docs/reference/access-authn-authz/admission-controllers.md +++ b/content/en/docs/reference/access-authn-authz/admission-controllers.md @@ -30,9 +30,9 @@ mutating and validating (respectively) which are configured in the API. Admission controllers may be "validating", "mutating", or both. Mutating -controllers may modify the objects they admit; validating controllers may not. +controllers may modify related objects to the requests they admit; validating controllers may not. -Admission controllers limit requests to create, delete, modify or connect to (proxy). They do not support read requests. +Admission controllers limit requests to create, delete, modify objects or connect to proxy. They do not limit requests to read objects. The admission control process proceeds in two phases. In the first phase, mutating admission controllers are run. In the second phase, validating