summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWilliam Chang <zhang.wanmin@zte.com.cn>2017-11-01 16:17:59 +0800
committerWilliam Chang <zhang.wanmin@zte.com.cn>2017-11-01 16:17:59 +0800
commit1bb425c2076a738f7d347d919032fc8eae610bf3 (patch)
tree4bb6dbdf05a1f94e93281515994a567008d60681
parent691b2d6a3c23f1a7aaca986f431fd2ff335d4447 (diff)
Fix the path of api-conventions doc.
-rw-r--r--contributors/design-proposals/api-machinery/aggregated-api-servers.md2
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 db6d038c..24ca495b 100644
--- a/contributors/design-proposals/api-machinery/aggregated-api-servers.md
+++ b/contributors/design-proposals/api-machinery/aggregated-api-servers.md
@@ -80,7 +80,7 @@ There are two configurations in which it makes sense to run `kube-aggregator`.
`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).
+ conventions](../../devel/api-conventions.md).
* Support discovery API: Each API server should support the kubernetes discovery API
(list the supported groupVersions at `/apis` and list the supported resources
at `/apis/<groupVersion>/`)