diff options
| author | Daniel Smith <dbsmith@google.com> | 2017-03-24 16:18:26 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-03-24 16:18:26 -0700 |
| commit | f783f4a2736b0de40deda0a543cbf30c9201a0bc (patch) | |
| tree | 908c3521b7447a0227db1fdb883ca6e881dd50fc | |
| parent | d635ca855a6a82c43a4c936fc8f0130ae00e0cd5 (diff) | |
| parent | 47fef84d87cf6f8d8078030e57ee3457194b4e3e (diff) | |
Merge pull request #475 from deads2k/ext-01-agg
embed aggregator inside of the kube-apiserver
| -rw-r--r-- | contributors/design-proposals/aggregated-api-servers.md | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/contributors/design-proposals/aggregated-api-servers.md b/contributors/design-proposals/aggregated-api-servers.md index 37cda329..7bed003c 100644 --- a/contributors/design-proposals/aggregated-api-servers.md +++ b/contributors/design-proposals/aggregated-api-servers.md @@ -41,8 +41,7 @@ The following are related but are not the goals of this specific proposal: ## High Level Architecture -There will be a new component in the cluster, `kube-aggregator`, which has these -responsibilities: +There will be a new component, `kube-aggregator`, which has these responsibilities: * Provide an API for registering API servers. * Summarize discovery information from all the servers. * Proxy client requests to individual servers. @@ -67,10 +66,9 @@ There are two configurations in which it makes sense to run `kube-aggregator`. this configuration, `kube-aggregator`'s built in proxy will lack the client cert that allows it to perform authentication that the rest of the cluster will trust, so its functionality will be somewhat limited. - 2. In **gateway mode**. Each cluster should run kube-aggregator as the official - gateway to the cluster, where it aggregates all of the apiservers the cluster - administer wishes to provide. This configuration is the intended usage of - `kube-aggregator`. + 2. In **gateway mode**. The `kube-apiserver` will embed the `kube-aggregator` component + and it will function as the official gateway to the cluster, where it aggregates + all of the apiservers the cluster administer wishes to provide. ### Constraints |