diff options
| author | Qiming Teng <tengqim@cn.ibm.com> | 2017-04-20 22:46:19 +0800 |
|---|---|---|
| committer | Qiming Teng <tengqim@cn.ibm.com> | 2017-04-20 22:46:19 +0800 |
| commit | 0227b78f3f7c8f10510ba05231c134b89ca5778a (patch) | |
| tree | bb7f4f247480e6fdd35912ee8f8c22295b33acf4 | |
| parent | f11408f7d60df686ac6ed1564096ab834765077c (diff) | |
Trivial: fix typo in aggregated-api-servers proposal
| -rw-r--r-- | contributors/design-proposals/aggregated-api-servers.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/aggregated-api-servers.md b/contributors/design-proposals/aggregated-api-servers.md index 7bed003c..676c81a3 100644 --- a/contributors/design-proposals/aggregated-api-servers.md +++ b/contributors/design-proposals/aggregated-api-servers.md @@ -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/v2` from another apiserver while you update clients. But 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. * Follow API conventions: APIs exposed by every API server should adhere to [kubernetes API conventions](../devel/api-conventions.md). |