From f5b05a4e4e3da9227aa71a7d1d3f2f0d26d8c9c1 Mon Sep 17 00:00:00 2001 From: Kevin Lefevre Date: Sun, 16 Sep 2018 09:39:50 +0200 Subject: [PATCH] Update configure-aggregation-layer.md (#10119) --- .../tasks/access-kubernetes-api/configure-aggregation-layer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 94dcf020e9..2781881e1b 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 @@ -31,7 +31,7 @@ Configuring the [aggregation layer](/docs/concepts/api-extension/apiserver-aggre Enable the aggregation layer via the following kube-apiserver flags. They may have already been taken care of by your provider. --requestheader-client-ca-file= - --requestheader-allowed-names=aggregator + --requestheader-allowed-names=front-proxy-client --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User