Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

Commit

Permalink
Clarifying the API aggregation system
Browse files Browse the repository at this point in the history
  • Loading branch information
@arschles
arschles committed Aug 29, 2017
1 parent 158fd71 commit cbb0726
Showing 1 changed file with 7 additions and 5 deletions.
12 changes: 7 additions & 5 deletions docs/install-1.7.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit cbb0726

Please sign in to comment.