From cbb0726e8ab2a4b3a51879bb6cf03803e5c8c9f9 Mon Sep 17 00:00:00 2001 From: Aaron Schlesinger Date: Tue, 29 Aug 2017 10:01:37 -0700 Subject: [PATCH] Clarifying the API aggregation system --- docs/install-1.7.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/install-1.7.md b/docs/install-1.7.md index ebdc6110a2a..282d57ee436 100644 --- a/docs/install-1.7.md +++ b/docs/install-1.7.md @@ -8,11 +8,13 @@ The aggregator allows user-defined, Kubernetes compatible API servers to come and go inside the cluster, and register themselves on demand to augment the externally facing API that kubernetes offers. -Instead of running multiple API servers on different ports, API aggregation -allows many servers to run inside the cluster, and all of their APIs to be -combined into one externally facing API. This system is very useful from an -end-user's perspective, as it allows the client to use a single API point -with familiar tooling, authentication and authorization. +Instead of requiring the end-user to access multiple API servers, the API +aggregation system allows many servers to run inside the cluster, and combines +all of their APIs into one externally facing API. + +This system is very useful from an end-user's perspective, as it allows the +client to use a single API point with familiar tooling, authentication and +authorization. The Service Catalog utilizes API aggregation to present its API. Read on to discover how to install it.