From 7dda0a4e73f4216bcb07613e2b3955a992386591 Mon Sep 17 00:00:00 2001 From: mhamdi semah Date: Fri, 21 Jun 2019 19:50:16 +0200 Subject: [PATCH] Issue with k8s.io/docs/reference/access-authn-authz/extensible-admission-controllers/ (#15049) --- .../extensible-admission-controllers.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md b/content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md index f9555caa51..1b4f8e46ee 100644 --- a/content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md +++ b/content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md @@ -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 * `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. - {{< note >}} - * the number of additional invocations is not guaranteed to be exactly one. - * 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. - * to validate an object after all mutations are guaranteed complete, use a validating admission webhook instead (recommended for webhooks with side-effects). - {{< /note >}} + +The important elements to note are: + +* The number of additional invocations is not guaranteed to be exactly one. +* 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. +* 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: