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

Trivial: fix typo in aggregated-api-servers proposal

This commit is contained in:
Qiming Teng 2017-04-20 22:46:19 +08:00
parent f11408f7d6
commit 0227b78f3f
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/aggregated-api-servers.md
View File

@ -77,7 +77,7 @@ There are two configurations in which it makes sense to run `kube-aggregator`.
`api.mycompany.com/v1` from one apiserver and the replacement `api.mycompany.com/v1` from one apiserver and the replacement
`api.mycompany.com/v2` from another apiserver while you update clients. But `api.mycompany.com/v2` from another apiserver while you update clients. But
you can't serve `api.mycompany.com/v1/frobbers` and you can't serve `api.mycompany.com/v1/frobbers` and
`api.mcompany.com/v1/grobinators` from different apiservers. This restriction `api.mycompany.com/v1/grobinators` from different apiservers. This restriction
allows us to limit the scope of `kube-aggregator` to a manageable level. allows us to limit the scope of `kube-aggregator` to a manageable level.
* 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).