From 4a7a977901b668a069ec573d36b6ac60fbbeb6f9 Mon Sep 17 00:00:00 2001 From: Guneetconvent2002 Date: Mon, 13 Sep 2021 17:59:53 +0530 Subject: [PATCH] Fix headings for well-known labels annotations and taints Co-authored-by: Qiming Teng Co-authored-by: Tim Bannister --- .../reference/labels-annotations-taints.md | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/content/en/docs/reference/labels-annotations-taints.md b/content/en/docs/reference/labels-annotations-taints.md index e2fc2b317e..325bfc2d9f 100644 --- a/content/en/docs/reference/labels-annotations-taints.md +++ b/content/en/docs/reference/labels-annotations-taints.md @@ -427,8 +427,18 @@ or updating objects that contain Pod templates, such as Deployments, Jobs, State See [Enforcing Pod Security at the Namespace Level](/docs/concepts/security/pod-security-admission) for more information. -## seccomp.security.alpha.kubernetes.io/pod and container.seccomp.security.alpha.kubernetes.io/[NAME] (deprecated) +## seccomp.security.alpha.kubernetes.io/pod (deprecated) {#seccomp-security-alpha-kubernetes-io-pod} -The seccomp annotations have been deprecated since Kubernetes v1.19 and will -become non-functional in v1.25. Please use the `seccompProfile` of the -`SecurityContext` instead. \ No newline at end of file +This annotation has been deprecated since Kubernetes v1.19 and will become non-functional in v1.25. +To specify security settings for a Pod, include the `securityContext` field in the Pod specification. +The [`securityContext`](/docs/reference/kubernetes-api/workload-resources/pod-v1/#security-context) field within a Pod's `.spec` defines pod-level security attributes. +When you [specify the security context for a Pod](/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod), +the settings you specify apply to all containers in that Pod. + +## container.seccomp.security.alpha.kubernetes.io/[NAME] {#container-seccomp-security-alpha-kubernetes-io} + +This annotation has been deprecated since Kubernetes v1.19 and will become non-functional in v1.25. +The tutorial [Restrict a Container's Syscalls with seccomp](/docs/tutorials/clusters/seccomp/) takes +you through the steps you follow to apply a seccomp profile to a Pod or to one of +its containers. That tutorial covers the supported mechanism for configuring seccomp in Kubernetes, +based on setting `securityContext` within the Pod's `.spec`. \ No newline at end of file