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

Merge pull request #3501 from nzoueidi/3477 

Fixing broken links in aggregated-api-servers.md
This commit is contained in:
Kubernetes Prow Robot 2019-04-10 11:40:09 -07:00 committed by GitHub
parent 2c773e5dd1 aedff33689
commit a3e65c4baf
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
contributors/design-proposals/api-machinery/aggregated-api-servers.md
View File

@ -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.