From f71bc6d90a4de4769c96226551135291b8400430 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Wed, 24 Nov 2021 23:28:06 +0000 Subject: [PATCH] Fix punctuation nit --- .../en/blog/_posts/2021-11-26-memory-qos-cgroups-v2/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2021-11-26-memory-qos-cgroups-v2/index.md b/content/en/blog/_posts/2021-11-26-memory-qos-cgroups-v2/index.md index 86995d3337..51f60cd0b4 100644 --- a/content/en/blog/_posts/2021-11-26-memory-qos-cgroups-v2/index.md +++ b/content/en/blog/_posts/2021-11-26-memory-qos-cgroups-v2/index.md @@ -99,7 +99,7 @@ Here are the prerequisites for enabling Memory QoS on your Linux node, some of t OCI runtimes such as runc and crun already support cgroups v2 [`Unified`](https://github.com/opencontainers/runtime-spec/blob/master/config-linux.md#unified), and Kubernetes CRI has also made the desired changes to support passing [`Unified`](https://github.com/kubernetes/kubernetes/pull/102578). However, CRI Runtime support is required as well. Memory QoS in Alpha phase is designed to support containerd and cri-o. Related PR [Feature: containerd-cri support LinuxContainerResources.Unified #5627](https://github.com/containerd/containerd/pull/5627) has been merged and will be released in containerd 1.6. CRI-O [implement kube alpha features for 1.22 #5207](https://github.com/cri-o/cri-o/pull/5207) is still in WIP. -With those prerequisites met, you can enable the memory QoS feature gate (see [Set kubelet parameters via a config file](/docs/tasks/administer-cluster/kubelet-config-file/). +With those prerequisites met, you can enable the memory QoS feature gate (see [Set kubelet parameters via a config file](/docs/tasks/administer-cluster/kubelet-config-file/)). ## How can I learn more?