From 7820dc3fc50401b40b9493ec7095693418cb1b1d Mon Sep 17 00:00:00 2001 From: yameiwang Date: Fri, 31 May 2019 18:42:59 +0800 Subject: [PATCH] fix typos in configure-aggregation-layer.md --- .../access-kubernetes-api/configure-aggregation-layer.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/access-kubernetes-api/configure-aggregation-layer.md b/content/en/docs/tasks/access-kubernetes-api/configure-aggregation-layer.md index 5114173e12c15..df2aecb5abc32 100644 --- a/content/en/docs/tasks/access-kubernetes-api/configure-aggregation-layer.md +++ b/content/en/docs/tasks/access-kubernetes-api/configure-aggregation-layer.md @@ -38,8 +38,8 @@ This section describes how the authentication and authorization flows work, and The high-level flow is as follows: -1. Kubenetes apiserver: authenticate the requesting user and authorize their rights to the requested API path. -2. Kubenetes apiserver: proxy the request to the extension apiserver +1. Kubernetes apiserver: authenticate the requesting user and authorize their rights to the requested API path. +2. Kubernetes apiserver: proxy the request to the extension apiserver 3. Extension apiserver: authenticate the request from the Kubernetes apiserver 4. Extension apiserver: authorize the request from the original user 5. Extension apiserver: execute