diff options
| author | Zhang Xingcai <zhangxingcai@ghostcloud.cn> | 2017-10-13 23:02:42 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-13 23:02:42 +0800 |
| commit | ef39f0c054f32b775aa9adb78db76520add79c6d (patch) | |
| tree | e7d58d0f157c736e4302058298d7e470c9c540c4 | |
| parent | 6dd32b68ba677ef4a3afb39694e19aaf15a2ab37 (diff) | |
Update aggregated-api-servers.md
| -rw-r--r-- | contributors/design-proposals/api-machinery/aggregated-api-servers.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/api-machinery/aggregated-api-servers.md b/contributors/design-proposals/api-machinery/aggregated-api-servers.md index ae3f59e0..94bc9a42 100644 --- a/contributors/design-proposals/api-machinery/aggregated-api-servers.md +++ b/contributors/design-proposals/api-machinery/aggregated-api-servers.md @@ -82,7 +82,7 @@ There are two configurations in which it makes sense to run `kube-aggregator`. * Follow API conventions: APIs exposed by every API server should adhere to [kubernetes API conventions](../devel/api-conventions.md). * Support discovery API: Each API server should support the kubernetes discovery API - (list the suported groupVersions at `/apis` and list the supported resources + (list the supported groupVersions at `/apis` and list the supported resources at `/apis/<groupVersion>/`) * No bootstrap problem: The core kubernetes apiserver must not depend on any other aggregated server to come up. Non-core apiservers may use other non-core |