From 9823ecda09c495b636707f26d8b90682a3019c05 Mon Sep 17 00:00:00 2001 From: Marco Voelz Date: Mon, 21 Feb 2022 10:54:50 +0100 Subject: [PATCH] Update proposal link to point to archive Original link says ``` Design proposals have been archived. To view the last version of this document, see the Design Proposals Archive Repo. Please remove after 2022-04-01 or the release of Kubernetes 1.24, whichever comes first. ``` --- .../docs/tasks/administer-cluster/reserve-compute-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md b/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md index 06e4958697..0dd24d3f6e 100644 --- a/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md +++ b/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md @@ -91,7 +91,7 @@ flag. It is recommended that the kubernetes system daemons are placed under a top level control group (`runtime.slice` on systemd machines for example). Each system daemon should ideally run within its own child control group. Refer to -[the design proposal](https://git.k8s.io/community/contributors/design-proposals/node/node-allocatable.md#recommended-cgroups-setup) +[the design proposal](https://git.k8s.io/design-proposals-archive/node/node-allocatable.md#recommended-cgroups-setup) for more details on recommended control group hierarchy. Note that Kubelet **does not** create `--kube-reserved-cgroup` if it doesn't