summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorzouyee <zouyee1989@gmail.com>2017-07-19 15:01:52 +0800
committerzouyee <zouyee1989@gmail.com>2017-07-19 15:01:52 +0800
commitdcfed0a225a737bc4786396e76c1a0d72cc8b64c (patch)
tree658ce8859fc9745a63aa30cd602bc377db176d99
parentd63e9f08f607015d3c9f3b4864ce4dd98d3f0a04 (diff)
update outdated links
-rw-r--r--contributors/design-proposals/aggregated-api-servers.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/contributors/design-proposals/aggregated-api-servers.md b/contributors/design-proposals/aggregated-api-servers.md
index 70deaf68..ca267269 100644
--- a/contributors/design-proposals/aggregated-api-servers.md
+++ b/contributors/design-proposals/aggregated-api-servers.md
@@ -210,7 +210,7 @@ API for all these operations.
While deleting a namespace, kubernetes server needs to ensure that resources in
that namespace maintained by other servers are deleted as well. We can do this
-using resource [finalizers](../design/namespaces.md#finalizers). Each server
+using resource [finalizers](../namespaces.md#finalizers). Each server
will add themselves in the set of finalizers before they create a resource in
the corresponding namespace and delete all their resources in that namespace,
whenever it is to be deleted (kubernetes API server already has this code, we
@@ -221,8 +221,8 @@ mechanism.
#### Limit ranges and resource quotas
-kubernetes server maintains [resource quotas](../admin/resourcequota/README.md) and
-[limit ranges](../admin/limitrange/README.md) for all resources.
+kubernetes server maintains [resource quotas](../admission_control_resource_quota.md) and
+[limit ranges](../admission_control_limit_range.md) for all resources.
Aggregated servers will need to check with the kubernetes server before creating any
resource.