Merge pull request #20726 from ZhiFeng1993/ZF--specify-verbs-in-admission-controller-doc
Specify verbs in admission controller doc
This commit is contained in:
@@ -32,6 +32,8 @@ which are configured in the API.
|
|||||||
Admission controllers may be "validating", "mutating", or both. Mutating
|
Admission controllers may be "validating", "mutating", or both. Mutating
|
||||||
controllers may modify the objects they admit; validating controllers may not.
|
controllers may modify the objects they admit; validating controllers may not.
|
||||||
|
|
||||||
|
Admission controllers limit requests to create, delete, modify or connect to (proxy). They do not support read requests.
|
||||||
|
|
||||||
The admission control process proceeds in two phases. In the first phase,
|
The admission control process proceeds in two phases. In the first phase,
|
||||||
mutating admission controllers are run. In the second phase, validating
|
mutating admission controllers are run. In the second phase, validating
|
||||||
admission controllers are run. Note again that some of the controllers are
|
admission controllers are run. Note again that some of the controllers are
|
||||||
|
|||||||
@@ -110,10 +110,11 @@ To learn more about Kubernetes authorization, including details about creating p
|
|||||||
|
|
||||||
Admission Control Modules are software modules that can modify or reject requests.
|
Admission Control Modules are software modules that can modify or reject requests.
|
||||||
In addition to the attributes available to Authorization Modules, Admission
|
In addition to the attributes available to Authorization Modules, Admission
|
||||||
Control Modules can access the contents of the object that is being created or updated.
|
Control Modules can access the contents of the object that is being created or modified.
|
||||||
They act on objects being created, deleted, updated or connected (proxy), but not reads.
|
|
||||||
|
|
||||||
Multiple admission controllers can be configured. Each is called in order.
|
Admission controllers act on requests that create, modify, delete, or connect to (proxy) an object.
|
||||||
|
Admission controllers do not act on requests that merely read objects.
|
||||||
|
When multiple admission controllers are configured, they are called in order.
|
||||||
|
|
||||||
This is shown as step **3** in the diagram.
|
This is shown as step **3** in the diagram.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user