Clarify v1beta1 API webhook behavior in 1.22

This commit is contained in:
Taylor Dolezal
2021-07-13 18:53:44 -07:00
parent 2c02aeb43a
commit d59c77f647
@@ -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 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) [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 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. switching to the stable API.
`SubjectAccessReview`, `SelfSubjectAccessReview` and `LocalSubjectAccessReview` `SubjectAccessReview`, `SelfSubjectAccessReview` and `LocalSubjectAccessReview`