From d59c77f6478659deb810098d3b0b73c49714cb3c Mon Sep 17 00:00:00 2001 From: Taylor Dolezal Date: Tue, 13 Jul 2021 18:53:44 -0700 Subject: [PATCH] Clarify v1beta1 API webhook behavior in 1.22 --- .../2021-07-14-upcoming-changes-in-kubernetes-1-22/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2021-07-14-upcoming-changes-in-kubernetes-1-22/index.md b/content/en/blog/_posts/2021-07-14-upcoming-changes-in-kubernetes-1-22/index.md index 337d9f2342..bfed8d9407 100644 --- a/content/en/blog/_posts/2021-07-14-upcoming-changes-in-kubernetes-1-22/index.md +++ b/content/en/blog/_posts/2021-07-14-upcoming-changes-in-kubernetes-1-22/index.md @@ -102,7 +102,7 @@ and explain the steps you'll need to take. As well as serving this API via HTTP, the Kubernetes API server uses the same format to [send](/docs/reference/access-authn-authz/authentication/#webhook-token-authentication) TokenReviews to webhooks. The v1.22 release continues to use the v1beta1 API for TokenReviews - sent to webhooks. See [Looking ahead](#looking-ahead) for some specific tips about + sent to webhooks by default. See [Looking ahead](#looking-ahead) for some specific tips about switching to the stable API. `SubjectAccessReview`, `SelfSubjectAccessReview` and `LocalSubjectAccessReview`