From 3ea996abd77a853be244dedc3fd0c9f77f3c63f8 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Mon, 7 Feb 2022 18:27:38 +0100 Subject: [PATCH] docs: add missing KernelMemoryTCP to api v1.40 and v1.41 Signed-off-by: Sebastiaan van Stijn (cherry picked from commit 9f3c238c2912205514e65a48272a3a65589c86c5) Signed-off-by: Sebastiaan van Stijn --- docs/api/v1.40.yaml | 8 ++++++++ docs/api/v1.41.yaml | 8 ++++++++ 2 files changed, 16 insertions(+) diff --git a/docs/api/v1.40.yaml b/docs/api/v1.40.yaml index b7c8a547c3..41638b5eb5 100644 --- a/docs/api/v1.40.yaml +++ b/docs/api/v1.40.yaml @@ -4346,6 +4346,14 @@ definitions: description: "Indicates if the host has kernel memory limit support enabled." type: "boolean" example: true + KernelMemoryTCP: + description: | + Indicates if the host has kernel memory TCP limit support enabled. + + Kernel memory TCP limits are not supported when using cgroups v2, which + does not support the corresponding `memory.kmem.tcp.limit_in_bytes` cgroup. + type: "boolean" + example: true CpuCfsPeriod: description: | Indicates if CPU CFS(Completely Fair Scheduler) period is supported by diff --git a/docs/api/v1.41.yaml b/docs/api/v1.41.yaml index 6389d51594..75181e174a 100644 --- a/docs/api/v1.41.yaml +++ b/docs/api/v1.41.yaml @@ -4467,6 +4467,14 @@ definitions: > `kmem.limit_in_bytes`. type: "boolean" example: true + KernelMemoryTCP: + description: | + Indicates if the host has kernel memory TCP limit support enabled. + + Kernel memory TCP limits are not supported when using cgroups v2, which + does not support the corresponding `memory.kmem.tcp.limit_in_bytes` cgroup. + type: "boolean" + example: true CpuCfsPeriod: description: | Indicates if CPU CFS(Completely Fair Scheduler) period is supported by