From bc12666f6896b95ddabcad4ec0160fe3cd987bb8 Mon Sep 17 00:00:00 2001 From: Daniel Shebib Date: Thu, 12 Jan 2023 19:09:14 -0600 Subject: [PATCH] document privileged containers as GC --- content/en/docs/concepts/workloads/pods/_index.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/_index.md b/content/en/docs/concepts/workloads/pods/_index.md index 21f339cca5e..93818c3dcd1 100644 --- a/content/en/docs/concepts/workloads/pods/_index.md +++ b/content/en/docs/concepts/workloads/pods/_index.md @@ -289,7 +289,11 @@ section. ## Privileged mode for containers -Any container in a pod can run in privileged mode to use operating system administrative capabilities +{{< note >}} +Your {{< glossary_tooltip text="container runtime" term_id="container-runtime" >}} must support the concept of a privileged container for this setting to be relevant. +{{< /note >}} + +Any container in a pod can run in priveleged mode to use operating system administrative capabilities that would otherwise be inaccessible. This is available for both Windows and Linux. ### Linux containers @@ -309,9 +313,6 @@ pods must run as Windows HostProcess containers. HostProcess pods run directly o to perform administrative tasks as is done with Linux privileged containers. In order to use this feature, the `WindowsHostProcessContainers`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) must be enabled. -{{< note >}} -Your {{< glossary_tooltip text="container runtime" term_id="container-runtime" >}} must support the concept of a privileged container for this setting to be relevant. -{{< /note >}} ## Static Pods