From d065457f691b4392f74ee3364b4e0e67be7312b0 Mon Sep 17 00:00:00 2001 From: Jay Pipes Date: Sat, 6 Jul 2019 07:16:36 -0400 Subject: [PATCH] correct request payload for imagepolicy webhook (#15228) The example request payload for the imagepolicy webhook mistakenly represented annotations as a list instead of an object. --- .../reference/access-authn-authz/admission-controllers.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 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 b3cf387d39..5b7a8c2c1a 100644 --- a/content/en/docs/reference/access-authn-authz/admission-controllers.md +++ b/content/en/docs/reference/access-authn-authz/admission-controllers.md @@ -292,15 +292,15 @@ An example request body: "image":"myrepo/myimage@sha256:beb6bd6a68f114c1dc2ea4b28db81bdf91de202a9014972bec5e4d9171d90ed" } ], - "annotations":[ + "annotations":{ "mycluster.image-policy.k8s.io/ticket-1234": "break-glass" - ], + }, "namespace":"mynamespace" } } ``` -The remote service is expected to fill the ImageReviewStatus field of the request and respond to either allow or disallow access. The response body's "spec" field is ignored and may be omitted. A permissive response would return: +The remote service is expected to fill the `ImageReviewStatus` field of the request and respond to either allow or disallow access. The response body's "spec" field is ignored and may be omitted. A permissive response would return: ```json { @@ -337,7 +337,7 @@ Examples of information you might put here are: * a ticket number from a ticket system that documents the break-glass request * provide a hint to the policy server as to the imageID of the image being provided, to save it a lookup -In any case, the annotations are provided by the user and are not validated by Kubernetes in any way. In the future, if an annotation is determined to be widely useful, it may be promoted to a named field of ImageReviewSpec. +In any case, the annotations are provided by the user and are not validated by Kubernetes in any way. In the future, if an annotation is determined to be widely useful, it may be promoted to a named field of `ImageReviewSpec`. ### LimitPodHardAntiAffinityTopology {#limitpodhardantiaffinitytopology}