whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Issue with k8s.io/docs/reference/access-authn-authz/extensible-admission-controllers/ (#15049)

Browse Source
This commit is contained in:
mhamdi semah
2019-06-21 19:50:16 +02:00
committed by Kubernetes Prow Robot
parent 028c51d03f
commit 7dda0a4e73
1 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md
+7 -6
View File
@@ -752,12 +752,13 @@ and mutating webhooks can specify a `reinvocationPolicy` to control whether they
* `Never`: the webhook must not be called more than once in a single admission evaluation * `Never`: the webhook must not be called more than once in a single admission evaluation
* `IfNeeded`: the webhook may be called again as part of the admission evaluation if the object * `IfNeeded`: the webhook may be called again as part of the admission evaluation if the object
being admitted is modified by other admission plugins after the initial webhook call. being admitted is modified by other admission plugins after the initial webhook call.
{{< note >}}
* the number of additional invocations is not guaranteed to be exactly one. The important elements to note are:
* if additional invocations result in further modifications to the object, webhooks are not guaranteed to be invoked again.
* webhooks that use this option may be reordered to minimize the number of additional invocations. * The number of additional invocations is not guaranteed to be exactly one.
* to validate an object after all mutations are guaranteed complete, use a validating admission webhook instead (recommended for webhooks with side-effects). * If additional invocations result in further modifications to the object, webhooks are not guaranteed to be invoked again.
{{< /note >}} * Webhooks that use this option may be reordered to minimize the number of additional invocations.
* To validate an object after all mutations are guaranteed complete, use a validating admission webhook instead (recommended for webhooks with side-effects).
Here is an example of a mutating webhook opting into being re-invoked if later admission plugins modify the object: Here is an example of a mutating webhook opting into being re-invoked if later admission plugins modify the object: