kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1179 from zhxcai/patch-1 

Automatic merge from submit-queue.

Update aggregated-api-servers.md misspelled word
This commit is contained in:
Kubernetes Submit Queue 2017-10-13 10:06:52 -07:00 committed by GitHub
parent 6dd32b68ba ef39f0c054
commit e7d035d628
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contributors/design-proposals/api-machinery/aggregated-api-servers.md
View File

@ -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 * Follow API conventions: APIs exposed by every API server should adhere to [kubernetes API
conventions](../devel/api-conventions.md). conventions](../devel/api-conventions.md).
* Support discovery API: Each API server should support the kubernetes discovery API * 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>/`) at `/apis/<groupVersion>/`)
* No bootstrap problem: The core kubernetes apiserver must not depend on any * 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 other aggregated server to come up. Non-core apiservers may use other non-core