From a904f65fa96b4025cdfa5175979683fafc1b322b Mon Sep 17 00:00:00 2001 From: Keith Burdis Date: Tue, 5 Dec 2017 14:57:57 -0600 Subject: [PATCH 1/3] Security Context glossary term --- _data/glossary/security-context.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 _data/glossary/security-context.yaml diff --git a/_data/glossary/security-context.yaml b/_data/glossary/security-context.yaml new file mode 100644 index 0000000000..6311cb283f --- /dev/null +++ b/_data/glossary/security-context.yaml @@ -0,0 +1,9 @@ +id: security-context +name: Security Context +full-link: /docs/concepts/security/ +tags: +- security +short-description: > + The securityContext field defines privilege and access control settings for a Pod or Container, including the runtime uid and gid. +long-description: > + The securityContext field in a {% glossary_tooltip term_id="pod" %} (applying to all containers) or Container (just one) is used to set the user (runAsUser) and group (fsGroup), capabilities, privilege settings and security policies (SELinux/AppArmor/Seccomp) that container processes use. From e87df7ff495c5b06a9b1f5dee5e06afc7f394068 Mon Sep 17 00:00:00 2001 From: Keith Burdis Date: Tue, 5 Dec 2017 14:59:43 -0600 Subject: [PATCH 2/3] Security Context glossary term --- _data/glossary/security-context.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_data/glossary/security-context.yaml b/_data/glossary/security-context.yaml index 6311cb283f..ad36f04a01 100644 --- a/_data/glossary/security-context.yaml +++ b/_data/glossary/security-context.yaml @@ -6,4 +6,4 @@ tags: short-description: > The securityContext field defines privilege and access control settings for a Pod or Container, including the runtime uid and gid. long-description: > - The securityContext field in a {% glossary_tooltip term_id="pod" %} (applying to all containers) or Container (just one) is used to set the user (runAsUser) and group (fsGroup), capabilities, privilege settings and security policies (SELinux/AppArmor/Seccomp) that container processes use. + The securityContext field in a {% glossary_tooltip term_id="pod" %} (applying to all containers) or container (just one) is used to set the user (runAsUser) and group (fsGroup), capabilities, privilege settings and security policies (SELinux/AppArmor/Seccomp) that container processes use. From b025865c186631c33354052a3dcaf6ac6cf2e038 Mon Sep 17 00:00:00 2001 From: Keith Burdis Date: Tue, 5 Dec 2017 15:33:08 -0600 Subject: [PATCH 3/3] Updates. KubeCon 2017. --- _data/glossary/security-context.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_data/glossary/security-context.yaml b/_data/glossary/security-context.yaml index ad36f04a01..7281a7e6cd 100644 --- a/_data/glossary/security-context.yaml +++ b/_data/glossary/security-context.yaml @@ -1,9 +1,9 @@ id: security-context name: Security Context -full-link: /docs/concepts/security/ +full-link: /docs/tasks/configure-pod-container/security-context/ tags: - security short-description: > - The securityContext field defines privilege and access control settings for a Pod or Container, including the runtime uid and gid. + The securityContext field defines privilege and access control settings for a Pod or Container, including the runtime UID and GID. long-description: > - The securityContext field in a {% glossary_tooltip term_id="pod" %} (applying to all containers) or container (just one) is used to set the user (runAsUser) and group (fsGroup), capabilities, privilege settings and security policies (SELinux/AppArmor/Seccomp) that container processes use. + The securityContext field in a {% glossary_tooltip term_id="pod" %} (applying to all containers) or container is used to set the user (runAsUser) and group (fsGroup), capabilities, privilege settings, and security policies (SELinux/AppArmor/Seccomp) that container processes use.