diff options
| -rw-r--r-- | contributors/design-proposals/api-machinery/aggregated-api-servers.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/contributors/design-proposals/api-machinery/aggregated-api-servers.md b/contributors/design-proposals/api-machinery/aggregated-api-servers.md index 3c3310b0..fdddddee 100644 --- a/contributors/design-proposals/api-machinery/aggregated-api-servers.md +++ b/contributors/design-proposals/api-machinery/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](namespaces.md#finalizers). Each server +using resource [finalizers](/contributors/design-proposals/architecture/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](admission_control_resource_quota.md) and -[limit ranges](admission_control_limit_range.md) for all resources. +kubernetes server maintains [resource quotas](/contributors/design-proposals/resource-management/admission_control_resource_quota.md) and +[limit ranges](/contributors/design-proposals/resource-management/admission_control_limit_range.md) for all resources. Aggregated servers will need to check with the kubernetes server before creating any resource. |