From 63564ba428579073702eb84acb5ada47a9267ca3 Mon Sep 17 00:00:00 2001 From: Brandon Philips Date: Thu, 6 Jul 2017 16:20:32 -0700 Subject: [PATCH] configure-aggregation-layer: remove proxy note The referenced doc doesn't mention "kube-proxy" anywhere and I don't think this is a general best-practice in many environments. And even if it is the opinion doesn't help users. --- docs/tasks/access-kubernetes-api/configure-aggregation-layer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/access-kubernetes-api/configure-aggregation-layer.md b/docs/tasks/access-kubernetes-api/configure-aggregation-layer.md index fb2fa5c43b..fbb3a41274 100644 --- a/docs/tasks/access-kubernetes-api/configure-aggregation-layer.md +++ b/docs/tasks/access-kubernetes-api/configure-aggregation-layer.md @@ -34,7 +34,7 @@ Enable the aggregation layer via the following kube-apiserver flags. They may ha --proxy-client-cert-file= --proxy-client-key-file= -The [Kubernetes Architectural Roadmap](https://docs.google.com/a/google.com/document/d/1XkjVm4bOeiVkj-Xt1LgoGiqWsBfNozJ51dyI-ljzt1o/edit?usp=sharing) recommends not running kube-proxy on the master. If you follow this recommendation, then you must make sure that the system is enabled with the following apiserver flag. Again, this may have already been taken care of by your provider. +If you are not running kube-proxy on a host running the API server then you must make sure that the system is enabled with the following apiserver flag: --enable-aggregator-routing=true