From 598a41884d75d40c498448ee3ab8a14d2422d57d Mon Sep 17 00:00:00 2001 From: Sergey Kanzhelev Date: Tue, 17 Sep 2024 12:05:46 -0700 Subject: [PATCH] Update content/en/docs/reference/node/kubelet-files.md Co-authored-by: Tim Bannister --- content/en/docs/reference/node/kubelet-files.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/content/en/docs/reference/node/kubelet-files.md b/content/en/docs/reference/node/kubelet-files.md index 86475e1c1c31c..d50b395294782 100644 --- a/content/en/docs/reference/node/kubelet-files.md +++ b/content/en/docs/reference/node/kubelet-files.md @@ -141,13 +141,17 @@ The types of plugins that can place socket files into that directory are: (typically `/var/lib/kubelet/plugins_registry`). -## Seccomp +## Security profiles & configuration -Seccomp profile files referenced from Pods should be placed in `/docs/reference/node/seccomp/`. -See [seccomp documentation](/docs/reference/node/seccomp/) for details. +### Seccomp -Note, apparmor profiles are being loaded via operating system rather then referenced by the path. -See [apparmor documentation](https://kubernetes.io/docs/tutorials/security/apparmor/#specifying-apparmor-confinement). +Seccomp profile files referenced from Pods should be placed in `/var/lib/kubelet/seccomp`. +See the [seccomp reference](/docs/reference/node/seccomp/) for details. + +### AppArmor + +The kubelet does not load or refer to AppArmor profiles by a Kubernetes-specific path. +AppArmor profiles are loaded via the node operating system rather then referenced by their path. ## Locking